Re: [dita] Last call for top DITA issues

[Erik Hennum <ehennum@us.ibm.com>]

Hi, Paul:

As Don was pointing out to me today, the <data> element presumably rides in on the coat tails of bookmap because the book metadata depends on it, but that should be okay because <data> is good to go (unless anyone has thought of ways to improve it while it has been sitting on ice).

Does glossary also ride in with bookmap as a requirement for having a complete book story?

Any other hangers on?


Thanks,


Erik Hennum
ehennum@us.ibm.com

"Paul Prescod" <paul.prescod@blastradius.com>

"Paul Prescod" <paul.prescod@blastradius.com>

02/17/2006 03:22 PM

To	<dita@lists.oasis-open.org>
cc
Subject	[dita] Last call for top DITA issues

So the current list of proposals is:

#20 Extensible metadata attributes
* customers ask for it and the current situation is just not
workable for many

#38 Bookmap / bkinfo revision
* in widespread quasi-standard use already
* often requested by customers

#35 Support foreign content vocabularies such as MathML and SVG
* MathML in particular is very popular, and has been hacked by
XMetaL customers

* graphic (image) scaling improvements (no issue number?)

Now is the time to jump in with any other DITA 1.1 issue that you
consider absolutely urgent and therefore a candidate for "early
release".

And then SOME STILL-TO-BE-RANKED SUBSET of indexing requirements:

- #44 Keep indextermref (or redefine its function)
- #45 Add See, See Also indexing elements
- #45a Add sort order indexing elements
- #45b Add page range indexing elements

I'll send another email about ranking the indexing requirements.

Paul Prescod