W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > February 2012

Re: V.next: attribute value templates

From: Innovimax W3C <innovimax+w3c@gmail.com>
Date: Thu, 2 Feb 2012 11:15:13 +0100
Message-ID: <CAAK2GfHfzvbTBvCsVW+BY9tRbAZQkYrR6P7AGCgXNtgPD-CLDg@mail.gmail.com>
To: Norman Walsh <ndw@nwalsh.com>
Cc: public-xml-processing-model-wg@w3.org
On Wed, Feb 1, 2012 at 7:17 PM, Norman Walsh <ndw@nwalsh.com> wrote:
> Innovimax W3C <innovimax+w3c@gmail.com> writes:
>> I don't think they are so uncontroversial than that
>> In XSLT or XQuery, the context is define EVERYWHERE
> That's not true. It's undefined in xsl:function.
>> But in XProc we made some shortcut to keep things simple to explains
>> I fear that AVT will reopen this can of worm
> You might be right, but I think we can say that the context is the
> (first?) document from the default readable port and that it's an
> error if an expression attempts to refer to the context when there is
> no such port.

Seems interesting but it also mean that each time someone uses AVT,
there is a NEW connection to the default readable port and there will
be a need to dynamically verify that the XPath uses the context or

Another option is to says that the context is always empty and if you
need to access some content you need to use the long form
(p:with-option select="...") and the AVT are there only to allow you
to do XPath that doesn't access the context (variables, computations,
string manipulations)


Innovimax SARL
Consulting, Training & XML Development
9, impasse des Orteaux
75020 Paris
Tel : +33 9 52 475787
Fax : +33 1 4356 1746
RCS Paris 488.018.631
SARL au capital de 10.000 
Received on Thursday, 2 February 2012 10:15:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:50 UTC