W3C home > Mailing lists > Public > www-forms-editor@w3.org > August 2002

"maxOccurs" oddity

From: Micah Dubinko <MDubinko@cardiff.com>
Date: Tue, 27 Aug 2002 08:15:36 -0700
Message-ID: <E840F0B7E6189547BDB91DA8BF2228AB28C6EF@csmail.cardiff.com>
To: "'www-forms-editor@w3.org'" <www-forms-editor@w3.org>

As I understand it, the naming guidelines in the latest XForms draft are:

1. For things specific to XForms, use all lower case names, without hyphens,
with a preference towards short names

2. For things defined by another spec and carried over into XForms, keep the
exact spelling already defined.

This is why, for example, there are attributes originally from XSLT that use
hyphens (omit-xml-declaration, etc.) in XForms.

In the Jan draft, "maxOccurs" was specified as either a nonNegativeInteger,
or the special value "undefined", just as in XML Schema.

In the Aug draft, "maxOccurs" is now a computed expression, specified as an
XPath expression. This leads to a few oddities, which should be resolved.

1) behavior should be specified for when the expression returns a negative
number, either of the infinities, or NaN.

2) the string value "undefined" doesn't need to be special cased any more.
(because one could always use "INF"). The expression needs to be specified
as always resolving to a Number.

3) since this substantially changes the semantics of this model item
property, in accordance with the naming guidelines, it should be called
"maxoccurs" instead of "maxOccurs".

Nearly everything in this message applies to minOccurs too.

Thanks,

.micah
Received on Tuesday, 27 August 2002 11:15:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 10 June 2009 18:12:11 GMT