The purpose of the NDR SC is to
recommend to the TC rules and guidelines for normative-form schema design,
instance design, and markup naming, and write and maintain documentation of
these rules and guidelines.
26 June 2002
Portal redesign: This portal and the
archives have been redesigned to support our ongoing and future volume of work.
Old links emanating from external sources should still work for now, but please
plan to change links to point into the new
Our approved charter wording is as follows:
The purpose of the NDR SC is to recommend to
the TC rules and guidelines for normative-form schema design, instance design,
and markup naming, and write and maintain documentation of these rules and
The primary deliverable of the NDR SC is a
document that provides the rules and guidelines. Auxiliary deliverables, which
may or may not be provided as part of the main document, might include analyses
of schema validator feature support and use cases that support our rules and
See the Schedule section below for information
about specific existing and planned outputs.
documents repository contains only the most recent and/or active
revisions of NDR SC outputs; it provides an ongoing snapshot of our work. Links
are provided below to the entire contents of this repository. Consult this
repository to review and give feedback on the NDR SC work. Comments on NDR SC
outputs should be sent to the
email@example.com mailing list (you must
subscribe first) using our
issues template; fill in columns B through I.
holds all versions of all documents produced by the NDR SC.
repository holds documents prepared by external sources that we have used in
our work. A selection of links to various inputs is provided below.
This paper is frozen. It contains the
major parts of the recommendation being made by the NDR SC and its rationales,
though further technical development is being done piecemeal on the actual rule
We produced our first outputs, consisting of a
reviewed document outline and an initial set of position papers to be taken up
by the group, by the week of 10 December 2001. Our second output on
17 March 2002 was a set of position papers that is minimally useful for
generating schema code from the Library Content SC output. We produced a
new/revised set of outputs prior to our 3-7 June 2002 F2F meeting.
workload through the end of September 2002 involves the following topics. An A
priority means we must cover the topic before the next F2F meeting. A B
priority means we should try to cover the topic. A C priority means the topic
is optional to cover.
A NDR document improvements (review every two weeks)
A+ Embedded documentation DONE EXCEPT FOR DOCUMENTING IT
A Code lists IN PROGRESS
A Dates and times IN PROGRESS
A Nested supplementary components
A Identifier references and whether to pass content by reference
A- Local vs. global elements
B Updating guiding principles
B Modnamver URN/schema location
B Referencing of content, e.g. for attachments
C Wildcards/open content
C Aggregation of similar information for XPath V1.0 addressing
We meet weekly by phone. Calls are held
8:30-10:30am GMT-8 / 11:30am-1:30pm GMT-5 / 5:30-7:30pm GMT+1 on Wednesdays.
Calls are open only to members. Please contact one of the
chairs if you need call-in