W3C home > Mailing lists > Public > public-grddl-wg@w3.org > August 2006

Re: On GRDDL and XML Documents

From: Harry Halpin <hhalpin@ibiblio.org>
Date: Tue, 29 Aug 2006 17:55:22 +0100
Message-ID: <44F4717A.3050804@ibiblio.org>
Cc: public-grddl-wg <public-grddl-wg@w3.org>


    Notice that we can use the "type" attribute to declare preferred
processing with HTML, so there's no reason why we can't indicate
symmetrically preferred processing as in XML as we do in XHTML by using
a "data-view:type" attribute for POX processing as well to indicate
preferred processing. However, this would break if one had a list of
differing processors as the attribute values of
"data-view:transformation" (like one XSL transform and another XQuery
transform) since there would be no-one "type" for all the processors.
Unless one had a list of media types in "data-view:type".

    Otherwise, I'm all for going and getting namespace documents and
looking for transforms in RDF. But requiring people to support that
might be difficult.
Ditto with xml-stylesheet PIs..

Chimezie Ogbuji wrote:
>
> 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
>
>


-- 
		-harry

Harry Halpin,  University of Edinburgh 
http://www.ibiblio.org/hhalpin 6B522426
Received on Tuesday, 29 August 2006 16:55:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:45 GMT