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

Hi Christian,

first, independent of your proposals, one suggestion:

s/Using a custom mechanism specific to a given format (e.g. the conref 
attribute in [DITA 1.0])./
Using a mechanism specific to a given format (e.g. the conref attribute 
in [DITA 1.0])./

Lieske, Christian wrote:
> Hi all,
>
> I had a look at "Best Practice 21: Ensure any inserted text is
> context-independent".
>
> Please find my high-level feedback below.
>
> Cheers,
> Christian
> ===
> 1. To me, the explanation "What is inserted text?" should come before the
> "Why do this". Maybe, we may
> 	even want to talk about "composite texts or documents" (see 4.
> below) since that term might
> 	be known to more people.
>
> 2. I wonder to which specific requirement this BP pertains. Is it "
> http://www.w3.org/TR/itsreq/#variables"?
>
> 3. Should we really have a separate BP about entity references (cf. BP 22).
> We mention them already in this BP.
>   

I would propose to drop BP 22.

> 4. I wonder if we should not point to far more information from the
> documents which we cite as references.
> 	See for example the very nice recommendations (e.g. advice against
> sentence-like arrangements) in the article on "composite messages"
> (http://www.w3.org/International/articles/composite-messages/).
>
> 5. Aren't we missing a BP for schema developers which corresponds to this
> BP? One of the key points is the
> 	use of identifiers which allow for example the reordering of
> variables/placeholders during translation.
> 	Those identifiers, however, need to be incorporated into the XML
> vocabulary by a schema developer in the first place ;-)
>   

by identifiers do you mean ID attributes? If yes, I would point to BP 
9about xml:id, and mention in that BP your use case.

Cheers,

Felix

> 6. In order to acknowledge the recommendation (from the article on
> "composite messages")
>
> 	> Provide information to the translator, where needed, to clarify
> what a substring represents
> 	> (eg. something like "%s near '%s' at line %d" can pose a challenge
> for a translator).
>
>    we could tell people that they can possible use the ITS data categories
> "Localization Note" and "Terminology" for doing this.
>
> 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.
>
>

Received on Tuesday, 28 August 2007 13:15:16 UTC