Re: [rights] Clarification...

[John Erickson <john_erickson@hplb.hpl.hp.com>]

Thomas writes:
> That issue asside, perhaps the following quote will put
> the question of "what is a JC" to rest:
>
> "A TC shall have no obligation to abide by any decision
> arrived at in a JC to which it contributes membership. The
> business of a JC to which a TC contributes membership shall
> be imparted to the TC through reports from the chair of its
> liaison subcommittee*. Such reports shall have the same force
> and shall be made, received, and acted upon in the same manner
> as reports from any other subcommittee of the TC."
> -- http://www.oasis-open.org/committees/process.shtml#sec1o
>

JSE: Okay. This makes it clear that OASIS envisioned JCs to be
liaison-facilitation mechanisms --- that is, rather than having many
point-to-point liaisons in "related" areas, implement this JC concept to make
liaisons more efficient amongst "related" activities.

The JC process is designed to utilize whatever liaison "interface" a given TC
has previously established, so no special policies or procedures should be
required. Note also that this does not seem to preclude individual TCs from
modifying their liaison mechanisms to accomodate JC-specialized input...

John