Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Not A Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: ARQ, Jena, RDF/XML
    • Labels:
      None
    • Environment:

      2.6.4

      Description

      As I understand, initial and final white spaces in xsd:hexBinary in xml should be ignored

      http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#hexBinary

      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: <http://www.w3.org/2001/XMLSchema#>

      SELECT ?S WHERE {
      ?S :related "AAAA"^^xsd:hexBinary .
      }

      hjs@bblfish[0]$ cat c1.rdf

      <rdf:RDF xmlns="http://me.example/p#"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

      <rdf:Description rdf:about="http://me.example/p#me">
      <related rdf:datatype="http://www.w3.org/2001/XMLSchema#hexBinary">
      AAAA
      </related>
      </rdf:Description>
      </rdf:RDF>

      hjs@bblfish[0]$ arq --query=q1.sparql --data=c1.rdf


      S

      =====


        Attachments

          Activity

            People

            • Assignee:
              andy.seaborne Andy Seaborne
              Reporter:
              bblfish Henry Story
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: