OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita] rubric for SC brainstorming


Doug, I see the point that many entities outside of the DITA TC provide guidance. I think the issue here is clarification that subcommittees do not issue guidance. Official OASIS Guidance, when it originates in a subcommittee, is the result of subcommittee deliverables being vetted and incorporated into guidance by the parent committee.

At least this is how I understand it as someone trying to follow the rules as a subcommittee co-chair. There are two things we have been asked to do:

	- place a caveat on our posts indicating their status as not approved for implementation (It looks like Bruce's wording achieves that). 

	- refrain from presenting subcommittee work as an official OASIS TC position in a public forum (webinar, conference, white paper, etc)

I still need clarification on the second issue, as my understanding may allow more exposure of the subcommittee work than the TC would like. Presenting some of the ideas of our subcommittee is the best way to vet them with the actual stakeholders in external organizations. We certainly can pass on that opportunity, but I need to make sure that is the TC's intention. It may be that any public presentations we make will need to include a disclaimer similar to the one we will place on posts.

Perhaps, Don, Michael, or others on the TC can clarify if and how we handle informing the public on progress and obtaining feedback.

Regards,

Michael Boses

 



-----Original Message-----
From: Doug Morrison [mailto:dmorrison@dita4all.com] 
Sent: Wednesday, October 13, 2010 11:07 AM
To: dita@lists.oasis-open.org
Subject: Re: [dita] rubric for SC brainstorming

  I think the final sentence "Such guidance is exclusively in the 
purview of the DITA Technical Committee" should be dropped - because it 
is not true as it stands, and not necessary.

Regards,

Doug Morrison
Information Architect
http://dita4all.com


On 13/10/2010 15:33, Bruce Nevin (bnevin) wrote:
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]