For example, on wikidata following two queries produce the same result:
SELECT ?cat
WHERE
{
?cat wdt:P31 wd:Q146 .
}
SELECT ?cat
WHERE
{
?cat wdt:P31 wd:%51146 .
}
(Notice %51 as a percent-encoded Q. This is used for example, In reality I face an issue with whitespaces and other non-URI-friendly characters. Query 1. Query 2.)
For example, on wikidata following two queries produce the same result:
(Notice
%51
as a percent-encodedQ
. This is used for example, In reality I face an issue with whitespaces and other non-URI-friendly characters. Query 1. Query 2.)This is the correct behaviour as you can notice percent encoding in the grammar for PrefixedName.
Blazegraph instead seem to take percent encoding literally.
Let's insert some test data into blazegraph (3):
Then try to query for it with prefixed URI-encoded object, nothing is returned (4):
If you use the full URI, correct result is returned (5):
Blazegraph version: BLAZEGRAPH_RELEASE_CANDIDATE_2_1_5 (via https://github.com/nawerprod/blazegraph/blob/master/2.1.5/Dockerfile)