W3C home > Mailing lists > Public > public-forms@w3.org > February 2012

Re: AVT in XForms 2.0 RNC

From: T.V Raman <raman@google.com>
Date: Wed, 8 Feb 2012 16:23:54 -0800
Message-ID: <20275.4634.547829.688114@retriever.mtv.corp.google.com>
To: Nick.Van.den.Bleeken@inventivegroup.com
Cc: leigh.klotz@xerox.com, public-forms@w3.org
You mostly want AVTs in dynamic places like <repeat> and <itemset>

Nick Van den Bleeken writes:
 > 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.) 
 > 
 >     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.
 > 
 > 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
 > www.inventivedesigners.com
 > 
 > [cid]   [cid]   [cid]   
 > 
 > 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 Thursday, 9 February 2012 00:24:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 October 2013 22:06:56 UTC