Input to BP 24: http://www.w3.org/International/its/techniques/its-techniques.html#AuthTermOver

Hi all,

I had a look at "Best Practice 24: Identify terms".

Please find my high-level feedback below. Sorry that I am only able to suggest alternatives in some cases.

Cheers,
Christian
=========

1.

Quote> Identify terms

Quote > Make sure to mark up any words or expressions that needs to be translated consistently.

I wonder if this captures properly what we from my understanding intend to say:

      Ensure that any terminology-related content is marked up properly. Proper markup has the following dimensions:

a. existence of terminology-related markup in your native vocabulary (e.g. a "term" element) or provisions for "its:term"
b. an ITS rules file which describes terminology-related markup in your native vocabulary in ITS terms
c. application of the terminology-related markup by authors for marking, supplementing, or overriding

With this perspective, I would say that alternative wording could be

Proposal> Use terminology-related markup properly

Proposal> Mark terms, supply term-related information, or override default terminology rules 
==
2.

Quote> Use its:term and its:termInfoRef (or their equivalent in your DTD or schema) to identify words or expressions that should remain consistent within the information set.

"Remain consistent" only captures one aspect. "information set" may evoke unwanted connotations.
==
3.

Quote> Terms include names of functions .

I would guess that we possibly evoke semi-philosophical feedback if we try to define what counts as term.
==
4.

I am would be interested in an example which show why one would want to "override".
==
5.

I wonder if, for example when mentioning "starting a translation project with the translation of terminology", we should have a bridge to terminology-related formats. You could for example say "If terms are marked up, they can be extracted and brought into a terminology-related exchange format such as X, Y, Z. That format then could be used to be imported into a terminology database (and in turn be used - after translation - in term lookup functionalities or translation memory contexts).
==
Christian Lieske
MultiLingual Technology Solutions (MLT)
SAP Language Services (SLS)
SAP Globalization Services
SAP AG
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
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.