- From: Jérôme Nègre <jerome.negre@e-xmlmedia.fr>
- Date: Wed, 24 Jul 2002 14:29:02 +0200
- To: "Micah Dubinko" <MDubinko@cardiff.com>, <www-forms@w3.org>
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 Wednesday, 24 July 2002 08:30:32 UTC