Internationalization Tag Set (ITS) Version 2.0

1.1 Overview

ITS 2.0 Content or software that is authored in one language (so-called source 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 multilingual production in many cases encompasses three phases: internationalization, translation, and localization (see the W3C's Internationalization Q&A for more information related to these concepts).

From the viewpoints of feasibility, cost, and efficiency, it is important that the original material is suitable for downstream phases such as translation. This is achieved by appropriate design and development. The corresponding phase is referred to as internationalization. A proprietary XML vocabulary may be internationalized by defining special markup to specify directionality in mixed direction text.

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. For example national or international laws may regulate linguistic dimensions like mandatory terminology or standard phrases in order to promote or ensure a translation's fidelity.

Although an agreed-upon definition of the localization phase is missing, this phase is usually seen as encompassing activities 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.

The technology described in this document – the Internationalization Tag Set (ITS) 2.0 addresses some of the challenges and opportunities related to add internationalization, translation, and localization. ITS 2.0 in particular contributes to concepts in the realm of metadata for internationalization, translation, and localization related to core Web content, technologies such as XML. ITS does for the benefit example assist in production scenarios, in which parts of localization, an XML-based document are to be excluded from translation. ITS 2.0 bears many commonalities with its predecessor, ITS 1.0 but provides additional concepts that are designed to foster enhanced automated processing – e.g. based on language technologies, and internationalization. The technology such as entity recognition – related to multilingual Web content.

Like ITS 1.0, ITS 2.0 specification both identifies concepts (such as “Translate”) that are important for internationalization and localization, “Translate” ), and defines implementations of these concepts (termed “ITS data categories”) as a set of elements and attributes called the Internationalization Tag Set (ITS) . The document provides implementations for HTML, serializations in NIF (NLP Interchange Format) , and provides definitions of ITS elements and attributes are provided in the form of XML Schema [XML Schema] and RELAX NG [RELAX NG] . This document aims (normative). Since one major step from ITS 1.0 to realize many of the ideas formulated in ITS 2.0 relates to coverage for HTML, ITS 2.0 also establishes a relationship between ITS markup and the various HTML flavors. Furthermore, ITS 2.0 Requirements document , in [ITS REQ] suggests when and how to leverage processing based on the XML Localization Interchange File Format ( [XLIFF 1.2] and [Localizable DTDs] [XLIFF 2.0] ), as well as the Natural Language Processing Interchange Format [NIF] .

Not all requirements listed there For the purpose of an introductory illustration, here is a series of examples related to the question, how ITS can indicate that certain parts of a document are addressed not intended for translation.

"color: #000096"><resources>
  
"color: #000096"><section id="Homepage">
    
"color: #000096"><arguments>
      
"color: #000096"><string>page</string>
      
"color: #000096"><string>childlist</string>
    
"color: #000096"></arguments>
    
"color: #000096"><variables>
      
"color: #000096"><string>POLICY</string>
      
"color: #000096"><string>Corporate Policy</string>
    
"color: #000096"></variables>
    
"color: #000096"><keyvalue_pairs>
      
"color: #000096"><string>Page</string>
      
"color: #000096"><string>ABC Corporation - Policy Repository</string>
      
"color: #000096"><string>Footer_Last</string>
      
"color: #000096"><string>Pages</string>
      
"color: #000096"><string>bgColor</string>
      
"color: #000096"><string>NavajoWhite</string>
      
"color: #000096"><string>title</string>
      
"color: #000096"><string>List of Available Policies</string>
    
"color: #000096"></keyvalue_pairs>
  
"color: #000096"></section>

"color: #000096"></resources>

ITS proposes several mechanisms, which differ among others in an as yet unwritten best practice document on multilingual Web content), or may terms of the usage scenario/user types for which the mechanism is most suitable.

"color: #000096"><resources xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><its:rules version="2.0">
    
"color: #000096"><its:translateRule selector="//arguments" translate="no"/>
    
"color: #000096"><its:translateRule selector="//keyvalue_pairs/string[(position() mod 2)=1]" translate="no"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><section id="Homepage">
    
"color: #000096"><arguments>
      
"color: #000096"><string>page</string>
      
"color: #000096"><string>childlist</string>
    
"color: #000096"></arguments>
    
"color: #000096"><variables>
      
"color: #000096"><string its:translate="no">POLICY</string>
      
"color: #000096"><string>Corporate Policy</string>
    
"color: #000096"></variables>
    
"color: #000096"><keyvalue_pairs>
      
"color: #000096"><string>Page</string>
      
"color: #000096"><string>ABC Corporation - Policy Repository</string>
      
"color: #000096"><string>Footer_Last</string>
      
"color: #000096"><string>Pages</string>
      
"color: #000096"><string>bgColor</string>
      
"color: #000096"><string its:translate='no'>NavajoWhite</string>
      
"color: #000096"><string>title</string>
      
"color: #000096"><string>List of Available Policies</string>
    
"color: #000096"></keyvalue_pairs>
  
"color: #000096"></section>

"color: #000096"></resources>

1.1 Relation to 1.2 General motivation for going beyond ITS 1.0 and New Principles

The basics of ITS 1.0 are simple:

1. ITS 2.0 has the following relations Provide metadata (e.g. “Do not translate”) to ITS 1.0 [ITS 1.0] : assist internationalization-related processes

2. It adopts and maintains Use XPath (so-called global approach ) to associate metadata with specific XML nodes (e.g. all elements named uitext ) or put the following principles from ITS 1.0: metadata straight onto the XML nodes themselves (so-called local approach )

3. It adopts Work with a well-defined set of metadata categories or values (e.g. only the use values "yes" and "no" for certain data categories)

4. Take advantage of existing metadata (e.g. terms already marked up with HTML markup such as dt )

This conciseness made real-world deployment of ITS 1.0 easy. The deployments helped to identify additional metadata categories for internationalization-related processes. The ITS Interest Group for example compiled a list of additional data categories to define discrete units (see this related summary ). Some of functionality these were then defined in ITS 2.0: ID Value ,local Elements Within Text ,Preserve Space ,and Locale Filter .Others are still discussed as requirements for possible future versions of ITS:

1. “Context” = What specific related information might be helpful?

2. It adopts “Automated Language” = Does this content lend itself to automatic processing?

The real-world deployments also helped to understand that for the separation of data category definition from Open Web Platform – the mapping ITS 1.0 restriction to XML was an obstacle for quite a number of environments. What was missing was, for example, the data category following:

1. Applicability of ITS to formats such as HTML in general, and HTML5 in particular

2. Easy use of ITS in various Web-exposed (multilingual) Natural Language Processing contexts

3. Computer-supported linguistic quality assurance

4. Content Management and translation platforms

5. Cross-language scenarios

6. Content enrichment

7. Support for W3C provenance [PROV-DM] ,“information about entities, activities, and people involved in producing a given content format piece of data or thing, which can be used to form assessments about its quality, reliability or trustworthiness”

8. It adopts Provisions for extended deployment in Semantic Web/Linked Open Data scenarios

ITS 2.0 was created by an alliance of stakeholders who are involved in content for global use. Thus, ITS 2.0 was developed with input from/with a view towards the conformance principle following:

• Providers of ITS1.0 that an implementation only needs content management and machine translation solutions who want to implement one data category easily integrate for efficient content updates in multilingual production chains

• Language technology providers who want to claim conformance automatically enrich content (e.g. via term candidate generation, entity recognition or disambiguation) in order to facilitate human translation

• Open standards endeavours (e.g. related to [XLIFF 1.2] ,[XLIFF 2.0] and [NIF] ) that are interested for example in information sharing, and lossless roundtrip of metadata in localization workflows

One example outcome of the resulting synergies is the ITS 2.0 Tool Annotation mechanism. It addresses the provenance-related requirement by allowing ITS processors to leave a trace: ITS processors can basically say “It is me that generated this bit of information”. Another example are the [NIF] related details of ITS 2.0, which provide a non-normative approach to couple Natural Language Processing with concepts of the Semantic Web.

1.3 Usage Scenarios

ITS 2.0 supports all The [ITS 1.0] introduction states: “ITS is a technology to easily create XML, which is internationalized and can be localized effectively”. In order to make this tangible, ITS 1.0 data category definitions provided examples for users and adds new definitions, with usages .Implicitly, these examples carried the exceptions information that ITS covers two areas: one that is related to the static dimension of Directionality mono-lingual content, and Ruby. one that is related to the dynamic dimension of multilingual production.

• Static mono-lingual (for example, the area of content authors): This part of the content has the directionality “right-to-left”.

• Dynamic multilingual: (for example, the area of machine translation systems): This part of the content has to be left untranslated.

Although ITS 1.0 made no assumptions about possible phases in a multilingual production process chain, it was slanted towards a simple three phase “write→internationalize→translate” model. Even a birds-eye-view at ITS 2.0 adds shows that ITS 2.0 explicitly targets a number much more comprehensive model for multilingual content production. The model comprises support for multilingual content production phases such as:

• Internationalization

• Pre-production (e.g. related to marking terminology)

• Automated content enrichment (e.g. automatic hyperlinking for entities)

• Extraction/filtering of new data categories not found in ITS 1.0. translation-relevant content

• While Segmentation

• Leveraging (e.g. of existing translation-related assets such as translation memories)

• Machine Translation (e.g. geared towards a specific domain)

• Quality assessment or control of source language or target language content

• Generation of translation kits (e.g. packages based on XLIFF)

• Post-production

• Publishing

The document [MLW US IMPL] lists a large variety of usage scenarios for ITS 2.0. Most of them are composed from the aforementioned phases.

In a similar vein, ITS 2.0 takes a much more comprehensive view on the actors that may participate in a multilingual content production process. ITS 1.0 addressed only XML, annotations (e.g. local markup for the Terminology data category) most of the time were conceived as being closely tied to human actors such as content authors or information architects. ITS 2.0 specifies implementations raises non-human actors such as word processors/editors, content management systems, machine translation systems, term candidate generators, entity identifiers/disambiguators to the same level. This change among others is reflected by the ITS 2.0 Tool Annotation ,which allows systems to record that they have processed a certain part of data categories in both XML and HTML. content.

1.1.2 Ruby 1.4 High-level differences between ITS 1.0 and ITS 2.0

The differences between ITS 1.0 and ITS 2.0 can be summarized as follows.

Coverage of [HTML5] :ITS 1.0 can be applied to XML content. ITS 2.0 extends the coverage to [HTML5] .Explanatory details about ITS 2.0 and [HTML5] are given in Section 2.5: Specific HTML support .

Addition of data categories :ITS 2.0 provides additional data categories and modifies existing ones. A summary of all ITS 2.0 data categories is given in Section 2.1: Data Categories .

Modification of data categories :

• ITS 1.0 provided the Ruby data category . ITS 2.0 does not provide ruby since because at the time of writing, a stable model for ruby was not available. There are ongoing discussions about writing the ruby model in HTML5 . was still under development. Once these discussions are settled, the Ruby data category possibly will be reintroduced, in a subsequent version of ITS, the ruby ITS.

• The Directionality data category may reflects directionality markup in [HTML 4.01] .The reason is that enhancements are being discussed in the context of HTML5 that are expected to change the approach to marking up directionality, in particular to support content whose directionality needs to be re-introduced. isolated from that of surrounding content. However, these enhancements are not finalized yet. They will be reflected in a future revision of ITS.

Additional or modified mechanisms: The following mechanisms from ITS 1.0 have been modified or added to ITS 2.0:

• ITS 1.0 used only XPath as the mechanism for selecting nodes in global rules .ITS 2.0 allows for choosing the query language of selectors .The default is XPath 1.0. An ITS 2.0 processor is free to support other selection mechanisms, like CSS selectors or other versions of XPath.

• In global rules it is now possible to set variables for the selectors (XPath expression). The param element serves this purpose.

• ITS 2.0 has an ITS Tools Annotation mechanism to associate processor information with the use of individual data categories. See Section 2.6: Traceability for details.

Mappings: ITS 2.0 provides a non-normative algorithm to convert ITS 2.0 information into [NIF] and links to guidance about how to relate ITS 2.0 to XLIFF. See Section 2.7: Mapping and conversion for details.

Changes to the conformance section :The Section 4: Conformance tells implementers how to implement ITS. For ITS 2.0, the conformance statements related to Ruby have been removed. For [HTML5] ,a dedicated conformance section has been created. Finally, a conformance clause related to Non-ITS elements and attributes has been added.

1.5 Extended implementation hints

As a general guidance, implementations of ITS 2.0 are encouraged to use a normalizing transcoder .It converts from a legacy encoding to a Unicode encoding form and ensures that the result is in Unicode Normalization Form C. Further information on the topic of Unicode normalization is provided in [Charmod Norm] .

2.1 Data Categories

A key concept of ITS 2.0 is the abstract notion of data categories are intended to . Data categories define the information that can be format neutral, with support conveyed via ITS. An example is the Translate data category. It conveys information about translatability of content.

Section 8: Description of Data Categories defines data categories. It also describes their implementation, i.e. ways to use them for XML, HTML, and NIF: a example in an XML context. The motivation for separating data category definitions from their implementation only needs is to support enable different implementations with the following characteristics:

• For various types of content (XML in general or HTML ).

• For a single piece of content, e.g. a p element. This is the so-called local approach .

• For several pieces of content format mapping in order to support one document or even a claim set of ITS 2.0 conformance. documents. This is the so-called global approach .

• For a complete markup vocabulary. This is done by adding ITS 2.0 provides algorithms markup declarations to generate NIF out of HTML or XML with ITS 2.0 metadata. the schema for the vocabulary.

A global implementation of ITS 2.0 requires at least provides the XPath version 1.0 . Other versions following data categories:

• Translate :expresses information about whether a selected piece of XPath content is intended for translation or other query languages (e.g., CSS Selectors) can be expressed via a dedicated queryLanguage attribute. not.

• Localization Note :communicates notes to localizers about a particular item of content.

• The new Terminology :marks terms and optionally associates them with information, such as definitions or references to a term data categories included in ITS 2.0 are: base.

• Directionality :specifies the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional algorithm.

• Language Information :expresses the language of a given piece of content.

• Elements Within Text: expresses how content of an element is related to the text flow (constitutes its own segment like paragraphs, is part of a segment like emphasis marker etc.).

• Domain : identifies the topic or subject of the annotated content for translation-related applications.

• Text Analysis : annotates content with lexical or conceptual information (e.g. for the purpose of contextual disambiguation).

• Locale Filter : specifies that a piece of content is only applicable to certain locales.

• Provenance : communicates the identity of agents that have been involved processing content.

• External Resource : indicates reference points in a resource outside the document that need to be considered during localization or translation. Examples of such resources are external images and audio or video files.

• Target Pointer : associates the markup node of a given source content (i.e. the content to be translated) and the markup node of its corresponding target content (i.e. the source content translated into a given target language). This is relevant for formats that hold the same content in different languages inside a single document.

• Id Value : identifies a value that can be used as unique identifier for a given part of the content.

• Preserve Space : indicates how whitespace is to be handled in content.

• Localization Quality Issue : describes the nature and severity of an error detected during a language-oriented quality assurance (QA) process.

• Localization Quality Rating : expresses an overall measurement of the localization quality of a document or an item in a document.

• MT Confidence : indicates the confidence that MT systems provide about their translation.

• Allowed Characters : specifies the characters that are permitted in a given piece of content.

• Storage Size : specifies the maximum storage size of a given piece of content.

Most of the existing ITS 1.0 data categories are included and new ones have been added. Modifications of existing ITS 1.0 data categories are summarized in Section 1.4: High-level differences between ITS 1.0 and ITS 2.0 .

1.2 Motivation for ITS 2.2 Selection

Content or software that is authored in Information (e.g. “translate this”) captured by an ITS data category always pertains to one language (the source language ) is often made available in additional languages or adapted more XML or HTML nodes, primarily element and attribute nodes. In a sense, the relevant node(s) get “selected”. Selection may be explicit or implicit. ITS distinguishes two mechanisms for explicit selection: (1) local and (2) global (via rules ). Both local and global approaches can interact with regard each other, and with additional ITS dimensions such as inheritance and defaults.

The mechanisms defined for ITS selection resemble those defined in [CSS 2.1] .The local approach can be compared to other cultural aspects. This is done through a process called localization , where the original material is translated style attribute in HTML/XHTML, and adapted the global approach is similar to the target audience. style element in HTML/XHTML:

• In addition, document formats expressed by schemas may be used by people The local approach puts ITS markup in different parts the relevant element of the world, and these people may need special markup to support host vocabulary (e.g. the local language or script. For example, people authoring author element in languages such as Arabic, Hebrew, Persian, or Urdu need special DocBook)

• The global rule-based approach puts the ITS markup to specify directionality in mixed direction text. elements defined by ITS itself (namely the rules element)

From the viewpoints of feasibility, cost, ITS usually uses XPath in rules for identifying nodes although CSS Selectors and efficiency, it is important that the original material should other query languages can in addition be suitable for localization. This is achieved implemented by appropriate design and development, and the corresponding process is referred to as internationalization. For a detailed explanation of the terms “localization” and “internationalization”, see [l10n i18n] . applications.

The increasing usage of ITS 2.0 can be used with XML as a medium for documentation-related content documents (e.g. a DocBook and DITA as formats for writing structured documentation, well suited to computer hardware and software manuals) and software-related content article), HTML documents, document schemas (e.g. the eXtensible User Interface Language [XUL] ) creates challenges and opportunities an XML Schema document for a proprietary document format), or data models in RDF.

The following two examples provide more details about the domain of XML internationalization distinction between the local and localization. global approach, using the Translate data category as an example.

"color: #000096"><article xmlns="http://docbook.org/ns/docbook"
         
"color: #F5844C">xmlns:its="http://www.w3.org/2005/11/its"
         
"color: #F5844C">its:version="2.0" version="5.0" xml:lang="en">
  
"color: #000096"><info>
    
"color: #000096"><title>An example article</title>
    
"color: #000096"><author its:translate="no">
      
"color: #000096"><personname>
        
"color: #000096"><firstname>John</firstname>
        
"color: #000096"><surname>Doe</surname>
      
"color: #000096"></personname>
      
"color: #000096"><affiliation>
        
"color: #000096"><address><email>foo@example.com</email></address>
      
"color: #000096"></affiliation>
    
"color: #000096"></author>
  
"color: #000096"></info>
  
"color: #000096"><para>This is a short article.</para>

"color: #000096"></article>

"color: #000096"><myTopic xmlns="http://mynsuri.example.com" id="topic01" xml:lang="en-us">
  
"color: #000096"><prolog>
    
"color: #000096"><title>Using ITS</title>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
      
"color: #000096"><its:translateRule selector="//n:term" translate="no" xmlns:n="http://mynsuri.example.com"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><p>ITS defines <term>data category</term> as an abstract concept for a particular type of
      information for internationalization and localization of XML schemas and documents.</p>
  
"color: #000096"></body>

"color: #000096"></myTopic>

1.3.2 Ways to Use ITS 2.3 Overriding, Inheritance and Defaults

The ITS specification proposes several mechanisms for supporting worldwide use and effective internationalization and localization of content. We will sketch them below by looking at them from the perspectives power of certain user types. For the purpose of illustration, we will demonstrate how ITS can indicate that certain parts of content should or should not be translated. A content author uses an attribute on selection mechanisms comes at a particular element price: rules related to overriding/precedence and inheritance have to say that the text in the element should not be translated. established.

The its:translate="no" attributes indicate that document in Example 5 shows how inheritance and overriding work for the path and the directory. Then from there, run batch file [Source file: examples/xml/EX-ways-to-use-its-1.xml Translate ] data category:

• A content author or information architect uses markup at the top of the document to identify a particular type of element or context in which the content should not be translated. The ITS default is that all elements are translatable.

• Example 4: Use of ITS by information architect

• The translateRule element is used declared in the header of overrides the document to indicate that none of default for the path head or element inside text and for all its children.

• Because the cmd title elements should element is actually translatable, the global rule needs to be translated. To re-compile all the modules of the Zebulon toolkit you need to go in the directory. Then from there, run batch file [Source file: examples/xml/EX-ways-to-use-its-2.xml ] overridden by a local its:translate="yes" .

• A processor may insert markup at In the top body of the document which links to ITS information outside of the document. default applies, and its:translate="no" is used to set "faux pas" as non-translatable.

"color: #000096"><text xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><head>
    
"color: #000096"><revision>Sep-10-2006 v5</revision>
    
"color: #000096"><author>Ealasaidh McIan</author>
    
"color: #000096"><contact>ealasaidh@hogw.ac.uk</contact>
    
"color: #000096"><title its:translate="yes">The Origins of Modern Novel</title>
    
"color: #000096"><its:rules version="2.0">
      
"color: #000096"><its:translateRule translate="no" selector="/text/head"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><div xml:id="intro">
      
"color: #000096"><head>Introduction</head>
      
"color: #000096"><p>It would certainly be quite a <span its:translate="no">faux pas</span> to start a
        dissertation on the origin of modern novel without mentioning the <tl>Epic of
        Gilgamesh</tl>...</p>
    
"color: #000096"></div>
  
"color: #000096"></body>

"color: #000096"></text>

The rules element contains several ITS rules that For XML content, data category specific defaults are common to different documents. One provided. These are independent of them is a translateRule element that indicates that no [Source file: examples/xml/EX-ways-to-use-its-4.xml the actual XML markup vocabulary. Example for the Translate ] data category: translate="yes" for elements, and translate="no" for attributes.

A schema developer integrates ITS markup declarations in his schema to allow users For [HTML5] ,several HTML5 elements and attributes map exactly to indicate ITS 2.0 data categories. Hence that specific parts of the content should not be translated. [Ed. note: Following schema example has to updated once we have final XSD schema for HTML markup is normatively interpreted as ITS 2.0] Example 7: An XSD schema 2.0 data category information (see Section 2.5.3: HTML markup with ITS declaration The declarations 2.0 counterparts for the translate attribute is added to a group of common attributes </xs:schema> more information).

[Source file: examples/xml/EX-ways-to-use-its-5.xsd ] 2.4 Adding Information or Pointing to Existing Information

The first two approaches above Data categories can be likened add information or point to information for the use of CSS in [XHTML 1.0] . Using selected nodes. For example, the Localization Note data category can add information to selected nodes (using a style locNote attribute, an XHTML content author may assign a color element), or point to a particular paragraph. That author could also have used existing information elsewhere in the style document (using a locNotePointer element at attribute).

The data category overview table ,in Section 8.1: Position, Defaults, Inheritance, and Overriding of Data Categories ,provides an overview of which data categories allow the top addition of information and which allow to point to existing information.

Adding information and pointing to existing information are mutually exclusive ; attributes for adding information and attributes for pointing to the page same information are not allowed to say that all paragraphs of a particular class or in a particular context would be colored red. appear at the same rule element.

1.4 Usage in 2.5 Specific HTML support

For applying ITS 2.0 data categories to HTML, four five aspects must be considered: are of importance:

1. referencing global rules Global approach in HTML5

2. specifities of inserting local Local Approach

3. HTML markup with ITS 2.0 data categories counterparts

4. relationship between HTML Standoff markup and data categories, and in HTML5

5. Version of HTML version.

In the following sections these aspects are briefly discussed.

"color: blue"><!DOCTYPE html>

<html>
  
    
    
    
  
  
     element should not be translated.
      Of course there are always exceptions: certain code values should be translated,
      e.g. to a value in your language like 
  
</html>

  "color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>Translate flag global rules example</title>
    
"color: #000096"><link href=EX-translateRule-html5-1.xml rel=its-rules>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>This sentence should be translated, but code names like
      the <code>span</code> element should not be translated.
      Of course there are always exceptions: certain 
      code values should be translated, e.g. to a value 
      in your language like <code translate=yes>warning</code>.</p>
  
"color: #000096"></body>

"color: #000096"></html>

<its:rules
version
=
"2.0"
xmlns:its
=
"http://www.w3.org/2005/11/its"
xmlns:h
=
"http://www.w3.org/1999/xhtml"
>
<its:translateRule
translate
=
"no"
selector
=
"//h:code"
/>
</its:rules>

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
           
"color: #F5844C">xmlns:h="http://www.w3.org/1999/xhtml">
  
"color: #000096"><its:translateRule translate="no" selector="//h:code"/>

"color: #000096"></its:rules>

"color: blue"><!DOCTYPE html>
<html>  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>Translate flag global rules example</title>
    
"color: #000096"><script type=application/its+xml id=ru1>
      
"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
           
"color: #F5844C">xmlns:h="http://www.w3.org/1999/xhtml">
      
"color: #000096"><its:translateRule translate="no" selector="//h:code"/>
    
"color: #000096"></its:rules>
    
"color: #000096"></script>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>This sentence should be translated, but code names like
      the <code>span</code> element should not be translated.
      Of course there are always exceptions: certain
      code values should be translated, e.g. to a value in
      your language like <code translate=yes>warning</code>.</p>
  
"color: #000096"></body>

"color: #000096"></html>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
      
"color: #000096"><title>HTML native markup expressing three ITS 2.0 data categories</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p id="p1" translate="no">This is a <em>motherboard</em> and image: 
      
"color: #000096"><img src="http://example.com/myimg.png" alt="My image"/>.</p>
  
"color: #000096"></body>

"color: #000096"></html>

1.5 ITS and XLIFF 2.6 Traceability

The ITS 2.0 has no normative dependency on [XLIFF] (XML Interchange File format). Nevertheless, important usage scenarios for ITS 2.0 are 1) XLIFF generation with e.g. HTML as an input file containing ITS 2.0 metadata, and 2) Direct representation of ITS 2.0 data categories within XLIFF files. See [MLW US IMPL] Tools Annotation for more mechanism allows processor information on these and other usage scenarios for ITS 2.0. For both scenarios, a non-normative definition of how to represent ITS 2.0 be associated with individual data categories in XLIFF 1.2 or XLIFF 2.0 is being defined within the Internationalization Tag Set Interest Group . Readers of this specification are encouraged to evaluate whether that mapping fulfills their needs and to provide comments in the ITS IG mailing list (public archive) . 1.6 Out of Scope 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 document, independently from data formats (sometimes called localization project parameters) that may be needed category annotations themselves (e.g. the Entity Type related to configure localization workflows or process specific formats. However, it does define standard Text Analysis). The mechanism associates identifiers for tools with data categories that may be used in defining localization workflows or processing specific formats. Note: “ XML localization project parameters ” 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 project parameters are the Trados “DTD Settings” file, and via the SDLX “Analysis” file. annotatorsRef attribute (or annotators-ref in [HTML5] 1.7 Important Design Principles Abstraction via data categories : ITS defines data categories as an abstract notion for information needed for the internationalization and localization of XML documents ) and HTML documents. This abstraction is helpful in realizing independence from any one particular implementation (e.g., as an element or attribute). (See Section 3.2: Data category for a definition of the term data categories, Section 8: Description of Data Categories mandatory for the definition of the various ITS data categories, and subsections in Section 8: Description of Data Categories MT Confidence for the data category implementations.) Powerful selection mechanism: category. 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 selection Terminology 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 [XML Infoset] . ITS applications may implement inclusion mechanisms such as XInclude or DITA's [DITA 1.0] conref. Content authors, for example, need a simple way to work with the Translate Text Analysis data category in order to express whether the content of an element or attribute should be translated or not. Localization managers, on the other hand, need an efficient way to manage translations of large document sets based on categories the same schema. These needs could by realized by a specification of defaults for ITS Tools Annotation is mandatory if the Translate data category along with exceptions to those defaults (e.g. all p elements should be translated, but not p elements inside of an index element). To meet these requirements this specification introduces mechanisms that add ITS information to XML documents, see Section 5: Processing of ITS information . These mechanisms also categories provide a means for specifying ITS information for attributes (a task for which no standard means previously existed). The confidence information. Nevertheless, ITS selection mechanisms allows you to provide information about content locally (specified at the XML or HTML element to which it pertains) or globally Tools Annotation (specified in another part of the document). Global selection mechanisms can be in the same document, or in a separate file. No dedicated extensibility : It may be useful or necessary to extend the set of information available for internationalization or localization purposes beyond what is provided by ITS. This specification does not define a dedicated extension mechanism, since ordinary XML mechanisms (e.g. XML Namespaces [XML Names] ) may be used. Ease of integration : ITS follows the example from section 4 of [XLink 1.1] , by providing mostly global attributes used for the implementation of ITS all data categories. Avoiding elements for ITS purposes as much as possible ensures ease of integration into existing markup schemes, see section 3.14 Example 23 in [ITS REQ] . ITS has no dependency on technologies which are still under development. ITS fits with existing work in demonstrates the W3C architecture (e.g. use of [XPath 1.0] for usage in the selection mechanism and use context of IRI's [RFC 3987] as references to relevant external resources). several data categories.

1.8 ITS 2.0 2.7 Mapping and Unicode Normalization conversion

it pertains to the Translate data category 2.8 ITS 2.0 Implementations and Conformance

What does it mean to implement ITS 2.0? This specification provides several conformance clauses as the attribute translate holds a value of "no" normative answer (see Section 4: Conformance ). The ITS selector attribute allows: clauses target different types of implementers:

• Conformance clauses in Section 4.1: Conformance Type 1: ITS data category attributes Markup Declarations tell markup vocabulary developers how to appear in global rules (even outside of an XML document or schema) add ITS 2.0 markup declarations to their schemas.

• Conformance clauses in Section 4.2: Conformance Type 2: The Processing Expectations for ITS data categories attributes to pertain Markup tell implementers how to sets of XML nodes (for example all p elements in an process XML document) content according to ITS 2.0 data categories.

• Conformance clauses in Section 4.3: Conformance Type 3: Processing Expectations for ITS markup to pertain Markup in HTML tell implementers how to attributes process [HTML5] content.

• Conformance clauses in Section 4.4: Conformance Type 4: Markup conformance for HTML5+ITS documents tell implementers how ITS 2.0 markup to associate with existing markup (for example the term element in DITA) is integrated into [HTML5] .

The power of the conformance clauses in Section 4.2: Conformance Type 2: The Processing Expectations for ITS selection mechanisms comes at a price: rules related to overriding/precedence , Markup and inheritance , have to be established. The document Section 4.3: Conformance Type 3: Processing Expectations for ITS Markup in Example 13 HTML shows clarify how inheritance and overriding work information needs to be made available for the Translate given pieces of markup when processing a dedicated ITS 2.0 data category. By default elements To allow for flexibility, an implementation can choose whether it wants to support only ITS 2.0 global or local information, or XML or HTML content. These choices are translatable. Here, the translateRule element declared reflected in the header overrides the default for the head element inside text separate conformance clauses and for all its children. Because the title element is actually translatable, also in the global rule ITS 2.0 test suite .

ITS 2.0 processing expectations only define which information needs to be overridden by a local its:translate="yes" . Note that the global rule is processed first, regardless of its position inside the document. In the main body of the document, the default applies, and here it is its:translate="no" made available. They do not define how that is used to set “faux pas” as non-translatable. to start a dissertation on the origin of modern novel without mentioning the Epic of Gilgamesh [Source file: examples/xml/EX-basic-concepts-3.xml ] 2.3 Adding Information or Pointing to Existing Information For some data categories, special attributes add or point to information about the selected nodes. For example, the Localization Note data category can add information actually is to selected nodes (using a locNote element), or point be used. This is due to existing information elsewhere in the document (using fact that there is a locNotePointer attribute). The data category overview table , in Section 8.1: Position, Defaults, Inheritance wide variety of usage scenarios for ITS 2.0, and Overriding a wide variety of Data Categories , provides an overview tools for working with ITS 2.0 is possible. Each of what these tools may have its own way of using ITS 2.0 data categories allow to point to existing information or to add information. The functionalities of adding information and pointing to existing information are mutually exclusive . That is to say, attributes (see [MLW US IMPL] for pointing and adding the same information must not appear at the same rule element. more information).

3.1 Notation

The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC 2119] .

The namespace URI that MUST be used by implementations of this specification is:

http://www.w3.org/2005/11/its

The namespace prefix used in this specification for XML implementations of ITS for the above URI is "its". its . It is recommended that XML implementations of this specification use this prefix, unless there is existing dedicated markup in use for a given data category. In HTML there is no namespace prefix: "its-" its- is used instead to indicate ITS 2.0 attributes in HTML documents. See Section 6.1: Mapping 6.1: Mapping of Local Data Categories to HTML for details.

In addition, the following namespaces are used in this document:

• http://www.w3.org/2001/XMLSchema for the XML Schema namespace, here used with the prefix “xs” xs

• http://www.w3.org/1999/xlink for the XLink namespace, here used with the prefix “xlink” xlink

• http://www.w3.org/1999/xhtml for the HTML namespace, here used with the prefix “h” h

3.2 Data category

[ Definition : ITS defines data category as an abstract concept for a particular type of information for internationalization and localization of XML schemas and documents.] The concept of a data category is independent of its implementation in an XML and HTML environment (e.g. (e.g., using an element or attribute).

For each data category, ITS distinguishes between the following:

• the prose description, see Section 8: Description 8: Description of Data Categories

• schema language independent language-independent formalization, see the "implementation" subsections in Section 8: Description 8: Description of Data Categories

• schema language specific language-specific implementations, see Appendix D: Schemas D: Schemas for ITS

3.3 Selection

[ Definition : selection encompasses mechanisms to specify to what parts of an XML or HTML document an ITS data category and its values should be applied to.] apply.] Selection is discussed in detail in Section 5: Processing 5: Processing of ITS information . Selection can be applied globally, see Section 5.2.1: Global, 5.2.1: Global, Rule-based Selection , and locally, see Section 5.2.2: Local 5.2.2: Local Selection in an XML Document . As for global selection, ITS information can be added to the selected nodes, or it can point to existing information which that is related to selected nodes.

<text>  
"color: #000096"><its:rules version="2.0" 
             
"color: #F5844C">xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><its:translateRule translate="yes" selector="//p/img/@src"/>
  
"color: #000096"></its:rules>

  ...
  As you can see in
    

  "color: #000096"><p xmlns:its="http://www.w3.org/2005/11/its">As you can see in
    
"color: #000096"><img src="instructions.jpg"/>, the truth is not always out there.</p>

"color: #000096"></text>

3.4 ITS Local Attributes

[ Definition : ITS Local Attributes are all attributes defined in Section 8: Description 8: Description of Data Categories as a local markup.]

3.5 Rule Elements

[ Definition : Rule Elements are all elements defined in Section 8: Description 8: Description of Data Categories as elements for global rules.]

3.6 Usage of Internationalized Resource Identifiers in ITS

All attributes that have the type anyURI in the normative RELAX NG schema in Appendix D: Schemas D: Schemas for ITS MUST allow the usage of Internationalized Resource Identifiers (IRIs, [RFC 3987] or its successor) to ease the adoption of ITS in international application scenarios.

3.7 The Term HTML

This specification uses the term HTML to refer to HTML5 or its successor in HTML syntax [HTML5] .

3.8 The Term CSS Selectors

This specification uses the term CSS Selectors in the sense of Selectors as specifies specified in [Selectors Level 3] to prevent confusion with the generic use of the word "selector". [Selectors Level 3] .

4.1 Conformance Type 1: ITS Markup Declarations

Description: ITS markup declarations encompass all declarations that are part of the Internationalization Tag Set. They do not concern the usage of the markup in XML documents. Such markup is subject to the conformance clauses in Section 4.2: Conformance 4.2: Conformance Type 2: The Processing Expectations for ITS Markup .

Definitions related to this conformance type: ITS markup declarations are defined in various subsections in in a schema language independent manner.

Who uses this conformance type: Schema designers integrating ITS markup declarations into a schema. All conformance clauses for this conformance type concern the position of ITS markup declarations in that schema, and their status as mandatory or optional.

Conformance clauses:

• 1-1: At least one of the following MUST be in the schema:

  • rules element

  • one of the local ITS attributes

  • span element

• 1-2: If the rules element is used, it MUST be part of the content model of at least one element declared in the schema. It SHOULD be in a content model for meta information, if this is available in that schema (e.g. (e.g., the head element in [XHTML 1.0] ).

• 1-4: 1-3: If the span element is used, it SHOULD be declared as an inline element.

Full implementations of this conformance type will implement all markup declarations for ITS. Statements related to this conformance type MUST list all markup declarations they implement.

Examples: Examples of the usage of ITS markup declarations in various existing schemas are given in a separate document [XML i18n BP] .

4.2 Conformance Type 2: The Processing Expectations for ITS Markup

Description: Processors need to compute the ITS information that pertains to a node in an XML document. The ITS processing expectations define how the computation has to be carried out. Correct computation involves support for selection mechanism , defaults / inheritance / overriding characteristics , and precedence . The markup MAY be valid against a schema which that conforms to the clauses in Section 4.1: Conformance 4.1: Conformance Type 1: ITS Markup Declarations .

Definitions related to this conformance type: The processing expectations for ITS markup make use of selection mechanisms defined in Section 5: Processing 5: Processing of ITS information . The individual data categories defined in Section 8: Description 8: Description of Data Categories have defaults / inheritance / overriding characteristics , and allow for using ITS markup in various positions ( global and local ).

Who uses this conformance type: Applications that need to process the nodes captured by a data category for internationalization or localization. Examples of this type of application are: ITS markup-aware editors, or translation tools that make use of ITS markup to filter translatable text as an input to the localization process.

Conformance clauses:

• 2-1: A processor MUST implement at least one data category . For each implemented data category , the following MUST be taken into account:

  • 2-1-1: processing of at least one selection mechanism ( global or local ).

  • 2-1-2: the default selections for the data category .

  • 2-1-3: the precedence definitions for selections defined in Section 5.5: Precedence 5.5: Precedence between Selections , for the type of selections it processes.

• 2-2: If an application claims to process ITS markup for the global selection mechanism, it MUST process an XLink href attribute found on a rules elements. element.

• 2-3: If an application claims to process ITS markup implementing the conformance clauses 2-1, 2-2 and 2-3, it MUST process that markup with XML documents.

• 2-4: After processing ITS information on the basis of conformance clauses 2-1 and 2-2 , an application MAY convert an XML document to NIF, using the algorithm described in Section 5.7: Conversion to NIF . 2-5: 2-4: Non-ITS elements and attributes found in ITS elements MAY be ignored.

Statements related to this conformance type MUST list all data categories they implement, and for each data category , which type of selection they support, whether they support processing of XML. If the implementation provides the conversion to NIF (see conformance clause 2-4 ), this MUST be stated.

4.3 Conformance Type 3: Processing Expectations for ITS Markup in HTML

Description: Processors need to compute the ITS information that pertains to a node in a an HTML document. The ITS processing expectations define how the computation has to be carried out. Correct computation involves support for selection mechanism , defaults / inheritance / overriding characteristics , and precedence .

Definitions related to this conformance type: The processing expectations for ITS markup make use of selection mechanisms defined in Section 5: Processing 5: Processing of ITS information . The individual data categories defined in Section 8: Description 8: Description of Data Categories have defaults / inheritance / overriding characteristics , and allow for using ITS markup in various positions ( local , external global and inline global ).

Who uses this conformance type: Applications that need to process the nodes captured by a data category for internationalization or localization. Examples of this type of application are: are ITS markup-aware editors, editors or translation tools that make use of ITS markup to filter translatable text as an input to the localization process.

Conformance clauses:

• 3-1: A processor MUST implement at least one data category . For each implemented data category , the following MUST be taken into account:

  • 3-1-1: processing of at least one selection mechanism ( global or local ).

  • 3-1-2: the default selections for the data category .

  • 3-1-3: the precedence definitions for selections defined in Section 6.4: Precedence 6.4: Precedence between Selections , for the type of selections it processes.

• 3-2: If an application claims to process ITS markup for the global selection mechanism, it MUST process a href attribute found on a link elements which element that has a rel attribute with the value its-rules .

• 3-3: If an application claims to process ITS markup implementing the conformance clauses 3-1 and 3-2, it MUST process that markup within HTML documents.

Statements related to this conformance type MUST list all data categories they implement, and implement and, for each data category , which type of selection they support.

4.4 Conformance Class Type 4: Markup conformance for HTML5+ITS documents

Conforming HTML5+ITS documents are those that comply with all the conformance criteria for documents as defined in [HTML5] with the following exception:

• Conformance clause 4-1: Global attributes which that can be used on all HTML elements are extended by attributes for local data categories as defined in Section 6.1: Mapping 6.1: Mapping of Local Data Categories to HTML .

5.1 Indicating the Version of ITS

The version of the ITS schema defined in this specification is "2.0". The version is indicated by the ITS version attribute. This attribute is mandatory for the rules element, where it MUST be in no namespace.

If there is no rules element in an XML document, a prefixed ITS version attribute (e.g. (e.g., its:version ) MUST be provided on the element where the ITS markup is used, or on one of its ancestors.

If there is no rules element and there are elements with standoff ITS markup in an XML document, an ITS version attribute MUST be provided on element with standoff ITS markup or a prefixed ITS version attribute (e.g. (e.g., its:version ) MUST be provided on one of its ancestors.

There MUST NOT be two different versions of ITS in the same document.

External, linked rules can have different versions than internal rules.

5.2 Locations of Data Categories

ITS data categories can appear in two places:

• Global rules : the selection is realized within a rules element. It contains rule elements for each data category. Each rule element has a selector attribute and possibly other attributes. The selector attribute contains an absolute selector as defined in Section 5.3: Query 5.3: Query Language of Selectors .

• Locally in a document : the selection is realized using ITS local attributes, which are attached to an element node, or the span element. There is no additional selector attribute. The default selection for each data category defines whether the selection covers attributes and child elements. See Section 8.1: Position, 8.1: Position, Defaults, Inheritance Inheritance, and Overriding of Data Categories .

The two locations are described in detail below.

"color: #000096"><text xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0" xml:lang="en">
  
"color: #000096"><head its:translate="no">
    
"color: #000096"><author>Sven Corneliusson</author>
    
"color: #000096"><date>2006-09-26T17:34:04Z</date>
    
"color: #000096"><title its:translate="yes" role="header">Bidirectional Text</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><par>In Arabic, the title <quote xml:lang="ar" its:dir="rtl">نشاط التدويل، W3C</quote> means
        
"color: #000096"><quote>Internationalization Activity, W3C</quote>.</par>
  
"color: #000096"></body>

"color: #000096"></text>

5.3 Query Language of Selectors

"color: silver"><!-- Definitions for TEI -->

"color: #000096"><its:rules version="2.0"  xmlns:its="http://www.w3.org/2005/11/its">
 
"color: #000096"><its:termRule selector="//tei:term" term="yes" xmlns:tei="http://www.tei-c.org/ns/1.0"/>

"color: #000096"></its:rules>

"color: silver"><!-- Definitions for DocBook -->

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:termRule selector="//term" term="yes"/>

"color: #000096"></its:rules>

<!--
Definitions
for
DocBook
-->
<its:rules
version
=
"2.0"
xmlns:its
=
"http://www.w3.org/2005/11/its"
>
<its:termRule
selector
=
"//term"
term
=
"yes"
/>
</its:rules>

"color: #000096"><doc its:version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:rules version="2.0">
    
"color: #000096"><its:param name="LCID">0x0409</its:param>
    
"color: #000096"><its:translateRule selector="/doc" translate="no"/>
    
"color: #000096"><its:translateRule selector="//msg[@lcid=$LCID]" translate="yes"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><msg lcid="0x0409" num="1">Create a folder</msg>
  
"color: #000096"><msg lcid="0x0411" num="1">フォルダーを作成する</msg>
  
"color: #000096"><msg lcid="0x0407" num="1">Erstellen Sie einen Ordner</msg>
  
"color: #000096"><msg lcid="0x040c" num="1">Créer un dossier</msg>

</doc>

5.4 Link to External Rules

One way to associate a document with a set of external ITS rules is to use the optional XLink [XLink 1.1] href attribute in the rules element. The referenced document must MUST be a valid XML document containing at most one rules element. That rules element can be the root element or be located anywhere within the document tree (for example, the document could be an XML Schema).

The rules contained in the referenced document MUST be processed as if they were at the top of the rules element with the XLink href attribute.

"color: #000096"><myFormatInfo>
  
"color: #000096"><desc>ITS rules used by the Open University</desc>
  
"color: #000096"><hostVoc>http://www.tei-c.org/ns/1.0</hostVoc>
  
"color: #000096"><rulesId>98ECED99DF63D511B1250008C784EFB1</rulesId>
  
"color: #000096"><rulesVersion>v 1.81 2006/03/28 07:43:21</rulesVersion>

  ... 
  
    
    
    
    
  

  "color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><its:translateRule selector="//header" translate="no"/>
    
"color: #000096"><its:translateRule selector="//term" translate="no"/>
    
"color: #000096"><its:termRule selector="//term" term="yes"/>
    
"color: #000096"><its:withinTextRule withinText="yes" selector="//term | //b"/>
  
"color: #000096"></its:rules>

"color: #000096"></myFormatInfo>

<myDoc>
<header>
<its:rules
version
=
"2.0"
xmlns:its
=
"http://www.w3.org/2005/11/its"
xmlns:xlink
=
"http://www.w3.org/1999/xlink"
xlink:href
=
"EX-link-external-rules-1.xml"
>
<its:translateRule
selector
=
"//term"
translate
=
"yes"
/>
</its:rules>
<author>
Theo
Brumble
</author>
<lastUpdate>
Apr-01-2006
</lastUpdate>
</header>
<body>
<p>
A
<term>
Palouse
horse
</term>
has
a
spotted
coat.
</p>
</body>
</myDoc>

"color: #000096"><myDoc>
  
"color: #000096"><header>
    
"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
      
"color: #F5844C">xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="EX-link-external-rules-1.xml">
      
"color: #000096"><its:translateRule selector="//term" translate="yes"/>
    
"color: #000096"></its:rules>
    
"color: #000096"><author>Theo Brumble</author>
    
"color: #000096"><lastUpdate>Apr-01-2006</lastUpdate>
  
"color: #000096"></header>
  
"color: #000096"><body>
    
"color: #000096"><p>A <term>Palouse horse</term> has a spotted coat.</p>
  
"color: #000096"></body>

"color: #000096"></myDoc>

The result of processing the two documents above is the same as processing the following document. following document.

"color: #000096"><myDoc>
  
"color: #000096"><header>
    
"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
      
"color: #000096"><its:translateRule selector="//header" translate="no"/>
      
"color: #000096"><its:translateRule selector="//term" translate="no"/>
      
"color: #000096"><its:termRule selector="//term" term="yes"/>
      
"color: #000096"><its:withinTextRule withinText="yes" selector="//term | //b"/>
      
"color: #000096"><its:translateRule selector="//term" translate="yes"/>
    
"color: #000096"></its:rules>
    
"color: #000096"><author>Theo Brumble</author>
    
"color: #000096"><lastUpdate>Apr-01-2006</lastUpdate>
  
"color: #000096"></header>
  
"color: #000096"><body>
    
"color: #000096"><p>A <term>Palouse horse</term> has a spotted coat.</p>
  
"color: #000096"></body>

"color: #000096"></myDoc>

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:translateRule selector="//header" translate="no"/>
  
"color: #000096"><its:translateRule selector="//term" translate="no"/>
  
"color: #000096"><its:termRule selector="//term" term="yes"/>
  
"color: #000096"><its:withinTextRule withinText="yes" selector="//term | //b"/>

"color: #000096"></its:rules>

Applications processing global ITS markup MUST recognize the XLink href attribute in the rules element; they MUST load the corresponding referenced document and process its rules element before processing the content of the rules element where the original XLink href attribute is.

External rules may also have links to other external rules (see Example 21 17 ). The linking mechanism is recursive in a depth-first approach, and subsequently after the processing the rules MUST be read top-down (see Example 22 18 ).

5.5 Precedence between Selections

The following precedence order is defined for selections of ITS information in various positions (the first item in the list has the highest precedence):

1. Selection via explicit (that is, (i.e., not inherited) local ITS markup in documents ( ITS local attributes on a specific element)

2. Global selections in documents (using a rules element)

   Inside each rules element the precedence order is:

   1. Any rule inside the rules element

   2. Any rule linked via the XLink href attribute

   Note:

   ITS does not define precedence related to rules defined or linked based on non-ITS mechanisms (such as processing instructions for linking rules).

3. Selection via inherited values. This applies only to element nodes. The inheritance rules are laid out in a dedicated datacategory data category overview table , : see the column " Inheritance for element nodes ". Selection via inheritance takes precedence over default values, see below item.

4. Selections via defaults for data categories, see Section 8.1: Position, 8.1: Position, Defaults, Inheritance Inheritance, and Overriding of Data Categories

In case of conflicts between global selections via multiple rules elements, elements or conflicts between multiple param elements with the same name, the last rule or last param element has higher precedence.

<text>  
"color: #000096"><prolog>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
      
"color: #000096"><its:withinTextRule withinText="yes" selector="//title|//author"/>
      
"color: #000096"><its:withinTextRule withinText="no" selector="//prolog/title|//prolog/author"/>
    
"color: #000096"></its:rules>
    
"color: #000096"><title>Designing User Interfaces</title>
    
"color: #000096"><author>Janice Prakash</author>
    
"color: #000096"><keywords>user interface, ui, software interface</keywords>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><p>The book <title>Of Mice and Screens</title> by <author>Aldus Brandywine</author> is one of
      the best introductions to the vast topic of designing user interfaces.</p>
  
"color: #000096"></body>

"color: #000096"></text>

5.6 Associating ITS Data Categories with Existing Markup

Some markup schemes provide markup which that can be used to express ITS data categories. ITS data categories can be associated with such existing markup, using the global selection mechanism described in Section 5.2.1: Global, 5.2.1: Global, Rule-based Selection .

Associating existing markup with ITS data categories can be done only if the processing expectations of the host markup are the same as, or greater than, those of ITS. For example, the [DITA 1.0] format can use its translate attribute to apply to “transcluded” content, going beyond the ITS 2.0 local selection mechanism, but not contradicting it.

"color: #000096"><topic id="myTopic">
  
"color: #000096"><title>The ITS Topic</title>
  
"color: #000096"><prolog>
    
"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
      
"color: #000096"><its:translateRule selector="//*[@translate='no']" translate="no"/>
      
"color: #000096"><its:translateRule selector="//*[@translate='yes']" translate="yes"/>
      
"color: #000096"><its:termRule selector="//term | //dt" term="yes"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><dl>
      
"color: #000096"><dlentry id="tDataCat">
        
"color: #000096"><dt>Data category</dt>
        
"color: #000096"><dd>ITS defines <term>data category</term> as an abstract concept for a particular type of

          information related to internationalization and localization of XML schemas and
          documents.
      
    
    
    
      
      
      
      
    
    
  

          documents.</dd>
      
"color: #000096"></dlentry>
    
"color: #000096"></dl>
    
"color: #000096"><p>For the implementation of ITS, apply the rules in the order:</p>
    
"color: #000096"><ul>
      
"color: #000096"><li>Defaults</li>
      
"color: #000096"><li>Rules in external files</li>
      
"color: #000096"><li>Rules in the document</li>
      
"color: #000096"><li>Local attributes</li>
    
"color: #000096"></ul>
    
"color: #000096"><p><ph translate="no" xml:lang="fr">Et voilà !</ph>.</p>
  
"color: #000096"></body>

"color: #000096"></topic>

Global rules can be associated with a given XML document using different means:

• By using an rules element in the document itself:

  • with the rules directly inside the document, as shown in Example 25 21

  • with a link to an external rules file using the XLink href attribute, as shown in Example 20 16

• By associating the rules and the document through a tool-specific mechanism. For example, for in the case of a command-line tool: tool by providing the paths of both the XML document to process and its corresponding external rules file.

5.7 Conversion to NIF 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 [NIF] . The conversion results in RDF triples. Note: The algorithm is intended to extract the text from the XML/HTML/DOM for an NLP tool. It can produce a lot of " phantom " predicates from excessive whitespace, which 1) increases the size of the intermediate mapping and 2) extracts this whitespace as text, and therefore might decrease NLP performance. It is strongly recommended to normalize whitespace in the input XML/HTML/DOM in order to minimize such phantom predicates. A normalized example is given below. Since the whitespace normalization algorithm itself is format dependent, for example, it differs for HTML compared to general XML, no normative algorithm for whitespace normalization is given as part of this specification. Note: The output of the algorithm shown below uses the ITS RDF ontology [ITS RDF] and its namespace http://www.w3.org/2005/11/its/rdf# translate = "no" > Dublin </span> in <b translate = "no" its-within-text = "yes" > Ireland </b> ! </h2> </body> </html> The conversion algorithm to generate NIF consists of seven steps. STEP 1: Get an ordered list of all text nodes of the document. STEP 2: Generate an XPath expression for each non-empty text node of all leaf elements and memorize them. STEP 3: Get the text for each node and make a tuple with the XPath expressions (X,T). Since the text nodes have a certain order we now have a list of ordered tuples ((x0,t0), (x1,t1), ..., (xn,tn)). STEP 4 (optional): Serialize as XML or as RDF. The list with the XPath-to-text mapping can also be kept in memory. Part of a serialization example is given below. Note that in the example consists both of an RDF part and and XML part (the @prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> . <http://example.com/exampledoc.html#xpath(x0)> nif:convertedFrom <http://example.com/exampledoc.html#char=b0,e0> <http://example.com/exampledoc.html#xpath(x1)> nif:convertedFrom <http://example.com/exampledoc.html#char=b1,e1> # ... <http://example.com/exampledoc.html#xpath(xn)> nif:convertedFrom <http://example.com/exampledoc.html#char=bn,en> <mappings> <mapping x="xpath(x0)" b="b0" e="e0" /> <mapping x="xpath(x1)" b="b1" e="e1" /> <!-- ... --> <mapping x="xpath(xn)" b="bn" e="en" /> </mappings> where b0 = 0 e0 = b0 + (Number of characters of t0) b1 = e0 +1 e1 = b1 + (Number of characters of t1) ... bn = e(n-1) +1 en = bn + (Number of characters of tn) Example (continued) @prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> . # "Welcome to " <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[1])> itsrdf:nif <http://example.com/exampledoc.html#char=0,11> . # "Dublin" <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/span[1]/text()[1])> itsrdf:nif <http://example.com/exampledoc.html#char=11,17> . # " in " <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[2])> itsrdf:nif <http://example.com/exampledoc.html#char=17,21> . # "Ireland" <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/b[1]/text()[1])> itsrdf:nif <http://example.com/exampledoc.html#char=21,28> . # "!" <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text()[3])> itsrdf:nif <http://example.com/exampledoc.html#char=28,29> . # "Welcome to Dublin Ireland!" <http://example.com/exampledoc.html#xpath(/html/body[1]/h2[1]/text())> itsrdf:nif <http://example.com/exampledoc.html#char=0,29> . <mappings> <mapping x="xpath(/html/body[1]/h2[1]/text()[1])" b="0" e="11" /> <mapping x="xpath(/html/body[1]/h2[1]/span[1]/text()[1])" b="11" e="17" /> <mapping x="xpath(/html/body[1]/h2[1]/text()[2])" b="17" e="21" /> <mapping x="xpath(/html/body[1]/h2[1]/b[1]/text()[1])" b="21" e="28" /> <mapping x="xpath(/html/body[1]/h2[1]/text()[3])" b="28" e="29" /> <mapping x="xpath(/html/body[1]/h2[1])" b="0" e="29" /> </mappings> STEP 5: Create a context URI and attach the whole concatenated text of the document as reference.@prefix itsrdf: <http://www.w3.org/2005/11/its/rdf#> . @prefix nif: <http://persistence.uni-leipzig.org/nlp2rdf/ontologies/nif-core#> <http://example.com/exampledoc.html#char=0,29> rdf:type nif:Context ; rdf:type nif:RFC5147String ; # concatenate the whole text nif:isString "$(t0+t1+t2+...+tn)" ; itsrdf:translate "yes"; nif:sourceUrl <http://example.com/exampledoc.html> . <http://example.com/exampledoc.html#char=11,17> rdf:type nif:String; rdf:type nif:RFC5147String ; itsrdf:translate "no"; itsrdf:taIdentRef <http://dbpedia.org/resource/Dublin> ; nif:referenceContext <http://example.com/exampledoc.html#char=0,29> . <http://example.com/exampledoc.html#char=21,28> rdf:type nif:String; rdf:type nif:RFC5147String ; itsrdf:translate "no"; nif:referenceContext <http://example.com/exampledoc.html#char=0,29> . A complete sample output in RDF/XML format after step 7, given the input document Example 26 , is available at examples/nif/EX-nif-conversion-output.xml . Note: The conversion to NIF is a possible basis for a natural language processing (NLP) application that creates, for example, named entity annotations. A non-normative algorithm to integrate these annotations into the original input document is given in Appendix F: Conversion NIF2ITS . This algorithm is non-normative because many decisions depend on the actually employed NLP application. 5.8 ITS Tools Annotation

In some cases, it may be important for instances of data categories to be associated with information about the processor that generated them. For example, the score of the MT Confidence data category (provided via the mtConfidence attribute) is meaningful only when the consumer of the information also knows what which MT engine produced it, because the score provides the relative confidence of translations from the same MT engine but does not provide a score that can be reliably compared between MT engines. The same is true for confidence provided for the Text Analysis data category, providing confidence information via the taConfidence attribute, or the Terminology data category, providing confidence information via the termConfidence attribute.

ITS 2.0 provides a mechanism to associate such processor information with the use of individual data categories in a document, independently from data category annotations themselves.

The attribute annotatorsRef provides a way to associate all the annotations of a given data category within the element with information about the processor that generated those data category annotations.

The value of annotatorsRef is a space-separated list of references where each reference is composed of two parts: a data category identifier and an IRI. These two parts are separated by a character | VERTICAL LINE (U+007C). (U+007C) character:

• The data category identifier MUST be one of the identifiers specified in the data category overview table .

• Within one annotatorsRef value, a data category identifier MUST NOT appear more than one time.

• The IRI indicates information about the processor used to generate the data category annotation. No single means is specified for how this IRI should has to be used to indicate processor information. Possible mechanisms are: to encode information directly in the IRI, e.g. e.g., as parameters; to reference an external resource that provides such information, e.g. an XML file or an RDF declaration; or to reference another part of the document that provides such information.

In HTML documents, the mechanism is implemented with the its-annotators-ref attribute.

The attribute applies to the content of the element where it is declared (including its children elements) and to the attributes of that element.

On any given node, the information provided by this mechanism is a space-separated list of the accumulated references found in the annotatorsRef attributes declared in the enclosing elements and sorted by data category identifiers. For each data category, the IRI part is the one of the inner-most declaration.

"color: #000096"><doc its:version="2.0" xmlns:its="http://www.w3.org/2005/11/its"
  
"color: #F5844C">its:annotatorsRef="mt-confidence|MT1"

  >doc node: "mt-confidence|MT1"
  

  "color: #000096"><group its:annotatorsRef="terminology|ABC"

    >group node: "mt-confidence|MT1 terminology|ABC"
    
      >
    
      >
 
  <!-- To make this example real life usable, in the document we would have 
    annotations of the three data categories text-analysis, mt-confidence and terminology -->
  
   >

    "color: #000096"><p its:annotatorsRef="text-analysis|Tool3"
      >This p node: "text-analysis|Tool3 mt-confidence|MT1 terminology|ABC"</p>
    
"color: #000096"><p its:annotatorsRef="mt-confidence|MT123"
      >This p node: "mt-confidence|MT123 terminology|ABC"</p>
 
"color: #000096"></group>
  
"color: silver"><!-- To make this example usable in real life, we would have 
    annotations of the three data categories - text-analysis, mt-confidence and terminology 
    - in the document -->
  
"color: #000096"><p its:annotatorsRef="text-analysis|XYZ"
   >This p node: "text-analysis|XYZ mt-confidence|MT1"</p>

</doc>

"color: #000096"><doc its:version="2.0"
    
"color: #F5844C">its:annotatorsRef=
    
"color: #993300">"mt-confidence|file:///tools.xml#T1 localization-quality-issue
    |http://www.qalsp-ex.com/qatools/transcheckv1.3"
    
"color: #F5844C">xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><p its:mtConfidence="0.78">Text translated with tool T1</p>
    
"color: #000096"><p its:mtConfidence="0.55" its:locQualityIssueType="typographical"
        
"color: #F5844C">its:locQualityIssueComment="Sentence without capitalization"
        
"color: #F5844C">its:locQualityIssueSeverity="50">text also translated with tool T1</p>
    
"color: #000096"><p its:mtConfidence="0.34" 
      
"color: #F5844C">its:annotatorsRef="mt-confidence|file:///tools.xml#T2"> Text translated
        with tool T2</p>

</doc>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
    
"color: #000096"><head>
        
"color: #000096"><meta charset=utf-8>
            
"color: #000096"><title>Sentences about capital cities 
                machine translated into English with mtConfidence defined 
                locally.</title>
    
"color: #000096"></head>
    
"color: #000096"><body its-annotators-ref="mt-confidence|http://www.exmt-prov.com/2012/11/9/fr-t-en">
        
"color: #000096"><p>     
 
"color: #000096"><span its-mt-confidence=0.8982>Dublin is the capital of Ireland.</span>
 
"color: #000096"><span its-mt-confidence=0.8536>The capital of the Czech Republic is Prague.</span>
 
"color: #000096"><span its-mt-confidence=0.7009
  
"color: #F5844C">its-annotators-ref="mt-confidence|http://www.exmt-prov.com/2012/11/9/it-t-en">
  The capital Italia is Roma.</span>
        
"color: #000096"></p>  
    
"color: #000096"></body>

"color: #000096"></html>

6.1 Mapping of Local Data Categories to HTML

All data categories defined in Section 8: Description 8: Description of Data Categories and having local implementation might may be used in HTML with the exception of the Translate , Directionality and Language Information data categories.

In HTML data categories are implemented as attributes. Name The name of the HTML attribute is derived from the name of the attribute defined in the local implementation by using the following rules:

1. Attribute The attribute name is prefixed with its-

2. Each uppercase letter in the attribute name is replaced by - (U+002D) followed by a lowercase variant of the letter.

Example 52 48 demonstrates the Elements Within Text data category with the local XML attribute withinText . Example 53 49 demonstrates the counterpart in HTML, that is i.e., the local attribute its-within-text .

Values of attributes attributes, which corresponds to data categories with a predefined set of values values, MUST be matched ASCII-case-insensitively.

Values of attributes which corresponds that correspond to data categories which that use XML Schema double data type MUST be also valid floating-point numbers as defined in [HTML5] .

6.2 Global rules

Various aspects for global rules in general, external global rules rules, or inline global rules need to be taken into account. An example of an HTML5 document using global rules is Example 8 6 . The corresponding rules file is Example 9 7 .

Link Linking to external global rules is specified in the href attribute of link element, elements, with the link relation its-rules .

Inline global rules MUST be specified inside a script which element that has a type attribute with the value application/its+xml . The script element itself SHOULD be a child of the head element. Comments MUST NOT be used inside global rules. Each script element MUST NOT contain more than one rules element.

6.3 Standoff Markup in HTML

The constraints for Provenance standoff markup in HTML and Localization quality issues markup in HTML MUST be followed.

6.4 Precedence between Selections

The following precedence order is defined for selections of ITS information in various positions of HTML document (the first item in the list has the highest precedence):

1. Implicit local selection in documents ( ITS local attributes on a specific element)

2. Global selections in documents (using the mechanism of external global rules or inline global rules ), to be processed in a document order, see Section 5.2.1: Global, 5.2.1: Global, Rule-based Selection for details.

   Note:

   ITS does not define precedence related to rules defined or linked based on non-ITS mechanisms (such as processing instructions for linking rules). Selection via inheritance takes precedence over default values, see below item. values (see below).

3. Selection via inherited values. This applies only to element nodes. The inheritance rules are laid out in a dedicated datacategory data category overview table , see (see the column " Inheritance for element nodes ". nodes). Selection via inheritance takes precedence over default values, see below item. values (see below). "

4. Selections via defaults for data categories, see Section 8.1: Position, 8.1: Position, Defaults, Inheritance Inheritance, and Overriding of Data Categories .

In case of conflicts between global selections via multiple rules elements, elements or conflicts between multiple param elements with the same name, the last rule or last param element has higher precedence.

The forehand mentioned Example 8 6 ,previously discussed, demonstrates the precedence: the code element with the translate attribute set to yes has precedence over the global rule setting all code elements as untranslatable.

8.1 Position, Defaults, Inheritance Inheritance, and Overriding of Data Categories

The following table summarizes for each data category which selection, default value, and inheritance and overriding behavior applies. apply. It also provides data category identifiers used in Section 5.8: ITS 5.7: ITS Tools Annotation . :

• Default values apply if both local and global selection are absent. The default value for the Translate data category category, for example example, mandates that elements are translatable, and attributes are not translatable if there is no translateRule element and no translate attribute available.

• Inheritance describes whether ITS information is applicable to child elements of nodes and attributes related to these nodes or their child notes. The inheritance for the Translate data category category, for example example, mandates that all child elements of nodes are translatable whereas all attributes related to these the nodes or their child notes are not translatable.

• For ITS data categories with inheritance, the information conveyed by the data category can be overridden. For example, a local translate attribute overrides the Translate information conveyed by a global translateRule .

Foreign elements can be used only inside rules .Foreign attributes can be used on any element defined in ITS.

"color: #000096"><Res xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><prolog its:translate="no">
    
"color: #000096"><revision>Sep-07-2006</revision>
        
"color: #000096"><profile>
                
"color: #000096"><reviser>John Doe</reviser>
                
"color: #000096"><field>Computing Engineering</field>
        
"color: #000096"></profile>
        
"color: #000096"><its:rules version="2.0">
          
"color: #000096"><its:translateRule selector="//prolog" translate="yes"/>
          
"color: #000096"><its:translateRule selector="/Res/prolog/profile/field" translate="yes"/>
      
"color: #000096"><its:translateRule selector="//msg/type" translate="no"/>
      
"color: #000096"><its:locNoteRule locNoteType="description" selector="//msg/data">
        
"color: #000096"><its:locNote>The variable {0} is the name of the host.</its:locNote>
      
"color: #000096"></its:locNoteRule>
    
"color: #000096"></its:rules>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><msg id="HostNotFound">
      
"color: #000096"><type>Error</type>
      
"color: #000096"><data>Host {0} cannot be found.</data>
    
"color: #000096"></msg>
    
"color: #000096"><msg id="HostDisconnected">
      
"color: #000096"><type>Error</type>
      
"color: #000096"><data>The connection with {0} has been lost.</data>
    
"color: #000096"></msg>
    
"color: #000096"><msg id="FileNotFound">
      
"color: #000096"><type>Error</type>
      
"color: #000096"><data its:locNote="{0} is a filename">{0} not found.</data>
    
"color: #000096"></msg>
  
"color: #000096"></body>

</Res>

8.2 Translate

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:translateRule translate="no" selector="//code"/>

"color: #000096"></its:rules>

"color: #000096"><messages its:version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><msg num="123">Click Resume Button on Status Display or <panelmsg its:translate="no"
      >CONTINUE</panelmsg> Button on printer panel</msg>

"color: #000096"></messages>

"color: blue"><!DOCTYPE html>

<html>
  
    
    
  
  
     is
      making the World Wide Web worldwide!
  

  "color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>Translate flag test: Default</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>The <span translate=no>World Wide Web Consortium</span> is
      making the World Wide Web worldwide!</p>
  
"color: #000096"></body>

"color: #000096"></html>

8.3 Localization Note

"color: #000096"><myRes>
  
"color: #000096"><head>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0" its:translate="no">
      
"color: #000096"><its:locNoteRule locNoteType="alert" selector="//msg[@id='DisableInfo']">
        
"color: #000096"><its:locNote>The variable {0} has three possible values: 'printer', 'stacker' and 'stapler
          options'.</its:locNote>
      
"color: #000096"></its:locNoteRule>
    
"color: #000096"></its:rules>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><msg id="DisableInfo">The {0} has been disabled.</msg>
  
"color: #000096"></body>

"color: #000096"></myRes>

<Res>  
"color: #000096"><prolog>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
      
"color: #000096"><its:translateRule selector="//msg/notes" translate="no"/>
      
"color: #000096"><its:locNoteRule locNoteType="description" selector="//msg/data" locNotePointer="../notes"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><msg id="FileNotFound">
      
"color: #000096"><notes>Indicates that the resource file {0} could not be loaded.</notes>
      
"color: #000096"><data>Cannot find the file {0}.</data>
    
"color: #000096"></msg>
    
"color: #000096"><msg id="DivByZero">
      
"color: #000096"><notes>A division by 0 was going to be computed.</notes>
      
"color: #000096"><data>Invalid parameter.</data>
    
"color: #000096"></msg>
  
"color: #000096"></body>
</Res>

"color: #000096"><myRes>
  
"color: #000096"><head>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
      
"color: #000096"><its:locNoteRule locNoteType="description" selector="//msg[@id='NotFound']"
                       
"color: #F5844C">locNoteRef="ErrorsInfo.html#NotFound"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><msg id="NotFound">Cannot find {0} on {1}.</msg>
  
"color: #000096"></body>

"color: #000096"></myRes>

"color: #000096"><dataFile>
  
"color: #000096"><prolog>
    
"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
      
"color: #000096"><its:locNoteRule locNoteType="description" selector="//data"
                       
"color: #F5844C">locNoteRefPointer="../@noteFile"/>
    
"color: #000096"></its:rules>
  
"color: #000096"></prolog>
  
"color: #000096"><body>
    
"color: #000096"><string id="FileNotFound" noteFile="Comments.html#FileNotFound">
      
"color: #000096"><data>Cannot find the file {0}.</data>
    
"color: #000096"></string>
    
"color: #000096"><string id="DivByZero" noteFile="Comments.html#DivByZero">
      
"color: #000096"><data>Invalid parameter.</data>
    
"color: #000096"></string>
  
"color: #000096"></body>

"color: #000096"></dataFile>

"color: #000096"><msgList xmlns:its="http://www.w3.org/2005/11/its" xml:space="preserve" its:version="2.0">
 
"color: #000096"><data name="LISTFILTERS_VARIANT" its:locNote="Keep the leading space!" its:locNoteType="alert">
  
"color: #000096"><value> Variant {0} = {1} ({2})</value>
 
"color: #000096"></data>
 
"color: #000096"><data its:locNote="%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT">
  
"color: #000096"><value>Translated from English content dated <span id="version-info">%1\$s</span> GMT.</value>
 
"color: #000096"></data>

"color: #000096"></msgList>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>LocNote test: Default</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>This is a 
    
"color: #000096"><span its-loc-note="Check with terminology engineer" its-loc-note-type=alert>
     motherboard</span>.</p>
  
"color: #000096"></body>

"color: #000096"></html>

8.4 Terminology

<text>
  "color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><its:termRule selector="//term" term="yes" termInfoPointer="id(@def)"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><p>We may define <term def="TDPV">discoursal point of view</term> as 
    
"color: #000096"><gloss xml:id="TDPV">the relationship, expressed through discourse structure, between the
    implied author or some other addresser, and the fiction.</gloss></p>

"color: #000096"></text>

<text>
<its:rules
version
=
"2.0"
xmlns:its
=
"http://www.w3.org/2005/11/its"
>
<its:termRule
selector
=
"//term[1]"
term
=
"yes"
termInfoRef
=
"#TDPV"
/>
</its:rules>
<p>
We
may
define
<term>
discoursal
point
of
view
</term>
as
<gloss
xml:id
=
"TDPV"
>
the
relationship,
expressed
through
discourse
structure,
between
the
implied
author
or
some
other
addresser,
and
the
fiction.
</gloss>
</p>
</text>

<text>
  "color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><its:termRule selector="//term[1]" term="yes"
                  
"color: #F5844C">termInfoRef="#TDPV"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><p>We may define <term>discoursal point of view</term>
as <gloss xml:id="TDPV">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss></p>

"color: #000096"></text>

<text>
<its:rules
version
=
"2.0"
xmlns:its
=
"http://www.w3.org/2005/11/its"
>
<its:termRule
selector
=
"//term"
term
=
"yes"
termInfoRefPointer
=
"@target"
/>
</its:rules>
<p>
We
may
define
<term
target
=
"#TDPV"
>
discoursal
point
of
view
</term>
as
<gloss
xml:id
=
"TDPV"
>
the
relationship,
expressed
through
discourse
structure,
between
the
implied
author
or
some
other
addresser,
and
the
fiction.
</gloss>
</p>
</text>

<text>
  "color: #000096"><its:rules version="2.0"  xmlns:its="http://www.w3.org/2005/11/its">
    
"color: #000096"><its:termRule selector="//term" term="yes"
                   
"color: #F5844C">termInfoRefPointer="@target"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><p>We may define <term target="#TDPV">discoursal point of view</term>
as <gloss xml:id="TDPV">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss></p>

"color: #000096"></text>

"color: #000096"><book its:version="2.0" xmlns:its="http://www.w3.org/2005/11/its" 
  
"color: #F5844C">its:annotatorsRef="terminology|http://example.com/term-tool">
  
"color: #000096"><head>...</head>
  
"color: #000096"><body>

    ... 
    And he said: you need a new 
       
        

    "color: #000096"><p>And he said: you need a new 
      
"color: #000096"><quote its:term="yes" 
        
"color: #F5844C">its:termInfoRef="http://www.directron.com/motherboards1.html"
        
"color: #F5844C">its:termConfidence="0.5">motherboard</quote></p>

    ...
  

 "color: #000096"></body> 

"color: #000096"></book>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>Terminology test: default</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>We need a new <span its-term=yes>motherboard</span>
    
"color: #000096"></p>
  
"color: #000096"></body>

"color: #000096"></html>

8.5 Directionality

"color: #000096"><text xml:lang="en">
  
"color: #000096"><body>
    
"color: #000096"><par>In Hebrew, the title <quote xml:lang="he" direction="rtlText">פעילות
      ×”×‘×™× ××•×, W3C</quote> means "Internationalization Activity, W3C",
      and the order of characters is <bdo direction='rtlText'>פעילות 
          ×”×‘×™× ××•×, W3C</bdo>.</par>
  
"color: #000096"></body>

"color: #000096"></text>

"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
  
"color: #000096"><its:dirRule dir="rtl" selector="//*[@direction='rtlText']"/>
  
"color: #000096"><its:dirRule dir="rlo" selector="//bdo[@direction='rtlText']"/>

"color: #000096"></its:rules>

"color: #000096"><text xml:lang="en" xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><body>
    
"color: #000096"><par>In Arabic, the title <quote xml:lang="ar" its:dir="rtl">نشاط التدويل،
        W3C</quote> means "Internationalization Activity, W3C".</par>
  
"color: #000096"></body>

"color: #000096"></text>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
    
"color: #000096"><title>Dir test: Default</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>In Arabic, the title <q dir=rtl lang=ar>نشاط التدويل، W3C</q>
      means "Internationalization Activity, W3C".</p>
  
"color: #000096"></body>

"color: #000096"></html>

8.6 Language Information

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:langRule selector="//p" langPointer="@mylangattribute"/>

"color: #000096"></its:rules>

8.7 Elements Within Text

"color: blue"><!DOCTYPE html>
<html>  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8> 
    
"color: #000096"><title>Elements within Text defaults for HTML5</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
   
"color: #000096"><p>The element p is not within text. But <em>the element em is</em>.</p>
   
"color: #000096"><p>A button <button onclick="display()">Click Here</button> is also within text.
But <textarea>The content of textarea</textarea> is nested.</p>
Some additional text...

"color: #000096"><script><!--
function display() {
alert("The script element is nested."); }
//-->

"color: #000096"></script>

"color: #000096"><noscript>The noscript element is nested.</noscript>
  
"color: #000096"></body>

"color: #000096"></html>

"color: #000096"><its:rules version="2.0" xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><its:withinTextRule withinText="yes" selector="//b | //em | //i"/>

"color: #000096"></its:rules>

"color: #000096"><text xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><body>
    
"color: #000096"><par>Text with <bold its:withinText="yes">bold</bold>.</par>
  
"color: #000096"></body>

"color: #000096"></text>

"color: blue"><!DOCTYPE html>

<html>
  
     
    
  
  
    
  
</html>

  "color: #000096"><head>
    
"color: #000096"><meta charset=utf-8> 
    
"color: #000096"><title>Within text test: Default</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p>Text with <span its-within-text='yes'>bold</span>.</p>
  
"color: #000096"></body>

"color: #000096"></html>

8.8 Domain

"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0"
           
"color: #F5844C">xmlns:h="http://www.w3.org/1999/xhtml">
  
"color: #000096"><its:domainRule selector="/h:html/h:body"
                  
"color: #F5844C">domainPointer="/h:html/h:head/h:meta[@name='keywords']/@content"/>

"color: #000096"></its:rules>

"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0"
           
"color: #F5844C">xmlns:h="http://www.w3.org/1999/xhtml">
  
"color: #000096"><its:domainRule selector="/h:html/h:body"
    
"color: #F5844C">domainPointer="/h:html/h:head/h:meta[@name='dcterms.subject' or @name='keywords']/@content"
    
"color: #F5844C">domainMapping="automotive auto, medical medicine, 'criminal law' law, 'property law' law"/>

"color: #000096"></its:rules>

8.9 Text Analysis

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang="en" its-annotators-ref="text-analysis|http://enrycher.ijs.si">
  
"color: #000096"><head>
    
"color: #000096"><meta charset="utf-8" />
    
"color: #000096"><title>Text analysis: Local Test</title>
  
"color: #000096"></head>      
  
"color: #000096"><body>
    
"color: #000096"><p><span 
          
"color: #F5844C">its-ta-confidence="0.7"
          
"color: #F5844C">its-ta-class-ref="http://nerd.eurecom.fr/ontology#Location"  
          
"color: #F5844C">its-ta-ident-ref="http://dbpedia.org/resource/Dublin">Dublin</span> 
      is the <span 
          
"color: #F5844C">its-ta-source="Wordnet3.0" 
          
"color: #F5844C">its-ta-ident="301467919" 
          
"color: #F5844C">its-ta-confidence="0.5"
          >capital</span> of Ireland.</p>
  
"color: #000096"></body>

"color: #000096"></html>

"color: blue"><!DOCTYPE html>

"color: #000096"><html lang=en>
  
"color: #000096"><head>
    
"color: #000096"><meta charset=utf-8>
      
"color: #000096"><link href=EX-text-analysis-html5-rdfa.xml rel=its-rules>
        
"color: #000096"><title>Entity: Local Test</title>
  
"color: #000096"></head>
  
"color: #000096"><body>
    
"color: #000096"><p><span property="http://xmlns.com/foaf/0.1/name"
      
"color: #F5844C">about="http://dbpedia.org/resource/Dublin"
      
"color: #F5844C">typeof="http:/nerd.eurecom.fr/ontology#Location">Dublin</span> is 
      the capital of Ireland.</p>
  
"color: #000096"></body>

"color: #000096"></html>

"color: #000096"><its:rules xmlns:its="http://www.w3.org/2005/11/its" version="2.0">
  
"color: #000096"><its:textAnalysisRule selector="//*[@typeof and @about]" 
    
"color: #F5844C">taClassRefPointer="@typeof" taIdentRefPointer="@about"/>

"color: #000096"></its:rules>

8.10 Locale Filter

"color: #000096"><book xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><info>
    
"color: #000096"><its:rules version="2.0">
      
"color: #000096"><its:localeFilterRule selector="//legalnotice[@role='Canada']"
        
"color: #F5844C">localeFilterList="*-CA"/>
      
"color: #000096"><its:localeFilterRule selector="//legalnotice[@role='nonCanada']"
        
"color: #F5844C">localeFilterList="*-CA" localeFilterType="exclude"/>
      
"color: #000096"><its:localeFilterRule selector="//remark"
        
"color: #F5844C">localeFilterList=""/>
    
"color: #000096"></its:rules>
    
"color: #000096"><legalnotice role="Canada">
      
"color: #000096"><para>This notice is only for Canadian locales.</para>
    
"color: #000096"></legalnotice>
    
"color: #000096"><legalnotice role="nonCanada">
      
"color: #000096"><para>This notice is for locales that are non-Canadian locales.</para>
    
"color: #000096"></legalnotice>
    
"color: #000096"><remark>Note: This section will be written later.</remark>
  
"color: #000096"></info>

"color: #000096"></book>

"color: blue"><!DOCTYPE html>

<html>
 
   
  
   
  
  
   
  
  
   
  
 

 "color: #000096"><head>
  
"color: #000096"><meta charset=utf-8> 
  
"color: #000096"><title>Locale filter</title>
 
"color: #000096"></head>  
 
"color: #000096"><body> 
  
"color: #000096"><div its-locale-filter-list="*-ca">
   
"color: #000096"><p>Text for Canadian locales.</p>
  
"color: #000096"></div>
  
"color: #000096"><div its-locale-filter-list="*-ca" its-locale-filter-type="exclude">
   
"color: #000096"><p>Text for non-Canadian locales.</p>
  
"color: #000096"></div>
 
"color: #000096"></body>

"color: #000096"></html>

"color: #000096"><book xmlns:its="http://www.w3.org/2005/11/its">
  
"color: #000096"><info>
    
"color: #000096"><legalnotice its:localeFilterList="en-CA, fr-CA">
      
"color: #000096"><para>This legal notice is only for English and French Canadian locales.</para>
    
"color: #000096"></legalnotice>
  
"color: #000096"></info>

"color: #000096"></book>

8.11 Provenance

"color: #000096"><text xmlns:dc="http://purl.org/dc/elements/1.1/"
  
"color: #F5844C">xmlns:its="http://www.w3.org/2005/11/its" its:version="2.0">
  
"color: #000096"><dc:creator>John Doe</dc:creator>
  
"color: #000096"><its:provenanceRecords xml:id="pr1">
    
"color: #000096"><its:provenanceRecord
      
"color: #F5844C">toolRef="http://www.example.onlinemtex.com/2012/7/25/wsdl/"
      
"color: #F5844C">org="acme-CAT-v2.3"
      
"color: #F5844C">revToolRef="http://www.mycat.com/v1.0/download"
      
"color: #F5844C">revOrg="acme-CAT-v2.3"
      
"color: #F5844C">provRef="http://www.examplelsp.com/excontent987/production/prov/e6354"/>
  
"color: #000096"></its:provenanceRecords>
  
"color: #000096"><its:provenanceRecords xml:id="pr2">
    
"color: #000096"><its:provenanceRecord
      
"color: #F5844C">person="John Doe"
      
"color: #F5844C">orgRef="http://www.legaltrans-ex.com"
      
"color: #F5844C">revPerson="Tommy Atkins"
      
"color: #F5844C">revOrgRef="http://www.example.myorg.com"
      
"color: #F5844C">provRef="http://www.example.myorg.com/job-12-7-15-X31/reviewed/prov/re8573469"/>
    
"color: #000096"><its:provenanceRecord
      
"color: #F5844C">revPerson="John Smith"
      
"color: #F5844C">revOrgRef="http://john-smith.qa.example.com"/>
  
"color: #000096"></its:provenanceRecords>
  
"color: #000096"><its:rules version="2.0">
    
"color: #000096"><its:provRule selector="//*[@ref]" provenanceRecordsRefPointer="@ref"/>
  
"color: #000096"></its:rules>
  
"color: #000096"><title>Translation Revision Provenance Agent: Global Test in XML</title>
  
"color: #000096"><body>
    
"color: #000096"><par ref="#pr1"> This paragraph was translated from the machine.</par>
    
"color: #000096"><legalnotice postediting-by="http://www.example.myorg.com" ref="#pr2">This text was
      translated directly by a person.</legalnotice>
  
"color: #000096"></body>

"color: #000096"></text>