Re: Issue: TREX elements appearing in foreign elements (Re: ATREX<documentation> element)

[James Clark <jjc@jclark.com>]

I don't see any need to treat TREX elements in foreign elements
specially.  They are ignored just like any other elements.  It is very
easy to implement this. I can well imagine wanting an annotation that
includes a TREX element.  For example, I might want to have an
annotation on a URI reference that gives a pattern for the referenced
document.

Murata Makoto wrote:
> 
> Michael Fitzgerald wrote:
> 
> > I guess there is no reason why someone could not just use:
> >
> > <grammar xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> >   <element name="block">
> >     <xsd:annotation>
> >       <xsd:documentation>This element represents...</xsd:documentation>
> >     </xsd:annotation>
> >   </element>
> >  ...
> 
> Are elements of the TREX namespace allowed to appear in subelements
> of foreign namespaces?  For example:
> 
> <grammar xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>   <element name="block">
>     <xsd:annotation>
>       <xsd:documentation>This element represents...</xsd:documentation>
>        <element name="block">
>        </element name="block">
>     </xsd:annotation>
>   </element>
> 
> Some SAX programmers will fail to handle such patterns correctly.  I
> would propose to disallow such patterns, since I see no advantages
> in allowing them.
> 
> Cheers,
> 
> Makoto