- From: CVS User fsasaki <cvsmail@w3.org>
- Date: Wed, 29 May 2013 16:53:24 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv29280
Modified Files:
its20-for-editing-sec1-sec2.odd
Log Message:
update odd file for sec1-sec2
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/29 16:14:02 1.1
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20-for-editing-sec1-sec2.odd 2013/05/29 16:53:24 1.2
@@ -129,528 +129,373 @@
</header>
<text>
<body>
- <div xml:id="introduction">
- <head>Introduction</head>
+ <div xml:id="introduction">
+
+ <head>Introduction</head>
+
+
+
+ <div xml:id="overview">
+
+ <head>Overview</head>
+
+
+
+ <p>
+
+ Content or software that is authored in one language (so-called
+
+ original
+
+ language) for one locale (e.g. the French-speaking part of
+
+ Canada) is often made available in additional languages or adapted
+
+ with regard to other cultural aspects. A prevailing paradigm for
+
+ the
+
+ corresponding approach to production in many cases encompasses
+
+ three
+
+ phases: internationalize, translate,
+
+ and localize (see the <ref target="http://www.w3.org/International/questions/qa-i18n/"> W3C's Internationalization Q&A</ref>
+
+ for more information related to these concepts).
+
+ </p>
+
+ <p>
+
+ From the viewpoints of feasibility, cost, and efficiency, it is
+
+ important
+
+ that the original material should be suitable for
+
+ downstream
+
+ phases such as translation. This
+
+ is
+
+ achieved by
+
+ appropriate design and
+
+ development.
+
+ The corresponding
+
+ phase is
+
+ referred to as
+
+ internationalization.
+
+ 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>During the translation phase, the meaning of a source language
+
+ text
+
+ is
+
+ analyzed, and a target language text that is equivalent in
+
+ meaning
+
+ is
+
+ determined. In order to promote or ensure a translation's
+
+ fidelity,
+
+ national or international laws may for example regulate
+
+ linguistic
+
+ dimensions such as mandatory terminology or standard
+
+ phrases.
+
+ </p>
+
+ <p>
+
+ Although an agreed-upon definition of the localization phase is
+
+ missing,
+
+ this phase is usually seen as encompassing activites such as
+
+ creating locale-specific content (e.g. adding a link for a
+
+ country-specific reseller), or modifying functionality (e.g. to
+
+ establish a fit with country-specific regulations for financial
+
+ reporting).
+
+ Sometimes, the insertion of special markup to support a
+
+ local language
+
+ or script is also subsumed under the localization phase.
+
+ 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>
+
+ The technology described in this document - the
+
+ <emph>Internationalization Tag Set (ITS)
+
+ 2.0</emph>
+
+ addresses some of the challenges and opportunities related to
+
+ internationalization,
+
+ translation, and localization. ITS 2.0 in
+
+ particular contributes to concepts in the realm of meta data for
+
+ internationalization,
+
+ translation, and localization related to core Web
+
+ technologies. ITS does for example assist in usage scenarios in which parts of an
+
+ XML-based document should not be translated. ITS 2.0 bears many
+
+ commonalities with is
+
+ predecessor,
+
+ <ref target="http://www.w3.org/TR/2007/REC-its-20070403/">ITS 1.0</ref>
+
+ but provides additional
+
+ concepts that are designed to foster enhanced
+
+ automated processing - e.g. based on language technology such as
+
+ entity recognition - related to multilingual
+
+ Web content.
+
+ </p>
+
+ <p>ITS proposes several mechanisms which differ
+
+ amongst others in terms of the usage scenario/user types for which the
+
+ mechanism is most suitable. For the purpose of
+
+ illustration, here is an example how ITS can indicate that certain parts of
+
+ content should not be translated.</p>
+
+ <exemplum xml:id="EX-ways-to-use-its-0">
+
+ <head>Use of ITS to indicate that parts of an XML-based document - maybe to be transformed into HTML by a Web Content Management System (WCMS) -
+
+ should or should not be translated</head>
+
+ <p>
+
+ The
+
+ <code>its:translate="no"</code>
+
+ attributes indicate that the
+
+ <code>path</code>
+
+ and the
+
+ <code>cmd</code>
+
+ elements should not be translated.
+
+ </p>
+
+ <egXML xmlns="http://www.tei-c.org/ns/Examples" target="examples/xml/EX-ways-to-use-its-0.xml" />
+
+ </exemplum>
+
+ <p>
+
+ Like ITS 1.0, ITS 2.0
+
+ both identifies
+
+ concepts (such as
+
+ <q>Translate</q>
+
+ ), 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
+
+ definitions of ITS elements and attributes are provided in the
+
+ form of XML Schema
+
+ <ptr target="#xmlschema1" type="bibref" />
+
+ (non-normative)
+
+ and RELAX NG
+
+ <ptr target="#relaxng" type="bibref" />
+
+ (normative).
+
+ Since one major step from ITS 1.0 to ITS 2.0 relates to coverage for
+
+ HTML, ITS 2.0 also regulates the relationship between ITS markup and
+
+ the
+
+ various HTML flavours.
+
+ Furthermore, ITS 2.0
+
+ suggests when and how to leverage
+
+ processing based on the XML Localization
+
+ Interchange File Format
+
+ (XLIFF), as
+
+ well as the
+
+ Natural Language
+
+ Processing Interchange
+
+ Format
+
+ <ref target="http://nlp2rdf.org/nif-1-0">NIF (NLP Interchange Format)</ref>
+
+ .
+
+ </p>
+
+</div>
+
+ <div xml:id="general-motiviation-for-ITS2.0"><head>General motivation for going beyond ITS 1.0</head> <p>tbd</p></div>
+
+ <div xml:id="usage-scenarios"><head>Broader Usage Scenarios</head> <p>tbd</p></div>
+
+ <div xml:id="high-level-differences-between-1.0-and-2.0"><head>High-level differences between ITS 1.0 and ITS 2.0</head>
+
+ <!-- http://lists.w3.org/Archives/Public/public-multilingualweb-lt-comments/2013Jan/0018.html
+
+
+
+1. list of additional data categories (that's already in the current draft)
+
+2. modified data categories (e.g. "termConfidence" for term, or the model for Ruby)
+
+3. query language on rules element
+
+4. parameters/variables in selectors
+
+5. modified selectors (absolute and relative)
+
+6. toolsRef to record which tools generated data category related information
+
+7. changes to conformance section (e.g. clause for processing ITS with HTML)
+
+8. conversion to NIF
+
+9. more "implementation hints" (e.g. RDFa Lite)
+
+
+
+Furthermore, the section could mention some additional background:
+
+
+
+10. (implicit) clustering of data categories (as in http://www.w3.org/TR/2012/WD-its2req-20120524/#Descriptions_of_proposed_metadata_categories)
+
+11. liasons and coordination (e.g. attention to Unicode registered extensions "u" and "t")
+
+12. focus on real-world use cases (thus for example no "...confidence" for all data categories, since that would hardly be needed)
+
+
+
+ -->
+
+ <div xml:id="additional-data-categories"><head>Additional data categories</head>
+ <p>tbd</p></div>
+
+ <div xml:id="modified-datacategories"><head>Modified data categories</head> <p>tbd</p></div>
+
+ <div xml:id="additional-mechanisms"><head>Additional or modified mechanisms</head>
+
+ <div xml:id="query-language-on-rules-element"><head>Query language on rules element</head> <p>tbd</p></div>
+
+ <div xml:id="modified-selectors"><head>Modified selectors</head> <p>tbd</p></div>
+
+ <div xml:id="parameters-in-selectors"><head>Parameters in selectors</head> <p>tbd</p></div>
+
+ <div xml:id="traceability"><head>Traceability</head> <p>tbd</p></div>
+
+ </div>
+
+ <div xml:id="specific-HTML-support"><head>Specific HTML support</head> <p>tbd</p></div>
+
+ <div xml:id="mappings"><head>Mappings</head>
+
+ <div xml:id="mapping-NIF"><head>NIF</head> <p>tbd</p></div>
+
+ <div xml:id="mapping-XLIFF"><head>XLIFF</head> <p>tbd</p></div>
+
+ </div>
+
+ <div xml:id="unicode-normalization"><head>Unicode normalization</head> <p>tbd</p></div>
+
+ <div xml:id="extended-implementation-hints"><head>Extended implementation hints</head> <p>tbd</p></div>
+
+ </div>
- <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 HTML, serializations in <ref target="http://persistence.uni-leipzig.org/nlp2rdf/">NIF</ref> (NLP Interchange Format) <ptr target="#nif-reference" type="bibref"/>, 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">
[497 lines skipped]
Received on Wednesday, 29 May 2013 16:53:25 UTC