Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Serializing RDF...why not start with the triples?

From: Leeh <Leeh@-----.--->
To: NULL
Date: 1/5/2007 10:22:00 AM

I'm new to the world of RDF and RDF/XML so pardon my naive question:

I understand that the "real" RDF model is the conceptual network of 
nodes (Subjects and Objects) connected by predicate arcs; and that the 
official way to serialize the graph is to use the RDF/XML specification.

So far so good; but N3 and/or N-Triple notations are also used, and it 
sure seems to me that N3 is  "iso-morphic" to the graph; i.e. The 
triples (properly constructed) represent the graph, the whole graph and 
nothing but the graph.

And now the question:

If we need to express the graph model in an XML -ish form, why wouldnt 
it be easier, simpler, less fattening, whatever, to start with the the 
triples thus:

<tripleSet>
    <triple>
      <subject>http://mydomain.com/myStuff/Thing42.doc</subject>
      <predicate>http://mydomain.com/myvocabulary#title</predicate>
      <object>Sitting On A Fence</object>
    </triple>
    ...
    etc for all the known triples


</tripleSet>

But as far as I can tell, no one has done or proposed such a thing. Has 
it got some sort of fatal flaw, conceptual or practical, that I'm 
looking right past?

What makes RDF/XML , which to my inexperienced eye seems a bit clunky in 
comparison, the preferred notation over N3 or an xml-ized version of N3 ?





transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent