- From: Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>
- Date: Fri, 25 Aug 2006 00:01:09 -0400 (EDT)
- To: public-grddl-wg <public-grddl-wg@w3.org>
Just some thoughts on the GRDDL mechanism WRT to POX: The only mechanism (currently) [1] outlined for a GRDDL client to follow with an XML document is by grddl:transformation on the root element or by dereferencing the URI associated with the namespace of the document (root) element. The term namespace document is used but it's not clear how this 'document' is resolved from the URI I don't see a reason why not to include a much older precedent [2] in how transforms are associated with XML documents - especially for POX (instead of XHTML where the mechanisms are more specific). Dereferencing namespace documents over HTTP, determining transformation by HTTP content-type, and using XHTML semantics of rel='transformation' & head/@profile seem appropriate for XHTML, but shouldn't the fallback options for POX be (in this order)?: - Respond to grddl:transformation attribute on root document, resolving transform by HTTP URL - Respond to <?xml-stylesheet type='..' href='..' appropriately to resolve transformation (fail if not one of the *expected* transformation types) - Resolve RDF from namespace URI and respond to namespaceTransformation assertions (in RDF) - Resolve a (master/default) RDF document from a URI (which would this be?) for a set of 'default' namespaceTransformation assertions [1] http://www.w3.org/2004/01/rdxh/spec#ns-bind [2] http://www.w3.org/TR/xml-stylesheet/ Chimezie Ogbuji Lead Systems Analyst Thoracic and Cardiovascular Surgery Cleveland Clinic Foundation 9500 Euclid Avenue/ W26 Cleveland, Ohio 44195 Office: (216)444-8593 ogbujic@ccf.org
Received on Friday, 25 August 2006 04:01:22 UTC