- From: Leigh L Klotz Jr <leigh.klotz@xerox.com>
- Date: Fri, 03 Feb 2012 14:24:55 -0800
- To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
- CC: Public Forms <public-forms@w3.org>
- Message-ID: <4F2C5EB7.8090409@xerox.com>
On 02/02/2012 12:38 PM, Nick Van den Bleeken wrote: > Leigh, > >> 2. I didn't put AVT on @ref or @nodeset because it wasn't clear to me >> which we were doing and which we weren't > both ref and nodeset contain path expressions and therefore don't > support AVTs by definition (from the spec: Curly brackets are not > treated specially in an attribute value in an XForms document if the > attribute doesn't support attribute value templates or if the content > model of the attribute is already an expression.) OK, that's what I did in the RNC as well; if it was already an XPath expression I didn't make it be AVT. >> 3. I asked a question about adding header/@name and header/@value and >> have added them in to the RNC for now. >> Note that header/@value is slightly different from >> header/value/@value because you can have multiple header/value[] >> elements. > I think we should not add a name and value attribute to the header > element. > It would be good to discuss this in the group. > Kind regards, > > Nick Van den Bleeken > R&D Manager > > Phone: +32 3 425 41 02 > Office fax: +32 3 821 01 71 > nick.van.den.bleeken@inventivegroup.com > <mailto:nick.van.den.bleeken@inventivegroup.com> > www.inventivedesigners.com > > > > On 01 Feb 2012, at 23:13, Leigh L Klotz Jr wrote: > >> I've added a first draft of AVT support in the XForms 2.0 RNC schema >> as asked in this action: >> https://www.w3.org/2005/06/tracker/xforms/actions/1852 >> >> 1. I didn't verify every attribute agains the specification >> 2. I didn't put AVT on @ref or @nodeset because it wasn't clear to me >> which we were doing and which we weren't >> 3. I asked a question about adding header/@name and header/@value and >> have added them in to the RNC for now. >> Note that header/@value is slightly different from >> header/value/@value because you can have multiple header/value[] >> elements. >> >> Leigh. >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> > > > ------------------------------------------------------------------------ > > Inventive Designers' Email Disclaimer: > http://www.inventivedesigners.com/email-disclaimer
Received on Friday, 3 February 2012 22:25:31 UTC