incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-170) hexBinary whitespace issue
Date Mon, 28 Nov 2011 16:29:40 GMT


Henry Story commented on JENA-170:

perhaps one could have that be settable.

Our use case is the WebID protocol, of which a recent spec is up here
This protocol needs to fetch a document and do an ASK query match -- this is the simplest
way of explaining to implementers what needs to be done. If people can be failed to be logged
in because of a space on either side of the number then I think that people will be justified
in saying the SPARQL and RDF is too brittle to be used on the web... 

Now that an RDF engine does not process other datatypes that it does not know the semantics
for, I understand. But hexBinary is one of those standard types.

In the case of Clerezza which does not use SPARQL I'll fix that with the sameValueAs. But
on the ReadWriteWeb project 
 I am using SPARQL.

It really helps make the case for how easy and powerful the semantic web is. So it would be
nice if I could keep things that simple :-)

> hexBinary whitespace issue
> --------------------------
>                 Key: JENA-170
>                 URL:
>             Project: Jena
>          Issue Type: Bug
>          Components: ARQ, Jena, RDF/XML
>         Environment: 2.6.4
>            Reporter: Henry Story
>            Assignee: Andy Seaborne
>            Priority: Minor
> As I understand, initial and final white spaces in xsd:hexBinary in xml should be ignored
> because of the whitespace facet.
> With Jena 2.6.4 this is not the case, as shown by the test below. 
> I found that in Clerezza when using the graph api, so this is a problem even when one
does not use SPARQL.
> Removing the white space solves the proble. 
> xsd:hexBinary is already a very fragile encoding. Making it this fragile is bound to
lead to issues in communication.
> The same is true with the N3 encoding.
> -----------------------------------------------------------------
> hjs@bblfish[0]$ cat q1.sparql 
> PREFIX : <http://me.example/p#> 
> PREFIX xsd: <> 
>   ?S :related "AAAA"^^xsd:hexBinary .
> }
> hjs@bblfish[0]$ cat c1.rdf 
> <rdf:RDF xmlns="http://me.example/p#"
>     xmlns:rdf="">
>     <rdf:Description rdf:about="http://me.example/p#me">
>         <related rdf:datatype="">
> </related>
>     </rdf:Description>
> </rdf:RDF>
> hjs@bblfish[0]$ arq --query=q1.sparql --data=c1.rdf
> -----
> | S |
> =====
> -----

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message