OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] "Non-Normative"

[ Lists Home | Date Index | Thread Index ]

And here's an example of Jonathan's first situation:

In the XML Schema specification there is a non-normative Primer (Part 0) as
well as normative parts 1 and 2 (Structures and Datatypes).

In 5.4 of the non-normative primer
(http://www.w3.org/TR/xmlschema-0/#import) it says (near the end of the
section) "The import elements themselves must appear as the first children
of the schema element. Furthermore, each namespace must be associated with a
prefix, using a standard namespace declaration, and that prefix is used to
qualify references to any schema components belonging to that namespace. "

However, as far as I can tell the normative document defining <import>
(http://www.w3.org/TR/xmlschema-1/#composition-schemaImport) does not make
any such statement about having to associate each namespace with a prefix
(thus allowing you to omit that association if no elements from the imported
namespace are actually referenced in the importing schema).

The normative document overrides the non-normative one.

Hugh Wallis

----- Original Message -----
From: "Jonathan Robie" <jonathan.robie@datadirect-technologies.com>
To: "Gregory Murphy" <Gregory.Murphy@eng.sun.com>; <xml-dev@lists.xml.org>
Sent: Wednesday, 19 February, 2003 9:20 AM
Subject: Re: [xml-dev] "Non-Normative"

At 02:38 PM 2/18/2003 -0800, Gregory Murphy wrote:

>The term "non-normative" is used frequently in XML 1.0 and in related
>specs. What a document means when it purports to be normative is clear to
>me, but when a section is labled "non-normative", I know what it is not,
>but not necessarily what it is.
>Can someone offer paraphrase what the specs mean when they use this term?

The reason we divide specs into "normative" and "non-normative" is so that
people know which source to trust if they disagree. For instance, a Working
Group might write a tutorial or a set of examples or a position paper that
contains an error which contradicts the normative specification. The
normative specification is the one you should trust.

Sometimes a Working Group will cover the same material in different ways in
two normative specs. When they do this, they are saying that these two
specifications *must* agree, and any disagreement between them is an error
which must be corrected by the Working Group.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS