1 / 40

Workshop on cultural and linguistic adaptability

Workshop on cultural and linguistic adaptability. References ISO/TC 211 N 772 Summary of activity concerning cultural and linguistic adaptability ISO/TC 211 N 785 Report on Unique Identifiers for encoding purposes. September 28, 1999 Kyoto, Japan.

kaiyo
Download Presentation

Workshop on cultural and linguistic adaptability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workshop on cultural and linguistic adaptability ReferencesISO/TC 211 N 772Summary of activity concerning cultural and linguistic adaptabilityISO/TC 211 N 785 Report on Unique Identifiers for encoding purposes September 28, 1999 Kyoto, Japan

  2. Resolution 91 - Cultural and linguistic adaptability ISO/TC 211 recognizes the importance of cultural and linguistic adaptability and requests nations to review the relevant documents from ISO/IEC JTC 1, JTC 1/SC 35 and other sources (including national/regional requirements) and to provide comments to the secretariat by 1999-06-01.ISO/TC 211 requests its chairman to compile these comments and prepare a summary for review by members prior to the 9th Plenary in Kyoto. ISO/TC 211 requests its chairman to convene during the meeting week in Kyoto a workshop to address the summary report on cultural and linguistic adaptability within ISO/TC 211.

  3. ISO/IEC JTC 1/SC 35 : Cultural and Linguistic Adaptability" is the ability for a product, while keeping its portablilty and interoperability properties, to: - be internationalized, that is, be adapted to the special characteristics of natural languages and the commonly accepted rules for their use, or of cultures in a given geographic region; - fully take into account the needs of any category of users.

  4. Internationalization The term "internationalization" is defined in ISO/IEC TR 11017 as a process of producing an application platform or application which is easily capable af being localized for (almost) any cultural environment. Examples of characteristics of natural languages are: national characters and associated elements (such as hyphens, dashes, and punctuation marks), writing systems, correct transformation of characters, dates and measures, sorting and searching rules, coding of national entities, (such as country and currency codes), presentation of telephone numbers and keyboard layouts. Related terms are localization, jurisdiction and multilingualism.

  5. NB of Japan Japan points to the importance of the issue and the work of ISO/IEC JTC 1/SC 35. Japan believes that Cultural and linguistic adaptability should be respected. We are now reviewing concrete examples. ISO/IEC JTC1,JTC 1/SC 35 is discussing this problem, so we had better to get as much information as possible from them. The relationship with ISO/IEC JTC 1/SC 35 will be discussed later in this document.

  6. NB of Spain The NB of Spain points at the following important points for considering CLA: to fully address specific cultural characteristics • to avoid potential reluctance against the implementation of the standard • to speed up the process of dissemination and implementation of the standard Spain especially emphasizes the need for CLA in concern with the following ISO/TC 211 projects Part 10 Feature Cataloguing Methodology, Part 15 Metadata and Part 18 Encoding. CLA must be considered with respect to neutral identifiers and also with respect to neutral codification of possible values for items

  7. SC 35 scope Standardization in the field of interfaces between users (including people with special needs) and systems, encompassing input and output devices in information technology environments, with the priority of meeting the JTC 1 requirements for cultural and linguistic adaptability. The standardization work on SC 35 includes the following areas: • interfaces between users and devices, such as keyboards, mice, pointers, pens, visual displays, and forms of audio and tactile input/output, with the emphasis on functionality • rules for system control by voice, vision, movement, gestures, etc. • presentation techniques, icons, graphical symbols, etc. • dialogue control and navigation in interactions between humans and systems systems assistance and tutoring

  8. SC 35 resolution RESOLUTION N 27 (Québec, May 1999) IT-Interface and user Interfaces: Cultural and linguistic Adaptability SC 35 resolves that with respect to interworking among information and communication systems, JTC1 should ensure that future standards support the development of unique, unambiguous and linguistically neutral identifiers for values. This will facilitate the production of multilingual equivalent values from a human user interface perspective. SC 35 recommends that JTC1 solicit input from its SCs on how best to accomplish this.

  9. SC 35 resolution RESOLUTION N 29 (Québec, May 1999) Liaison with ISO/TC 211 ISO/IEC JTC 1/SC 35 appreciates the excellent presentation by Mr Yves Hudon of ISO/TC 211 (Geographic information/Geomatics) activities. SC 35 is interested to cooperate with ISO/TC 211 in a cultural and linguisticadaptability and user interface perspective. SC 35 will value to have a formal liaison with ISO/TC 211 in a near future.

  10. SC 35 resolution RESOLUTION N 34 (Québec, May 1999) Next meetings SC 35 next meeting is scheduled in Paris, 22nd to 26th November 1999. The following meeting is scheduled in Japan. Tentative date is May 15th to 19th 2000.

  11. Recommendations The following should be discussed by the ISO/TC 211 in the Kyoto plenary: • ISO/TC 211 should welcome the invitation from SC 35 and request a liaison connection to be established with ISO/IEC JTC 1/SC 35 User Interfaces • ISO/TC 211 should adopt and implement appropriate principles of CLA as soon as possible. Such principles must be in compliance with ISO/IEC JTC 1/SC 35 work in the field

  12. Recommendations, …cont. • A survey of relevant places in the standards under development by ISO/TC 211 where CLA should be taken into account, should be conducted prior to and presented at the next plenary in South Africa • Compliance with CLA principles should not delay the progress of accepted work items – where appropriate work on technical addendums, or other means, should be started as soon as practically possible • Following the liaison request for SC 35, ISO/TC 211 representatives should attend SC 35 meeting in Paris, November 22-26

  13. Report on Unique Identifiers for Encoding Purposes Report regarding resolution 92 in Vienna For review by the TC211 workshop on Cultural and Linguistic Adaptability and by WG4 Work Item 18 Ad hoc Group on Unique Identifiers September 29-30, 1999 Kyoto, Japan

  14. Background • In the ISO/TC 211 Vienna-plenary the following resolution was adopted: • Resolution 92 - Unique identifiers for encoding purposes • ISO/TC 211 accepts Canada's offer to resource the work to develop rules for the generation of unique identifiers for encoding purposes. As this work is related to 15046-18 (encoding), the work should be done in close communication with the project team for 15046-18. • The work shall address the issue of cultural and linguistic adaptability, and be completed in time to be sent out one month prior to 9th ISO/TC211 Plenary in Kyoto.

  15. Use of Identifiers • The suite of TC211 standards is linked by identifiers. • Each part of the TC211 suite of standards defines a set of rules or a component model that can be integrated based on the UML object or attribute identifiers for requirements and specifications stated in that part. • A profile can then be defined based in these integrated parts. In fact it is only the profile that is ever implemented. The suite of TC211 standards define an abstract model for the creation of profiles.

  16. UML Names • The TC 211 standards usethe UML modelling language, to the model components and present an integrated (harmonized) abstract model of the common requirements and definitions stated and specified in these standards . • UML uses the term “names” for identifiers. These exist for objects, attributes and relationships. These ID names must be used consistently across the TC211 model components and in profiles.

  17. Names in Profiles • Since the TC211 standards are abstract, profiles may be freely developed out of any of the parts, and may be integrated with profile specific elements. • A profile may give a more specific meaning to any named element. • Since profiles may be defined in application domains that already have well established terminology there is a need to define a mechanism to address the relationship between independent ID name spaces. • Names in conflict with TC211 names, may be in use in the domain in which a profile is defined. Such conflicts can be accommodated.

  18. Names in Multiple Languages • The TC211 standards and profiles may be defined in different languages. It is normal practise in ISO that an equivalent parallel edition be issued in French. • Many countries may adopt the standards and publish relevant parts or all of the standards in any other language. • This will also require a mechanism to address the relationship between different name spaces(directly or indirectly).

  19. Encoding Name Space • 15046-18 defines a mechanism for encoding data in accordance with an application schema specified in a profile. • Different encoding standards may be used to actually exchange the data. XML is defined as a neutral encoding method. • An encoding process defines delimiters and identifiers (tags) for instances of named entities in the model defined in a profile. • A mechanism is needed to address the relationship between entities in a name spaces and tags/identifiers for encoding. • Note: encoding is not the same as assigning codes to a value.

  20. Independent Name Spaces in Profiles

  21. Equivalence Table A table is required that relates the objects, attributes and relations in the profile to that in the base standards. For example:

  22. Different Language TC211 Standards Example from 15046-7 (English Edition)

  23. Different Language TC211 Standards Example in French

  24. Different Language TC211 Standards Example in Chinese

  25. Equivalence Tables • All three of these schemas are equivalent, but they have different names. • It is necessary to have a mechanism which equates the common identifiers to the namesused in each of these linguistically equivalent schemas for “the same requirements”.

  26. Form of Equivalence Tables • All three of these schemas are equivalent, but they have different namesfor the same IDs. • The English edition of the standard would contain a table of all Objects, Attributes, and Relations including Role names and Constraints in English. • A similar table would exist in the other language editions of the standard. • The numeric order of the elements in this table establishes the pivot upon which equivalences from one language to another can occur. The numeric pivot provides an indirect relationship.

  27. Example Equivalence Tables

  28. Example Equivalence Tables Chinese edition of standard

  29. Unique Identifiers for Encoding • The encoding process requires the definition of "Tags" or some other equivalent form of identifier.. • Identifiers are central to the encoding/decoding process. However it is not possible to define a universal set of tags/identifiers that will suite all applications. • The encoding process must deal with the definition of tags within the context of a profile. • The encoding process also needs a table to assign tags to model elements. • This table would also include other information that is required for encoding such as the basic data types and whether an item is to be encoded as an attribute or an element. • These should all be defined and specified.

  30. Unique Identifiers for Encoding • The proposed structure of the multilingual equivalencies table is given below: • NAME - The name used in the UML Schema REFERENCED • NT - NameType: The type of the name, e.g., class(c), attribute (cp),association/aggregation (ca) and composition (cc). • M - Multiplicity: The multiplicity of the attribute/association. • DT - DataType: The data type of the attribute, association-end. • ESD - Encoding-service-directive: Directive to the encoding service on how to encodeattributes, data types, and other information. (A) Attribute, (E) - Element • TAG - An optional short name or "Tag". If no name is given the UML name is used.

  31. Unique Identifiers for Encoding • # PACKAGE Distribution (in English edition of the standard) • ID NAME NT M DT ESD TAG • 168 Medium C Med • 169 name cp 1 String A • 170 density cp 1 Real E dnst • 171 densityUnits cp 1 String E dnsu • 172 volumes cp 1 Integer E vol • 173 mediaFormat cp 1 String E form • 174 compatibility cp 1 String E comp • 175 DigitalTransferOptions C • 176 unitsOfDistribution cp 1 String A uodis • 177 transferSize cp 1 Real A tsize • 178 offLine ca 0..1 Medium E • 179 onLine ca 0..1 Online Resource E • etc....

  32. Cultural and Linguistic Adaptability • The principals of Cultural and Linguistic Adaptability have a broad general acceptance. • Endeavouring to produce neutral codes and identifiers is difficult, since there is no frame of reference. • Defining "neutral” can be avoided by the use of equivalence tables. • This is Cultural and Linguistic Adaptability, rather than neutrality.

  33. Cultural and Linguistic Adaptability The cultural and linguistic adaptability as set out by ISO JTC1 SC35 is described below. "Cultural and Linguistic Adaptability" is the ability for a product, while keeping its portability and interoperability properties, to: - be internationalized, that is, be adapted to the special characteristics of natural languages and the commonly accepted rules for their use, or of cultures in a given geographic region; - fully take into account the needs of any category of users. The term "internationalization" is defined in ISO/IEC TR 11017 as a process of producing an application platform or application, which is easily capable of being localized for (almost) any cultural environment.

  34. The Domain of Localization • Most of the aspects of a system that require localization relate to the User Interface to that system. This includes the correct presentation of character sets, dates, systems of measure, currency, telephone numbers, etc. • Other aspects of localization relate to the user interface or implementation of a Geographic Information System are sorting and searching rules. • Encoding is concerned that the domain of values that are encoded are sufficiently broad to accommodate all needs. • Character sets are particularly important and should use ISO/IEC 10646.

  35. Localization Mechanism • There are two mechanisms available to allow for localization of the TC211 standards. These are: • the definition of " unique, unambiguous and linguistically neutral identifiers", and • the use of equivalence tables. These approaches are complementary.

  36. Neutral Identifiers • Examples of Neutral Identifiers: • In botany and medicine the use of Latin language based terms is deemed to be linguistically neutral. • In ICAO/IATA, a specialized use of terms based on the English language is deemed to be linguistically neutral (look at airport codes). • Some "Special languages" used in industry sectors are deemed to be linguistically neutral. • The main challenge is that of assignment of identifiers within value domains. • Neutral Identifiers must be developed by agreement and are difficult to achieve in general.

  37. Equivalence Tables • Using equivalence tables the entire localization is the responsibility of the national group that developed a national version of an ISO standard or developed a profile. • In the case of international standard components and standardized schemas, equivalence tables should exist in each of the different language versions of the international standard. • The equivalence table approach works on the order of elements in the table. ID numbers are implied. A tag code described uniquely in terms of one table can easily be converted to that in another table. • All other aspects of localization can also be accomplished through use of the equivalence table.

  38. Equivalence Tables • The equivalence table approach has other benefits. It also provides specific information that assists the encoding process. • This information is necessary even if the equivalence table were not used for localization.

  39. Recommendations • Recommendation 1: It is proposed that an equivalence table mechanism be used in TC211 to facilitate encoding and to permit for Cultural and Linguistic Adaptability. • Recommendation 2: It is proposed that TC211 adopts the following resolution. Resolution xx - Equivalence tables ISO/TC211 recognises the need for Cultural and Linguist Adaptability in the TC211 suite of standards and the utility of providing additional information to assist an encoding process. It therefore adopts the use of equivalence tables for the use of Localization and encoding. Each of the parts of the TC211 suite of standards that contain schemas or define data elements shall include a normative annex containing a equivalence table identifying all of the schema and data elements. The Encoding Project Team in co-operation with the Model Harmonization Team shall provide the format of this table.

  40. Aspects of Adaptability • There are four areas of Cultural and Linguistic Adaptability that need to be addressed in TC211. • Character set -  Handled by ISO Standard 10646 • Identifier -  Handled by Equivalence Tables • Enumerated values - 70% handled • Multi languages in Free Text - Propose to use ISO 11179-3

More Related