xml-dev - Re: XML-Schemas: purpose of elementFormDefault?

[ht@cogsci.ed.ac.uk (Henry S. Thompson)]

Sorry for continuing confusion.

Elements in instances covered by local declarations are
required to be _unqualified_, if the 'form' attribute of that
declaration is 'unqualified', or absent and the 'elementFormDefault'
attribute higher up is 'unqualified'.

Elements in instances covered by local declarations are
required to be _qualified_, if the 'form' attribute of that
declaration is 'qualified', or absent and the 'elementFormDefault'
attribute higher up is 'qualified'.

'Qualified' and 'unqualified' are _not_ the same as 'prefixed' and
'unprefixed' (for elements).  Your example document had _unprefixed_,
_qualified_ names for its elements (because it had a default namespace 
declaration).

So your schema needs to have form='qualified', or
elementFormDefault='qualified', in order to schema-validate your
instance.

There is indeed a misprint in the primer: as I hope the context around 
it makes clear, the relevant sentence in section 3.1 [1] should read

  "In po1.xsd we globally specify the qualification of elements and
  attributes by setting the values of both elementFormDefault and
  attributeFormDefault to unqualified."

Hope this helps.

ht
-- 
  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************