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.
|
|
2001-05-31
|
translations
·
errata
"Ruby" are short runs of text alongside
the base text, typically used in East Asian
documents to indicate pronunciation or to
provide a short annotation. This
specification defines markup for ruby, in
the form of an XHTML module.
|
Group Notes
|
2009-09-15
|
This document was written as the first step towards a character model for W3C specifications. The views expressed have evolved over the intervening years, and the document was re-published purely to preserve the historical record.
|
|
2009-09-08
|
Provides HTML/XHTML authors with best
practice for developing internationalized
HTML supported by CSS to create pages for
languages that use bidirectional text, such
as Arabic and Hebrew.
|
|
2009-06-04
|
translations
·
errata
Describes requirements for general
Japanese layout realized with technologies
like CSS, SVG and XSL-FO. The document is
mainly based on a standard for Japanese
layout, JIS X 4051, however, it also
addresses areas which are not covered by
JIS X 4051.
|
|
2008-11-03
|
translations
For historic reasons, some formats have
allowed variants of IRIs that are somewhat
less restricted in syntax, for example XML
system identifiers and W3C XML Schema
anyURIs. This document provides a
definition and a name (Legacy Extended IRI
or LEIRI) for these variants for easy
reference.
|
|
2008-02-13
|
translations
Provides a set of guidelines for
developing XML documents and schemas that
are properly internationalized, aimed at
both developers of XML applications and
authors of XML content.
|
|
2007-05-16
|
This document contains guidelines on the
use of the Unicode Standard in conjunction
with markup languages such as XML.
|
|
2007-04-12
|
Provides HTML/XHTML authors with best
practices for developing internationalized
content, supported by CSS, and focusing
specifically on advice about specifying the
language of content.
|
|
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.
|
|
2004-11-16
|
Developed to help achieve worldwide
usability for Web services, these
requirements address the way
internationalization options are exposed in
Web services definitions, descriptions,
messages, and discovery mechanisms.
|
|
2004-07-30
|
Describes internationalization usage
patterns and scenarios for Web services.
Provides additional guidance for
implementers of Web service technologies,
suggesting methods for dealing with general
international interoperability issues in
services and service descriptions. Provides
a template for Web service designers to
implement international capabilities in
their services.
|
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.
|
|
2003-05-14
|
"Ruby" are short runs of text alongside
the base text, typically used in East Asian
documents to indicate pronunciation or to
provide a short annotation. This document
proposes a set of CSS properties associated
with the 'Ruby' elements. They can be used
in combination with the Ruby elements of
HTML.
|
Other Working Drafts
|
2009-06-18
|
This CSS3 module describes how font
properties are specified and how font
resources are loaded dynamically. The
contents of this specification are a
consolidation of content previously divided
into CSS3 Fonts and CSS3 Web Fonts
modules.
|
|
2008-04-15
|
Describes enhancements to SOAP messaging
to provide internationalized and localized
operations using locale and international
preferences. These mechanisms can be used
to accommodate a wide variety of
development models for international
usage.
|
|
2007-03-06
|
This CSS3 module defines properties for
text manipulation and specifies their
processing model. It covers line breaking,
justification and alignment, white space
handling, text decoration and text
transformation.
|
|
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 the use of resource
identifiers building on Unicode.
|
|
2004-05-09
|
Provides HTML/XHTML authors with best
practice for developing internationalized
HTML supported by CSS, focusing
specifically on advice about character
sets, encodings, and other
character-specific matters.
|
|
2002-11-07
|
CSS is a language for describing the
rendering of structured documents (such as
HTML and XML) on screen, on paper, in
speech, etc. This draft contains the
features of CSS level 3 relating to list
styling.
|
|
2002-05-15
|
The CSS formatting model provides for a
flow of elements and text inside of a
container to be wrapped into lines. This
module describes the positioning in the
block progression direction both of
elements and text within lines and of the
lines themselves. This positioning is often
relative to a baseline. It also describes
special features for formatting of first
lines and drop caps.
|
Obsolete Specifications
These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.
Retired
|
2003-04-17
|
This is a discussion document produced
by the Guidelines, Education & Outreach
Task Force (GEO) of the W3C
Internationalization Working Group (I18N
WG). It describes plans for producing
documents that provide guidelines on
internationalization of W3C
technologies.
|
|
1998-03-13
|
Thoughts on how to mark the primary
language(s) in a HTML document.
|
Resources Developed Outside W3C
The following resources are relevant to this area of
work.
Internationalized Resource Identifiers (RFC
3987)
RFC
3987: Internationalization Resource Identifiers
defines a new protocol element, the Internationalized
Resource Identifier (IRI), as a complement to the Uniform
Resource Identifier (URI).
Internet-Draft: BCP 47 (RFC 4646 and RFC 4647)
IETF Best Current Practice 47 describes language tags and language tag matching for cases where it is desirable to indicate the language used in an information object. Comprises two IETF RFCs: RFC 4646 Tags for Identifying Languages and RFC 4647 Matching of Language Tags. The two editors of this best practice participate in the Internationalization Working Group.
W3C
