Hi Chak, as opposed to attributes with their #REQUIRED constraint, elements content has no such constraint. So you may specify:
<!ELEMENT PARENT_ITEM ((I1+,((I2+, I3+)|(I3+, I2+))) | (I2+,((I1+, I3+)|(I3+, I1+))) | (I3+,((I1+, I2+)|(I2+, I1+))))> you may !not! write nondeterministic models like ((I1, I2) | (I1, I3)). This is for SGML compatibility (http://www.w3.org/TR/2000/REC-xml-20001006#determinism) Marc > -----Urspr�ngliche Nachricht----- > Von: Chakradhar [SMTP:[EMAIL PROTECTED] > Gesendet am: Mittwoch, 6. Juni 2001 02:01 > An: [EMAIL PROTECTED] > Betreff: specifing elements in arbitary order in DTD > > Hello, > > Is there any way I can descibe Elements in DTD, where its child elements > SHOULD BE present but can > arrive in any arbitary order. > > I cant use ANY as that will allow some undesired elements to come through. > > For eg., > <!ELEMENT PARENT_ITEM (ITEM1, ITEM2, ITEM3)> > <!ELEMENT ITEM1 (#PCDATA)> > <!ELEMENT ITEM2 (#PCDATA)> > <!ELEMENT ITEM3 (#PCDATA)> > > Or is this where XMLSchema has an upper hand. > > And help is appreciated. Thanks. > > -Chak > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
