Re: Implementing statement grouping, contexts, quads and scopes

Patrick Stickler wrote:

> On 2002-06-24 18:00, "ext Jonathan Borden" <jonathan@openhealth.org> wrote:
>
> Note that the approach I am proposing also would support arbitrary
> "colored" triples, not just a binary unasserted/asserted distinction:
>
> <rdf:Statement rdf:about="#foo"/>
>   <xxx:bar rdf:resource="#bas"/>
> </rdf:Statement>
>
> <rdf:Description rdf:about="&xxx;bar">
>    <rdf:type rdf:resource="#redPredicate"/>
> </rdf:Description>
>
> <rdf:Statement rdf:about="#foo"/>
>   <yyy:bar rdf:resource="#bas"/>
> </rdf:Statement>
>
> <rdf:Description rdf:about="&yyy;bar">
>    <rdf:type rdf:resource="#bluePredicate"/>
> </rdf:Description>
>
> <rdf:Statement rdf:about="#foo"/>
>   <zzz:bar rdf:resource="#bas"/>
> </rdf:Statement>
>
> <rdf:Description rdf:about="&zzz;bar">
>    <rdf:type rdf:resource="#greenPredicate"/>
> </rdf:Description>
>
> etc. where a given application (e.g. via a "color"
> specific API) would interact with the knowledge
> base, seeing as asserted both the fundamental
> RDF asserted triples as well as the colored
> triples of interest.

could you  try to make an example which uses the above syntax to encode a
rule/formula? i.e. X=>Y

can your syntax "scope" asserted and un-asserted as well then? i.e. doing
things similar to the rdf:bagID effect :-)

thank you

Alberto

Received on Tuesday, 25 June 2002 09:01:54 UTC