[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: How to store the DITA 2.0 editing guidelines? Example of rewriting normative statement
If the below subcommittees are each reorganizing existing DITA content, how do people want to be able to access the (evolving) materials and guidelines? We have various options:
And maybe something that I am not thinking of ... This cropped up because I am looking through already-edited (base) spec topics, and I came across the following good example of rewriting a normative statement to be standalone that I wanted to share: DITA 2.0 rewrite Processors SHOULD provide a mechanism that causes the content of
the <draft-comment> element to be rendered in draft output
only. By default, processors SHOULD strip out
<draft-comment> elements to prevent publishing internal
comments by mistake. DITA 1.3 content: Processing systems SHOULD provide a mechanism that causes the
content of this element to be rendered in draft output only. By
default, processors SHOULD strip them out to prevent publishing
internal comments by mistake. --
Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Principal consultant, Eberlein Consulting www.eberleinconsulting.com +1 919 622-1501; kriseberlein (skype) |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]