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

[#issue-mt-ns] GRDDL and Processing Order

From: Harry Halpin <hhalpin@ibiblio.org>
Date: Fri, 06 Oct 2006 17:18:59 +0100
Message-ID: <452681F3.4030408@ibiblio.org>
To: public-grddl-wg <public-grddl-wg@w3.org>

I'm just going to sort of do an exegesis of Murray's proposal [1], which
I *think* can be summarized as "A GRDDL transformation applies to the
document as received by the client from the server with no additional
processing assumed to be done. "

Then maybe to clear things up: "If additional processing needs to be
done in order to extract valid RDF, it should be done either by the
server before it sends the document to the server or as the processing
should be included in the GRDDL transform itself."

Adding sentences to those effect in the Spec would be useful, maybe with
one of the following examples:

 This means a GRDDL transformation would *not* use XInclude to include
items before running a GRDDL transform, or if the document itself
contained XSLT elements it would *not* run that XSLT and then run the
GRDDL transform, but would just run the GRDDL transform. If you wanted
the include via XInclude items or run another XSLT transformation before
running GRDDL,  you would use some sort of pipeline language like
XMLProc as your GRDDL Transformation [2].

    There used to be some issues, originally brought up by Brian McBride
I believe, that dealt with whether or not XIncludes should resovled, if
XSLT code in the source document should be run before GRDDL, and the
such but I can't find them [3] except for issues involving RDF as a
namespace document [4], which I don't think Murray's suggestion applies to.




Harry Halpin,  University of Edinburgh 
http://www.ibiblio.org/hhalpin 6B522426
Received on Friday, 6 October 2006 21:19:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:52:33 UTC