Summary of glossary elements: what to keep, what not

[Robert Anderson <robert.dan.anderson@oracle.com>]

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

Thanks,

Robert