Hi there,
Overall, I do think that the structure can be simplified, but I do have the following questions:
- If we remove glossAlternateFor and glossSynonym, how are we making associations to other terms? For associating other
glossary topics, are we relying on xref or related-links? What if you want to include only text?
- Are we proposing to consolidate all the alternative forms to use glossAcronym? If so, then glossShortForm will also
be removed?
My apologies if these questions have already been addressed.
Thanks, Amber
Creating Opportunity through Information Architecture
DITA Specialist
| DITA Strategies, Inc.
| +1 503.922.3038
|
amber@ditastrategies.com
|
www.ditastrategies.com
From: dita@lists.oasis-open.org <dita@lists.oasis-open.org>
On Behalf Of Robert Anderson
Sent: Tuesday, February 6, 2024 6:29 AM
To: dita@lists.oasis-open.org
Subject: [dita] Summary of glossary elements: what to keep, what not
Forwarding the analysis that Kris put together based on our reading of the latest review comments.
Basic principles:
-
Keep what is needed for basic glossary
-
Keep what is needed for <abbreviated-form> to work
-
If there are two overlapping elements, keep one (the one that can be used in most places)
Element
|
Keep
|
Get rid of
|
Purpose
|
<glossAbbreviation>
|
|
X
|
|
<glossAcronym>
|
X
|
|
Functionality with <abbreviated-form>
|
<glossAlt>
|
X
|
|
Functionality with <abbreviated-form>
|
<glossAlternateFor>
|
|
X
|
|
<glossBody>
|
X
|
|
Functionality with <abbreviated-form>
|
<glossdef>
|
X
|
|
Basic glossary functionality
|
<glossentry>
|
X
|
|
Basic glossary functionality
|
<glossPartOfSpeech>
|
|
X
|
|
<glossProperty
|
|
X
|
|
<glossScopeNote>
|
|
X
|
|
<glossStatus>
|
|
X
|
|
<glossSurfaceForm>
|
X
|
|
Functionality with <abbreviated-form>
|
<glossSymbol>
|
X
|
|
Extra functionality, not confusing or overlapping with other elements
|
<glossSynonym>
|
|
X
|
|
<glossterm>
|
X
|
|
Basic glossary functionality
|
<glossUsage>
|
X
|
|
Extra functionality, not confusing or overlapping with other elements
|