atom feed13 messages in org.oasis-open.lists.dita[dita] rubric for SC brainstorming
FromSent OnAttachments
Bruce Nevin (bnevin)Oct 13, 2010 7:33 am 
Doug MorrisonOct 13, 2010 8:07 am 
Michael BosesOct 13, 2010 8:32 am 
Su-Laine YeoOct 19, 2010 2:37 pm 
Michael PriestleyOct 20, 2010 7:00 am 
Bruce Nevin (bnevin)Oct 20, 2010 9:22 am 
Jang F.M. GraatOct 20, 2010 11:40 am 
Don Day (LbW)Oct 20, 2010 11:55 am 
Su-Laine YeoOct 20, 2010 11:57 am 
Bruce Nevin (bnevin)Oct 20, 2010 12:01 pm 
Michael BosesOct 20, 2010 12:06 pm 
Jang F.M. GraatOct 20, 2010 8:04 pm 
Don Day (LbW)Oct 20, 2010 9:46 pm 
Subject:[dita] rubric for SC brainstorming
From:Bruce Nevin (bnevin) (bne@cisco.com)
Date:Oct 13, 2010 7:33:07 am
List:org.oasis-open.lists.dita

In yesterday's call, we talked about subcommittees needing some kind of cover for creative discussion and brainstorming so that outside readers of the discussion won't take it as guidance from the TC. The relevant bit from the minutes (as amended to include Seth's name):

Seth Park: For DITA and composite environments, we came up with a feature request that was technically not implementable. Is there a `code word' under which to talk in papers and not shut down creativity. MB: A standard disclaimer would be wonderful. Don, MP: Let's pursue that on the alias.

I imagine two aspects of a disclaimer, its content and its location.

For example, on the title page or in a footnote on the title or in a note paragraph placed prominently on the first page (to be decided), a subcommittee document might say something like:

This paper reflects exploratory work by a subcommittee of the DITA Technical Committee. It is not a reliable guide as to the future direction of DITA, and should not be taken as guidance for implementing or using DITA. Such guidance is exclusively in the purview of the DITA Technical Committee.

Let the discussion begin!

/B