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

RE: BP 8 - change update

From: Lieske, Christian <christian.lieske@sap.com>
Date: Wed, 4 Jul 2007 10:31:55 +0200
Message-ID: <544FBEB6875DAA46A08323B58D26B80101D23728@dewdfe14.wdf.sap.corp>
To: <public-i18n-its@w3.org>
Hi Yves/all,

>From my point of view, the proposed wording enhances the text we had before.

Having said that, two remarks:

Quote> The its:rules element provides access to the its:locNoteRule element

I am looking for an alternative to "provides access to". What about "allows
definition of"?

Quote> Note: its:rules can be created in a separate file, but it is more
efficient to allow the authors
Quote> to include the rules directly into their documents.

I don't understand, why "inclusion into a document" is more efficient.

Best regards,
Christian

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.
-----Original Message-----
From: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org]
On Behalf Of Yves Savourel
Sent: Mittwoch, 27. Juni 2007 18:39
To: public-i18n-its@w3.org
Subject: BP 8 - change update


Hi all,

During today's teleconf we discussed BP8, and we came up with some changes.
When I started to implement them I realize that they
don't seem right.

We had:

"Make sure the attributes its:locNote, its:locNoteType, as well as
its:locNoteRef are available in your DTD or schema.
Make also sure that the its:rules element is available somewhere in your
documents, for example in the header part if there is one."

We decided we could change to:

"Make sure the attributes its:locNote, its:locNoteType, as well as
its:locNoteRef are available in your DTD or schema.
Make also sure that the its:rules element is available in your document or a
separate file, for example in the header part if there
is one."

The idea was that its:rules can be outside the host document, and fill the
same role. But I think we don't have the right wording
for the audience of that BP (the developers)


=== First I think the first sentence needs to be more precise

"Make sure the attributes its:locNote, its:locNoteType, as well as
its:locNoteRef are available in your DTD or schema." I would use
'defined' instead of 'available':

"Make sure the attributes its:locNote, its:locNoteType, as well as
its:locNoteRef are defined in your DTD or schema."


=== Then for its:rules:

"Make also sure that the its:rules element is available in your document or
a separate file, for example in the header part if there
is one."

The developer of the schema (the audience here) cannot do anything about
having an external its:rule in a separate file. He/she can
only make sure it's defined in the schema so it can be used in the document.

This said, as Christian noted, the its:rules can also be a separate file. To
me it means having its:rules define in the schema is
less important than the local locnote markup (since the author as a way to
stll use it). We could mark than by different wording.
Maybe something like this (all sentences):

---------------------------------

"How to do this

Make sure the attributes its:locNote, its:locNoteType, as well as
its:locNoteRef are defined in your DTD or schema.

It is also recommended to define the its:rules element in your DTD or
schema, for example in a header if there is one. The its:rules
element provides access to the its:locNoteRule element which can be used to
specify localization-related notes and instruction at a
more general level. The its:locNoteRule element also allows for specifying
existing comments in an XML document via the
locNotePointer attribute, or providing an existing reference to comments via
the locNoteRefPointer attribute.

Note: its:rules can be created in a separate file, but it is more efficient
to allow the authors to include the rules directly into
their documents.

----------------------------------

What do you think?
-yves



Received on Wednesday, 4 July 2007 08:32:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:09 UTC