- From: Micah Dubinko <MDubinko@cardiff.com>
- Date: Tue, 30 Jul 2002 16:49:14 -0700
- To: 'Jérôme Nègre' <jerome.negre@e-xmlmedia.fr>, www-forms@w3.org
Greetings, Roland did an outstanding job answering some of your questions. Let's see if I can keep up the trend. :-) 1) In <model>, shouldn't it be <xsd:group ref="xforms:actionGroup"/> instead of <xsd:element ref="xforms:action"/>? Yes, that is certainly a bug. 2) In <submission>, may-be that providing a default value for @method would be useful. Yes, it would. I will check to see what we said about what the default value should be. 5) I think there's a missing minOccurs="0" in the xsd:sequence of <label>, <hint>, <help> and <alert>. Are you talking about xforms:optionalUIChildren? Or somewhere else? 6) @id of <choices> and <item> should have an explicit use="optional" to be more consistent. and 12) In <switch>, @id could be optional. I need to check on the overall structure of id attributes, and how this will interact with a host language. Any useful <switch> will require an @id, since <toggle> actions need to refer to it. 8) I'm not sure that the new name <select1> is better than the old <selectOne>. Same issue with <select> and <selectMany>. At least the new names are all lowercase. :-) 13) In <switch>, what's the use of @default? Shouldn't @selected in <case> be used instead? That's a Schema typo--@default shouldn't be there anymore. Thanks! .micah P.S. As Martin noticed, the attribute on <bind> should be named 'nodeset', not 'bind'. Thanks! -m -----Original Message----- From: Jérôme Nègre [mailto:jerome.negre@e-xmlmedia.fr] Sent: Wednesday, July 24, 2002 5:29 AM To: Micah Dubinko; www-forms@w3.org Subject: Re: XForms Schema Attached Hi, Glad to have some news from the Working Group! This schema resolves several issues, but the following points are unclear to me: 1) In <model>, shouldn't it be <xsd:group ref="xforms:actionGroup"/> instead of <xsd:element ref="xforms:action"/>? 2) In <submission>, may-be that providing a default value for @method would be useful. 3) Why use @ref in <bind> instead of @nodeset? It would be much more consistent IMHO. 4) Everything is now in lowercase, except @minOccurs and @maxOccurs of <bind>, is it on purpose? 5) I think there's a missing minOccurs="0" in the xsd:sequence of <label>, <hint>, <help> and <alert>. 6) @id of <choices> and <item> should have an explicit use="optional" to be more consistent. 7) Does incremental="true" means the use of a spinner or equivalent? If the answer is yes, I'm not sure it's very relevant on <secret>. 8) I'm not sure that the new name <select1> is better than the old <selectOne>. Same issue with <select> and <selectMany>. 9) <selectMany>, er no, <select> has now @selection, I hope a suggestion of rendering for a graphical browser will be available. 10) what's the use of bindFirstAttributes on <trigger>? 11) where is <repeat> gone, and what's the use of all those @repeat-*? 12) In <switch>, @id could be optional. 13) In <switch>, what's the use of @default? Shouldn't @selected in <case> be used instead? Regards, Jérôme
Received on Tuesday, 30 July 2002 19:49:17 UTC