Re: Why you should avoid Notation Declarations (byKohsuke Kawa
NOTATION isn't broken in W3C XML Schema, it's just grown up and uses namespaces, like all other named aspects of the spec. Things defined in W3C XML Schema schemas have names, which may be in namespaces. So if your schema document specifies a target namespace, the Notations you define in it will be in that namespace. So to refer to them, you have to use a qualified name. None of this should be surprising, it's the same for referring to types (that is, depending on the namespace declarations available, you may have to write xsi:type="xs:integer" or XS:type="xsd:integer" or . . . in your instances). XSV doesn't currently implement a check on things of type NOTATION, sorry, that's why you didn't get the error you should have. Personally, I don't think the problem NOTATIONs were designed to solve has gone away, and I think they still can be used to solve it. 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@i... URL: http://www.ltg.ed.ac.uk/~ht/ [mail really from me _always_ has this .sig -- mail without it is forged spam]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format