[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Last call for top DITA issues
I was about to say that glossaries are not a dependent part of the bookmap
design. The generalized booklist facility allows subsequent development of
any type of collection that could be desired. I'll note that the 80/20
rule for usefulness of DITA 1.0.5 (?) to the community could be satisfied
by a simple booklist reference to a topic titled Glossary ( reversible back
into structured glossaries, if needed).
Regards,
--
Don Day
Chair, OASIS DITA Technical Committee
IBM Lead DITA Architect
Email: dond@us.ibm.com
11501 Burnet Rd. MS9033E015, Austin TX 78758
Phone: +1 512-838-8550
T/L: 678-8550
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?"
--T.S. Eliot
"Paul Prescod"
<paul.prescod@bla
stradius.com> To
Erik Hennum/Oakland/IBM@IBMUS,
02/20/2006 12:59 "Esrig, Bruce \(Bruce\)"
PM <esrig@lucent.com>
cc
<dita@lists.oasis-open.org>
Subject
RE: [dita] Last call for top DITA
issues
Guys: As self-appointed group minimalist I would argue that we should defer
the glossaries.
* there seem to be many open questions
* glossaries can be authored "by hand"
* multi-use glossaries can be created with conditional text and conref
* we can't do everything at once
Other opinions?
From: Erik Hennum [mailto:ehennum@us.ibm.com]
Sent: Monday, February 20, 2006 8:43 AM
To: Esrig, Bruce (Bruce)
Cc: dita@lists.oasis-open.org; Paul Prescod
Subject: RE: [dita] Last call for top DITA issues
Hi, Bruce:
My apologies for neglecting to clarify the term concerns -- I think the
existing glossary proposal already handles both the case where the same
term has multiple senses:
<glossentry id="ac-air">
<glossterm>AC</glossterm>
<glossdef>Air conditioning</glossdef>
</glossentry>
...
<glossentry id="ac-electric">
<glossterm>AC</glossterm>
<glossdef>Alternating current</glossdef>
</glossentry>
It would be up to the processing to collate by term and format definitions
on output.
The proposal also includes a <glsynonym> element to specify synonym terms
with the same meaning.
If one of the themes of DITA 1.1 / DITA 1.0.5 is enabling books, I'm
wondering whether the shortdesc enhancements would be important for the
narrative glue.
Hoping that's interesting,
Erik Hennum
ehennum@us.ibm.com
(Embedded image moved to file: pic15494.gif)Inactive hide details for
"Esrig, Bruce (Bruce)" <esrig@lucent.com>"Esrig, Bruce (Bruce)"
<esrig@lucent.com>
"Esrig,
Bruce
(Bruce)"
<esrig@luc (Embedded image moved to file:
ent.com> pic32384.gif)
To
(Embedded image moved to file:
02/20/2006 pic12956.gif)
03:49 AM Erik Hennum/Oakland/IBM@IBMUS,
Paul Prescod
<paul.prescod@blastradius.com>
(Embedded image moved to file:
pic14503.gif)
cc
(Embedded image moved to file:
pic08403.gif)
dita@lists.oasis-open.org
(Embedded image moved to file:
pic09168.gif)
Subject
(Embedded image moved to file:
pic00618.gif)
RE: [dita] Last call for top
DITA issues
(Embedded image moved to file:
pic14777.gif)
(Embedded image moved to file:
pic04135.gif)
1. How about a simple generalization of task to allow tables and graphics
in parallel with steps.
That would leave the following compatible extensions for the future:
- the div elements
- nested steps
2. For glossary, I'd still like to close on the issue of terms with
multiple senses. This was raised privately with Erik Hennum earlier, but
I'd be glad to discuss it more broadly in case it could easily cause
incompatible changes if we decided to tackle it after a simple glossary
mechanism was already fielded.
Specifically, we have cases where a project uses the same term in multiple
senses, and being able to gloss the correct sense would be really helpful.
For example: AC := i. Air Conditioning, ii. Alternating Current. It's just
an abbreviation, but I can imagine it happening with terms as well. Quick,
define "interface" in a way that is specific enough to indicate how you
mean it in three interesting contexts and yet not ambiguous when glossed.
Fun challenge, right?
The opposite also happens: multiple terms for a single sense. This might
be easy for DITA to handle because of conref.
Best wishes,
Bruce
====
To merge the threads ... JoAnn Hackos wrote:
Which index-related issues would you prioritize?
- #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 wouldn't leave the others out if we can manage it.
-----Original Message-----
From: Erik Hennum [mailto:ehennum@us.ibm.com]
Sent: Friday, February 17, 2006 6:39 PM
To: Paul Prescod
Cc: dita@lists.oasis-open.org
Subject: Re: [dita] Last call for top DITA issues
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
(Embedded image moved to file: pic09480.gif)Inactive hide
details for "Paul Prescod" <paul.prescod@blastradius.com>"Paul
Prescod" <paul.prescod@blastradius.com>
"Pa
ul
Pre
sco (Embedded image moved
d" to file:
<pa pic21092.gif)
ul. To
pre (Embedded
sco image moved to
d@b file:
las pic22767.gif)
tra <dita@lists.oa
diu sis-open.org>
s.c (Embedded image moved
om> to file:
pic01296.gif)
cc
02/ (Embedded
17/ image moved to
200 file:
6 pic20744.gif)
03: (Embedded image moved
22 to file:
PM pic12285.gif)
Subject
(Embedded
image moved to
file:
pic10443.gif)
[dita] Last
call for top
DITA issues
(Embedded image moved
to file:
pic14746.gif)
(Embe
dded
image
moved
to
file:
pic13
026.g
if)
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
[attachment "graycol.gif" deleted by Erik Hennum/Oakland/IBM]
[attachment "ecblank.gif" deleted by Erik Hennum/Oakland/IBM]
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
