[DuraSpace JIRA] (FCREPO-1023) No W3C SPARQL Query Results XML Format
Egbert Gramsbergen (Created) (DuraSpace JIRA)
--------------------------------------
Key: FCREPO-1023
URL: https://jira.duraspace.org/browse/FCREPO-1023
Project: Fedora Repository Project
Issue Type: Bug
Components: Fedora
Affects Versions: Fedora 3.4.2
Reporter: Egbert Gramsbergen
The current Sparql result format for queries in the RI index does not conform to the W3C recommendation at http://www.w3.org/TR/rdf-sparql-XMLres/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Stephen Bayliss (Commented) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22959#comment-22959 ]
Stephen Bayliss commented on FCREPO-1023:
-----------------------------------------
Thanks - could you identify what the specific differences are?
Benjamin Armintor (Commented) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22960#comment-22960 ]
Benjamin Armintor commented on FCREPO-1023:
-------------------------------------------
There's certainly a namespace issue:
Actual: <sparql xmlns="http://www.w3.org/2001/sw/DataAccess/rf1/result">
W3C: <sparql xmlns="http://www.w3.org/2005/sparql-results#">
This may be just passed along from Mulgara; will need follow-up.
Egbert Gramsbergen (Commented) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen commented on FCREPO-1023:
--------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:55 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
{{{
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
}}}
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:56 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
# <binding name="hpage">
## <uri>http://work.example.org/bob/</uri>
# </binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:55 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
# <binding name="hpage">
## <uri>http://work.example.org/bob/</uri>
# </binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
{{{
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
}}}
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:56 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/\</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:57 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/ </uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:57 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/\</uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Egbert Gramsbergen (Issue Comment Edited) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22961#comment-22961 ]
Egbert Gramsbergen edited comment on FCREPO-1023 at 11/1/11 3:59 PM:
---------------------------------------------------------------------
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/ </uri>
</binding>
(where I added a space after /bob/ because otherwise the Wiki screws things up)
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
was (Author: efgramsbergen):
The currently used format follows a very early draft at http://www.w3.org/TR/2004/WD-rdf-sparql-XMLres-20041221/
It is more than just a namespace issue. As an illustration, compare (within a <result> element)
old:
<hpage uri="http://work.example.org/bob/"/>
and new:
<binding name="hpage">
<uri>http://work.example.org/bob/ </uri>
</binding>
Btw, it would be nice if both forms would be available e.g. through a different "format" parameter in the RI search service. Speaking for myself, I have lots of predefined queries where the results are processed with xslt and modifying all these is more than a trivial task.
Stephen Bayliss (Commented) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22963#comment-22963 ]
Stephen Bayliss commented on FCREPO-1023:
-----------------------------------------
Thanks - and a good point on providing both "old" and "new" outputs as this would effectively be an API change that would break people's existing code without this.
Chris Wilper (Updated) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Wilper updated FCREPO-1023:
---------------------------------
Status: Open (was: Received)
Chris Wilper (Commented) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=23008#comment-23008 ]
Chris Wilper commented on FCREPO-1023:
--------------------------------------
I think we should deprecate the old format eventually, giving people some warning about it changing....a time period where both work, but where the old way eventually doesn't need to be maintained anymore.
Chris Wilper (Updated) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Wilper updated FCREPO-1023:
---------------------------------
Summary: No Support for Latest W3C SPARQL Query Results XML Format (was: No W3C SPARQL Query Results XML Format)
> No Support for Latest W3C SPARQL Query Results XML Format
> ---------------------------------------------------------
Benjamin Armintor (Updated) (DuraSpace JIRA)
[ https://jira.duraspace.org/browse/FCREPO-1023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Armintor updated FCREPO-1023:
--------------------------------------
Component/s: Trippi
Fix Version/s: Fedora 3.6
> No Support for Latest W3C SPARQL Query Results XML Format
> ---------------------------------------------------------
>
> Key: FCREPO-1023
> URL: https://jira.duraspace.org/browse/FCREPO-1023
> Project: Fedora Repository Project
> Issue Type: Bug
> Components: Fedora, Trippi
> Affects Versions: Fedora 3.4.2
> Reporter: Egbert Gramsbergen
> Fix For: Fedora 3.6