[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] The whatever-we-call-it factor
Associating "networking" with the collection helps in explaining
Eliot's sense of the linking/addressing discussion. However, a DITA
topic may also be used individually or in a collection that that
has no processing requirement for networking (a zip manifest for
example). My concern is that any core redefinition in that sense
tends to constrain rather than maintain the options we have already
in the spec's language. DITA is not only about defining structured
information networks, which is why I want to keep doors open for
adoption. I have a separate concern about the thin line between the conceptual or marketing nature of explanations that we are considering. There are definitely separate venues for any marketing or educational story that merits more space than we should give in the spec beyond setting the concepts (the issue we've been cleaning up ever since DITA 1.0 went out as a "user guide" in effect!). -- Don On 3/12/2015 9:34 AM, Bob Thomas wrote:
--
Don R. Day
Founding Chair, OASIS DITA Technical Committee LinkedIn: donrday Twitter: @donrday About.me: Don R. Day Skype: don.r.day<
"Where is the wisdom we have lost in knowledge?
Where is the knowledge we have lost in information?" --T.S. Eliot
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]