Re: [dita-comment] no support for <sup> and <sub> in some glossaryelements?

["Don Day (LbW)" <donday@learningbywrote.com>]

The DITA TC has been collecting outstanding issues for DITA 1.3 consideration at this page on the TC's wiki site:
http://wiki.oasis-open.org/dita/DocIssuesDeferredtoDITA1.3#preview

I have just added this issue there.

It may have been presumed that the content models were fine for the default domain of discourse.  However, if ph is not allowed, then extension by domain specialization would be prohibited as well. We'll need to look at the content models for the archetypes for glossary markup.

--

Don R. Day

DITA and XML Consultant, 512 244-2868
Co-Chair, OASIS DITA Technical Committee

"Where is the wisdom we have lost in knowledge?

Where is the knowledge we have lost in information?"

--T.S. Eliot

On 2/9/2011 4:48 PM, Amber Swope wrote:

00ba01cbc8ab$6876cc90$396465b0$@com" type="cite">

Thanks for the prompt response, Eliot. 

Is the next appropriate step to log a defect?
Thanks, A

Amber Swope
dita specialist
<dita strategies>
503.922.3038
amberswope@gmail.com


-----Original Message-----
From: Eliot Kimber [mailto:ekimber@reallysi.com] 
Sent: Wednesday, February 09, 2011 2:44 PM
To: Amber Swope; dita-comment@lists.oasis-open.org
Subject: Re: [dita-comment] no support for <sup> and <sub> in some glossary
elements?

I can't speak to the design decisions behind the glossary markup, but it
does seem odd that the content model for e.g., glossAbbreviation does not
allow <ph>:

<!ENTITY % glossAbbreviation.content
                       "(#PCDATA |
                         %keyword; |
                         %term; |
                         %tm;)*"

Since <sup> and <sub> are specializations of <ph> they are excluded from
this content model.

Cheers,

Eliot

On 2/9/11 4:29 PM, "Amber Swope" <amberswope@gmail.com> wrote:

I need to indicate a chemical or equation ³formula² for a glossary term

and

the glossary elements that seem to be the most appropriate for this usage

do

not support the <sup> and <sub> elements:  <glossAbbreviation>,
<glossAcronym>, <glossShortForm>, and <glossSynonym>.  For example, for

the

term ³water², the chemical expression is H2O; my first choice for

capturing

the expression is <glossShortForm>, but it doesn¹t support <sub>. Another
example is the term ³terminal velocity² with the equation symbol of Vt.
 
Is there a specific reason for this limitation? Any suggestions for a
workaround other than appropriating <glossProperty>? In these cases,
<glossUsage> is already taken.
 
Thanks, A
 
 
Amber Swope
dita specialist
<dita strategies>
503.922.3038
amberswope@gmail.com