w3c / dx-connegp

Content Negotiation by Profile
https://w3c.github.io/dx-connegp/connegp/
Other
6 stars 5 forks source link

Example 10 contains flawed Turtle #31

Closed ssstolk closed 1 year ago

ssstolk commented 3 years ago

Example 10 of https://www.w3.org/TR/2019/WD-dx-prof-conneg-20191126/ contains typos that mean it does not conform to the Turtle format.

# Link headers above represented in Alternate Profiles Data Model
# as an OWL ontology
<http://example.org/resource/a>
    altp:hasDefaultRepresentation [
        dct:format "text/turtle" ;
        dct:conformsTo <urn:example:profile:x> ;
    ] ,
    altp:hasRepresentation [
        dct:format "text/turtle" ;
        dct:conformsTo <urn:example:profile:y> ;
    ] ,
    [
        dct:format "application/xml" ;
        dct:conformsTo <urn:example:profile:x> ;
    ] ,
    <http://example.org/resource/different> ,
    [
        dct:format "text/html" ;
    ] .

<http://example.org/resource/different>
    dct:format "application/xml" ;
    dct:conformsTo <urn:example:profile:y> .

Here, semicolons instead of commas ought to be used whenever a property follows (lines 7 and 15 in the snippet above).

rob-metalinkage commented 1 year ago

addressed in https://github.com/w3c/dx-connegp/pull/42

pchampin commented 1 year ago

The comma line 7 (,) should indeed be replaced by a semicolon (;). Line 15, on the other hand, is correct (the IRI following the comma is another object to the predicate altp:hasDefaultRepresentation).

rob-metalinkage commented 1 year ago

Extracted example into a separate TTL file - to explore building spec from validated examples instead of inline code.