Re: XForms document versioning

I think the global xf:version appearing on the root element of the 
document would not be just an authoring hint.

An XForms processor already has to scan the whole document anyway to find 
its models and UI controls, and indeed the other global attributes.

If it doesn't appear, then versioning by the local attribute on model 
would take over (and the default of 1.0 is already specified),

But if xf:version appears, then it should provide the version and a 
version exception should occur if it conflicts with the version numbering 
provided by the local attribute.

John M. Boyer, Ph.D.
STSM: Workplace Forms Architect and Researcher
Co-Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com 

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer





"T. V. Raman" <raman@users.sf.net> 
Sent by: www-forms-request@w3.org
04/05/2007 06:25 AM
Please respond to
raman@users.sf.net


To
steven.pemberton@cwi.nl
cc
mark.birbeck@x-port.net, www-forms@w3.org, www-forms-editor@w3.org
Subject
Re: XForms document versioning








My own preference is to have a version attribute (re: the TAG
discussion).

One possibility -- since xf:version is an author hint -- and
given that 1.0 didn't explicitly use it -- would be to default
xf:version to 1.0 when missing.

>>>>> "Steven" == Steven Pemberton <steven.pemberton@cwi.nl> writes:
    Steven> Funnily enough, a similar discussion is going on in
    Steven> the TAG. See for instance
    Steven> http://lists.w3.org/Archives/Public/www-tag/2007Apr/0031.html
    Steven> 
    Steven> Steven
    Steven> 
    Steven> On Wed, 04 Apr 2007 18:02:12 +0200, Mark Birbeck
    Steven> <mark.birbeck@x-port.net> wrote:
    Steven> 
    >> 
> 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
    >> 
    Steven>

-- 
Best Regards,
--raman

 
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs

Received on Thursday, 5 April 2007 18:43:01 UTC