- From: CVS User alommel <cvsmail@w3.org>
- Date: Tue, 20 Nov 2012 07:51:10 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20 In directory gil:/tmp/cvs-serv27166 Modified Files: its20.odd Log Message: format and indent prior to editing. No substantive change --- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/19 20:55:09 1.229 +++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2012/11/20 07:51:10 1.230 @@ -1,742 +1,722 @@ <?xml version="1.0" encoding="UTF-8"?><?oxygen RNGSchema="tools/tei-w3c.rnc" type="compact"?> <TEI xmlns="http://www.tei-c.org/ns/1.0" xmlns:its="http://www.w3.org/2005/11/its" - xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rng="http://relaxng.org/ns/structure/1.0" - xmlns:spec="http://example.com/xmlspec" xmlns:xlink="http://www.w3.org/1999/xlink" - xmlns:xi="http://www.w3.org/2001/XInclude" xml:lang="en"> - <header xmlns="http://example.com/xmlspec"> - <title>Internationalization Tag Set (ITS) Version 2.0</title> - <w3c-designation>ITS20</w3c-designation> - <w3c-doctype>W3C Working Draft</w3c-doctype> - <pubdate> - <day>23</day> - <month>October</month> - <year>2012</year> - </pubdate> - <publoc> - <loc href="http://www.w3.org/TR/2012/WD-its20-20121023/"> - http://www.w3.org/TR/2012/WD-its20-20121023/</loc> - </publoc> - <altlocs> - <loc href="its20.odd">ODD/XML document</loc> - <loc href="itstagset20.zip">self-contained zipped archive</loc> - <loc href="diffs/diff-wd20120626-its10-20070403.html">XHTML Diff markup to ITS 1.0 - Recommendation 3 April 2007</loc> - <loc href="diffs/diff-wd20120731-wd20120626.html">XHTML Diff markup to publication from - 26 June 2012</loc> - <loc href="diffs/diff-wd20120829-wd20120731.html">XHTML Diff markup to publication from - 31 July 2012</loc> - <loc href="diffs/diff-wd20121023-wd20120829.html">XHTML Diff markup to publication from - 29 August July 2012</loc> - </altlocs> - <prevlocs> - <loc href="http://www.w3.org/TR/2012/WD-its20-20120829/"> - http://www.w3.org/TR/2012/WD-its20-20120829/</loc> - </prevlocs> - - <latestloc> - <loc href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</loc> - </latestloc> - <authlist> - <author> - <name>Shaun McCane</name> - <affiliation>Invited Expert</affiliation> - </author> - <author> - <name>Dave Lewis</name> - <affiliation>TCD</affiliation> - </author> - <author> - <name>Arle Lommel</name> - <affiliation>DFKI</affiliation> - </author> - <author> - <name>Jirka Kosek</name> - <affiliation>UEP</affiliation> - </author> - <author> - <name>Felix Sasaki</name> - <affiliation>DFKI / W3C Fellow</affiliation> - </author> - <author> - <name>Yves Savourel</name> - <affiliation>ENLASO</affiliation> - </author> - </authlist> - <!-- <errataloc role="spec-conditional" href="http://www.w3.org/International/its/itstagset/its-errata.html"/> + xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:rng="http://relaxng.org/ns/structure/1.0" + xmlns:spec="http://example.com/xmlspec" xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:xi="http://www.w3.org/2001/XInclude" xml:lang="en"> + <header xmlns="http://example.com/xmlspec"> + <title>Internationalization Tag Set (ITS) Version 2.0</title> + <w3c-designation>ITS20</w3c-designation> + <w3c-doctype>W3C Working Draft</w3c-doctype> + <pubdate> + <day>23</day> + <month>October</month> + <year>2012</year> + </pubdate> + <publoc> + <loc href="http://www.w3.org/TR/2012/WD-its20-20121023/"> + http://www.w3.org/TR/2012/WD-its20-20121023/</loc> + </publoc> + <altlocs> + <loc href="its20.odd">ODD/XML document</loc> + <loc href="itstagset20.zip">self-contained zipped archive</loc> + <loc href="diffs/diff-wd20120626-its10-20070403.html">XHTML Diff markup to ITS 1.0 + Recommendation 3 April 2007</loc> + <loc href="diffs/diff-wd20120731-wd20120626.html">XHTML Diff markup to publication from 26 + June 2012</loc> + <loc href="diffs/diff-wd20120829-wd20120731.html">XHTML Diff markup to publication from 31 + July 2012</loc> + <loc href="diffs/diff-wd20121023-wd20120829.html">XHTML Diff markup to publication from 29 + August July 2012</loc> + </altlocs> + <prevlocs> + <loc href="http://www.w3.org/TR/2012/WD-its20-20120829/"> + http://www.w3.org/TR/2012/WD-its20-20120829/</loc> + </prevlocs> + + <latestloc> + <loc href="http://www.w3.org/TR/its20/">http://www.w3.org/TR/its20/</loc> + </latestloc> + <authlist> + <author> + <name>Shaun McCane</name> + <affiliation>Invited Expert</affiliation> + </author> + <author> + <name>Dave Lewis</name> + <affiliation>TCD</affiliation> + </author> + <author> + <name>Arle Lommel</name> + <affiliation>DFKI</affiliation> + </author> + <author> + <name>Jirka Kosek</name> + <affiliation>UEP</affiliation> + </author> + <author> + <name>Felix Sasaki</name> + <affiliation>DFKI / W3C Fellow</affiliation> + </author> + <author> + <name>Yves Savourel</name> + <affiliation>ENLASO</affiliation> + </author> + </authlist> + <!-- <errataloc role="spec-conditional" href="http://www.w3.org/International/its/itstagset/its-errata.html"/> <translationloc role="spec-conditional" href="http://www.w3.org/2003/03/Translations/byTechnology?technology=its"/> --> - <abstract> - <p>This document defines data categories and their implementation as a set of elements - and attributes called the <emph>Internationalization Tag Set (ITS)</emph> 2.0. ITS - 2.0 is the successor of <loc href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS - 1.0</loc>; it is designed to foster the creation of multilingual Web content, - focusing on HTML5, XML based formats in general, and to leverage localization - workflows based on the XML Localization Interchange File Format (XLIFF). In addition - to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content to NIF is - provided.</p> - </abstract> - <status> - <p> - <emph>This section describes the status of this document at the time of its - publication. Other documents may supersede this document. A list of current W3C - publications and the latest revision of this technical report can be found in - the <loc href="http://www.w3.org/TR/">W3C technical reports index</loc> at - http://www.w3.org/TR/.</emph> - </p> - <p>This document defines data categories and their implementation as a set of elements - and attributes called the <emph>Internationalization Tag Set (ITS)</emph> 2.0. ITS - 2.0 is the successor of <loc href="http://www.w3.org/TR/2007/REC-its-20070403/">ITS - 1.0</loc>; it is designed to foster the creation of multilingual Web content, - focusing on HTML5, XML based formats in general, and to leverage localization - workflows based on the XML Localization Interchange File Format (XLIFF). In addition - to using ITS 2.0 for HTML5 and XML content, an algorithm to convert that content to NIF is - provided.</p> - - <p>This document is an updated Public Working Draft published by the <loc - href="http://www.w3.org/International/multilingualweb/lt/">MultilingualWeb-LT - Working Group</loc>, part of the <loc href="https://www.w3.org/International/" - >W3C Internationalization Activity</loc>. The Working Group expects to advance - this Working Draft to Recommendation status (see <loc - href="http://www.w3.org/2004/02/Process-20040205/tr.html#maturity-levels">W3C - document maturity levels</loc>).</p> - - <p xml:id="major-changes">A list of <loc href="#changelog-since-20120829">major changes since the previous publication</loc> is available. This working draft is planned to be the last ordinary working draft before moving to last call. Hence we encourage wide feedback from outside the working group.</p> - - <p>Feedback about the content of this document is encouraged. See also <loc - href="https://www.w3.org/International/multilingualweb/lt/track/issues/">issues - discussed within the Working Group</loc>. Send your comments to <loc - href="mailto:public-multilingualweb-lt-comments@w3.org" - >public-multilingualweb-lt-comments@w3.org</loc>. Use "Comment on ITS 2.0 - specification WD" in the subject line of your email. The <loc - href="http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/" - >archives for this list</loc> are publicly available.</p> - - <p>Publication as a Working Draft does not imply endorsement by the W3C Membership. This - is a draft document and may be updated, replaced or obsoleted by other documents at - any time. It is inappropriate to cite this document as other than work in - progress.</p> - - <p> This document was produced by a group operating under the <loc - href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 W3C - Patent Policy</loc>. W3C maintains a <loc - href="http://www.w3.org/2004/01/pp-impl/53116/status">public list of any patent - disclosures</loc> made in connection with the deliverables of the group; that - page also includes instructions for disclosing a patent. An individual who has - actual knowledge of a patent which the individual believes contains <loc - href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential" - >Essential Claim(s)</loc> must disclose the information in accordance with <loc - href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure" - >section 6 of the W3C Patent Policy</loc>. </p> - </status> - <langusage> - <language id="en">en</language> - </langusage> - <revisiondesc> - <p>This is the first version of this document.</p> - </revisiondesc> - </header> - <text> - <body> - <div xml:id="introduction"> - <head>Introduction</head> - - <p> - <emph>This section is informative.</emph> - </p> - <p>ITS 2.0 is a technology to add metadata to Web content, for the benefit of - localization, language technologies, and internationalization. The ITS 2.0 - specification both identifies concepts (such as <q>Translate</q>) that are - important for internationalization and localization, and defines implementations - of these concepts (termed “ITS data categories”) as a set of elements and - attributes called the <emph>Internationalization Tag Set (ITS)</emph>. The - document provides implementations for HTML5, serializations in <ref - target="http://nlp2rdf.org/nif-1-0">NIF</ref>, and provides definitions - of ITS elements and attributes in the form of XML Schema <ptr - target="#xmlschema1" type="bibref"/> and RELAX NG <ptr target="#relaxng" - type="bibref"/>.</p> - - <p>This document aims to realize many of the ideas formulated in the <ref - target="http://www.w3.org/TR/2012/WD-its2req-20120524/">ITS 2.0 Requirements - document</ref>, in <ptr target="#itsreq" type="bibref"/> and <ptr - target="#reqlocdtd" type="bibref"/>.</p> - <p>Not all requirements listed there are addressed in this document. Those which are - not addressed here are either covered in <ptr type="bibref" - target="#xml-i18n-bp"/> (potentially in an as yet unwritten best practice - document on multilingual Web content), or may be addressed in a future version - of this specification.</p> - - <div xml:id="relation-to-its10-and-new-principles"> - <head>Relation to ITS 1.0 and New Principles</head> - <div xml:id="relation-to-its10"> - <head>Relation to ITS 1.0</head> - <p>ITS 2.0 has the following relations to ITS 1.0:</p> - <list type="unorderd"> - <item><p>It adopts and maintains the following principles from ITS 1.0: - </p><list type="unorderd"> - <item>It adopts the use of data categories to define discrete - units of functionality</item> - <item>It adopts the separation of data category definition from - the mapping of the data category to a given content - format</item> - <item>It adopts the conformance principle of ITS1.0 that an - implementation only needs to implement one data category to - claim conformance to ITS 2.0</item> - </list> - </item> - <item>ITS 2.0 supports all ITS 1.0 data category definitions and adds - new definitions, with the exceptions of <ref target="#directionality">Directionality</ref> and <ref target="#ruby-annotation">Ruby</ref>.</item> - <item>ITS 2.0 adds a number of new data categories not found in ITS - 1.0.</item> - <item>While ITS 1.0 addressed only XML, ITS 2.0 specifies - implementations of data categories in <emph>both</emph> XML - <emph>and</emph> HTML5.</item> - </list> - </div> - <div xml:id="new-principles"> - <head>New Principles</head> - <p>ITS 2.0 also adds the following principles and features not found in ITS - 1.0:</p> - <list type="unorderd"> - <item>ITS 2.0 data categories are intended to be format neutral, with - support for XML, HTML5, and NIF: a data category - implementation only needs to support a single content format mapping - in order to support a claim of ITS 2.0 conformance.</item> - <item>ITS 2.0 provides algorithms to generate NIF out of HTML5 - or XML with ITS 2.0 metadata.</item> - <item>A global implementation of ITS 2.0 requires at least the XPath - version 1.0. Other versions of XPath or other query languages (e.g., - CSS selectors) can be expressed via a dedicated <ref - target="#queryLanguage">queryLanguage</ref> attribute.</item> - </list> - <p>As of the time of this writing, the new data categories included in ITS - 2.0 are:</p> - <note type="ed">Below needs to be updated before each publication before last call.</note> - <list type="unorderd"> - <item><ref target="#domain">Domain</ref></item> - <item><ref target="#Disambiguation">Disambiguation</ref></item> - <item><ref target="#LocaleFilter">Locale Filter</ref></item> - <item><ref target="#provenance">Provenance</ref></item> - <item><ref target="#TextAnalyisAnnotation">Text Analysis - Annotation</ref></item> - <item><ref target="#externalresource">External Resource</ref></item> - <item><ref target="#target-pointer">Target Pointer</ref></item> - <item><ref target="#idvalue">Id Value</ref></item> - <item><ref target="#preservespace">Preserve Space</ref></item> - <item><ref target="#lqissue">Localization Quality Issue</ref></item> - <item><ref target="#lqprecis">Localization Quality Précis</ref></item> - <item><ref target="#mtconfidence">MT Confidence</ref></item> - <item><ref target="#allowedchars">Allowed Characters</ref></item> - <item><ref target="#storagesize">Storage Size</ref></item> - </list> - </div> - </div> - - <div xml:id="motivation-its"> - <head>Motivation for ITS</head> - <p>Content or software that is authored in one language (the <term>source - language</term>) is often made available in additional languages or - adapted with regard to other cultural aspects. This is done through a - process called <term>localization</term>, where the original material is - translated and adapted to the target audience.</p> - <p>In addition, document formats expressed by schemas may be used by people in - different parts of the world, and these people may need special markup to - support the local language or script. For example, people authoring in - languages such as Arabic, Hebrew, Persian, or Urdu need special markup to - specify directionality in mixed direction text.</p> - <p>From the viewpoints of feasibility, cost, and efficiency, it is important - that the original material should be suitable for localization. This is - achieved by appropriate design and development, and the corresponding - process is referred to as internationalization. For a detailed explanation - of the terms “localization” and “internationalization”, see <ptr - target="#geo-i18n-l10n" type="bibref"/>.</p> - <note type="ed">Note: This should refer to the best practice document as well, - when ready.</note> - <p>The increasing usage of XML as a medium for documentation-related content - (e.g. DocBook and DITA as formats for writing structured documentation, well - suited to computer hardware and software manuals) and software-related - content (e.g. the eXtensible User Interface Language <ptr target="#xul" - type="bibref"/>) creates challenges and opportunities in the domain of - XML internationalization and localization.</p> - - <div xml:id="motivation-its-issues"> - <head>Typical Problems</head> - - <p>The following examples sketch one of the issues that currently hinder - efficient XML-related localization: the lack of a standard, declarative - mechanism that identifies which parts of an XML document need to be - translated. Tools often cannot automatically perform this - identification.</p> - <exemplum> - <head>Document with partially translatable content</head> - <p>In this document it is difficult to distinguish between those - <gi>string</gi> elements that are translatable and those that - are not. Only the addition of an explicit flag could resolve the - issue.</p> - <egXML xmlns="http://www.tei-c.org/ns/Examples" - target="examples/xml/EX-motivation-its-1.xml"/> - </exemplum> - <exemplum> - <head>Document with partially translatable content</head> - <p>Even when metadata are available to identify non-translatable text, - the conditions may be quite complex and not directly indicated with - a simple flag. Here, for instance, only the text in the nodes - matching the expression - <code>//component[@type!='image']/data[@type='text']</code> is - translatable.</p> - <egXML xmlns="http://www.tei-c.org/ns/Examples" - target="examples/xml/EX-motivation-its-2.xml"/> - </exemplum> - </div> - </div> - <div xml:id="users-usage"> - <head>Users and Usages of ITS</head> - <div xml:id="potential-users"> - <head>Potential Users of ITS</head> - <p>The ITS specification aims to provide different types of users with - information about what markup should be supported to enable worldwide - use and effective internationalization and localization of content. The - following paragraphs sketch these different types of users, and their - usage of ITS. In order to support all of these users, the information - about what markup should be supported to enable worldwide use and - effective localization of content is provided in this specification in - two ways:</p> - <list> - <item>abstractly in the data category descriptions: <ptr - target="#datacategory-description" type="specref"/> - </item> - <item>concretely in the ITS schemas: <ptr target="#its-schemas" - type="specref"/> - </item> - </list> - <div xml:id="schema-dev-new"> - <head>Schema developers starting a schema from the ground up</head> - <p>This type of user will find proposals for attribute and element names - to be included in their new schema (also called "host vocabulary"). - Using the attribute and element names proposed in the ITS - specification may be helpful because it leads to easier recognition - of the concepts represented by both schema users and processors. It - is perfectly possible, however, for a schema developer to develop - his own set of attribute and element names. The specification sets - out, first and foremost, to ensure that the required markup is - available, and that the behavior of that markup meets established - needs.</p> - </div> - <div xml:id="schema-dev-existing"> - <head>Schema developers working with an existing schema</head> - <p>This type of user will be working with schemas such as DocBook, DITA, - or perhaps a proprietary schema. The ITS Working Group has sought - input from experts developing widely used formats such as the ones - mentioned.</p> - <note><p>The question "How to use ITS with existing popular markup - schemes?" is covered in more details (including examples) in a - separate document: <ptr target="#xml-i18n-bp" type="bibref" - />.</p></note> - <p>Developers working on existing schemas should check whether their [11154 lines skipped]
Received on Tuesday, 20 November 2012 07:51:23 UTC