- From: CVS User dfilip <cvsmail@w3.org>
- Date: Mon, 17 Jun 2013 11:48:50 +0000
- To: public-multilingualweb-lt-commits@w3.org
Update of /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20
In directory gil:/tmp/cvs-serv29120
Modified Files:
its20.odd
Log Message:
meta data -> metadata
--- /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 11:38:58 1.468
+++ /w3ccvs/WWW/International/multilingualweb/lt/drafts/its20/its20.odd 2013/06/17 11:48:50 1.469
@@ -210,7 +210,7 @@
<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
+ to concepts in the realm of metadata for internationalization, translation, and
localization related to core Web technologies such as XML. ITS does for example assist
in production scenarios in which parts of an XML-based document should not be
translated. ITS 2.0 bears many commonalities with its predecessor, <ref
@@ -233,7 +233,7 @@
<exemplum xml:id="EX-motivation-its-1">
<head>Document in which some content must not be translated</head>
- <p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit meta data is needed to resolve the issue.</p>
+ <p>In this document it is difficult to distinguish between those <code>string</code> elements that should be translated and those that must not be translated. Explicit metadata is needed to resolve the issue.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-1.xml"/>
</exemplum>
@@ -241,7 +241,7 @@
<exemplum xml:id="EX-motivation-its-2">
<head>Document that uses two different ITS mechanisms to indicate that some parts must not be translated.</head>
- <p>ITS provides two mechanisms to explicitly associate meta data with one or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <ref target="#basic-concepts-overinher">overwrites</ref> this rule for two of the <code>data</code> elements of type <val>text</val>.</p>
+ <p>ITS provides two mechanisms to explicitly associate metadata with one or more pieces of content (e.g. XML nodes): a <ref target="#basic-concepts-selection-global">global</ref>, rule-based approach as well as a <ref target="#basic-concepts-selection-local">local</ref>, attribute-based approached). Here, for instance, a rule first specifies that no <code>data</code> element must be translated; later, an attribute <ref target="#basic-concepts-overinher">overwrites</ref> this rule for two of the <code>data</code> elements of type <val>text</val>.</p>
<egXML xmlns="http://www.tei-c.org/ns/Examples"
target="examples/xml/EX-motivation-its-2.xml"/>
</exemplum>
@@ -254,18 +254,18 @@
<list type="ordered">
- <item>Provide meta data (e.g. <q>Do not translate</q>) to assist internationalization-related processes</item>
+ <item>Provide metadata (e.g. <q>Do not translate</q>) to assist internationalization-related processes</item>
- <item>Use XPath (so-called <ref target="#selection-global">global appraoch</ref>) to associate meta data with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the meta data straight onto the XML nodes themselves (so-called <ref target="#def-local-attributes">local approach</ref>)</item>
+ <item>Use XPath (so-called <ref target="#selection-global">global appraoch</ref>) to associate metadata with specific XML nodes (e.g. all elements named <code>uitext</code>) or put the metadata straight onto the XML nodes themselves (so-called <ref target="#def-local-attributes">local approach</ref>)</item>
- <item>Work with a well-defined set of meta data categories or values (e.g. only the values <val>yes</val> and <val>no</val> for certain data categories)</item>
+ <item>Work with a well-defined set of metadata categories or values (e.g. only the values <val>yes</val> and <val>no</val> for certain data categories)</item>
- <item>Take advantage of existing meta data (e.g. terms already marked up with HTML markup such as <code>dt</code>)</item></list>
+ <item>Take advantage of existing metadata (e.g. terms already marked up with HTML markup such as <code>dt</code>)</item></list>
<p>This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to
- identify additional meta data categories for internationalization-related processes. The
+ identify additional metadata categories for internationalization-related processes. The
<ref target="http://www.w3.org/International/its/ig/">ITS Interest Group</ref> for
example compiled a list of additional data categories (see this <ref
target="http://www.w3.org/International/multilingualweb/limerick/slides/lieske.pdf"
@@ -309,8 +309,8 @@
<item>Open standards endeavours (e.g. related to <ptr target="#xliff1.2" type="bibref"/>, <ptr
target="#xliff2.0" type="bibref"/> and <ptr target="#nif-reference" type="bibref"/>)
- that are interested for example in information sharing, and lossless round tripping of
- meta data in localization workflows</item></list>
+ that are interested for example in information sharing, and lossless roundtrip of
+ metadata in localization workflows</item></list>
@@ -772,9 +772,9 @@
<p>ITS 2.0 defines an algorithm to convert XML or HTML documents (or their DOM
representations) that contain ITS metadata to the RDF format based on <ptr
target="#nif-reference" type="bibref"/>. NIF is an RDF/OWL-based format that aims at interoperability between Natural Language Processing (NLP) tools, language resources and annotations.</p>
- <p>The conversion <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content related triples and relies on an <ref target="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</ref>.</p>
+ <p>The conversion from <ref target="#conversion-to-nif">ITS 2.0 to NIF</ref> results in RDF triples. These triples represent the textual content of the original document as RDF typed information. The ITS annotation is represented as properties of content-related triples and relies on an <ref target="http://www.w3.org/2005/11/its/rdf#">ITS RDF vocabulary</ref>.</p>
- <p>The back conversion from <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively. One motivation for the back conversion is a round tripping work flow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <ref target="#textanalysis">Text Analysis</ref> markup. The outcome are HTML documents with linked information, see <ptr target="#EX-text-analysis-html5-local-1" type="exref"/>.</p></div>
+ <p>The back conversion from <ref target="#nif-backconversion">NIF to ITS 2.0</ref> is defined informatively. One motivation for the back conversion is a roundtrip workflow like: 1) conversion to NIF 2) in NIF representation detection of named entities using NLP tools 3) back conversion to HTML and generation of <ref target="#textanalysis">Text Analysis</ref> markup. The outcome are HTML documents with linked information, see <ptr target="#EX-text-analysis-html5-local-1" type="exref"/>.</p></div>
<div xml:id="mapping-XLIFF"><head>ITS and XLIFF</head>
<p>The XML Localization Interchange File Format <ptr target="#xliff1.2" type="bibref"/> is an OASIS standard that enables translatable source text and its translation to be passed between different tools within localization and translation workflows. <ptr target="#xliff2.0" type="bibref"/> is the successor of <ptr target="#xliff1.2" type="bibref"/> and under development. XLIFF has been widely implemented in various translation management systems, computer aided translation tools and in utilities for extracting translatable content from source documents and merging back the content in the target language..</p>
@@ -1640,7 +1640,7 @@
<div xml:id="conversion-to-nif">
<head>Conversion to NIF</head>
<p>This section defines an algorithm to convert XML or HTML documents (or their DOM
- representations) that contain ITS metadata to the RDF-based format based on <ptr
+ representations) that contain ITS metadata to the RDF format based on <ptr
target="#nif-reference" type="bibref"/>. The conversion results in RDF triples.</p>
<note><p>The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can
produce a lot of <quote>phantom</quote> predicates from excessive whitespace, which 1)
@@ -3090,7 +3090,7 @@
target="http://www.w3.org/TR/mlw-metadata-us-impl/">ITS 2.0 High-level Usage
Scenarios</ref>) is on “single engine” environments, ITS 2.0 (for example in the
context of the <ref target="#domain">Domain</ref> data category) can accommodate
- "workflow/multi engine" scenarios.</p>
+ ""workflow/multi engine" scenarios.</p>
<p>Example:</p>
<list type="unordered">
Received on Monday, 17 June 2013 11:48:51 UTC