W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2006

[Bug 3047] RQ-153 Schema 1.1 Namespace (xsd-1.1-namespace)

From: <bugzilla@wiggum.w3.org>
Date: Sat, 25 Mar 2006 18:04:02 +0000
CC:
To: www-xml-schema-comments@w3.org
Message-Id: <E1FND7K-00075P-V1@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3047

           Summary: RQ-153 Schema 1.1 Namespace (xsd-1.1-namespace)
           Product: XML Schema
           Version: 1.1 only
          Platform: Other
        OS/Version: All
            Status: NEW
          Keywords: unclassified
          Severity: normal
          Priority: P2
         Component: Structures: XSD Part 1
        AssignedTo: ht@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org


This issue was originally reported by David Ezell.

The XML Schema 1.1 specification must choose either to use the same
namespace as 1.0, or to use a different namespace, or to use more than
one namespace.  An explicit decision should be made.

In our general outline of compatibility goals for 1.1, the WG agreed
that we would avoid changes to the XML transfer syntax, in order that
XML Schema 1.0 processors can successfully process 1.1 schema
documents.  This seems to some to entail making no change in the
namespace.

At the same time, we also agreed that changes to the XML transfer
syntax might be made nevertheless, if they were necessary in order to
support versioning better.  This seems to some to imply that any final
decision on whether we will make breaking changes is still out; if we
do, some WG members will wish to entertain the possibility of changing
the namespace, or adding additional namespaces.

This topic was raised in the Working Group call of 1 July 2004
(http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2004Jul/nnnn.html),
and it was agreed to create a separate requirement to make it easier
to track.

The underlying issue applies to both Structures and Datatypes.  This
Bugzilla entry is for Structures.

According to the requirements document, this issue has not been classified.
Received on Saturday, 25 March 2006 18:04:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:50:05 UTC