Re: [w3c sml] [minutes] 2009-03-30 SML Telecon

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sandy Gao writes:

> I think E17 [1] is the erratum Henry is referring to. Is it considered part
> of Namespace 2nd Edition? If not, then E17 isn't normative, and the
> mismatch between XML 5E and NS 2E still exists. And if E17 is considered as
> part of NS 2E, then following the same logic, wouldn't E9 [2] be considered
> as part of XML 4th edition, which makes 4E == 5E?
>
> This can only be explained if there is a difference between the status of
> E9 in XML 4E and that of E17 in NS 2E. What am I missing?

E9 to XML 4E is normative, because it has been incorporated into a
new, now approved, edition.  I supposed you could interpret the
process document as saying it remains advisory for 4E, but is
normative, by incorporation, in 5E.

E17 to XMLNS 2E is advisory, because it has not (yet) been
incorporated into a new, now approved, edition, or subjected to review
independently.

See 7.6.2 Classes of Changes to a Recommendation in the Process
Document [3] for a discussion of this.

It had not seemed necessary to the XML Core WG to do more than publish
the E17 erratum, since all implementations we are aware of use only
one NCName parser, and the advisory status was felt to be sufficient,
but if it makes a difference to IBM and/or Apache, we'll put it out
for review and make it normative ASAP.  We already have three
interoperable implementations (libxml2, one from Intel and an
MS-internal implementation for .NET).

ht

> [1] http://www.w3.org/XML/2006/xml-names-errata#NE17
> [2] http://www.w3.org/XML/xml-V10-4e-errata#E09
[3] http://www.w3.org/2005/10/Process-20051014/tr.html#correction-classes
- -- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
                         Half-time member of W3C Team
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, 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)

iD8DBQFJ1P/gkjnJixAXWBoRAma8AJ48KWEn7bDV2TIarfq7Ll53uMMQswCfSLNr
ICeRgk1MjuwDZ8sJGVI6/PI=
=t9vi
-----END PGP SIGNATURE-----

Received on Thursday, 2 April 2009 18:12:22 UTC