- From: Jeremy Carroll <jjc@hpl.hp.com>
- Date: Fri, 22 Jun 2007 11:21:21 +0100
- To: "Booth, David (HP Software - Boston)" <dbooth@hp.com>
- CC: public-grddl-wg@w3.org, Fabien.Gandon@sophia.inria.fr
Booth, David (HP Software - Boston) wrote: > Key considerations in this use case > > * As RDF deserialization algorithms, Amy's GRDDL transformations > must be unambiguous: for a given XML document, it must be crystal > clear, exactly what RDF graph that XML document denotes. There are two variations of addressing this use case, in ways other than David's proposals. a) If the document is being served from the Web, and the publisher is not able to come to an out-of-band agreement with the intended consumers about how to manage the variability then: - the publisher should do server side processing to produce the 'unambiguous' RDF - this can be published using content negotiation for application/rdf+xml b) If the document is not being served from the Web, then it is inside some other application. This application then could set its local policy for GRDDL aware agents so that these particular goals are achievable. I believe part b) is applicable to XML messaging pipeline use case, which I think covers all of the use cases David has presented. Jeremy -- Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN Registered No: 690597 England
Received on Friday, 22 June 2007 10:21:48 UTC