legalxml-sc — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [legalxml-sc] RE: [legalxml-courtfiling] Apologies and follow-upto Jan 6th 2004 conference call
MHonArc v2.5.0b2 -->legalxml-sc message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [legalxml-sc] RE: [legalxml-courtfiling] Apologies and follow-upto Jan 6th 2004 conference call
- From: "Karl F. Best" <[email protected]>
- To: [email protected]
- Date: Fri, 09 Jan 2004 08:52:05 -0500
I don't know the fulll background of this discussion, but John's got it pretty much right. In general terms, TCs are proposed by the members of OASIS, and an OASIS TC sets its own agenda and schedule, etc. If a group of members wants to start the new TC suggested by Diane they may do so. If the Court Filing TC wants to start a new subcommittee it may do so. But where there's a member section (such as LegalXML) or a joint coordinating committee (such as ebXML or Security) there's another layer to consider. The member sections' steering committee, or the joint committee, may not override the above process but may wish to get involved in the discussion in order to coordinate efforts. If there's talk about a new TC having to do with LegalXML the steering committee would proably want to discuss how this would fit in with the existing LegalXML TCs to make sure that the charter and deliverables fits in with the other TCs and that there isn't overlap. Plus, the steering committee "owns" the LegalXML name at OASIS, so a new TC cannot use that name unless the members of the steering committee decide that the new TC fits in the purose of the member section. So the process is still "bottom up" and member driven, but a member section steering committee should get involved in the dicussion. -Karl jmessing wrote: > This email comments on the following (edited) exchange between Diane Lewis and Jim Cabral. > > <diane lewis> Suggest: separate initiative either as part of the Court Filing TC or through a proposal to the LegalXML section to create a separate TC for Electronic Preparation Provider spec development?? > .... > >> Shouldn't an "off-spring" of Blue be a TC or a Sub TC under Court Filing that constructs an XML compliant syntax for representing court filing documents authored by Court customers (e.g. attorneys)? Is there a need from such a specification? >> >> Decision for TC members to entertain: Is this type of standard/specification development of value to the legal/justice community? If so, where does it belong: OASIS Legal XML or OASIS e-government, or a different effort similar which could be defined along the lines of the Education TC purpose statement ? >> The purpose of the OASIS Education XML TC is to represent international pre-Kindergarten through 12th grade (PK12) interests by developing XML requirements documentation for shared extensible user profiles, controlled vocabularies, taxonomies, and thesauri, and other needed specifications. > > </diane lewis> > > <jim cabral> To me, these questions seem to be more appropriate for the LegalXML Steering Committe to decide rather than for the TC. Unfortunately, the Steering Committee has not provided sufficient direction to date in clarifying the relationships between the TCs in the Member Section. It is something that I, and I believe other Steering Committee members are hoping to resolve once the committee is fully constituted, hopefully by the end of this month. > </jim cabral> > >> > > > I think Jim's response to Diane misconceives the nature of a steering committee within the OASIS structure. OASIS is a "bottom-up" structure where the TC's are the basic units that govern the work of the organization and the rest of the organization in theory exists to support the TC's. If an Electronic Preparation Provider TC is thought to be useful, then three or more OASIS members are empowered to draft a charter and propose it as a TC. If the CourtFiling TC believes it proper to create a subcommittee for this purpose or any other purpose related to its charter, then it is authorized to do so as a TC. The Steering Committee's role is to review and approve or disapprove a newly proposed TC Charter. > > I was a member of the joint security steering committee of OASIS. From what Karl and others explained at that time, a steering committee represents a grouping of TC's. It exists to help the member TC's achieve their respective goals, largely in response to common concerns and requests of the TC's presented to the steering committee. The type of "leadership" which has been casually invoked as a criticism of the current Steering Committee of LegalXML-OASIS in the CourtFiling TC discussions is not suited to the structure that OASIS has created, although it might have been appropriate to the Board of Directors of LegalXML, which was a "top-down" structure, as it existed prior to the merger with OASIS. > > The LegalXML-OASIS Steering Committee has decided in its discretion to await its full complement of members before taking substantive decisions affecting the organization. If this is not to the liking of the CourtFiling TC then perhaps Roger Winters can advise the Steering Committee accordingly and we can take a different course. > > If the CourtFiling TC has proposals to make to the Steering Committee, then I invite the TC thought its representative to do so, directly and forthrightly, rather than by way of innuendo directed to the CourtFiling TC membership about the Steering Committee's presumed failure to meet its responsibilities, which is unfair to the newly constituted and hard-working volunteer Steering Committee members. > > Best regards and happy new year to all. > > John Messing > > > > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/legalxml-sc/members/leave_workgroup.php. > > > -- ================================================================= Karl F. Best Vice President, OASIS office +1 978.667.5115 x206 mobile +1 978.761.1648 [email protected] http://www.oasis-open.org
- References:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]