OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: FW: [dita] [I18N] Integrating the W3C ITS locNote into DITA: Options

Dear Friends,
Based on Christian's response to the question about the use of variable
substitutions, we had a discuss at the DITA TC today that is reflected in
Eliot's note attached here.

Best Practices 21 from the W3C ITS committee references the use of
loc.note to explain to translators the purpose of the variable name
(product name and so on). We would like to use loc.note in DITA for that
purpose as well but we cannot simply refer to the its namespace.

One question we had was a how translator tools display loc.note and
whether our solution possibilities noted below would apply. No point in
adding a DITA version of loc.note if the translator tools wouldn't be
about to see the comments.

Your help would be greatly appreciated. I'd also like to invite any member
of the SC to join the discussion at the DITA TC to help us understand the
usefulness of loc.note

Best regards,
JoAnn T. Hackos, PhD
Comtech Services Inc.
710 Kipling Street, Suite 400
Denver, CO 80215

On 1/29/13 10:05 AM, "Eliot Kimber" <ekimber@rsicms.com> wrote:

>Per the discussion on today's con call about integrating the ITS locNote
>element and/or attribute into DITA, I think the available options are:
>1. Use a specialization of foreign to hold the ITS elements as-is. This
>would provide full support for all of ITS markup at the cost of an
>additional level of wrapping, e.g.:
>  <its:locNote>...</its:locNote>
>2. Use <data> where the @name value is the ITS tag or attribute name:
><data name="its:locNote">This is a localization node</data>
>This can be done today but has more syntantic distance from the real ITS
>markup. An obvious enhancement would be to create a domain that
>from <data>, e.g. <its_locNote name="its:locNote">.
>This also raises the potential of introducing a commenting framework that
>would be parallel to <draft-comment>.
>3. Allow at least the @its:locNote attribute as global attributes on all
>DITA elements. 
>This would be easy to implement and would directly reflect part of the ITS
>markup. Because it's attributes it wouldn't affect any content models but
>would add a new namespace declaration, e.g.:
><topic xmlns:its="http://www.w3.org/2005/11/its:>
>  ...
>  <p its:locNote="This is a localization note">...
>  ...
>4. Define conventions and, ideally, a specialization of <draft-comment>
>capturing localization notes:
><draft-comment outputclass="its:locNote">This is a localization
>Which could be specialized to:
><its_locNote>This is a localization note</its_locNote>
>Note that we have a pending 1.3 enhancement to allow draft-comment in more
>5. Allow ITS elements directly. This would both break precendent of not
>having any non-DITA-defined elements directly-allowed and would be a major
>change to content models.
>Eliot Kimber
>Senior Solutions Architect, RSI Content Solutions
>"Bringing Strategy, Content, and Technology Together"
>Main: 512.554.9368
>Book: DITA For Practitioners, from XML Press,
>To unsubscribe from this mail list, you must leave the OASIS TC that
>generates this mail.  Follow this link to all your TCs in OASIS at:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]