- From: <Toman_Vojtech@emc.com>
- Date: Tue, 8 Dec 2009 07:34:51 -0500
- To: <public-xml-processing-model-wg@w3.org>
Good catch. What about simply renaming p:xslt/@version to p:xslt/@xslt-version? Regarding the nested p:declare-step, I think it does inherit the version information (at least in our implementation, it does). Section 2.13 currently says: "The version identified applies to the element on which the version attribute appears and all of its descendants, unless or until another version is explicitly identified." Regards, Vojtech > -----Original Message----- > From: public-xml-processing-model-wg-request@w3.org > [mailto:public-xml-processing-model-wg-request@w3.org] On > Behalf Of Norman Walsh > Sent: Tuesday, December 08, 2009 1:26 PM > To: public-xml-processing-model-wg@w3.org > Subject: Version attribute issues > > I just realized that the version attribute is problematic. It's > already present on p:xslt and means something else. We could limit > version to just selected steps (non atomic ones?) or we could rename > it to 'xproc-version'. Or something. Suggestions? > > Also, does a p:declare-step nested inside another pipeline inherit > the version on its ancestor? I assume it does... > > Be seeing you, > norm > > -- > Norman Walsh <ndw@nwalsh.com> | The only thing that makes > life possible > http://nwalsh.com/ | is permanent, intolerable uncertainty; > | not knowing what comes > next.--Ursula K. > | LeGuin >
Received on Tuesday, 8 December 2009 12:35:39 UTC