RE: lexical value of selectMany

Our processing model is somewhat different, but the functionality you
described below (<item>my value 1</item>) will be possible with XForms. Our
upcoming draft will explain this in greater detail. Stay tuned...

.micah

-----Original Message-----
From: Waleed Nema [mailto:wNema@MediaOne.net]
Sent: Sunday, July 15, 2001 3:14 PM
To: 'Micah Dubinko'; www-forms@w3.org
Subject: RE: lexical value of selectMany


I was afraid that would be the answer! This is just as hard to
understand -for me- as requiring the ID value to start with an alpha
character (NMTOKEN)! Why should a standard impose restrictions on the
"value" of things?

To me, the user should be able to determine the delimiter -may be through
attribute(s) such as DelimeterType="xml" & DelimiterValue="item" which would
then make the value of the multiple selections a node list of elements (i.e.
<item>my value1</item><item>my value2</item>).

-----Original Message-----
From: Micah Dubinko [mailto:MDubinko@cardiff.com]
Sent: Friday, July 13, 2001 1:15 PM
To: 'wNema@NemaCorp.com'; www-forms@w3.org
Subject: RE: lexical value of selectMany


This creates a lexical value compatible with Schema list-derived
simpleTypes, such as described in XML Schema part 2, section 4.1.2.2
Derivation by list.

We're also discussing a <repeat>-like feature to bind a selectMany to
multiple child elements.

Did you have another option in mind?

Thanks,

.micah

-----Original Message-----
From: Waleed Nema [mailto:wNema@MediaOne.net]
Sent: Friday, July 13, 2001 5:30 AM
To: www-forms@w3.org
Subject: lexical value of selectMany


why on earth use space as a delimiter when multiple values are selected?
(section 7.6)

Received on Monday, 16 July 2001 17:45:11 UTC