You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
864 lines
34 KiB
864 lines
34 KiB
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml">
|
|
<head>
|
|
<title>XML Schema Working Group Charter</title>
|
|
<link href="../../../StyleSheets/base.css" type="text/css" rel="stylesheet" />
|
|
<style type="text/css">
|
|
.rfc2119 {
|
|
text-transform: lowercase;
|
|
font-weight: bold
|
|
}
|
|
</style>
|
|
<style type="text/css" xml:space="preserve">
|
|
ins { background-color: #DDF; text-decoration: underline;}
|
|
</style>
|
|
</head>
|
|
<!--* to do
|
|
* revise dependency descriptions; these are out of date
|
|
*-->
|
|
<body>
|
|
<p>
|
|
<a href="/">
|
|
<img style="border:0" src="/Icons/w3c_home.gif" alt="W3C" height="48" width="72"/></a>
|
|
| <a href="/Architecture/" rel="in-domain">
|
|
<img style="border:0" src="/Icons/arch" alt="Architecture Domain" height="48" width="212"/></a> | <a href="../../../XML">XML</a> |
|
|
<a href="/Member/">Member-Confidential!</a></p>
|
|
|
|
<div>
|
|
<h1>Charter of the XML Schema Working Group</h1>
|
|
|
|
<h3>[June 2004]</h3>
|
|
|
|
<p style="font-size: small; font-style: italic">
|
|
David Ezell, chair<br />
|
|
C. M. Sperberg-McQueen and Henry Thompson, Team contacts<br/>
|
|
$Revision: 1.52 $ of $Date: 2004/06/16 18:55:46 $ by $Author: plehegar $
|
|
</p>
|
|
<blockquote>
|
|
<p>
|
|
The <a href="../../../XML/Group/Schemas.html">XML Schema Working Group</a> is a
|
|
Working Group of the W3C and follows the working group process
|
|
described in the <a href="/Consortium/Process/">W3C Process
|
|
Document</a>. Except as outlined elsewhere in this charter, the
|
|
Working Group follows the <a href="xml-common-proc.html">Common
|
|
Procedures for XML Working Groups</a>.
|
|
<!--*
|
|
, as elaborated in the <a href="/1999/05/xmlp436.html">XML
|
|
Activity Membership and Decision Process</a> (except as outlined
|
|
below).
|
|
*--></p>
|
|
<p>This is the
|
|
charter for this Working Group.
|
|
It extends and supersedes the Working Group's
|
|
<a href="http://www.w3.org/2001/12/xmlbp/xml-schema-wg-charter.html">previous charter</a>.
|
|
<!--* <a href="http://www.w3.org/XML/Group/2001/04/xmlschema-charter.html"
|
|
>previous charter</a>.
|
|
*-->
|
|
<!--* [<em>N.B. Text which must be
|
|
deleted or modified at the time this charter goes to the Advisory
|
|
Committee, or which otherwise needs to be readily findable for
|
|
revisions in the meantime (such as dates) is marked by square
|
|
brackets.</em>]</p> *-->
|
|
</p>
|
|
</blockquote>
|
|
</div>
|
|
<hr/>
|
|
<div>
|
|
<ol>
|
|
<li><a href="#xml-scope">Scope</a></li>
|
|
<li><a href="#Deliverables">Deliverables and Schedule</a></li>
|
|
<li><a href="#x-rel">Relationship with Other Activities</a></li>
|
|
<li><a href="#WGmembership">Working Group participation</a></li>
|
|
<li><a href="#AEN117">Communication</a></li>
|
|
<li><a href="#Confident">Confidentiality</a></li>
|
|
<li><a href="#AEN124">Face-to-Face Meetings</a></li>
|
|
<li><a href="#pp">Patent Policy</a></li>
|
|
</ol>
|
|
</div>
|
|
<hr/>
|
|
|
|
<div>
|
|
<h2>
|
|
1. <a name="xml-scope">Scope</a>
|
|
</h2>
|
|
|
|
<p>The XML specification defines the concepts of
|
|
<em>well-formedness</em> and <em>validity</em>; the former
|
|
characteristic is very simple to check, while the latter requires more
|
|
work to check, and allows the user to define more powerful constraints
|
|
on document structure. XML validity requires that a document follow
|
|
the constraints expressed in its <em>document type definition</em>,
|
|
which provides the rough equivalent of a context-free grammar for a
|
|
document type.</p>
|
|
|
|
<p>In some contexts, there is need for constraints tighter than,
|
|
looser than, or simply different from those which can be expressed
|
|
using document type definitions as defined in XML. There is also a
|
|
widespread desire for an XML-based syntax for expressing constraints
|
|
on document types, in order to allow tools for XML documents to be
|
|
used on the constraint specifications.</p>
|
|
|
|
<p>Using a term borrowed from database terminology, the expression of
|
|
constraints on a document type is called (in this document, at least)
|
|
a <em>schema</em>. (Note that the term <em>schema</em> has two
|
|
plurals, <em>schemas</em> and <em>schemata</em>; we use the
|
|
former.)</p>
|
|
|
|
<p>The XML Schema working group will maintain and revise the XML
|
|
Schema specification developed beginning in 1998 and published as a
|
|
W3C Recommendation on 2 May 2001. The XML Schema specification
|
|
addresses several topics relevant to users of XML:</p>
|
|
|
|
<ul>
|
|
<li>
|
|
<b><a name="x-s-pdt">primitive data typing</a></b>: XML Schema defines
|
|
a type system for integers, dates, and the like, based on experience
|
|
with SQL, Java primitives, etc.</li>
|
|
|
|
<li><b><a name="x-s-schemas">structural constraints</a></b>: XML
|
|
Schema provides a mechanism roughly analogous to DTDs for constraining
|
|
document structure (order, occurrence of elements, attributes). XML
|
|
Schema differs from DTDs in expressing these constraints in the form
|
|
of an XML document, rather than in a special-purpose ad hoc
|
|
notation. Unlike DTDs, which contain declarations both for the logical
|
|
structure of elements and attributes, and for the physical structure
|
|
of entities, XML Schema provides declarations only for constraining
|
|
elements and attributes; <em>entity declarations continue to use DTD
|
|
syntax</em>. In addition to DTD-like functionality, XML Schema:
|
|
<ul>
|
|
<li>is integrated with namespaces;</li>
|
|
<li>allows incomplete constraints on the content of an element type
|
|
in the form of wildcards, so-called ‘black box’ validation, and
|
|
so-called ‘white box’ validation;</li>
|
|
<li>is integrated with primitive data types;</li>
|
|
<li>defines inheritance for datatypes;</li>
|
|
<li>provides various hooks for safe adaptation and reuse of
|
|
schemas.</li>
|
|
</ul></li>
|
|
|
|
<li><b>conformance</b>: XML Schema defines the relation of schemas to
|
|
XML document instances and specifies the obligations of schema-aware
|
|
processors. </li>
|
|
|
|
</ul>
|
|
|
|
<h3>Goals</h3>
|
|
<p>The goals of the work group in the period described by this
|
|
charter are <!--* two- *--><!--* four *-->five-fold:</p>
|
|
<ul>
|
|
|
|
<li>to prepare a version 1.1 of the XML Schema Recommendation,
|
|
which corrects known errors and may make modest improvements to
|
|
the language. Function or syntax incompatible with XML Schema 1.0
|
|
will be adopted only if the resulting improvements compellingly
|
|
justify the loss of interoperability with existing systems and
|
|
documentation.
|
|
Some substantive changes may be made in the interests of aligning
|
|
version 1.1 with the needs of the XML Query 1.0, XPath 2.0, and
|
|
XSLT 2.0 family of specifications and with XML 1.1. Request for
|
|
substantive changes may also come from other groups.
|
|
<!--* do we want this compatibility clause? *-->
|
|
</li>
|
|
|
|
<li>to provide continuing maintenance and support for
|
|
XML Schema 1.0 and future versions of that specification.
|
|
The Working Group has published and will maintain
|
|
an Errata document containing corrections of identified errors
|
|
and clarifications of points which experience shows are
|
|
obscure to careful readers. Corrected re-editions of
|
|
XML Schema 1.0 and future versions are also expected.
|
|
We also plan
|
|
to complete the document <cite>XML Schema: Formal Description</cite>,
|
|
which provides a more formal treatment of schema-based type assignment
|
|
and validation <!--* in terms of a Gentzen calculus *--></li>
|
|
<li>to complete the document <a href="http://www.w3.org/TR/xmlschema-ref/"><cite>XML Schema: Component
|
|
Designators</cite></a></li>
|
|
|
|
<li>as needed and feasible, to clarify related problem areas, and do
|
|
technical work leading possibly to Recommendations, possibly to Notes,
|
|
and possibly to the determination that no publication is necessary, on
|
|
technical questions connected with the design, implementation, use,
|
|
and uptake of the XML Schema specification; some problem areas
|
|
of concern are listed below.
|
|
</li>
|
|
|
|
<li>to cooperate with other W3C working groups and assist them in
|
|
exploiting XML Schema for their work and adding schema-awareness
|
|
to their specifications where appropriate; this will include
|
|
work on the problem of schema-annotation and the problem of mapping
|
|
from the XML vocabularies defined by a schema into target data models
|
|
</li>
|
|
|
|
</ul>
|
|
|
|
<h3>Additional areas of work</h3>
|
|
|
|
<p>In addition to work directly related to XML Schema 1.1,
|
|
technical areas relevant to the work under this charter
|
|
include:</p>
|
|
<ul>
|
|
<!--* <li>the application-programming interface (API)
|
|
for the post-schema-validation (PSV) information set; this
|
|
work is undertaken in response to comments on the Last-Call
|
|
draft of XML Schema, and will be performed in consultation with the DOM WG.
|
|
It is expected to be an extension of their generic interface to
|
|
content models and related information</li> *-->
|
|
<!--*
|
|
<li>useful ways of handling the functionality provided in XML 1.0
|
|
DTDs by entities (with special reference to the use of entities to
|
|
provide names for special characters); this remains a topic of
|
|
discussion.
|
|
(although it currently appears likely that any new
|
|
developments in this area are likely to be in the
|
|
XML specification itself, or in a new specification, rather
|
|
than by new additions to XML Schema)</li>
|
|
*-->
|
|
<li>the systematic development of test cases for XML Schema</li>
|
|
<li>the framework and interoperability rules which should govern evolution
|
|
of the XML Schema language</li>
|
|
<li>interoperability of schemas, data governed by them, and software, as
|
|
user vocabularies evolve</li>
|
|
<li>provision of a sample library of common types, for illustration
|
|
of the construction of type libraries using XML Schema and, as
|
|
appropriate, for reference from schemas for W3C specifications</li>
|
|
<li>definition of operators on XML-Schema types, in collaboration
|
|
with XML Query and XSL. (This work is currently driven by the
|
|
other two Working Groups; XML Schema participates in order to provide
|
|
expertise and help avert problems.)</li>
|
|
<!--*
|
|
<li>the study of various proposals for new architectural approaches
|
|
to schema definition and schema validation, with an eye to their
|
|
potential inclusion in future versions of XML Schema; these proposals
|
|
include but are not limited to:<ul>
|
|
<li>an even sharper separation between the level of abstract schema
|
|
components and the XML transfer-syntax level than is present in
|
|
XML Schema 1.0, possibly including separation of the abstract and
|
|
concrete levels into separate specifications</li>
|
|
<li>possible use of multiple transfer syntaxes which 'compile' to
|
|
the same set of abstract components</li>
|
|
<li>multiple inheritance</li>
|
|
<li>abstract simple types</li>
|
|
<li>co-constraints between attributes and content, or between attributes
|
|
and other attributes</li>
|
|
<li>various proposals postponed from the work on XML Schema 1.0</li>
|
|
</ul>
|
|
</li>
|
|
*-->
|
|
<li>use cases and requirements for a possible XML Schema 2.0</li>
|
|
<li>schema annotation and the specification of mappings which
|
|
allow software to translate data from XML document instances which
|
|
conform to a given schema into other formalisms or data models, such
|
|
as application-specific data structures, generic data structures (e.g.
|
|
relational tables), the entity-relationship model, and RDF. This
|
|
work follows on from the discussions reported in the <a href="http://www.w3.org/TR/schema-arch">Cambridge
|
|
Communiqué</a> of 1999, with the aim of showing how the
|
|
goals described there can be achieved.</li>
|
|
<li>the formalization of XML Schema in a manner suitable for use
|
|
by XML Query and others</li>
|
|
<li>interoperability with other schema languages such as RELAX-NG
|
|
and Schematron</li>
|
|
</ul>
|
|
|
|
<h3>Parallelism of work on 1.1 and preliminary discussion of 2.0</h3>
|
|
|
|
<p>The XML Schema Working Group has repeatedly experienced tension between
|
|
the desire to explore some proposal for a relatively major change in
|
|
the design of the XML Schema language, and the desire to have a
|
|
non-proprietary specification available for use as soon as possible.
|
|
In order to allow adequate time for consideration of possible
|
|
major changes in approach,
|
|
<!--*
|
|
we propose to begin work immediately on XML Schema 2.0, while also
|
|
working, in parallel, on XML Schema 1.1.
|
|
*-->
|
|
the Working Group may (time permitting) do technical work on proposals intended
|
|
for future versions of XML Schema (such as those listed above)
|
|
in parallel with its work on XML Schema 1.1.
|
|
</p>
|
|
</div>
|
|
|
|
<div>
|
|
<h2>2. <a name="Deliverables">Deliverables, Milestones, and Schedule</a></h2>
|
|
<h3>Deliverables</h3>
|
|
<p>The XML Schema Working Group has three main deliverables:</p>
|
|
<ul>
|
|
|
|
<li>XML Schema version 1.1; this will be a maintenance release
|
|
of the spec. It may differ from version 1.0 in incorporating:<ul>
|
|
<li>changes necessary to align the specification with the data model
|
|
and type logic of XPath 2.0, XQuery 1.0, XSLT 2.0 and related
|
|
specifications; these will include<ul>
|
|
<li>definition of duration types with total orders</li>
|
|
<li>addition of an <i>anyAtomic</i> type</li>
|
|
<li>revision of the treatment of time zones in date/time types</li>
|
|
<li>revision of the <i>float</i> and <i>double</i> types to distinguish
|
|
positive and negative zero values</li>
|
|
<li>reformulation of the definition of complex type restriction to remove
|
|
anomalies</li>
|
|
</ul>
|
|
</li>
|
|
<li>changes necessary to provide better support for versioning
|
|
of schemas</li>
|
|
<li>fixes for errors in version 1.0</li>
|
|
<li>clearer (and if possible briefer) exposition</li>
|
|
<!--* <li>improvements to the XML transfer syntax, to improve
|
|
usability based on reports from users and implementors</li> *-->
|
|
<li>simplification and regularization of the
|
|
abstract component level, where changes can be made without
|
|
inconvenience to users of existing schemas or developers of existing
|
|
implementations</li>
|
|
<li>the definition of a limited-precision decimal type</li>
|
|
</ul>
|
|
</li>
|
|
<li>Errata list for XML Schema version 1.0, with new editions
|
|
of the 1.0 specification as needed</li>
|
|
<li>Schema Component Designators; this specification describes
|
|
a syntax for referring to schema components</li>
|
|
<!--*
|
|
<li>XML Schema version 2.0; this will be a revision, potentially
|
|
a major revision, of the XML 1.0 language. It will be based on
|
|
experience implementing and using XML Schema 1.0 and other schema
|
|
languages, and on the consideration of various proposals which
|
|
were considered during the development of XML Schema 1.0 and
|
|
then postponed for consideration in connection with some later
|
|
version of the specification. XML Schema 2.0 may extend the
|
|
functionality of XML Schema 1.0, and may provide for multiple
|
|
concrete syntaxes for schemas.</li>
|
|
*-->
|
|
</ul>
|
|
<p>In addition, there are several other deliverables:</p><ul>
|
|
<li>preliminary work on XML Schema 2.0: use cases, usage scenarios,
|
|
and requirements;
|
|
<!--*
|
|
and (if possible) working drafts;
|
|
*-->
|
|
it is not expected that XML Schema 2.0 will be
|
|
completed within this charter period</li>
|
|
<li>a collection of test cases for XML Schema, together with a
|
|
list of other XML Schema test suites and a report on coverage
|
|
<!--*
|
|
the procedure by which the WG expects to maintain the
|
|
test collection has been <a href="">documented</a> *-->
|
|
</li>
|
|
<li>possible documents stemming from the various ‘related problem areas’
|
|
mentioned above:<ul>
|
|
<li>a formal description of XML Schema</li>
|
|
<!--* <li>entities (especially for special characters)</li> *-->
|
|
<li>sample library of common types</li>
|
|
<li>work on schema annotation</li>
|
|
<li>working papers on other topics</li>
|
|
</ul></li>
|
|
</ul>
|
|
|
|
<h3>Milestones and schedule</h3>
|
|
<p>Listed here are the major expected milestones for the Working Group's
|
|
deliverables; for a summary of the current target dates
|
|
for these milestones, see the
|
|
<a href="../../../XML/Group/Schemas">XML Schema Working Group home page</a>.</p>
|
|
|
|
<p>Milestones for XML Schema 1.1:</p>
|
|
<ul>
|
|
<li>first public working draft</li>
|
|
<li>revision of 1.1 Requirements document</li>
|
|
<li>second public working draft</li>
|
|
<li>last-call working draft</li>
|
|
<li>Candidate Recommendation</li>
|
|
<li>Proposed Recommendation</li>
|
|
<li>Recommendation</li>
|
|
</ul>
|
|
<p>Milestones for XML Schema 1.0 errata:</p>
|
|
<ul>
|
|
<li>regular re-publication of errata lists with (non-normative) corrections</li>
|
|
<li>periodic re-publication of XML Schema 1.0, integrating corrections</li>
|
|
</ul>
|
|
<p>Milestones for XML Schema: Component Designators:</p>
|
|
<ul>
|
|
<li>revised working draft(s)</li>
|
|
<li>last-call working draft</li>
|
|
<li>Candidate Recommendation</li>
|
|
<li>Proposed Recommendation</li>
|
|
<li>Recommendation</li>
|
|
</ul>
|
|
<p>Milestones for work on XML Schema 2.0:</p>
|
|
<ul>
|
|
<li>first working draft(s) of use cases and requirements document(s)</li>
|
|
<li>stable use cases and requirements document(s)</li>
|
|
<li>possible working papers on high-level design and architecture principles
|
|
for XML Schema 2.0</li>
|
|
<li>decision on whether to proceed with XML Schema 2.0</li>
|
|
<li>(if appropriate) first public working draft</li>
|
|
</ul>
|
|
<p>Milestones for work on XML Schema: Formal Description:</p>
|
|
<ul>
|
|
<li>revised working draft(s)</li>
|
|
<li>last-call working draft</li>
|
|
<li>Candidate Recommendation</li>
|
|
<li>Proposed Recommendation</li>
|
|
<li>Recommendation</li>
|
|
</ul>
|
|
<p>Milestones for work on XML Schema test collections:</p>
|
|
<ul>
|
|
<li>agreement on disclosure statement to be made by test contributors</li>
|
|
<li>creation of collection of donated tests</li>
|
|
<li>public release of test collection</li>
|
|
<li>period integration of new tests, new releases of test collection</li>
|
|
<li>creation of collection of test results</li>
|
|
<li>collection of information about other available test collections</li>
|
|
<li>report on coverage of test collection(s)</li>
|
|
</ul>
|
|
|
|
<!--*
|
|
<p>
|
|
The schedule given below is subject to revision due to editorial
|
|
needs and external scheduling issues; updates will be negotiated
|
|
with the related groups and recorded on
|
|
the <a href="../../Schemas">XML Schema WG home page</a>.</p>
|
|
*-->
|
|
|
|
<p>
|
|
Note that public working drafts will be made available at least once every
|
|
three months, in accordance with the
|
|
<a href="/Consortium/Process/#GroupsWG">W3C Process</a>.</p>
|
|
|
|
<p>Expected schedule:</p>
|
|
<ul>
|
|
<li>Q3 2004: first public working draft of XML Schema 1.1</li>
|
|
<li>Q3 2004: revised XML Schema 1.1 Requirements document</li>
|
|
<li>Q3 2004: public working draft of XML Schema: Component Designators</li>
|
|
<li>Q3 2004: first public release of new XML Schema test collection
|
|
(periodic republication as new contributions warrant)</li>
|
|
<!--* <li>September 2004: revised working draft of XML Schema: Formal Description</li> *-->
|
|
<li>Q4 2004: public working draft of XML Schema 1.1</li>
|
|
<li>Q4 2004: last-call working draft of XML Schema: Component Designators</li>
|
|
<li>Q4 2004: Candidate Recommendation draft of XML Schema: Component Designators</li>
|
|
<li>Q1 2005: last-call working draft of XML Schema 1.1</li>
|
|
<li>Q1 2005: report on existing test collections, coverage</li>
|
|
<li>Q1 2005: Proposed Recommendation draft of XML Schema: Component Designators</li>
|
|
<li>Q1 2005: Candidate Recommendation draft of XML Schema 1.1</li>
|
|
<!--* <li>Q1 2005: last-call working draft of XML Schema: Formal Description</li> *-->
|
|
<li>Q2 2005: XML Schema: Component Designators Recommendation</li>
|
|
<li>Q2 2005: first public working draft of XML Schema 2.0 use cases
|
|
and requirements</li>
|
|
<li>Q3 2005: Proposed Recommendation draft of XML Schema 1.1</li>
|
|
<!--* <li>Q3 2005: Candidate Recommendation draft of XML Schema: Formal Description</li> *-->
|
|
<li>Q3 2005: XML Schema 1.1 Recommendation</li>
|
|
<li>Q4 2005: decision on whether to proceed with XML Schema 2.0
|
|
(and possible request for charter alteration)</li>
|
|
<!--* <li>Q4 2005: Proposed Recommendation draft of XML Schema: Formal Description</li>
|
|
<li>Q4 2005: XML Schema: Formal Description Recommendation</li>
|
|
*-->
|
|
</ul>
|
|
|
|
<p>For details of dates and locations of face to face meetings,
|
|
see the <a href="../../../XML/Group/Schemas.html">Working Group home page</a>.</p>
|
|
|
|
<p>
|
|
The expiration date of this charter is 30 June 2006.
|
|
</p>
|
|
</div>
|
|
|
|
<div>
|
|
<h2>
|
|
3. <a name="x-rel">Relationship with Other Activities</a>
|
|
</h2>
|
|
<p>
|
|
XML has become a strategic technology in W3C and elsewhere. The deliverable
|
|
of the XML Schema Working Group must satisfy the dependencies from other W3C Working
|
|
Groups. Some dependencies
|
|
to and from other W3C Working Groups will require close cooperation during
|
|
the development process; the requirements posed for the Schema work by these
|
|
Working Groups may change during the development process, which means the interdependency
|
|
of the Schema work with these Working Groups must be managed actively: <!-- awk -->
|
|
<!--* our home page should have a statement of the current
|
|
* state of each of these relationships.
|
|
*--></p>
|
|
<dl>
|
|
<dt>
|
|
<a href="http://www.w3.org/XML/Group/Query">XML Query Working Group</a></dt>
|
|
<dd>
|
|
The XML Query Working Group expects to use schema-related information in the
|
|
processing of queries; we will discuss points of mutual interest in an
|
|
effort to ensure that XML Schema provides the information Query
|
|
needs. In particular, the XML Query Working Group has expressed particular
|
|
interest
|
|
<!--* in the work on a formal description of XML Schema, and *-->
|
|
in the definition of the post-schema-validation infoset (PSVI).
|
|
The XML Schema Working Group will continue to collaborate with XML Query and XSL in
|
|
work on operators for XML Schema datatypes and (as appropriate) on
|
|
the integration of support for the XML Schema type inventory
|
|
into future versions of XPath.
|
|
An important goal of XML Schema 1.1 will be to align its type
|
|
system more fully with the needs of the XML Query language
|
|
and related specifications.
|
|
Work on XQuery 1.1, updates, and full-text search may raise
|
|
schema-related problems, and the Working Groups will cooperate
|
|
in resolving them.
|
|
</dd>
|
|
|
|
<dt>
|
|
<a href="http://www.w3.org/Style/XSL/Group/">XSL Working Group</a></dt>
|
|
<dd>
|
|
In collaboration with the XML Query Working Group, the XSL Working Group expects to
|
|
make future versions of XPath and XSLT support schema-related
|
|
information, in particular types.
|
|
The XML Schema Working Group will continue to collaborate with XML Query and XSL in
|
|
work on operators for XML Schema datatypes and (as appropriate) on
|
|
the integration of support for the XML Schema type inventory
|
|
into future versions of XPath.
|
|
An important goal of XML Schema 1.1 will be to align its type
|
|
system more fully with the needs of the XSLT and XPath 2.0 languages
|
|
and related specifications.
|
|
</dd>
|
|
<!--*
|
|
<dt>
|
|
<a href="http://www.w3.org/DOM/Group/">DOM WG</a></dt>
|
|
<dd>
|
|
The DOM WG may wish to provide access to details of the data types and
|
|
structural relationships (e.g. inheritance) among element and
|
|
attribute types for schema-validated documents. We expect to work
|
|
together with the DOM both on their definition of a generic interface
|
|
to DTD- and schema-related information, and on our possible definition
|
|
of an API to XML-Schema information and the PSVI.</dd>
|
|
*-->
|
|
<!--*
|
|
<dt>
|
|
<a href="http://www.w3.org/RDF/Group/Schema/">RDF Schemas</a></dt>
|
|
<dd>
|
|
It is a goal of the RDF Schema working group to integrate
|
|
<a href="#x-s-pdt">primitive datatypes</a>. The activities of the Schema
|
|
WG will be coordinated with those of the RDF WG at the requirements level,
|
|
with additional coordination as appropriate.</dd>
|
|
*-->
|
|
<dt>HTML and XForms Working Groups</dt>
|
|
<dd>
|
|
It is a goal of the XML Schema work to ensure that the
|
|
schema language we define will suffice for the requirements of current
|
|
and future versions of the HTML specification and XForms.
|
|
<!--*
|
|
In particular, this includes solving the problem of references to
|
|
named characters.
|
|
*-->
|
|
</dd>
|
|
|
|
<dt>
|
|
<a href="http://www.w3.org/XML/Group/Core">XML Core Working Group</a></dt>
|
|
<dd>
|
|
The XML Schema work defines methods for specifying constraints on XML
|
|
documents; those constraints should apply to objects and properties identified
|
|
as significant by the XML Information Set specification.
|
|
<!--*
|
|
When XML Schema specifications
|
|
are written as XML instances, it is possible to explain and process
|
|
the schema specification without recourse to information not included in
|
|
the XML information set.
|
|
*-->
|
|
The XML structural schema specification
|
|
<!--* what is the XML structural schema specification? where defined? *-->
|
|
uses namespaces to combine
|
|
fragmentary structural specifications; it also defines schema-validation
|
|
for documents using namespaces. (In short: the XML Schema work is
|
|
namespace-aware.)
|
|
</dd>
|
|
<!--*
|
|
<dt>
|
|
<a href="http://www.w3.org/">XForms WG</a></dt>
|
|
<dd>
|
|
The XForms WG is responsible for a datatype-aware replacement for HTML
|
|
forms; we will discuss points of mutual interest in order to ensure
|
|
the alignment of the two specs and the utility of XML Schema for the
|
|
work of XForms.
|
|
</dd>
|
|
*-->
|
|
<dt>
|
|
<a href="http://www.w3.org/International/Group/">Internationalization Working Group</a></dt>
|
|
<dd>
|
|
Since XML Schema is expected to be an important tool for the definition
|
|
of markup vocabularies, it may have follow-on effects on a larger number
|
|
of people than create XML Schema documents directly.
|
|
The XML Schema Working Group and the Internationalization Working Group will work together
|
|
to clarify and resolve internationalization and localization issues
|
|
in XML Schema, and will jointly ensure that it satisfies W3C goals for
|
|
international access to the Web.</dd>
|
|
<dt>
|
|
<a href="http://www.w3.org/2001/sw/RDFCore/">RDF Core Working Group</a></dt>
|
|
<dd>
|
|
The RDF Core Working Group is preparing a new version of RDF Schema, which will
|
|
use and build upon XML Schema datatypes. The RDF Core Working Group is also
|
|
chartered to "provide an account of the relationship between RDF
|
|
and the XML family of technologies (particularly Schemas ...)".
|
|
RDF has also expressed particular interest in the problem of
|
|
schema annotation and will be asked to provide feedback on the work
|
|
the XML Schema Working Group does in that area.
|
|
</dd>
|
|
<dt>
|
|
<a href="http://www.w3.org/2002/ws/">Web Services Working Groups</a></dt>
|
|
<dd>
|
|
The XML Protocol Working Group and the Web Services Description Working Group in the Web
|
|
Services Activity use XML Schema extensively. The Web Services
|
|
Choreography Working Group is working in an area which may be
|
|
expected to raise complex questions for type systems and schemas.
|
|
The XML Schema Working Group will
|
|
ensure that
|
|
the schema language is sufficient to meet the requirements of deliverables
|
|
from these Web Services Working Groups. The XML Schema Working Group will also discuss points of
|
|
mutual interest and will review deliverables from the Web Services
|
|
Working Groups and provide them with feedback.
|
|
</dd>
|
|
</dl>
|
|
<p>
|
|
Some other work groups should be mentioned here; there are no requirements
|
|
for co-development of features with these Working Groups, but there are points of contact
|
|
between their work and that of this Working Group, and thus logical dependency between
|
|
their deliverables and those of this Working Group. Requirements from these Working Groups are
|
|
expected to be well suited for communication via documents.</p>
|
|
<dl>
|
|
<dt>
|
|
<a href="http://www.w3.org/WAI/PF/Group/">WAI Protocols & Formats Working Group</a></dt>
|
|
<dd>
|
|
Reuse of common constructs greatly facilitates accessibility; the WAI PF
|
|
Working Group will review work on structural schemas to be sure cost/benefit design
|
|
decisions are informed of the benefits of accessibility.</dd>
|
|
<!--*
|
|
<dt>
|
|
<a href="http://www.w3.org/XML/Group/Linking.html">XML Linking</a></dt>
|
|
<dd>
|
|
The XML Linking and Schema WGs will consult with each other on the question
|
|
of declaring element types and attributes as links or addresses.</dd>
|
|
*-->
|
|
<!--* they better hurry up, Linking WG is no longer active! should this
|
|
* item be struck?
|
|
*-->
|
|
|
|
<!--*
|
|
* <dt>
|
|
* <a href="http://www.w3.org/">XML Binary Interchange WG</a>
|
|
* </dt>
|
|
* <dd>
|
|
* A Binary Interchange WG may be chartered to produce requirements or
|
|
* specifications concerned with transmitting binary representations of
|
|
* W3C XML Schema documents; the XML Schema WG may need to review these
|
|
* and provide feedback.
|
|
* </dd>
|
|
*-->
|
|
</dl>
|
|
<!--*
|
|
<p>
|
|
Formal liaison between the XML Schema Working Group and other W3C working
|
|
groups, including the other XML working groups and the WAI (Web Accessibility
|
|
Initiative) group, as well as organizations outside of the W3C, shall be
|
|
accomplished by the exchange of documents (requirements, reviews, etc.)
|
|
transmitted through the XML Coordination Group. Any memorandum or inquiry
|
|
directed to another group shall be submitted by the Chair of the XML Schema
|
|
WG to the Chair of the XML CG, who shall in turn, after consultation with
|
|
the CG, either transmit it unchanged to the appropriate body, transmit it
|
|
with modifications, or return it to the originating WG with comments. Informal
|
|
communication between the XML Schema Working Group and other XML working
|
|
groups shall take place in the <tt>
|
|
<a href="mailto:w3c-xml-plenary@w3.org">w3c-xml-plenary@w3.org</a></tt> mailing
|
|
list.</p>
|
|
*-->
|
|
|
|
<p>
|
|
Formal liaison between the XML Schema Working Group and other W3C
|
|
Working Groups, including the other XML Working Groups and the WAI
|
|
(Web Accessibility Initiative) group, as well as organizations outside
|
|
of the W3C, shall normally be accomplished by the exchange of
|
|
documents (requirements, reviews, etc.) transmitted through the XML
|
|
Coordination Group.</p>
|
|
|
|
<p>
|
|
When approved by the XML Coordination Group, liaison with other W3C
|
|
Working Groups can be accomplished through direct exchange of
|
|
documents or by joint task forces. It is
|
|
expected that this be required for liaison with at least the XML
|
|
Query, XSL, and Internationalization Working Groups, and, where
|
|
appropriate, direct liaison with task forces such as the
|
|
<!--* succinctly named *-->
|
|
Semantic Web Best Practicies Working Group XML Schema Datatypes
|
|
and Semantic Web Task Force.
|
|
</p>
|
|
</div>
|
|
|
|
<div>
|
|
<h2>
|
|
4. <a name="WGmembership">Working Group participation</a>
|
|
</h2>
|
|
<p>
|
|
To be successful, we expect the XML Schema Working Group to have 15 or more
|
|
active participants for its duration.
|
|
<!--*
|
|
<p>
|
|
To become a member of the XML Schema Working Group, a representative of a
|
|
W3C member organization must be nominated by their Advisory Committee
|
|
Representative. In addition, every participant
|
|
must disclose all the IPR claims relevant to the XML Schema working group
|
|
according to the <a href="http://www.w3.org/Consortium/Process/#ipr">W3C's
|
|
IPR Policy</a>.</p>
|
|
*-->
|
|
Participation is expected to
|
|
consume one to two days per week of each participant's time, though the time
|
|
commitment for the chair and editors may be higher.
|
|
<a href="../../../XML/Group/Schemas.html#membership">The list of members
|
|
and details about joining</a> are on the group home page.</p>
|
|
<p>
|
|
The level of participation expected for this Working Group suggests that representatives
|
|
be experts in the development or exploitation of schemas for XML-based
|
|
markup languages. In addition to the time commitment noted above,
|
|
each participant of the Working Group will be expected to show evidence to the Chair,
|
|
each six months, of active work in the general topic area. Such active
|
|
cultivation may take the form of:</p><ul>
|
|
<li>development of at least one non-trivial schema, using XML Schema 1.0
|
|
or a draft under development</li>
|
|
<li>development of at least a small piece of software which processes
|
|
XML Schema documents, or participation in the development of larger
|
|
software packages which support XML Schema.</li>
|
|
</ul>
|
|
<div>
|
|
<h3>
|
|
Chair
|
|
</h3>
|
|
<p>The initial Chair of the XML Schema Working Group is
|
|
David Ezell, National Association of Convenience Stores.
|
|
</p>
|
|
<!--* <p>The term <i>chair</i> in this document refers to either
|
|
co-chair.</p> *-->
|
|
|
|
<h3>
|
|
<a name="W3CResources">W3C Team resources</a>
|
|
</h3>
|
|
<p>
|
|
<!--The W3C shall be represented by one or more participants.
|
|
The W3C Team resource commitment is no more than the minimum
|
|
level of participation required of WG members in good standing by the W3C
|
|
Process Document.--></p>
|
|
<p>
|
|
The initial W3C Team contacts for this Working Group are
|
|
C. M. Sperberg-McQueen and Henry Thompson. It is expected that this Working Group would consume
|
|
about 0.9 FTE, including administrative
|
|
logistics.
|
|
</p>
|
|
</div>
|
|
|
|
</div>
|
|
|
|
|
|
<div>
|
|
<h2>
|
|
5. <a name="AEN117">Communication</a>
|
|
</h2>
|
|
<p>
|
|
The XML Schema Working Group shall communicate among its
|
|
participants using the <code><a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg">
|
|
w3c-xml-schema-wg</a></code> mailing list and with the other XML
|
|
Working Groups through the
|
|
<a href="http://lists.w3.org/Archives/Member/w3c-xml-plenary"><code>w3c-xml-plenary@w3.org
|
|
</code></a> mailing list. Both lists are archived.
|
|
</p>
|
|
<p>The XML Schema Working Group communicates with the public through the
|
|
<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/"
|
|
>www-xml-schema-comments</a> and
|
|
<a href="http://lists.w3.org/Archives/Public/xmlschema-dev/">xmlschema-dev</a>
|
|
mailing lists, both of which
|
|
are public.</p>
|
|
<!--* <p>Otherwise,
|
|
it shall communicate with the general public only through its
|
|
Chair.</p> *-->
|
|
</div>
|
|
|
|
<div>
|
|
<h2>
|
|
6. <a name="Confident">Confidentiality</a>
|
|
</h2>
|
|
|
|
<!--*
|
|
<blockquote>
|
|
<p>
|
|
|
|
"Member-only" information is available to authorized parties only,
|
|
including representatives of Member organizations, invited experts,
|
|
the Advisory Board, the TAG, and the Team. ...
|
|
Those authorized to access Member-only and Team-only information:
|
|
</p>
|
|
<ul>
|
|
<li><strong>must</strong> treat the information as confidential within
|
|
W3C,</li>
|
|
<li><strong>must</strong> use reasonable efforts to maintain the
|
|
proper level confidentiality, and</li>
|
|
<li><strong>must not</strong> release this information to the general
|
|
public or press.</li>
|
|
</ul>
|
|
<div style="margin-left: 40%; right; margin-right: 3em;">
|
|
-<a href="http://www.w3.org/2003/06/Process-20030618/comm.html#confidentiality-levels">W3C Process Document (18 June 2003), section 4.1</a>
|
|
</div>
|
|
</blockquote>
|
|
*-->
|
|
|
|
<p>
|
|
The proceedings of this working group are Member-confidential<!--,
|
|
subject to exceptions made by the chair-->.
|
|
In support of public accountability, the Working Group will
|
|
periodically make public a summary of all technical decisions made since
|
|
the last public summary, and the rationales for these decisions.
|
|
</p>
|
|
|
|
<!--*
|
|
<p>The proceedings of this working group are publicly readable,
|
|
subject to exceptions made by the chair. In particular, the archive
|
|
of the mailing list used for technical discussion and the Group home
|
|
page are publicly readable.
|
|
</p>
|
|
*-->
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<h2>
|
|
7. <a name="AEN124">Face-to-Face Meetings</a>
|
|
</h2>
|
|
<p>
|
|
Face-to-face meetings will be held as needed; it is expected that
|
|
such meetings will be held about every two to three months.</p>
|
|
</div>
|
|
|
|
|
|
|
|
<div><h2>8. <a name="pp">Patent policy</a></h2>
|
|
|
|
<p>This Working Group operates under the <a
|
|
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent
|
|
Policy</a> (5 February 2004 Version). To promote the widest adoption of
|
|
Web standards, W3C seeks to issue Recommendations that can be
|
|
implemented, according to this policy, on a Royalty-Free basis.</p>
|
|
|
|
</div>
|
|
|
|
<div>
|
|
<!--<p>
|
|
Communications resources for press and media relations and speaking
|
|
appearances or meeting planning resources are amortized across the
|
|
working groups in the XML Activity, and concentrated in the XML
|
|
Coordination Group.</p>-->
|
|
</div>
|
|
|
|
<hr/>
|
|
<address>Chair, W3C XML Schema Working Group: <a href="mailto:david_e3@verifone.com">David Ezell</a>
|
|
<br />W3C Team contacts: C. M. Sperberg-McQueen and
|
|
Henry Thompson
|
|
<br />Last Modified: $Date: 2004/06/16 18:55:46 $ </address>
|
|
<!--* <p>
|
|
[<small>
|
|
This revision:
|
|
$Id: xml-schema-wg-charter.html,v 1.52 2004/06/16 18:55:46 plehegar Exp $
|
|
</small>]
|
|
</p> *-->
|
|
</body></html>
|
|
<!-- Keep this comment at the end of the file
|
|
Local variables:
|
|
mode:xml
|
|
sgml-omittag:t
|
|
sgml-shorttag:t
|
|
End:
|
|
-->
|
|
|