RE: [dita-busdocs] FW: [dita-help] Upcoming Meeting

["Bruce Nevin (bnevin)" <bnevin@cisco.com>]

OK, so those members of the present BusDocs SC who are also members of
the Adoption TC could constitute a BusDocs SC of the Adoption TC. To
increase that number, other members of the present SC could join the
Adoption TC and other members of the Adoption TC could serve on its new
BusDocs SC.

So long as the SC agendas are separate (and the associated conversations
and work products), and each answerable to the respective parent TC, the
meetings of the two SCs could occur back to back. In support of that, I
note that even if they have separate meeting times, invitations, and
conference facilities, there will be interchange of information and
topics passed from the discussion of one to the agenda of the other.

Does that sound right, Mary? Or is a more strict logistical separation
required?

The same considerations would apply to the Help SC.

	/Bruce

> -----Original Message-----
> From: Mary McRae [mailto:mary.mcrae@oasis-open.org] 
> Sent: Tuesday, March 30, 2010 6:14 PM
> To: Bruce Nevin (bnevin)
> Cc: dita-busdocs@lists.oasis-open.org
> Subject: Re: [dita-busdocs] FW: [dita-help] Upcoming Meeting
> 
> Hi Bruce,
> 
>  Sorry, but that doesn't work.
> 
>   For any committee there is a unique membership associated 
> with that committee, IPR obligations incurred, and a full 
> record of meetings, conversations and work products to be 
> maintained. That work can't be shared across two committees; 
> it's either one or the other. The Adoption TC could also 
> create a busdocs subcommittee but it would report to the 
> Adoption TC rather than the DITA TC. Liaisons are established 
> at the committee level.
> 
>   The difficulty arises when a subcommittee tries to take on 
> the characteristics of a committee. A subcommittee is really 
> nothing more than a working sub-group of the main committee 
> that is typically focused on a particular subset of the work 
> of that committee. All members of a subcommittee must be 
> members of the committee, and all approvals happen at the 
> committee level.
> 
> Regards,
> 
> Mary
> 
> 
> Mary P McRae
> Director, Standards Development
> Technical Committee Administrator
> OASIS: Advancing open standards for the information society
> email: mary.mcrae@oasis-open.org
> web: www.oasis-open.org
> twitter: @fiberartisan  #oasisopen
> phone: 1.603.232.9090
> 
> Standards are like parachutes: they work best when they're open.
> 
> 
> 
> On Mar 29, 2010, at 6:35 PM, Bruce Nevin (bnevin) wrote:
> 
> > I mentioned the idea (a discovery of the Help SC) that we 
> should clone 
> > ourselves as a SC of the Adoption TC.
> > 
> > I got some clarification of this in the Help SC meeting today. We 
> > would be a subcommittee of the TC and of the Adoption Committee 
> > simultaneously. One membership, one meeting, reporting to two 
> > committees. The reporting is by cross membership and by e.g. Ann or 
> > Michael visiting to make a presentation.
> > 
> > If you agree, I can tell JoAnn et al. that, following the 
> example of 
> > the Help SC, we henceforth want to be a SC of the Adoption 
> TC. (We're 
> > already a SC of the TC.)
> > 
> > 	/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
> > 
> 
>