Re: Issue: <element name="foo"/> v <attribute name="foo"/>

James Clark wrote:

> Currently, RELAX NG allows
> 
>   <attribute name="foo"/>
> 
> (it matches an attribute named foo with any value), but doesn't allow
> 
>   <element name="foo"/>

Although the current syntax lacks symmetry, I like it.  (RELAX Core 
is exactly the same.)

If we prohibit <attribute name="foo"/>, our schema will be verbose.  
I don't want to allow <element name="foo"?> to have arbitrary attributes.

Cheers,

Makoto