- From: Felix Sasaki <fsasaki@w3.org>
- Date: Mon, 19 Nov 2012 13:55:44 +0100
- To: public-multilingualweb-lt@w3.org
Hi all, I just realized that I had done edits without a CVS commit. Now done, see the diff before the commit below. Maybe we can find a reviewer for these, see agenda item 9) at http://lists.w3.org/Archives/Public/public-multilingualweb-lt/2012Nov/0136.html Best, Felix @@ -190,9 +190,6 @@ <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> - <item>Where ITS 1.0 data categories are implemented in XML, the - implementation must be conformant with the ITS 1.0 approach to XML - to claim conformance to ITS 2.0.</item> </list> </div> <div xml:id="new-principles"> @@ -218,7 +215,7 @@ <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="#translation-agent-provenance">Translation Agent Provenance</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> @@ -512,15 +509,15 @@ <head>Out of Scope</head> <p>The definition of what a localization process or localization parameters must address is outside the scope of this standard and it does not address all of - the mechanisms or data formats (sometimes called Localization Properties) + the mechanisms or data formats (sometimes called localization project parameters) that may be needed to configure localization workflows or process specific formats. However, it does define standard data categories that may be used in defining localization workflows or processing specific formats.</p> <note> - <p>“<term>XML localization properties</term>” is a generic term to name the + <p>“<term>XML localization project parameters</term>” is a generic term to name the mechanisms and data formats that allow localization tools to be configured in order to process a specific XML format. Examples of XML - localization properties are the Trados “DTD Settings” file, and the SDLX + localization project parameters are the Trados “DTD Settings” file, and the SDLX “Analysis” file.</p> </note> </div> @@ -528,7 +525,7 @@ <head>Important Design Principles</head> <p>Abstraction via <emph>data categories</emph>: ITS defines <term>data categories</term> as an abstract notion for information needed for the - internationalization and localization of XML schemas and documents and HTML5 + internationalization and localization of XML documents and HTML5 documents. This abstraction is helpful in realizing independence from any one particular implementation (e.g., as an element or attribute). (See <ptr target="#def-datacat" type="specref"/> for a definition of the term data @@ -536,9 +533,8 @@ definition of the various ITS data categories, and subsections in <ptr target="#datacategory-description" type="specref"/> for the data category implementations.)</p> - <p>Powerful <emph>selection mechanism:</emph> For ITS markup that appears in an - XML instance, which XML nodes the ITS-related information pertains to must - be clearly defined. Thus, ITS defines <ref target="#termdef-selection" + <p>Powerful <emph>selection mechanism:</emph> For ITS markup that appears in an XML instance, the XML nodes to which the + ITS-related information pertains must be clearly defined. Thus, ITS defines <ref target="#termdef-selection" >selection</ref> mechanisms to specify to what parts of an XML document an ITS data category and its values should be applied. Selection relies on the information which is given in the XML Information Set <ptr @@ -588,7 +584,8 @@ <item>ITS has no dependency on technologies which are still under development.<?Pub Caret?></item> <item>ITS fits with existing work in the W3C architecture (e.g. use of <ptr - target="#xpath" type="bibref"/> for the selection mechanism).</item> + target="#xpath" type="bibref"/> for the selection mechanism and use of IRI's <ptr target="#rfc3987" type="bibref"/> as references + to relevant external resources).</item> </list> </div> @@ -1643,8 +1640,7 @@ <note> <p>The precedence order fulfills the same purpose as the built-in template rules of <ptr target="#xslt10" type="bibref"/>. Override semantics are - always complete, that is all information that is specified in one rule - element is overridden by the next one.</p> + always complete, that is all information provided via lower precedence is overriden by the higher precedence. E.g. defaults are overridden by inherited values, these are overriden by nodes selected via global rules, and these are overriden via local markup.</p> </note> <exemplum> <head>Conflicts between selections of ITS information which are resolved @@ -2136,7 +2132,7 @@ </row> <row> <cell> - <ref target="#translation-agent-provenance">Translation Agent Provenance</ref> + <ref target="#provenance">Provenance</ref> </cell> <cell>Yes</cell> @@ -2144,8 +2140,7 @@ <cell>Yes</cell> <cell>Yes</cell> <cell>None</cell> - <cell>Textual content of element, <emph>including</emph> child elements, - but excluding attributes</cell> + <cell>Textual content of element, <emph>including</emph> child elements and attributes</cell> <cell>tbd</cell> <cell>tbd</cell> </row> @@ -3200,9 +3195,9 @@ <item>To specify the target type class, exactly one of the following: <list> <item><p>A <att>disambigClassPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> - pointing to a node specifying the entity type class behind the selector.</p></item> + pointing to a node specifying the type of entity or concept class behind the selector.</p></item> <item><p>A <att>disambigClassRefPointer</att> attribute that contains a <ref target="#selectors">relative selector</ref> - pointing to a node that holds a IRI that specifies the entity type class behind the selector.</p></item> + pointing to a node that holds a IRI that specifies the type of entity or concept class behind the selector.</p></item> </list> </item> <item>To specify the target identity, exactly one of the following: @@ -3215,6 +3210,9 @@ </item> </list> </item> + <item>An optional <att>disambigGranularity</att> attribute that contains a string, specifying the + granularity level of the disambiguation. The value can be one of the following identifiers: + <code>lexicalConcept</code>, <code>ontologyConcept</code>, or <code>entity</code></item> </list> <p>For an example, see <ptr type="exref" target="#EX-disambiguation-html5-rdfa-companion-document"/>.</p> <p xml:id="disambiguation-local">LOCAL: The following local markup is @@ -3229,8 +3227,7 @@ <list> <item>To specify the target type class: <list> - <item>A <att>disambigClassRef</att> attribute that contains a IRI, specifying the type class - of the concept or entity behind the selector.</item> + <item>A <att>disambigClassRef</att> attribute that contains a IRI, specifying the type of entity or concept class behind the selector.</item> </list> </item> <item>To specify the target identity, exactly one of the following: @@ -3368,26 +3365,26 @@ </div>
Received on Monday, 19 November 2012 12:56:16 UTC