This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
Completed Work
W3C Recommendations have
been reviewed by W3C Members, by software developers, and by other
W3C groups and interested parties, and are endorsed by the
Director as Web Standards. Learn more about the W3C Recommendation
Track.
Group Notes are not standards and do not
have the same level of W3C endorsement.
Standards
|
2007-04-03
|
translations
·
errata
A set of recommendations for data
categories that can be mapped to elements
and attributes to support the
internationalization and localization of
marked up content. Implementations are
provided for DTDs, XML Schema and Relax NG,
and for existing vocabularies like XHTML,
DocBook and OpenDocument.
|
|
2005-02-15
|
translations
·
errata
Architectural Specification building on
Unicode to provide authors of
specifications, software developers, and
content developers with a common reference
for interoperable text handling on the
World Wide Web.
|
Group Notes
|
2005-10-13
|
translations
Discusses some of the problems encountered when working with the date, time, and dateTime values from XML Schema when those value include (or omit) time zone offsets. Many W3C technologies rely on date and time types.
|
Drafts
Below are draft documents:
Candidate Recommendations, other Working Drafts.
Some of these may become Web Standards through the W3C Recommendation Track
process. Others may be published as Group Notes or
become obsolete specifications.
Candidate Recommendations
|
2004-11-22
|
Architectural Specification providing authors of specifications, software developers, and content developers with a common reference for the use of resource identifiers building on Unicode.
|
Other Working Drafts
|
2006-06-12
|
Describes mechanisms based on BCP 47 for identifying or selecting the language of content or locale preferences used to process information using Web technologies.
|
|
2006-05-18
|
When creating schemas (XML Schema, DTD, etc.), it is important to include constructs that meet the needs of content authors dealing with international audiences, and address the needs of the localization community. This document provides a list of key requirements to achieve such a goal.
|
|
2005-10-27
|
Architectural Specification providing authors of specifications, software developers, and content developers with a common reference for normalization and string identity matching to improve interoperable text handling on the World Wide Web.
|
W3C
