Separation dot without space and prefixed name #250
Conversation
|
With this change we match Blazegraph behavior for the given examples. |
Previously with a prefixed name a final dot was not recognized as
separating triple blocks.
Sadly in SPARQL this is quite messy.
For example the following query works (in Blazegraph):
SELECT ?item WHERE {
?item wdt:P31 wd:Q2934.?item wdt:P39 wd:Q41240317
}
Using `^` reversing the following also works
SELECT ?item WHERE {
?item wdt:P31 wd:Q2934. wd:Q41240317 ^wdt:P39 ?item
}
However removing the ` ` after the `.` breaks parsing even though it's
not needed at the same position when the `?` disambiguates.
So yeah we really should use a proper parser that naturally handles this
weirdness.
|
@niklas88 I'm currently working on supporting the |
|
@floriankramer that sounds good to me, will keep this in my development/test instances until then because this makes rewriting Blazegraph stuff much easier. |
|
@floriankramer by the way I'm making progress on testing against Blazegraph using the Wikidata Example queries. It's looking pretty good performance wise and maybe you can use some of the uses of |
|
This has been made obsolete (as discussed) by the recent parser changes |
Previously with a prefixed name a final dot was not recognized as
separating triple blocks.
Sadly in SPARQL this is quite messy.
For example the following query works (in Blazegraph):
Using
^reversing the following also worksHowever removing the
.breaks parsing even though it'snot needed at the same position when the
?disambiguates.So yeah we really should use a proper parser that naturally handles this
weirdness.
Note: This still uses the current hacky parser. #236 is absolutely still
relevant but this case is just a bit too frustrating with a lot of Wikidata queries.