[
https://issues.apache.org/jira/browse/JENA-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-319.
--------------------------------
Resolution: Not A Problem
Assignee: Andy Seaborne
This is not a bug.
Jena does not resolve URIs through the API (it's expensive for one thing if
proper checking is done - the Jena IRI library exists because of the need for a
good checking library). API calls can be made at frequency.
<uri> in the query string is a relative URI and is resolved relative to the
base of the query (defaults to the current working directory of the process).
dataset.addNamedModel("uri", m) puts in an absolute (and badly formed) URI.
GRAPH <uri> { ... }
is
GRAPH <file:///dir/uri> { ... }
after parsing.
try looking at the output of "qparse -print=op 'SELECT * { GRAPH <uri> { ?s ?p
?o }}'
> If the URI for the named graph in a Dataset does not contain a colon ":" it
> is accepted but can not be retrieved.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JENA-319
> URL: https://issues.apache.org/jira/browse/JENA-319
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Claude Warren
> Assignee: Andy Seaborne
> Attachments: DatasetGraphNameTest.java
>
>
> If dataset.addNamedModel(uri, m) is called and 'uri' does not have a colon
> the query select * { graph <uri> { ?s ?o ?p }} does not return any results
> even though select ?g { graph ?g { ?s ?o ?p }} will return the uri as ?g.
> JUnit based test case attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
