- From: David Allsopp <dallsopp@signal.dera.gov.uk>
- Date: Wed, 28 Mar 2001 14:27:33 +0100
- To: "Karsten-A. Otto" <ottoka@cs.tu-berlin.de>
- CC: www-rdf-interest@w3.org
"Karsten-A. Otto" wrote:
> The main difference between chunked and streaming approach here is the
> semantics of transmitted data. With (self contained) chunks, each
> message represents a complete RDF model. With a "stream" of triples,
> a "session" is a single RDF model that changes over time.
>
> The choice of semantics depends on the way the message data is supposed
> to interact with the sending/receiving application. Are the message
> triples simply added to the applications internal data model? Is it
> an "event" that the application interprets to change its internal model?
> What if the application does not use RDF internally?
Perhaps I could make the (fairly obvious) point that if incoming triples
are added to a model, which changes over time, the model may not be
"reasonable" RDF until they have all arrived, e.g. if arbitrary parts of
an RDF:Bag arrive, or parts of a reified statement. A hierarchical
structure of triples may not make sense until all parts have arrived.
Regards,
David Allsopp
DERA Malvern
UK
--
/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 Wednesday, 28 March 2001 08:28:04 UTC