xsv bug? Nested attributeGroup behavior?

Given the following schema

<schema xmlns='http://www.w3.org/1999/XMLSchema'
        targetNamespace='http://www.nwalsh.com/foo'
        xmlns:foo='http://www.nwalsh.com/foo'
        elementFormDefault='qualified'>

<attributeGroup name='role.att'>
  <attribute name='role' type='NMTOKEN'/>
</attributeGroup>

<attributeGroup name='common.att'>
  <attribute name='id' type='ID'/>
  <attributeGroup ref='foo:role.att'/>
</attributeGroup>

<complexType name='doc'>
  <choice minOccurs='1' maxOccurs='unbounded'>
    <element ref='foo:p'/>
  </choice>
</complexType>

<complexType name='p' content='mixed'>
  <attributeGroup ref='foo:common.att'/>
</complexType>

<element name='doc' type='foo:doc'/>
<element name='p' type='foo:p'/>

</schema>

I'm surprised that the following document does not validate:

<doc xmlns='http://www.nwalsh.com/foo'>
<p role='test'>foo</p>
</doc>

My intent was that id and role should be common attributes. My reading
of 4.3.4 seems to support my intent, but xsv complains that {None}:role
is an undeclared attribute on 'p'. Am I missing something?

                                        Be seeing you,
                                          norm

-- 
Norman Walsh <ndw@nwalsh.com> | Life always comes to a bad end.--Marcel
http://nwalsh.com/            | Aym\'e

Received on Sunday, 20 August 2000 16:00:49 UTC