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

Re: [Moderator Action] Re: 8.1.7 - range Element

From: Thierry Michel <tmichel@w3.org>
Date: Tue, 3 Sep 2002 18:11:53 +0200
Message-ID: <153c01c25364$9e5ac8e0$228a608a@inria.fr>
To: <AndrewWatt2001@aol.com>, <www-forms@w3.org>, <www-forms-editor@w3.org>
Moderator: sent to www-forms@w3.org and www-forms-editor@w3.org 
  ----- Original Message ----- 
  From: AndrewWatt2001@aol.com 
  To: jerome.negre@e-xmlmedia.fr ; xforms@yahoogroups.com ; www-forms@w3.org ; www-forms-editor@w3.org 
  Sent: Tuesday, September 03, 2002 2:42 PM
  Subject: [Moderator Action] Re: 8.1.7 - range Element


  In a message dated 03/09/2002 13:31:03 GMT Daylight Time, jerome.negre@e-xmlmedia.fr writes:



    > The start and end attributes are stated to be optional.
    > 
    > How can a user agent render a range for which it does not know the start 
    > bound and the end bound or both?
    > 
    > Andrew Watt

    By looking at the facets (minInclusive, maxExclusive) of the datatype.

    Jérôme


  If that's the intended mechanism what's the purpose of an optional pair of "hint" attributes? Can the user agent ignore the "hint"?

  What happens if the two sources of information are inconsistent? Which value takes precedence?

  It seems to me to invite problems in scenarios where a developer/data model person is writing the code for the schema and an interface person is writing the XForms form control markup.

  Andrew Watt 
Received on Tuesday, 3 September 2002 12:12:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:52 GMT