[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Implicit work for DITA 1.1
What is the extent of this fix, Erik? Simply adding its declaration into
the attlist for topicref? And what are the processing implications? I
assume the normal behavior would be "ignore," but can see an extended
behavior of providing some kind of cast to the referenced topic (possibly
non-trivial).
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
Erik
Hennum/Oakland/IB
M@IBMUS To
Don Day/Austin/IBM@IBMUS
02/23/2006 01:12 cc
PM "DITA TC list "
<dita@lists.oasis-open.org>
Subject
Re: [dita] Implicit work for DITA
1.1
Hi, Don and Committee Folk:
With regard to
* "bug fixes" for the specification docs (gather all comments and
known reports)
One bug that's fallen through the cracks is that the outputclass attribute
is available only on the topic elements and not on the map elements. As a
result, a writer can't indicate special kinds of topic relationship in the
map.
The outputclass attribute provides an informal mechanism for narrowing the
semantic of the element. We might think of it as a role or the poor man's
specialization -- an approach available to writers without defining new
schema modules.
If we agree that's a bug fix, we might address it in DITA 1.1. If we feel
it's an enhancement, we should defer it until DITA 1.2 to maintain our
focus and momentum.
Thanks,
Erik Hennum
ehennum@us.ibm.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]