- From: Patrick Stickler <patrick.stickler@nokia.com>
- Date: Tue, 04 Jun 2002 09:42:54 +0300
- To: ext Michael Kifer <kifer@cs.sunysb.edu>, Seth Russell <seth@robustai.net>
- CC: Aaron Swartz <me@aaronsw.com>, "Sean B. Palmer" <sean@mysterylights.com>, RDF Interest <www-rdf-interest@w3.org>
On 2002-06-04 3:11, "ext Michael Kifer" <kifer@cs.sunysb.edu> wrote:
>>>>>> "SR" == "Seth Russell" <of Mon, 03 Jun 2002 10:35:26 PDT> writes:
>
> MK> NTriples can be naturally encoded in XML and exchanged.
>
> SR> Is that actually true? How?
>
> <triple><subject ...>subj</subject><property>...</property> <object> ...
> </object> </triple>
Why of course. Why did we not see this before?!
We can just use a subset of RDF instead of NTriples:
<rdf:RDF ...>
<rdf:Statement>
<rdf:subject rdf:resource="http://foo.com/bar"/>
<rdf:predicate rdf:resource="voc://abc.org/blarrg"/>
<rdf:object rdf:resource="#node12345"/>
</rdf:Statement>
<rdf:Statement>
<rdf:subject rdf:resource="#node12345"/>
<rdf:predicate rdf:resource="voc://abc.org/booga"/>
<rdf:object>Gumby</rdf:object>
</rdf:Statement>
...
</rdf:RDF>
I hereby propose we toss NTriples altogether and just use RDF/XML
as above for all test cases output.
RDF/XML provides all the mechanisms needed to explicitly express
the precise triples existing in any RDF graph, as RDF/XML.
(not really joking about this, actually ;-)
Patrick
--
Patrick Stickler Phone: +358 50 483 9453
Senior Research Scientist Fax: +358 7180 35409
Nokia Research Center Email: patrick.stickler@nokia.com
Received on Tuesday, 4 June 2002 02:39:50 UTC