W3C home > Mailing lists > Public > www-rdf-logic@w3.org > June 2001

Re: Nests and abstract syntax: Quads vs. nests as sets of Triples

From: David Allsopp <dallsopp@signal.dera.gov.uk>
Date: Fri, 08 Jun 2001 09:53:04 +0100
Message-ID: <3B209270.47928AD@signal.dera.gov.uk>
To: Tim Berners-Lee <timbl@w3.org>
CC: www-rdf-logic@w3.org


Tim Berners-Lee wrote:
> 
> ----- Original Message -----
> From: "Jonathan Borden" <jborden@mediaone.net>
> [...]
> . The issue arises when the RDF 'page' (e.g. as represented by text
> > or an internal representation of the XML Infoset) is chopped and flattened
> > into triples. The document hierarchy and element order is then lost.
> 
> But you can't do that, surely, anymore than you can strip the parentheses
> out of
> a mathamatical expression or the elements out of an XML document.

I think you can, since the information isn't actually 'lost' (apart from
the document order, which shouldn't matter). Consider the current RDF
API's - the triples are often not stored in an actual graph, with
explicit pointers to each other, but in some kind of array or hash or
whatever. The graph can be reconstructed from these triples though, by
checking for resources that occur in more than one triple. Isn't that
all we're talking about when we speak of 'flattening into triples'?

Regards,

David Allsopp.

-- 
/d{def}def/u{dup}d[0 -185 u 0 300 u]concat/q 5e-3 d/m{mul}d/z{A u m B u
m}d/r{rlineto}d/X -2 q 1{d/Y -2 q 2{d/A 0 d/B 0 d 64 -1 1{/f exch d/B
A/A z sub X add d B 2 m m Y add d z add 4 gt{exit}if/f 64 d}for f 64 div
setgray X Y moveto 0 q neg u 0 0 q u 0 r r r r fill/Y}for/X}for showpage
Received on Friday, 8 June 2001 04:54:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:52:40 GMT