- From: Dan Connolly <connolly@w3.org>
- Date: Tue, 06 Feb 2007 08:17:19 -0600
- To: Ian Davis <Ian.Davis@talis.com>
- Cc: public-grddl-wg@w3.org
On Tue, 2007-02-06 at 09:45 +0000, Ian Davis wrote: > I couldn't see this in the GRDDL spec, but I've looked so hard perhaps > I'm blind to it. My assumption is that a client is licensed to apply all > or none of the GRDDL transformations it can discover. Yes... the relevant rule is: "If F and G are GRDDL results of IR, then the merge [RDF-MT] of F and G is also a GRDDL result of IR" -- http://www.w3.org/2004/01/rdxh/spec#grddl-xml > This has to be > true because there may be transformation procedures that a given client > is not capable of performing, e.g. javascript. > > So the HTTP header is just another transformation that may or may not be > performed by the client. However if the header is present the client > should make an attempt to process it in the same way it would if the > transformation were in a link element or the namespace document. > > Is this correct? Sounds right. -- Dan Connolly, W3C http://www.w3.org/People/Connolly/ D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
Received on Tuesday, 6 February 2007 14:17:25 UTC