W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > October 2001

Re: Interpretation property

From: <jos.deroo.jd@belgium.agfa.com>
Date: Sat, 13 Oct 2001 14:19:54 +0100
To: melnik@db.stanford.edu
Cc: w3c-rdfcore-wg@w3.org
Message-Id: <OF4A221A0D.EBAE9BEE-ON41256AE4.004815F4@bayer-ag.com>

[sorry for the late reply, but my home telephone line is broken
but now I can make use of my friends facilities]

Sergey,

W.r.t. interpretation properties, please have a look at
  http://www.w3.org/DesignIssues/InterpretationProperties.html

e.g.
[[
  <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
           xmlns:play="http://example.org/play#"
           xmlns:enc="http://example.org/enc#">
    <rdf:Description rdf:about="http://www.w3.org/">
      <play:xml-cannonicalized rdf:parseType="Resource">
        <enc:hash-sha-1 rdf:parseType="Resource">
          <enc:base64>jd8734djr08347jyd4</enc:base64>
        </enc:hash-sha-1>
      </play:xml-cannonicalized>
    </rdf:Description>
  </rdf:RDF>
]]

or in RDF/NT
[[
  <http://www.w3.org/> <http://example.org/play#xml-cannonicalized> _:bNode1 .
  _:bNode1 <http://example.org/enc#hash-sha-1> _:bNode2 .
  _:bNode2 <http://example.org/enc#base64> "jd8734djr08347jyd4" .
]]
so it is just like 'inserting' interpretation properties via bNode chains

also for a dt case one could have e.g.
[[
  play:some-subject play:some-property _:bNode .
  _:bNode xsi:some-type "plain-xml-schema-instance-with-ns-decl-and-\n-escaping" .
]]

--
Jos

P.S. If we transform back the former N-Triples to RDF/XML we get
1. with "python /n3/cwm.py ip2.nt --rdf"
[[
  <!-- Processed by Id: cwm.py,v 1.79 2001/09/27 19:45:28 connolly Exp -->
  <!--     using base file:/rdf/ip2.nt-->


  <rdf:RDF xmlns="http://example.org/enc#"
      xmlns:log="http://www.w3.org/2000/10/swap/log#"
      xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

      <rdf:Description rdf:about="http://www.w3.org/">
          <xml-cannonicalized xmlns="http://example.org/play#"
              rdf:parseType="Resource">
              <hash-sha-1 xmlns="http://example.org/enc#"
                  rdf:parseType="Resource">
                  <base64>jd8734djr08347jyd4</base64>
              </hash-sha-1>
          </xml-cannonicalized>
      </rdf:Description>
  </rdf:RDF>
]]
which seems reasonable as far as I can see

2. with "java -cp /Jena-1.2.0/lib/jena.jar;/Jena-1.2.0/lib/xerces.jar
   jena.rdfcopy ip2.nt N-TRIPLE RDF/XML"
[[
  <rdf:RDF
    xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
    xmlns:NS0='http://example.org/enc#'
    xmlns:NS1='http://example.org/play#'
   >
    <rdf:Description rdf:about='#A0'>
      <NS0:base64>jd8734djr08347jyd4</NS0:base64>
    </rdf:Description>
    <rdf:Description rdf:about='http://www.w3.org/'>
      <NS1:xml-cannonicalized rdf:resource='#A1'/>
    </rdf:Description>
    <rdf:Description rdf:about='#A1'>
      <NS0:hash-sha-1 rdf:resource='#A0'/>
    </rdf:Description>
  </rdf:RDF>
]]
which is problematic I think because that are
*not* bNodes anymore (and that is maybe what
Ron was seeing as a problem, I don't know)
Received on Saturday, 13 October 2001 09:13:15 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 3 September 2003 09:41:02 EDT