RE: N3 contexts vs RDF reification

I'll observe that BOTH of these approaches can be mapped onto the 
underlying RDF core of triples, given suitable additional 
vocabulary.  Implementations don't have to use the triple model internally, 
as long as they can serialize to/from it.  This suggests it's too early to 
try and 'fix' this particular issue now, if ever.


At 11:12 AM 4/25/01 +0100, Lee Jonas wrote:
> >I think that all the advantages you ascribe to the (c,p,s,o) technique like
> >reification can also be attributed to the (id,p,s,o) technique see [2], but
> >with the added benefits above.
> >
> >This was suggested by Graham Klyne in his recent paper [3] and is the basis
> >of my work in progress.
> >
> >[1]
> >[2]
> >[3]
> >
> >Seth Russell
>I like the concept, but does it mean n+1 tuples? e.g.:
>Also, you have to explicitly identify all statement occurrences
>consistently, even across documents - this could prove yet another problem
>for generating valid rdf.
>Rather than an 'artificial key' for statements, what if the key were
>regarded as (p,s,o)?
>represents two contexts refering to the same statement.  The consumer of
>statements is free to 'import' them into their own contexts if they wish:

Graham Klyne

Received on Monday, 7 May 2001 12:00:10 UTC