[
Lists Home |
Date Index |
Thread Index
]
A new OASIS technical committee is being formed. The OASIS LegalXML
Online Dispute Resolution (ODR) Technical Committee has been proposed by
the following members of OASIS: Hon. Arthur M. Ahalt (Ret.), LexisNexis;
Donald L. Bergeron, Lexis-Nexis; Eddie O’Brien, Ringtail Solutions; and
the following individual members: Rolly L. Chambers, Daniel Greenwood,
James I. Keane, and Debi-Miller Moore.
The proposal for a new TC meets the requirements of the OASIS TC Process
(see http://oasis-open.org/committees/process.shtml), and is appended to
this message. The proposal, which includes a statement of purpose, list
of deliverables, and proposed schedule, will constitute the TC's
charter. The TC Process allows these items to be clarified (revised) by
the TC members; such clarifications (revisions), as well as submissions
of technology for consideration by the TC and the beginning of technical
discussions, may occur no sooner than the TC's first meeting.
To become a member of this new TC you must 1) be an employee of an OASIS
member organization or an Individual member of OASIS; 2) notify the TC
co-chairs, James I. Keane (JIK@JKeane.com) and Debi-Miller Moore
(MooreD@adr.org), of your intent to participate at least 15 days prior
to the first meeting; and 3) attend the first meeting on 5 December. You
should also subscribe to the TC's mail list. Note that membership in
OASIS TCs is by individual, and not by organization. You must be
eligible for participation at the time you time you notify the chair.
The private mail list legalxml-odr@lists.oasis-open.org is for committee
discussions. TC members as well as any other interested OASIS members
should subscribe to the list by going to the mail list web page at
http://lists.oasis-open.org/ob/adm.pl, or by sending a message to
legalxml-odr-request@lists.oasis-open.org with the word "subscribe" as
the body of the message. (Note that subscribing to the mail list does
not make you a member of the TC; to become a member you must contact the
TC chair and attend the first meeting as described in the preceeding
paragraph.)
A public comment list will be available for the public to make comments
on the work of this TC; a message may be sent to the TC via the address
legalxml-odr-comment@lists.oasis-open.org.
The archives of both of these mail lists are visible to the public at
http://lists.oasis-open.org/archives/
-Karl
=================================================================
Karl F. Best
OASIS - Director, Technical Operations
+1 978.667.5115 x206
karl.best@oasis-open.org http://www.oasis-open.org
ONLINE DISPUTE RESOLUTION TECHNICAL COMMITTEE
OASIS LegalXML Member Section
1. Name of Technical Committee
The name of the committee shall be the Online Dispute Resolution
Technical Committee (OdrXML TC) within the LegalXML Member Section of
OASIS. The Technical Committee may constitute subcommittees or other
groupings as appear necessary and appropriate to carrying out the
Technical Committee's purpose.
2. Purpose of the Technical Committee
A. Mission
The OdrXML mission is to develop open XML standards for the markup of
information and documents used in online dispute resolution systems. The
primary goal is to allow the public to gain standardized access to
justice through private and government sponsored dispute resolution
systems. These efforts will draw on standards that seek to establish
electronic commerce and allow dispute resolution information to flow
into agencies, court and corporations who sponsor or utilize dispute
resolution services. The Technical committee will develop and review
requirements, specifications and schemas for OdrXML and to harmonize
current document type definitions (DTD) and schemas among developers,
providers, vendors, agencies and other organizations involved in online
dispute resolution.
B. Language and Applicable Legal Domain
The OdrXML TC will focus on online dispute resolution and related
documents in the legal domain in the United States, Europe and other
countries as they participate. The TC will conduct the eMail
discussion, teleconference and face to face meetings in English. The TC
will coordinate its work with the efforts of others countries. It will
enlarge the scope of the TC to allow consideration of other countries
and international bodies requirements into the development of standards.
C. Stakeholders
The stakeholders in the ODR community include:
1. Parties who participate in online disputes, with particular
focus on parties involved in disputes arising from eCommerce and other
transactions over the Internet
2. Neutrals who wish to use Internet resources to resolve disputes.
These include arbitrators, mediators, referees, facilitators and other
professionals and volunteers involved in Alternative Dispute Resolution.
3. Providers of software and services for Online Dispute Resolution;
4. Public and private organizations that refer disputes to on-line
services (e.g. Court, Consumer Complaint Agency, Insurance Company) and
receive reports and documents from ODR providers (such as status reports
to courts, or the filing of a final arbitration award)
D. Scope of Effort
The OdrXML Technical Committee will endeavor to:
1. Encourage the development and harmonization of standards,
schemas, DTD’s, data models, data dictionaries, requirements,
specifications, certifications, seals of approval and policies involved
in Online Dispute Resolution.
2. Foster communications between members of the Technical Committee
and keep the public informed of developments.
3. Examine options and offer proposals or requirements for an open
repository or registry for entities that use, reuse, exchange or report
on ODR activities.
4. Co-host meetings or conferences with relevant entities for
stakeholders to participate in the TC continuing the efforts to promote
open standards, and
5. Promote consideration of standards in the private and public
sectors.
To support this scope of activities, the TC shall seek to aggregate,
review and harmonize XML work product of developers, providers,
neutrals, end user, companies and public institution that use or plan to
use ODR. The TC will also promote the adoption of standards by
traditional providers of Alternative Dispute Resolution Services,
including professional organizations and institutional users of ADR
services.
To help achieve this scope, the OdrXML TC will
1. Facilitate, monitor, assess and publicize tests and
demonstrations, standards, requirements, specifications, data models,
DTD’s or Schemas for online dispute resolution.
2. Follow an open process of discussion and debate with full
consideration of the stakeholders’ different points of view.
3. Seek wide scale adoption of proposed LegalXML/OASIS - OdrXML
standards, and
4. Promote the use of recommended standards in the ODR, ADR and
related communities.
3. Requirements Definition
The TC will conduct a formal process to verify the initial requirements
definition in this section. That process will identify the relevant
needs and processes utilized by neutrals, providers, referring entities,
and end-users. It will also determine the extent to which upstream and
downstream users such as Courts, agencies, corporations, law firms,
business users and the public at large may affect requirements for the
work of this TC.
A. Stakeholders’ Requirements
The TC should reflect the requirements of the stakeholder community in
any DTD, Schemas or other work product it develops, harmonizes or
endorses. The standards should represent the way information is
exchanged between the parties. The exchange of information should also
include text chats, instant messaging, web conferencing and Voice or
Video over IP.
B. Specific Requirements
The TC will specifically consider the following requirements:
1. XML Syntax. The TC will adopt XML standards and syntax for a
party to inquire about ODR, choose a mode of ODR, select a suitable
mode, select a neutral, notify the neutral and other parties, submit
claims and counterclaims along with any digital documentation. The
syntax should also address how the parties and neutral communicate
electronically with each other and with referring or monitoring
institutions. The syntax should enable the parties and neutrals to
exchange information about claims. It should also allow attachments of
documents and other digital media, as well as any award or agreement,
and any information about resolution or closing report about the claim.
2. W3C and OASIS. The TC will seek to utilize W3C and OASIS
specifications as well as ISO or other appropriate standards, except in
those cases made impossible by the legal and binding adoption of
non-standard but legal requirements including any that protect the
public and foster dispute resolution.
3. Elements and Attributes. The TC will help develop and promote
specification that can be used universally by all users and providers.
These component specifications may include elements and attributes (e.g.
unique identifiers, creation dates, etc.), as appropriate.
C. Full Life Cycle Solution
The solution should allow a user, neutral, provider or referring entity
to manage the full life cycle of a dispute through resolution. The
solution should provide means for search and retrieval to locate
documents and extract data based on several criteria including metadata
and tags by means of Boolean and natural language queries appropriate.
4. Deliverables
A. Business Requirements
The OdrXML TC will work with its members and the ODR/ADR community to
define business requirements of all stakeholders and reflect them in the
scope of work. It should ensure that any standard have real value for
the public in the form of better access, lower cost, and/or easier
referencing. The initial starting point should be requirements
definition, which shall discussed openly and approved by consensus.
B. Data Models
The ODR TC will work with its members in reviewing and harmonizing one
or more data models meeting the requirements specified in this Charter;
C. DTD or Schema
The ODR TC shall complete one or more DTD(s) and/or Schema(s) meeting
the requirements specified in this Charter and deriving from the
specified data model(s).
D. Data Dictionary.
The TC shall review and approve a data dictionary that provides the
intended meaning of each element, attribute or other component of the
final specification.
E. Sample Data
The TC shall encourage the creation of documents, message, transactions
and case management records using sample data and documents marked up
according to the DTD/Schema developed through this TC.
F. Style-Sheets and Other Components
Beyond creating or arriving at consensus on the OdrXML data model and
DTD or Schema, the TC may also template style-sheets, CSS, XSLT, XPATH,
X-Query, XSL-FO to provide users and developers with a 'starting point'
to modify and create their own.
5. Meeting Schedule
A. Date and time of the first meeting
OdrXML will hold its first meeting by teleconference on Thursday,
December 5 from 4:30 p.m. to 6:30 p.m. EST. Persons intending to
participate in the first meeting must register to attend no later than
15 days prior to the event by notifying the person named as chair of the
new TC of their intention to attend the meeting, and must be eligible
for TC participation at the time they register. Every Eligible Person
who so notifies the chair and is present at the first meeting of a TC
shall be initially a voting member of the TC.
B. Regular Meetings
The OdrXML Technical Committee will hold at least two face-to-face
meetings a year with the option for members and guests to participate in
key segments of the meeting by teleconference as well as by
videoconference and web conferencing when available. Additional
meetings will be held by teleconference, web conference and videoconference.
The dates and places for the face-to-face meetings are:
* February 5-11, 2003 during the American Bar Association Mid-Year
Meeting in Seattle Washington, and
* August 7-12, 2002 during the American Bar Association Annual Meeting
in San Francisco, California.
6. Committee Roster
A. Sponsoring Members
Names, electronic addresses and membership affiliations of persons
eligible for OASIS Technical Committee Participation committed to the
stated meeting schedule
- Hon. Arthur M. Ahalt (Ret.), LexisNexis, mahalt@courtlink.com
- Donald L. Bergeron, Lexis-Nexis, Donald_Bergeron@LexisNexis.com
- Rolly L. Chambers, Individual member, rlchambers@smithcurrie.com
- Daniel Greenwood, Individual Member, DanG@mit.edu
- James I. Keane, Individual member, JIK@JKeane.com
- Debi-Miller Moore, Individual Member, MooreD@adr.org
- Eddie O’Brien, Ringtail Solutions, eddie@ringtailsolutions.com
B. Names of the Technical Committee Co-chairs
The co-chairs of the Electronic OdrXML Technical Committee are
- James Keane
- Debi Miller-Moore
Daniel Greenwood (DanG@mit.edu) will serve as Vice Chair of the
Technical Committee.
C. Names of phone sponsors
Legal XML/OASIS provides a phone bridge. Each participant pays his or
her own phone costs.
7. Compliance with OASIS and LegalXML By-Laws and Procedures
The OdrXML TC will conduct its business in compliance with:
A. All OASIS By-Laws and Rules of Procedures (ROP)
B. Oasis Technical Committee Process Revision Approved By OASIS Board Of
Directors, 16 September 2002
C. The LegalXML OASIS Member Section Rules of Procedures. The Technical
Committee shall comply with LegalXML TC Rules of Procedure as amended
from time to time. This Technical Committee specifically acknowledges
and adopts the following provisions from Section 2. Technical Process,
Management, Reporting.
a. “OdrXML" is an OASIS Technical Committee. It may be called a
“LegalXML Technical Committee" because of it topic and its association
with the LegalXML member section.
b. Technical work submitted to OASIS Technical Committees will be in
accordance with the OASIS Intellectual Property Rights (IPR) policy as a
base.
c. Any standard, specification or other work product resulting from the
work of the OdrXML technical committee shall remain free and open for
perpetual, global use. In no event shall this Technical Committee
finalize or approve any technical specification if it believes that the
use, distribution, or implementation of such specification would
necessarily require the unauthorized infringement of any third party
rights known to the Technical Committee, and such third party has not
agreed to provide necessary license rights on perpetual, royalty-free,
non-discriminatory terms.
d. Technical work products created and approved by this Technical
Committee must be designated as "LegalXML Technical Committee
Specifications". Only work products approved by a vote of the OASIS
general membership will be referred to as "OASIS Standards".
|
