Closed LaurensRietveld closed 10 months ago
I noticed an issue with object lists and property paths where the test cases in the test-suite do not follow the spec. See e.g. this query:
PREFIX dbpedia-owl:<http://dbpedia.org/owl/#> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#> SELECT ?movie WHERE { ?movie a dbpedia-owl:Film ; dbpedia-owl:starring [ rdfs:label "Brad Pitt"@en ; ^dbpedia-owl:starring ?otherMovie ] . }
This query includes a property path pattern (^dbpedia-owl:starring) that is not allowed according to the spec:
^dbpedia-owl:starring
[83] PropertyListPathNotEmpty ::= ( VerbPath | VerbSimple ) ObjectListPath ( ';' ( ( VerbPath | VerbSimple ) ObjectList )? )*
I.e., the ObjectListPath rule (which allows property paths) is permitted at the start of PropertyListPathNotEmpty, but not in the trailing part (here, ObjectList is used)
ObjectListPath
PropertyListPathNotEmpty
ObjectList
This issue was introduced in https://github.com/RubenVerborgh/SPARQL.js/pull/142
never mind, turns out this rule is mentioned in this errata: https://www.w3.org/2013/sparql-errata#errata-query-3
i.e., the behaviour of sparqlJS is correct
I noticed an issue with object lists and property paths where the test cases in the test-suite do not follow the spec. See e.g. this query:
This query includes a property path pattern (
^dbpedia-owl:starring
) that is not allowed according to the spec:I.e., the
ObjectListPath
rule (which allows property paths) is permitted at the start ofPropertyListPathNotEmpty
, but not in the trailing part (here,ObjectList
is used)This issue was introduced in https://github.com/RubenVerborgh/SPARQL.js/pull/142