Goals of the EDRM XML format

• Provide relief from the existing quagmire of proprietary load file formats

• Decrease the time and resources required to transfer ESI from one step of the EDRM process to another

• Minimize errors and risk associated with such transfers

• Provide a backward-compatible future expansion path

The EDRM XML Working Group is a “Who’s Who” of industry leaders

• 32 organizations actively involved in the effort– ~25 vendors– ~14 service providers– 2 law firms– 1 corporation

• 21 organizations shipping officially compliant products

What has the EDRM XML group done so far?

• Developed the e-discovery industry’s first widely adopted, vendor-neutral interchange format– February, 2008: 1.0 release– February, 2009: 1.1 follow-on

• Acted as a central resource for industry leaders to talk about data interchange issues in the e-discovery “value chain”

2010 XML project goals

• Define draft 2.0 schema for public comment by May, 2010• Additional core schema enhancements• Upstream integration (IMRM)• EDRM Search integration

• Ratify 2.0 schema by August, 2010• Develop more formal certification programs• Develop more resources to educate the market about

the merits of EDRM XML and how to use it

The EDRM is about more than the boxes: it’s about the connections, too

Processing

Review

Identification Analysis Production Presentation

Preservation

Collection

Today, there is a lot of risk and cost tied up in the connections:•Time spent by vendors massaging data to port from one application to another•Time spent by lit support professionals massaging data to work with a particular review tool

Challenge: No two tools speak the same language

Concordance DAT Introspect

Summation DII

Challenge: No standards for what should be in a load file

Concordance Out-of-the-Box DCB (Files)

Concordance Out-of-the-Box DCB (Email)

Challenge: No standard for mapping across similar but disparate file types

(e.g. emails) Exchange

Notes

So, without EDRM XML, life is ugly