- From: Lieske, Christian <christian.lieske@sap.com>
- Date: Thu, 10 Nov 2005 15:34:18 +0100
- To: <public-i18n-its@w3.org>
Dear all, Here's the second round of comments (pertaining to section 2) for the document which is available for comments (I copied the text on around 3pm of my working day). The methodology I used for commenting is the following: 1. quote text from original document 2. introduce general comment by [CL>] 3. possibly suggest specific modification, addition, rephrasing (bracketed by [CLXXXSuggestionStart>] and [CLXXXSuggestionEnd>] Best regards, Christian Christian Lieske MultiLingual Technology (MLT) Globalization Services (SLS) SAP AG --- [CLRephraseSuggestionStart>] This document defines the XML Localization and Internationalization Markup Language (XLIM), a language which supports the internationalization and localization of XML schemas and XML instances. In addition to background information, and usage scenarios, this document provides three formal definitions of XLIM: as XML DTD, XML Schema and RELAX NG. In addition, the document exemplifies how XLIM can be used with existing vocabularies (e.g. XHTML, DocBook, Open Document schema). [CLRephraseSuggestionEnd>] Send your comments to www-i18n-comments@w3.org. Use "Comment on its WD" in the subject line of your email. The archives for this list are publicly available. [CL>] Is this the correct list? 2 Notation and Terminology 2.1 Notation and Terminology [CL>] I suggest to drop this sub-heading and the subsequent ones (to condense the table of contents and make the document more compact in general). 2.2 Namespaces used in this Specification 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 this URI is "its". In addition, the following namespaces are used: http://www.w3.org/2000/10/XMLSchema for the XML Schema namespace, here used with the prefix "xs". http://relaxng.org/ns/structure/1.0 for the RELAX NG namespace, here used with the prefix "rng". [CL>] I suggest to add some words on the namespace approach ... [CLRephraseSuggestionStart>] Markup for information related to internationalization and localization needs to be recognized reliably by humans and applications in order to be handled properly. XLIM uses the mechanism described in the Namespaces in XML Recommendation [XML Names] to accomplish recognition of the constructs in the XLIM vocabulary. The XLIM namespace defined by this specification has the following URI: http://www.w3.org/2005/11/xlim The namespace prefix used in this specification for this URI is "xlim". In addition, the following namespaces are used: http://www.w3.org/2000/10/XMLSchema for the XML Schema namespace, here used with the prefix "xs". http://relaxng.org/ns/structure/1.0 for the RELAX NG namespace, here used with the prefix "rng". [CLRephraseSuggestionEnd>] 2.3 Data Category and Data Category Implementation ITS defines [Definition: data categories as a description of information for internationalization and localization of XML schemas and documents. This description is independent of its implementation e.g. via an element or attribute. ]. There are three levels to be taken into account: an informal description of data categories, cf. Section 4: Description of Data Categories schema language independent implementation of data categories, which is described separately for each data category in Section 4: Description of Data Categories schema language specific implementation of data categories, cf. Appendix A: Schemas for ITS Example 3: Data categories and their implementation The data category of translatability conveys mainly information whether a text should be translated or not. The simplest implementation of this informal description on a schema language independent level is a translate attribute with two possible values yes or no. Another implementation on a schema language independent level would be an element schemaRule which conveys rules about translatability via various attributes / subelements, describing defaults and exceptions. Such implementations can then be realized by the element and / or attribute declarations in various schema languages. [CL>] I suggest to move the above to the proposed section on 'Important Design Decisions'. Furthermore, I suggest the following rephrasing. Motivation for these suggestions: From my understanding, the abstraction layer which Felix has suggested to our work and which Sebastian's/the TEI's ODD allowed us to code, is a very central notion of our approach. The rephrasal suggestion is meant to capture the fact that our 'indicator of translatability' really intends to capture the information 'translate this!' or 'don't translate this!'. Furthermore, the suggestion covers the fact that the data category does not only pertain to text. Furthermore, 'translation trigger' appears to express that we don't want to say 'This is translatable' but rather that we want to trigger a translation. [CLRephraseSuggestionStart>] Data Category and Data Category Implementation: XLIM defines 'data category' as an abstract concept for a particular type of information for internationalization and localization of XML schemas and documents. The data category 'translation trigger' conveys mainly information whether a piece of content should be translated or not. The concept of a data category is independent of its implementation in an XML environment (e.g. via an element or attribute). For each data category, XLIM strictly destinguishes between the following - the prose description, cf. Section 4: Description of Data Categories - schema language independent formalization, cf. Section 4: Description of Data Categories - schema language specific implementation, cf. Appendix A: Schemas for ITS Example: The data category 'translation trigger' conveys mainly information whether a a piece of content should be translated or not. The simplest formalization on a schema language independent level is an unstructured 'translate' property with two possible values: 'yes' and 'no'. An implementation on a schema language specific level would be an attribute 'translate'. An alternative formalization on a schema language independent level is a structured 'schemaRule' property which conveys information about the necessity to translate via an element with various sub-properties describing defaults and exceptions. An implementation on a schema language specific level could be realized by an element with various sub-elements and attributes. [CLRephraseSuggestionEnd>] 2.5 Scope [Definition: Scope is a means to describe to what elements and / or attributes an ITS data category and its values should be applied to.]. Scope is discussed in detail in Section 3: Scope of ITS information. [CL>] I suggest to remove this paragraph altogether, since the content is already covered in to the proposed section on 'Important Design Decisions'.
Received on Thursday, 10 November 2005 14:34:36 UTC