-----Original Message-----
From: John Greacen
[mailto:john@greacen.net]
Sent: Monday, November 08, 2004
11:00 AM
To: Electronic Court Filing
Technical Committeee
Subject: [legalxml-courtfiling]
Tuesday conf call
Our next teleconference is tomorrow. Here are the details for the
call:
Leader's Name: John Greacen
Day/Date: Tuesday, November
9, 2004
Time of call: 1:00 to 2:00
pm Eastern time
Conference Dial-in:
512-225-3050
Conference Guest Code:
84759#
Number of lines needed:
Anticipated Total = 40
Duration of the call: 1 Hour
Leader's Phone Number:
505-780-1450
This is the tentative agenda:
Status of consultant recruitment – Jamie Clark
Action on charter revision – John Greacen
(The KAVI vote total was 16 to 1 in favor of the draft circulated, among 56 TC
members and
prospective members.
Members raised on the list the following issues – Should we remove
“Court” from our name to
recognize electronic exchanges of legal documents that may not include a
court? [No support, several
oppositions] Should we remove electronic service of process from our
charter since it is not within
the scope of Court Filing Blue? [No support, several opposed but a
request to maintain a record
of the issue for future standards releases]. Is there sufficient support
to present the revised charter
to the OASIS Board?)
Status of Requirements Subcommittee tasks - Tom Clarke
The current status
of our requirements development, as reported last month by the subcommittee
chair, is as follows:
1. We have
identified three components: filing assembly, filing review, court
record. These replace the old EFSP, EFM, CMS nomenclature.
2. We have
identified four interfaces: query, transaction, event, and policy.
These more abstract titles better align with the different types of technical
transactions that need to occur between components. Think of this as
being similar to the SOAP messaging scenarios, which are also deliberately
abstract.
3. The
technical, detailed or component use cases (the names are fairly
interchangeable) will be grouped by interface category.
4. Asynchronous
transactions will not be viewed as a non-functionality requirement.
Instead, we will pair use cases on the interacting components that together
complete the asynchronous exchange. We still need to identify a use case
descriptive mechanism for identifying these pairs.
5. Query
interface use cases are all synchronous.
6. Private
components will not be addressed by E Filing Blue. Shane Durham has
developed a nomenclature document that includes an explanation of
“private.”
7. The
following outstanding tasks and schedules are agreed to. All tasks will
be drafted by November 5th and presented to the TC before the
conference call on the 9th:
-
Shane Durham will define draft e-service use cases.
-
Scott Came will detail the draft policy interfaces. Good drafts
will be
available by the November 19th.
-
Scott Came and Jim Cabral will resolve the non-normative guidance for
migration from SOAP with Attachments to MTOM.
-
Jim Cabral will describe the message types and key contents.
-
The group will review the ebMS profile and its non-functional mapping
done by John Ruegg. This has already been posted.
-
Scott Came will revise all of the existing detailed use cases per
the
decisions above.
-
Shane Durham will revise the functional high-level use cases per the
decisions above.
Replacement of liaison to eGov – John Greacen
(John Ruegg offered to serve, with the understanding that he would not attend
meetings in DC.
Tom Carlson will determine whether the National Center would support his
serving, and attending
meetings.)
Status of Las Vegas face-to-face planning (Thursday and half
day Friday, December 16 and 17) – Robin Gibson
Suggested cancellation of December conference call in light
of face to face meeting two days later – John Greacen
Other items of interest to the members
John M. Greacen
Greacen Associates, LLC
HCR 78, Box 23
Regina, New Mexico 87046
505-289-2164
505-289-2163 (fax)
505-780-1450 (cell)