From 8a6422dbefd6119b33098ba93f91a4adf13d29a3 Mon Sep 17 00:00:00 2001
From: Antoine Bluchet <soyuka@users.noreply.github.com>
Date: Wed, 23 Oct 2024 11:09:11 +0200
Subject: [PATCH] fix turtle syntax errors

---
 .../2.3.complete-api-documentation.md            | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/api-documentation/2.3.complete-api-documentation.md b/api-documentation/2.3.complete-api-documentation.md
index 6be8b4e..d39d920 100644
--- a/api-documentation/2.3.complete-api-documentation.md
+++ b/api-documentation/2.3.complete-api-documentation.md
@@ -40,7 +40,7 @@ Example of such a description may be as follows (in Turtle syntax):
     hydra:entrypoint </> ;
     hydra:title "Hydra example API." ;
     hydra:description "Some example API described using Hydra vocabulary" ;
-    hydra:supportedClass schema:Event, schema:Person ;
+    hydra:supportedClass schema:Event, schema:Person .
 
 schema:Event a hydra:Class ;
     hydra:supportedOperation <#get-events-operation> ,
@@ -91,13 +91,13 @@ schema:Event a hydra:Class ;
 
 <#get-events-operation> a hydra:Operation ;
    hydra:method "GET"^^xsd:string ;
-   hydra:possibleStatus "200"^xsd:int, "500"^^xsd:int ;
+   hydra:possibleStatus "200"^^xsd:int, "500"^^xsd:int ;
    hydra:returns hydra:Collection .
 
 <#new-event-operation> a hydra:Operation, schema:CreateAction ;
     hydra:expects schema:Event ;
-    hydra:method "POST"^^xsd:string
-    hydra:possibleStatus "200"^xsd:int, "500"^^xsd:int .
+    hydra:method "POST"^^xsd:string ;
+    hydra:possibleStatus "200"^^xsd:int, "500"^^xsd:int .
 
 # Link with operation below does not mention directly that no value is returned.
 # Only hint of that may be taken from the 201 status.
@@ -111,19 +111,19 @@ schema:Event a hydra:Class ;
         a hydra:Operation, schema:UpdateAction ;
         hydra:title "Updates an event." ;
         hydra:method "PUT"^^xsd:string ;
-        hydra:possibleStatus "201"^xsd:int, "404"^^xsd:int, "500"^^xsd:int ;
+        hydra:possibleStatus "201"^^xsd:int, "404"^^xsd:int, "500"^^xsd:int ;
         hydra:expects schema:Event
     ], [
         a hydra:Operation, schema:DeleteAction ;
         hydra:title "Deletes an event." ;
         hydra:method "DELETE"^^xsd:string ;
-        hydra:possibleStatus "201"^xsd:int, "404"^^xsd:int, "500"^^xsd:int
+        hydra:possibleStatus "201"^^xsd:int, "404"^^xsd:int, "500"^^xsd:int
     ].
 
 <#id-mapping> a hydra:IriTemplateMapping ;
     hydra:variableRepresentation: hydra:BasicRepresentation ;
     hydra:variable "id"^^xsd:string ;
-    hydra:property vocab:id ;
+    hydra:property vocab:id .
 
 vocab:id a rdf:Property ;
     rdf:domain schema:Event ;
@@ -134,4 +134,4 @@ It is currently impossible to describe expected or returned cardinality of the l
 gathered above. Both `hydra:returns` and `hydra:expects` are allowed to receive statements related 
 to multiple resources of same type. While for `PUT` operations server may use only statements related 
 to the resource identified by the call's URL, in case of `POST` where the resource will have no 
-explicit identifier server may end up with an 4XX or some other unexpected behavior.
\ No newline at end of file
+explicit identifier server may end up with an 4XX or some other unexpected behavior.