- From: John Boyer <boyerj@ca.ibm.com>
- Date: Wed, 24 Oct 2007 18:29:58 -0700
- To: Nick_Van_den_Bleeken@inventivegroup.com
- Cc: Forms WG (new) <public-forms@w3.org>
- Message-ID: <OF1EFDCC71.647690F5-ON8825737F.0007C4CF-8825737F.00084A3A@ca.ibm.com>
Hi Nick, I don't understand why you defined ValueTemplate thus: <xsd:complexType name="ValueTemplate" mixed="true"> <xsd:attribute name="value" type="xforms:XPathExpression" use="optional"/> </xsd:complexType> I understand why you defined it (so you wouldn't have to write the same stuff over again), but this particular definition seems to allow the content of toggle/case, setfocus/control, load/resource, submission/resource to be other than character data. mixed seems to allow a mixture of characters and elements, whereas we want the content of these elements to be use when there is no value attribute. Wouldn't it be better to define it more like it is defined for the setvalue action, e.g. this: <xsd:complexType name="ValueTemplate"> <xsd:simpleContent> <xsd:extension base="xsd:string"> <xsd:attribute name="value" type="xforms:XPathExpression" use="optional"/> </xsd:extension> </xsd:simpleContent> </xsd:complexType> I'm going to risk it and make the change to this latter form now, but please tell me whether or not this is a good idea... Thank you, John M. Boyer, Ph.D. STSM: Lotus Forms Architect and Researcher Chair, W3C Forms Working Group Workplace, Portal and Collaboration Software IBM Victoria Software Lab E-Mail: boyerj@ca.ibm.com Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Received on Thursday, 25 October 2007 01:30:51 UTC