| |
| Schema Coordination | Inventory | Schema Design - File Metadata | Schema Design - Project Data | Schema Design - Audit Data | Liaison | Publication |
| |
| The EDRM XML project is composed of seven working groups. The groups are listed below, along with descriptions of the groups' focuses, where available, and lists of the working groups' member. |
| |
| XML Schema Coordinating Working Group |
| The goal of the Schema Coordination Working Group will be to coordinate the activities and integrate the products of all of the EDRM XML working groups. This group, consisting of the leaders of the various task-specific groups, will be responsible for the strategic and tactical management of the entire EDRM XML project. Aspects of this task will include (when appropriate):
* Identification of requirements and scope for the project
* Establishment of deadlines and deliverables to ensure measurable progress
* Integration of partial products from different working groups into a coherent whole
* Definition and delegation of responsibilities to be executed by specific task-groups |
|
| Leader |
| Socha, George (Socha Consulting LLC) |
| Participants |
| Baskin, David (ZANTAZ, Inc.) |
| Clark, Thom (DocuLex, Inc.) |
| Gaynor, Alan (None) |
| Johnson, Laurie (Attenex Corporation) |
| Nalle, Richard (KPMG LLP) |
| Rahman, Sami (iCONECT Development, LLC) |
|
|
|
| |
|
| XML Inventory Working Group |
| The Inventory Working Group will oversee the identification and organization of specific data values to be supported by the EDRM XML schema. The objective of the group will be to ensure that the final schema is both complete and non-redundant.
Aspects of this task will include:
* Integration of inventories compiled by the various Schema Design working groups (File-, Project-, and Audit-data) into a Master Inventory List
* Identification of shared or duplicated values that may warrant coordination between the Schema Design groups
* Industry outreach to discover missing data values or types
* Communication of findings to the various Schema Design groups for implementation within the schema
* Final review of the schema produced to ensure that the entire Master Inventory List is supported |
|
|
|
|
| |
|
| XML Schema Design - File Metadata Working Group |
| This group will define an XML standard for transferring file metadata between tools used in the discovery process. File metadata includes metadata stored with files in the repository systems that supply files to the discovery process and metadata added to those files as they pass through the processing steps described in the EDRM. The resulting standard will include metadata required to track chain of custody through the process and metadata describing the relationships between files (e.g. this is a pdf image of this attachment to this email that was extracted from this PST) in addition to simple file metadata (e.g. create date).
This group will not be responsible for defining an XML standard for describing the processing performed on each file or the metrics recorded for those processing steps. These will be covered by other groups. |
|
| Leader |
| Johnson, Laurie (Attenex Corporation) |
| Participants |
| Baskin, David (ZANTAZ, Inc.) |
| Cating, Mike (FTI Ringtail) |
| Chenchery, Rakesh (Symantec Corporation) |
| Garrity, Edward (CT Summation) |
| Gillin, Chris (Vivisimo, Inc.) |
| Harris, Brad (Fios, Inc.) |
| Johnson, Laurie (Attenex Corporation) |
| Kedidi, Leyth (InterLegis, Inc.) |
| Neustaetter, Greg (Stratify, Inc.) |
| van den Berge, Willem "Wim" (Altep, Inc.) |
|
|
|
| |
|
| XML Schema Design - Project Data Working Group |
| The EDRM XML - Project Data group's mission is to develop a schema that will pass long key performance indicators and information for each of the following areas:
1. Time
2. Cost
3. Project / Decision information log
4. Case / Matter information log
We will work closely with other group to develop the schema with the following criteria:
1. Whenever possible use industry standards, Universal Business Language or OASIS standards
2. To integrate with EDRM Metrics project data and tools
3. Meet the needs of the process and user groups in the EDRM model. |
|
|
|
|
| |
|
| XML Schema Design - Audit Data Working Group |
| The goal of the XML Schema Design - Audit Data Working Group is to define schema which will collect and maintain the entire history of data in the eDiscovery process as it is passed from one stage (and/or service provider) to another with the purpose of providing robust, appropriate chain-of-custody/auditing of data to ensure the integrity of every stage of the eDiscovery process. |
|
|
|
|
| |
|
| XML Liaison with Metrics Working Group |
| The purpose of the XML Liaison Working Group is to layout the acceptable channels of communication between the EDRM XML Team and the EDRM Metrics Team. The XML Liaison Working Group has documented a communication plan so that everyone on the team can share an understanding of appropriate means of communication. The XML Liaison Working Group will monitor EDRM XML Team communications, summarize and share this with the EDRM Metrics Team. |
|
|
|
|
| |
|
| XML Publication Working Group |
| The EDRM publications working group has two related responsibilities:
* Research
* Publication
We conduct research on topics for EDRM standards - as technical journalists do - by attending the meetings (via conference calls) of working groups that are the sources of the technical information and conducting interviews with designated subject matter experts (via e-mail, IM, or phone).
We publish EDRM standards by outlining, drafting, distributing drafts for review, and correcting drafts until they are approved by the EDRM XML team. We then make final publications available to the public (formats and methods to be determined). We will model our process on the W3C Technical Report Development Process, http://www.w3.org/2005/10/Process-20051014/tr.html#Reports. |
|
| Leader |
| Gaynor, Alan (None) |
| Participants |
| Esposito, Kevin (Pfizer Inc.) |
| Ethridge, Susan (Altep, Inc.) |
| Gaynor, Alan (None) |
| Holmes, Kate (Attenex Corporation) |
| Trovato, Frank (iCONECT Development, LLC) |
| Von Hagen, Bill (Vivisimo, Inc.) |
|
|
|
| |
|
