[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Proposed resolution for #19: attrInAttr
James Clark wrote: > For example, should >it give a warning for: > ><attribute name="foo"> > <choice> > <data type="xsd:string"> > <element name="bar">...</element> > </choice> ></attribute> > >? Why should it not be an error to have something like: > ><attribute name="foo"> > <element name="bar"/> ></attribute> > >? Is it because it is too hard to detect? If it's too hard to detect, then >I don't want to say that implementations "should" detect it. Ater normalization, <attribute> does not contain <element> or <attribute>. Is this hard to detect? Cheers, Makoto
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC