-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Kay writes: > I think the rules are as follows: > > (a) if "form" isn't specified for an element or attribute, then the > formDefault attribute of the textually containing xs:schema element provides > the default. The formDefault attribute of an including/importing schema does > not affect the value. > > (b) if the resulting value is "qualified", then the element or attribute > name is qualified by the target namespace of the schema document. In the > case of a chameleon include, this is the targetNamespace of the including > schema document. Those both accord with my understanding. The idea is that elt/attrFormDefault is just an authoring convenience, and never has any different impact compared to putting "form='[value of lexically enclosing appropriate elt/attrformDefault]'" on every elt/attr declaration. ht - -- Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh Half-time member of W3C Team 2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFHfM3EkjnJixAXWBoRAnHNAJ0VNmGABNORaLbRJef8btcBbcFY9gCfTr54 uss/CD10DhkLMMyYa57dIPU= =en/U -----END PGP SIGNATURE-----Received on Thursday, 3 January 2008 11:58:05 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 3 January 2008 11:58:05 GMT