Mark, we changed section 3.3.1 to default model version to empty, and defined empty to mean that the processor gets to choose the version. If no version chosen is available, the xforms-version-exception is dispatched to the default model. The declaration on the default model is used to make the choice. Later models may offer declarations of model version but xforms-version-exception is a gain dispatched to the default model if their declarations are incompatible with the version chosen. Regards, Ulrich Nicolas Lissé. For the Forms WG > Hello, > > I'd like to suggest that we have a version attribute that can be used > on any element in a host language. This would therefore be a global > attribute in the XForms namespace, and might be used as follows: > > <html xf:version="1.1"> > ... > </html> > > My feeling is that this attribute is less about enforcing behaviour of > processors, and more about providing a clear indication to authors > which type of document they are dealing with. > > For example, if a form contains a submission that uses the new > xf:resource attribute or element, it may not be immediately obvious to > a new author as they start to learn XForms, that this is not supported > in all processors. Rather than having a flurry of emails on one or > other list saying that some example doesn't work, I think we should > encourage authors to indicate what standard is being used by a form. > > Regards, > > Mark > > -- > Mark Birbeck, formsPlayer > > mark.birbeck@x-port.net | +44 (0) 20 7689 9232 > http://www.formsPlayer.com | http://internet-apps.blogspot.com > > standards. innovation. > >Received on Thursday, 14 June 2007 20:14:21 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 June 2008 13:19:44 GMT