W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > May 2001

Re: Issue #rdfms-not-id-and-resource-attr

From: Aaron Swartz <aswartz@upclink.com>
Date: Thu, 24 May 2001 14:54:09 -0700
To: Art Barstow <barstow@w3.org>
CC: Dave Beckett <dave.beckett@bristol.ac.uk>, w3c-rdfcore-wg <w3c-rdfcore-wg@w3.org>, Brian McBride <bwm@hplb.hpl.hp.com>
Message-ID: <B732D10F.C490%aswartz@upclink.com>
Art Barstow <barstow@w3.org> wrote:

>> <rdf:Description>
>>    <propName rdf:ID="foo" rdf:resource="bar"/>
>> </rdf:Description>
>> would also assign foo the the reification of the statement.
> Would you please enumerate the triples you would
> expect from the above RDF if it was legal (and doing so
> in Subject, Pred, Object format ala SiRPAC would be much
> appreciated)?

Sorry for not including this -- I've done it several times before (but not
in SiRPAC style) so I was getting tired, but here it is:

triple(r('#genid1'),r('http://rdf.example.org/#propName'),r('bar')) .
#genid1')) .
('http://rdf.example.org/#propName')) .
ar')) .

> Also, what triples would you expect if the RDF was:
> <rdf:Description about="some_resource">
>   <propName rdf:ID="foo" rdf:resource="bar"/>
> </rdf:Description>

The same as above except "some_resource" replaces "#genid1". This kind of
output is very much in line with what would happen with something like:

   <propName rdf:ID="foo">bar</propName>

and the same with an rdf:about.

[ Aaron Swartz | me@aaronsw.com | http://www.aaronsw.com ]
Received on Thursday, 24 May 2001 17:54:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:24:00 UTC