RE: [dita] Specialization support: a core philosophical issue

Cool—once I again I have not been paying close enough attention (it’s hard enough to try to get 1.1 implemented much less stay up with what we’re trying to do for 1.2).

Cheers,

----

W. Eliot Kimber

Senior Solutions Architect

Really Strategies, Inc.

512 554 9368

From: Michael Priestley [mailto:mpriestl@ca.ibm.com]
Sent: Tuesday, October 02, 2007 4:11 PM
To: Eliot Kimber
Cc: dita@lists.oasis-open.org; Don Day
Subject: RE: [dita] Specialization support: a core philosophical issue

Hi Eliot,

For context, check out the proposed refactoring of the spec for 1.2: a core architectural spec, language spec, and processing spec that documents topics and maps and core behaviors only (no specializations), and then a separate set of specification documents for each of the groupings of specializations.

http://wiki.oasis-open.org/dita/Draft_1.2_TOC

I should have included the link in the first note - it's what we were discussing in the TC meeting today that led to my email, and exactly the issues you're wrestling with here. I think if you reread my email in the context of that draft refactoring, the result should be very much in line with what you're proposing for post 1.2: a rigorous refactoring of the spec, with the core unspecialized markup support being required and all specializations being optional (aside from default inherited support).

dita message