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

Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv24561

Modified Files:
	its20.odd 
Log Message:
some word smithing in 2.5.3

--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/17 10:46:13	1.463
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd	2013/06/17 10:54:56	1.464
@@ -715,14 +715,15 @@
               provides an overview of the mapping for all data categories.</p>
           </div>
           <div xml:id="html5-existing-markup-versus-its"><head>HTML markup with ITS 2.0 counterparts</head>
-            <p>There are four ITS 2.0 data categories, which have counterparts in HTML markup. In these cases the native HTML markup locally overrides ITS 2.0 data categories as defined here:</p>
+            <p>There are four ITS 2.0 data categories, which have counterparts in HTML markup. In these cases, native HTML markup provides some information
+              in termms of ITS 2.0 data categories. For these data categories, ITS 2.0 defines the following:</p>
             <list type="unordered">
               <item><p>The <ref target="#language-information">Language Information</ref> data category has the HTML <code>lang</code> 
-                attribute as counterpart. In XHTML the counterpart is the <code>xml:lang</code> attribute. These attributes act as 
+                attribute as counterpart. In XHTML the counterpart is the <code>xml:lang</code> attribute. These HTML attributes act as 
                 local markup for the <ref target="#language-information">Language Information</ref> data category in HTML and 
                 take <ref target="#selection-precedence">precedence</ref> over language information conveyed via a global <gi>langRule</gi>.</p></item>
               <item><p>The <ref target="#idvalue">Id Value</ref> data category has the HTML or XHTML <code>id</code> attribute as counterpart. 
-                This attribute acts as local markup for the <ref target="#idvalue">Id Value</ref> data category in HTML and takes <ref target="#selection-precedence">precedence</ref> over 
+                This HTML attribute acts as local markup for the <ref target="#idvalue">Id Value</ref> data category in HTML and takes <ref target="#selection-precedence">precedence</ref> over 
                 identifier information conveyed via a global <gi>idValueRule</gi>.</p></item>
               <item><p>The <ref target="#elements-within-text">Elements within Text</ref> data category has a set of HTML 
                 elements (the so-called <ref target="http://www.w3.org/TR/html51/dom.html#phrasing-content-1">phrasing content</ref>) as counterpart.
@@ -745,7 +746,7 @@
               <egXML xmlns="http://www.tei-c.org/ns/Examples"
                 target="examples/html5/EX-its-and-existing-HTML5-markup.html"/>
             </exemplum>
-            <p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behavior than certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. Example: use a rule to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes</code>. For additional examples see the <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
+            <p>There are also some HTML markup elements that have or can have similar, but not necessarily identical, roles and behaviors as certain ITS 2.0 data categories. For example, the HTML <code>dfn</code> element could be used to identify a term in the sense of the <ref target="#terminology">Terminology</ref> data category. However, this is not always the case and it depends on the intentions of the HTML content author. To accommodate this situation, users of ITS 2.0 are encouraged to specify the semantics of existing HTML markup in an ITS 2.0 context with a dedicated global rules file. For example, a rule can be used to define that the HTML <code>dfn</code> has the semantics of ITS <code>term="yes"</code>. For additional examples see the <ref target="http://www.w3.org/TR/2008/NOTE-xml-i18n-bp-20080213/#relating-its-plus-xhtml">XML I18N Best Practices</ref> document.</p>
 
           </div>
           <div xml:id="html5-standoff-markup-explanation"><head>Standoff markup in HTML5</head>

Received on Monday, 17 June 2013 10:55:01 UTC