W3C home > Mailing lists > Public > www-forms@w3.org > April 2007

Re: XForms document versioning

From: Aaron Reed <aaronr@us.ibm.com>
Date: Wed, 04 Apr 2007 19:01:43 -0500
To: www-forms@w3.org
Message-ID: <ev1ee1$uh1$1@sea.gmane.org>

Hi Mark,

So any host language element could have this attribute on it?  What if 
there were multiple host language elements with xf:version and some of 
the version numbers were different?  This could certainly happen if we 
ever get the 'include' type functionality in XForms and we have 
different sections of the form coming from different documents.  And I 
assume xf:model's @version would win if the host-language element's and 
model element's @version differed?  Or is this meant to replace model's 
@version?  I could see them being different values because a 1.0 
processor can't honor the model's @version until it supports ALL of X.Y 
(whatever the value of @version is).  So the version on the 
host-language element could say 1.1 but there be no version on the model 
because someone could write a 1.1-level form using only the 1.1 pieces 
that their specific processor supports. .  This would also be true if 
the form author created some XBL to build up the processor's 
functionality to 1.1 level for things the author wants to use but the 
processor doesn't support, yet.

Having said all of that, I have no problem with the idea, just seems 
that it'll have the same drawbacks as model's @version where the version 
specified in the form may not match what the processor is capable of.


Mark Birbeck wrote:
> 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
Received on Thursday, 5 April 2007 00:09:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:20 UTC