W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > April to June 2000

Re: User interface default values

From: <Noah_Mendelsohn@lotus.com>
Date: Mon, 10 Apr 2000 21:10:34 -0400
To: "Curt Arnold" <carnold@houston.rr.com>
Cc: www-forms@w3.org, www-xml-schema-comments@w3.org
Message-ID: <OF0F528101.A393B215-ON852568BD.008140E0@lotus.com>
On the one hand, I'm sympathetic.  On the other hand, everyone always 
tells us the spec. has too much feature creep in it already.  Is this 
really worth even the modest added complexity over the existing "Default"? 
  I know they're not quite the same, but for many purposes a default is a 
fine way to prime a UI.  Of course, if forms needs something particular, 
<annotation> is available.

Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142

"Curt Arnold" <carnold@houston.rr.com>
Sent by: www-xml-schema-comments-request@w3.org
04/06/00 11:01 PM
Please respond to "Curt Arnold"

        To:     <www-xml-schema-comments@w3.org>
        cc:     <www-forms@w3.org>, (bcc: Noah Mendelsohn/CAM/Lotus)
        Subject:        User interface default values

I meant to mention this at XTech, but it may be useful to allow for 
and attribute a way that a user agent could obtain an initial or hint 
for an element or attribute that didn't add anything to the information 
Possibly something like:

<!-- For 'element' and 'attribute' -->
  <attributeGroup name="valueConstraint">
   <attribute name="default" type="string"/>
   <attribute name="fixed" type="string"/>
   <attribute name="initial" type="string"/>

When initial is specified, a user agent may use it to provide a initial
value for a user interface field, but an XML processor doesn't use it to
provide a value if it isn't specified.

<element name="order">
    <attribute name="quantity" type="non-negative-integer" initial="1"/>
    <attribute name="item" type="uri-Reference"/>

This could result in a Schema generated UI having a quantity field with
initialized to 1, but would not result in:

<order item="http://www.buyme.com/item.xml?5555"/>

being interpreted as having a quantity of 1.

Explicitly supporting this hint in XML Schema might make things a little
cleaner with XForms which is using default to mean what I called initial.
Received on Monday, 10 April 2000 21:14:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:47 UTC