- From: Johannes Koch <johannes.koch@fit.fraunhofer.de>
- Date: Thu, 27 Nov 2008 09:51:13 +0100
- To: Toby A Inkster <tai@g5n.co.uk>
- Cc: public-wai-ert@w3.org
Hi Toby Toby A Inkster schrieb: > On 21 Nov 2008, at 17:37, Johannes Koch wrote: >> Toby A Inkster schrieb: >>> I realise it's past the deadline for feedback, but I have one thing >>> I'd like to mention. Say I have: >>> <http:Request> >>> <http:methodName>GET</http:methodName> >>> <http:absoluteURI>http://example.org/foo</http:absoluteURI> >>> <http:response> >>> <http:Response> >>> <http:statusCodeNumber>200</http:statusCodeNumber> >>> </http:Response> >>> </http:response> >>> </http:Request> >>> And I also have some triples pertaining to the document itself: >>> <rdf:Description rdf:about="http://example.org/foo"> >>> <dc:title>Foo</dc:title> >>> <dc:creator>John Citizen</dc:creator> >>> </rdf:Description> >>> It would be nice if there were some sort of predicate for linking >>> from the Request resource to the Description resource, or vice versa. >> >> I'd propose to add an http:body property with a cnt:Content (see >> "Representing Content in RDF" <http://www.w3.org/TR/Content-in-RDF/>) >> object resource "http://example.org/foo" to the http:Response subject. > > I suppose that could work, but what about if http://example.org/foo is a > foaf:Person? Are we then saying that a physical person was sent down the > wire? I'm pretty sure, yes :-) So it's your responsibility to not add triples with rdf:type foaf:Person for "http://example.org/foo". -- Johannes Koch Fraunhofer Institute for Applied Information Technology FIT Web Compliance Center Schloss Birlinghoven, D-53757 Sankt Augustin, Germany Phone: +49-2241-142628 Fax: +49-2241-142065
Received on Thursday, 27 November 2008 08:51:53 UTC