I don't think so. An attribute called "id" has no special meaning in XML.
See http://www.w3.org/TR/2004/REC-xml-20040204/#id :
Validity constraint: ID
Values of type ID MUST match the Name production. A name MUST NOT appear more than once in an XML document as a value of this type; i.e., ID values MUST uniquely identify the elements which bear them.
This affects attributes of TYPE ID not with a NAME of id.
That's correct, but we also should have a future validation in mind. A form definition like Daniel's sample below must raise an exception then. Furthermore what happens if you have an additional widget (outside of repeater) with @id="foo.1.foo". This must raise an exception too of course thiugh the definition itself can be valid from XML point of view.
Joerg
Daniel Fagerstrom wrote:
What I mean is that the id attribute in the WD file not uniquely identifies a widget, let say that we have a widget definition:
<wd:repeater id="foo" initial-size="3"> <wd:widgets> <wd:field id="foo"> ... </wd:field> </wd:widgets> </wd:repeater>
Then it is paths like foo, foo.1.foo, foo.2.foo etc that uniquely identifies the widget.
