[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Why you should avoid Notation Declarations (byKohsuke Kawa

• To: Razvan MIHAIU <mihaiu@m...>
• Subject: Re: Why you should avoid Notation Declarations (byKohsuke Kawaguchi)
• From: ht@i... (Henry S. Thompson)
• Date: Wed, 23 Feb 2005 10:11:38 +0000
• Cc: xml-dev@l...
• In-reply-to: <20050222083637.4d0sah84h8o44ss4@w...> (RazvanMIHAIU's message of "Tue, 22 Feb 2005 08:36:37 +0200")
• References: <20050222083637.4d0sah84h8o44ss4@w...>
• User-agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security ThroughObscurity, linux)

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]

• Follow-Ups:
  • Re: Why you should avoid Notation Declarations (by Kohsuke Kawaguchi)
    • From: "G. Ken Holman" <gkholman@C...>
  • Re: Why you should avoid Notation Declarations (by KohsukeKawaguchi)
    • From: Elliotte Harold <elharo@m...>

• References:
  • Why you should avoid Notation Declarations (by Kohsuke Kawaguchi)
    • From: Razvan MIHAIU <mihaiu@m...>

• Prev by Date: Re: schema keyref to other schema.
• Next by Date: Re: schema keyref to other schema.
• Previous by thread: Why you should avoid Notation Declarations (by Kohsuke Kawaguchi)
• Next by thread: Re: Why you should avoid Notation Declarations (by KohsukeKawaguchi)
• Index(es):
  • Date
  • Thread