1 message in org.oasis-open.lists.ditaNested index terms| From | Sent On | Attachments |
|---|---|---|
| Paul Prescod | Sep 30, 2005 8:43 am |
| Subject: | Nested index terms | |
|---|---|---|
| From: | Paul Prescod (paul...@blastradius.com) | |
| Date: | Sep 30, 2005 8:43:16 am | |
| List: | org.oasis-open.lists.dita | |
I don't think that Paul got an answer to his question. Your code in the second example below should generate:
Top level Nested 1 Nested 2
That's how Blast Radius implemented it anyhow.
The second example should probably be treated as an error. It is a flaw of XML schemas and DTDs (inherited from SGML!) that does not make it possible for us to specify that explicitly in the DTD/schema.
-----Original Message----- From: Grosso, Paul [mailto:pgro...@ptc.com] Sent: Wednesday, September 28, 2005 11:08 AM To: di...@lists.oasis-open.org Subject: RE: [dita] Groups - DITA 1.1 Issue #45: Add See, See Also indexing elements (IssueNumber45.html) uploaded
There is something about indexterm (irrespective of this current proposal) that has always concerned me: its mixed content model. Is something like:
<indexterm>Top level <indexterm>Nested</indexterm> index term content. </indexterm>
allowed (the DTD allows it)? If so, what are the processing expectations?
Also, what are the processing expectations of
<indexterm>Top level <indexterm>Nested 1</indexterm> <indexterm>Nested 2</indexterm> </indexterm>
(the DTD allows this too)?