W3C home > Mailing lists > Public > www-rdf-interest@w3.org > October 2001

Re: a new way of thinking about RDF and RDF Schema

From: Sergey Melnik <melnik@db.stanford.edu>
Date: Mon, 22 Oct 2001 18:52:11 -0700
Message-ID: <3BD4CD4B.2374E58F@db.stanford.edu>
To: "Peter F. Patel-Schneider" <pfps@research.bell-labs.com>
CC: bwm@hplb.hpl.hp.com, www-rdf-interest@w3.org, simeon@research.bell-labs.com
"Peter F. Patel-Schneider" wrote:
> From: Sergey Melnik <melnik@db.stanford.edu>
> Subject: Re: a new way of thinking about RDF and RDF Schema
> Date: Mon, 22 Oct 2001 16:47:00 -0700
> >
> > The above suggestion does assign meaning to any well-formed XML
> > document. As explained in "syntax.html", by default every XML tag
> > encountered during processing is considered to be a property name.
> >
> > Sergey
> How can you handle
> <foo>
>  7
>  <bar>8</bar>
>  <baz>
>    <bay>9</bay>
>  </baz>
> </foo>
> You can't make all the tags be property names unless you do some serious
> surgery on the XML.  (It does appear that you are doing some surgery in
> your fusion document, but I can't seem find out just what you are doing.  A
> specification of what is going on would be very useful.)
> peter



contains a complete specification of a parsing algorithm. Think of
"getUniqueURI()" as a function that creates a bNode (aka anonymous
node). If two "property nodes" are nested, one of them is assumed to be
the type of a bNode.

http://www-db.stanford.edu/~melnik/rdf/fusion.html provides a graphical
interpretation of a sample XML document. In fact, in this example a
slighly different definition of "getObject()" is used that handles
dangling PCDATA like "7" in your example above. The example uses ordinal
properties to represent order. As of now, I'm not convinced that this is
a good idea any more. How would you represent order in an RDF graph?

Received on Monday, 22 October 2001 21:39:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:32 UTC