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] Issue for unifying acronyms and glossary

Dear SC members,
Please review Erik's proposal for integrating the acronym and the glossary proposals. Consider the difficulties this might present, if any, for writers and translators to handle.

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



From: Erik Hennum [mailto:ehennum@us.ibm.com]
Sent: Wednesday, December 19, 2007 9:16 PM
To: Gershon L Joseph; JoAnn Hackos
Cc: Don Day
Subject: Fw: [dita] Issue for unifying acronyms and glossary

Hi, Ambidextrous Folk:

Could someone on dita-translation@lists.oasis-open.org please forward the attached mail? I received a bounce from the OASIS mail agent.


Erik Hennum

----- Forwarded by Erik Hennum/Oakland/IBM on 12/19/2007 08:14 PM -----

          Erik Hennum/Oakland/IBM@IBMUS

          12/19/2007 06:25 PM


dita@lists.oasis-open.org, dita-translation@lists.oasis-open.org


"Andrzej Zydron" <azydron@xml-intl.com>, "Gershon L Joseph" <gershon@tech-tav.com>, "JoAnn Hackos" <joann.hackos@comtech-serv.com>, "Ogden, Jeff" <jogden@ptc.com>, "Kara Warburton" <KARA@CA.IBM.COM>


RE: [dita] Issue for unifying acronyms and glossary

Hi, Terminology Folk:

I've updated the integrated terminology proposal:

and, for convenience, the browsable HTML version:

This version makes the fixes proposed yesterday for the problems identified by JoAnn and Gershon on Monday (many thanks) including:

This version also fixes some expression issues noticed by Kara (including rewordings and corrections; again, many thanks).

I'd request that members of the Translation Subcommittee check for requirements that dropped out of this integrated proposal inadvertantly. In particular, please take a close look at the section on "Translation Issues for Abbreviated Forms" and consider whether the specified approach enables translation workbench software as expected.

Finally, given that some members of the Translation Subcommittee weren't at the full Technical Committee meeting on December 11th and may be wondering why an integration proposal even exists, let me summarize the problem that surfaced at that meeting.

The acronym proposal as submitted by the Translation Subcommittee supports markup like the following:

The glossary proposal as approved by the Technical Committee in November supports markup like the following:

Obviously, the two markups provide an overlapping set of properties about the same thing:

If we can integrate the information from both designs, we can eliminate this redundancy problem. DITA adopters will be able to declare a term once and have all terminology processes (including those we haven't anticipated yet) operate on that single declaration.

For instance, here's the superset of the two previous examples under the current integrated proposal:

Adopters who need all three requirements can use the full set of properties. Adopters with an exclusive goal of

FWIW, I won't be able to do much more on this issue until the first week of January.

Thanks for taking a look and best wishes for the ending and new year,

Erik Hennum

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