[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] DITAbase for conversion
Alan is correct that we were not assuming
that the general task was intended only for specializations when we originally
approved the 1.2 proposal. When I began work on the Adoption TC’s
feature description of general task, I worked directly with Alan’s
original proposal. I assumed, as you say, that this was a new task model to
accommodate different requirements for writing procedures. In fact, I thought
most of the changes were well considered. However, it seems that the DTD developers
took the TC’s approval of general task as the occasion to completely
rewrite the strict task using the constraint mechanism. I don’t believe
we ever voted to approve that. We could have more easily created two
independent task specializations. People would than have better understood the
conref requirements. Yes, we know that we cannot conref between concept, task,
and reference. Obviously, we can write about it, but even
the Adoption TC can’t work magic. I’m sure most new implementers of
DITA don’t know that our documents even exist, or know dita.xml.org exists
or how to find anything there. JoAnn From: Alan Houser [mailto:arh@groupwellesley.com] There is a lot going on in this thread, and I haven't
been able to fully digest everything. Alan Houser, President Group Wellesley, Inc. 412-363-3481 www.groupwellesley.com
My understanding was that one of the main reasons for the
general (looser) task model was as a basis for specialization (since a
specialization cannot be more general that its base, so you have to start with
a fairly general one). And, if it is
used by a customer as a basis for specialization, then what they will want to
have in their version of ditabase--for all the reasons we want the stricter
task in the TC one--is going to be their (stricter than general) specialization
of general task. So having a ditabase
with general task will do such users no good. I don't think we
should provide such. It will more likely than not just cause users more
problems when they think they can use such a ditabase with their
specialized-from-general tasks. paul |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]