W3C home > Mailing lists > Public > public-multilingualweb-lt-commits@w3.org > December 2012

CVS WWW/International/multilingualweb/lt/drafts/its20

From: CVS User fsasaki <cvsmail@w3.org>
Date: Tue, 11 Dec 2012 14:45:21 +0000
Message-Id: <E1TiR5F-0003ap-7G@gil.w3.org>
To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv13804

Modified Files:
	its20.html 
Log Message:
no change to content, just to stylesheet for the draft generation. See http://lists.w3.org/Archives/Public/public-i18n-its-ig/2012Dec/0001.html 

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2012/12/11 08:36:54	1.300
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.html	2012/12/11 14:45:21	1.301
@@ -243,7 +243,7 @@
               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><ul><li><p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 8: Description of Data Categories</a></p></li><li><p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p></li></ul><div class="div4">
-<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1Schema developers starting a schema from the ground up</h5><p>This type of user will find proposals for attribute and element names to be
+<h5><a name="schema-dev-new" id="schema-dev-new" shape="rect"/>1.3.1.1 Schema developers starting a schema from the ground up</h5><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
@@ -251,7 +251,7 @@
                 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 class="div4">
-<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2Schema developers working with an existing schema</h5><p>This type of user will be working with schemas such as DocBook, DITA, or perhaps a
+<h5><a name="schema-dev-existing" id="schema-dev-existing" shape="rect"/>1.3.1.2 Schema developers working with an existing schema</h5><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><div class="note"><p class="prefix"><b>Note:</b></p><p>The question "How to use ITS with existing popular markup schemes?" is
                   covered in more details (including examples) in a separate document: <a title="Best&#xA;                Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.</p></div><p>Developers working on existing schemas should check whether their schemas support
@@ -263,7 +263,7 @@
                 should, however, check that the behavior associated with the markup in their own
                 schema is fully compatible with the expectations described in this
                 specification.</p></div><div class="div4">
-<h5><a name="content-tool-vendor" id="content-tool-vendor" shape="rect"/>1.3.1.3Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for authoring, translation
+<h5><a name="content-tool-vendor" id="content-tool-vendor" shape="rect"/>1.3.1.3 Vendors of content-related tools</h5><p>This type of user includes companies which provide tools for authoring, translation
                 or other flavors of content-related software solutions. It is important to ensure
                 that such tools enable worldwide use and effective localization of content. For
                 example, translation tools should prevent content marked up as not for translation
@@ -271,7 +271,7 @@
                 the job of vendors easier by standardizing the format and processing expectations of
                 certain relevant markup items, and allowing them to more effectively identify how
                 content should be handled.</p></div><div class="div4">
-<h5><a name="content-producers" id="content-producers" shape="rect"/>1.3.1.4Content producers</h5><p>This type of user comprises authors, translators and other types of content author.
+<h5><a name="content-producers" id="content-producers" shape="rect"/>1.3.1.4 Content producers</h5><p>This type of user comprises authors, translators and other types of content author.
                 The markup proposed in this specification may be used by them to mark up specific
                 bits of content. Aside: The burden of inserting markup can be removed from content
                 producers by relating the ITS information to relevant bits of content in a global
@@ -284,7 +284,7 @@
                 way, apart from the ITS 2.0 standard. One way would be to allow HTML in these fields
                 if possible, or using an extra field which allows HTML input and save the plain text
                 of this extra field in the plain text field.</p></div><div class="div4">
-<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
+<h5><a name="users_machine-translation" id="users_machine-translation" shape="rect"/>1.3.1.5 Machine Translation Systems</h5><p>This type of service is intended for a broad user community ranging from developers
                 and integrators through translation companies and agencies, freelance translators
                 and post-editors to ordinary translation consumers and other types of MT employment.
                 Data categories are envisaged for supporting and guiding the different automated
@@ -295,7 +295,7 @@
                 third party users, for example, provenance information and quality scoring, and add
                 relevant information for follow-on tasks, processes and services, such as MT
                 post-editing, MT training and MT terminological enhancement.</p></div><div class="div4">
-<h5><a name="users_text_analytics" id="users_text_analytics" shape="rect"/>1.3.1.6Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation
+<h5><a name="users_text_analytics" id="users_text_analytics" shape="rect"/>1.3.1.6 Text Analytics</h5><p>These types of users fulfil the role of providing services for automatic generation
                 of metadata for improving localization, data integration or knowledge management
                 workflows. This class of users comprises of developers and integrators of services
                 that automate language technology tasks such as domain classification, named entity
@@ -305,7 +305,7 @@
                 translation systems, search result relevance in information retrieval systems, as
                 well as management and integration of unstructured data in knowledge management
                 systems.</p></div><div class="div4">
-<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7Localization Workflow Managers</h5><p>This type of users is concerend with localization workflows in which content goes
+<h5><a name="users_localization_workflow_managers" id="users_localization_workflow_managers" shape="rect"/>1.3.1.7 Localization Workflow Managers</h5><p>This type of users is concerend with localization workflows in which content goes
                 through certain steps: preparation for localization, start of the localization
                 process by e.g. a conversion into a bitext format like <a title="" href="#xliff" shape="rect">[XLIFF]</a>, the actual localization by human translators or machine
                 translation and other adaptations of content, and finally the integration of the
@@ -915,7 +915,7 @@
               used as a default query language.</p></div><div class="div3">
 <h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="d0e2063" id="d0e2063" shape="rect"/>5.3.2 XPath 1.0</h4><p>XPath 1.0 is identified by <code>xpath</code> value in <code class="its-attr-markup">queryLanguage</code>
               attribute.</p><div class="div4">
-<h5><a name="d0e2074" id="d0e2074" shape="rect"/>5.3.2.1Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
+<h5><a name="d0e2074" id="d0e2074" shape="rect"/>5.3.2.1 Absolute selector</h5><p>The absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
                 which starts with "<code>/</code>". That is, it must be an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
                   AbsoluteLocationPath</a> or union of <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">
                   AbsoluteLocationPath</a>s as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
@@ -937,7 +937,7 @@
 <strong class="hl-tag" style="color: #000096">&lt;/its:rules&gt;</strong>
 
 </pre></div><p>[Source file: <a href="examples/xml/EX-selection-global-2.xml" shape="rect">examples/xml/EX-selection-global-2.xml</a>]</p></div></div><div class="div4">
-<h5><a name="xpath-relative-selector" id="xpath-relative-selector" shape="rect"/>5.3.2.2Relative selector</h5><p>The relative selector <a href="#rfc-keywords" shape="rect">MUST</a> use a <a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath" shape="rect">RelativeLocationPath</a> or an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">AbsoluteLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
+<h5><a name="xpath-relative-selector" id="xpath-relative-selector" shape="rect"/>5.3.2.2 Relative selector</h5><p>The relative selector <a href="#rfc-keywords" shape="rect">MUST</a> use a <a href="http://www.w3.org/TR/xpath/#NT-RelativeLocationPath" shape="rect">RelativeLocationPath</a> or an <a href="http://www.w3.org/TR/xpath/#NT-AbsoluteLocationPath" shape="rect">AbsoluteLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a>.
                 The XPath expression is evaluated relative to the nodes selected by the selector
                 attribute.</p><p id="pointer-attributes-list">The following attributes point to existing
                 information: <code class="its-attr-markup">allowedCharactersPointer</code>, <code class="its-attr-markup">disambigClassPointer</code>,
@@ -956,10 +956,10 @@
                 implememtation commitment for CSS selectors. If this doesn't change CSS selectors
                 will be marked as feature at risk for the candidate recommendation draft.</p></div><p>CSS Selectors are identified by <code>css</code> value in <code class="its-attr-markup">queryLanguage</code>
               attribute.</p><div class="div4">
-<h5><a name="d0e2271" id="d0e2271" shape="rect"/>5.3.3.1Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2271" id="d0e2271" shape="rect"/>5.3.3.1 Absolute selector</h5><p>Absolute selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
                 as defined in <a href="#css3-selectors" shape="rect">Selectors Level 3</a>. Both simple
                 selectors and groups of selectors can be used.</p></div><div class="div4">
-<h5><a name="d0e2282" id="d0e2282" shape="rect"/>5.3.3.2Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
+<h5><a name="d0e2282" id="d0e2282" shape="rect"/>5.3.3.2 Relative selector</h5><p>Relative selector <a href="#rfc-keywords" shape="rect">MUST</a> be interpreted as selector
                 as defined in <a href="#css3-selectors" shape="rect">Selectors Level 3</a>. Selector is not
                 evaluated against the complete document tree but only against subtrees rooted at
                 nodes selected by selector in the <code class="its-attr-markup">selector</code> attribute.</p></div></div><div class="div3">
@@ -5699,7 +5699,7 @@
                      <code class="its-attr-markup">storageSize</code>, <code class="its-attr-markup">storageEncoding</code>?, <code class="its-attr-markup">lineBreakType</code>?</td><td rowspan="1" colspan="1">
                      <code class="its-attr-markup">its-storage-size</code>, <code class="its-attr-markup">its-storage-encoding</code>?, <code class="its-attr-markup">lits-line-break-type</code>?</td></tr></tbody></table></div><div class="div1">
 <h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents."/></a><a name="revisionlog" id="revisionlog" shape="rect"/>I Revision Log (Non-Normative)</h2><p id="changelog-since-20121206">The following log records major changes that have been
-          made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/" shape="rect">ITS 2.0 Working Draft 6 December 2012</a>.</p><ol class="depth1"><li><p>Fixed <a href="#EX-its-tool-annotation-1" shape="rect">Example 26</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58" shape="rect">issue-58</a></p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
+          made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121206/" shape="rect">ITS 2.0 Working Draft 6 December 2012</a>.</p><ol class="depth1"><li><p>Fixed <a href="#EX-its-tool-annotation-1" shape="rect">Example 26</a>, see <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/58" shape="rect">issue-58</a>.</p></li></ol><p id="changelog-since-20121023">The following log records major changes that have been
           made to this document since the <a href="http://www.w3.org/TR/2012/WD-its20-20121023/" shape="rect">ITS 2.0 Working Draft 23 October 2012</a>.</p><ol class="depth1"><li><p>Clarified usage of <a href="#domain" shape="rect">Domain</a> data category in HTML in
             response to <a href="https://www.w3.org/International/multilingualweb/lt/track/issues/56" shape="rect">issue-56</a>.</p></li><li><p>Added the <a href="#lqissueDefs" shape="rect">enabled information</a> in <a class="section-ref" href="#lqissue" shape="rect">Section 8.17: Localization Quality Issue</a>.</p></li><li><p>Updated the <a href="#Disambiguation" shape="rect">Disambiguation</a> data category.</p></li><li><p>Fine tuned the algorithm to compute the result values of the <a href="#domain" shape="rect">Domain</a> data category.</p></li><li><p>Fix on <a href="#EX-locQualityIssue-html5-local-2" shape="rect">Example 81</a>:
               <code>id</code> attribute of <code>script</code> element now the same as of containing
Received on Tuesday, 11 December 2012 14:45:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 11 December 2012 14:45:29 GMT