W3C home > Mailing lists > Public > public-i18n-its@w3.org > July to September 2007

Re: Input to BP 10 http://www.w3.org/International/its/techniques/its-techniques.html#DevTerm

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 13 Jul 2007 01:25:41 +0900
Message-ID: <46965605.1000803@w3.org>
To: "Lieske, Christian" <christian.lieske@sap.com>
CC: public-i18n-its@w3.org

Hi Christian,

Lieske, Christian wrote:
> Hi all,
> I had a look at "Best Practice 10: Indicate terminology-related elements".
> My high-level feedback is the following:
> 1.
> Quote>Define what elements are related to terminology information
> It may sound academic, but don't we really want to say "Define which element are related to designators?" (see ISO 1087).

we have not used the term "designators" in the ITS spec, but have been 
rather informal about what terminology information is. So I would 
propose not to introduce "designators" here.

> 2.
> Quote>You should provide an ITS rules document where you use its:termRule elements
> Quote>to indicate which elements are "terms" and information related to them (e.g. definitions).
> Quote>
> Quote>This set of ITS rules indicates the following:
> I would suggest to rephrase this as "The set of ITS rules below indicates ..."
> 3. 
> Quote>The capability of specifying terms within the source content is important for terminology management that is beneficial to translation and localization quality.
> We discussed, if I remember correctly, that also source language quality and change management benefit from properly marking designators. You can for example match designators against material management repositories.
> 4. 
> Quote>Identified terms could be used for indexing that may require some language specific information. For example, Japanese words are sorted not by script characters, but by phonetic characters. Therefore when a Japanese index item is created, it should be accompanied with a phonetic string, called Yomigana.
> Hmm. Shouldn't this read: 
> 	Note: Often, indices need to contain more than the designators which have been marked in the text. In Japanese, for example ...
> 5. 
> Quote>As a result, terms may require various attributes, such as part of speech, gender, number, term types, definitions, notes on usage, etc. To avoid such a large attribute data is repeated within a document, it should be possible for identified terms to link to externalized attribute data, such as glossary documents and terminology database.
> We may want to find an alternative way to talk about "term-related information" (such as "gender" etc.). "attributes" may be confusing in an XML setting. How about "meta data" or "supplementary information"?

in the ITS spec, we have "terminology information", "providing 
information about the term", ... to be in sync with this, "supplementary 
information" might fit.


> ===
> Cheers,
> Christian
> Christian Lieske
> MultiLingual Technology Solutions (MLT)
> SAP Language Services (SLS)
> SAP Globalization Services
> Dietmar-Hopp-Allee 16
> D-69190 Walldorf
> Germany
> T   +49 (62 27) 7 - 6 13 03
> F   +49 (62 27) 7 - 2 54 18
> christian.lieske@sap.com <blocked::mailto:christian.lieske@sap.com> 
> http://www.sap.com <blocked::http://www.sap.com/> 
> Sitz der Gesellschaft/Registered Office: Walldorf, Germany
> Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Léo
> Apotheker (stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus
> Heinrich, Gerhard Oswald, Peter Zencke
> Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board:
> Hasso Plattner 
> Registergericht/Commercial Register Mannheim No HRB 350269
> Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige
> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich
> erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine
> Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt.
> Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail.
> Vielen Dank.
> This e-mail may contain trade secrets or privileged, undisclosed, or
> otherwise confidential information. If you have received this e-mail in
> error, you are hereby notified that any review, copying, or distribution of
> it is strictly prohibited. Please inform us immediately and destroy the
> original transmittal. Thank you for your cooperation.
Received on Thursday, 12 July 2007 16:27:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:13 UTC