Mission | Goals |FAQs | Compliance | Schemas 2.0, 1.2, 1.1 | Posts | White Paper | Members

Our mission is to have EDRM XML be the primary format for e-discovery data exchange between parties and systems, reducing the time and risk involved with data exchange. We achieve this by providing a robust, flexible, transparent, and well documented schema supported by a robust tool set.

The ESI includes both underlying discovery materials (e.g., email messages and attachments, loose files, and databases) and information about those materials (e.g., the source of the underlying ESI, processing of that ESI, and production of that ESI).

EDRM XML will help practitioners significantly streamline processes and enable the integration of multiple e-discovery technologies. In the 2010-2011 project year, this group will development version 1.2 of the EDRM XML schema, including the validation tools and related materials. Additionally, the EDRM XML group will define the requirements and framework for version 2 of the EDRM XML schema to be implemented in the 2011-2012 project year. The group will continue to promote the use of the EDRM XML schema.

Effective use of the EDRM XML schema should:

  • 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

10 comments to XML

  • Is it easy to collaborate DRM XML with HTML 5?

  • Is it easy to collaborate DRM XML with HTML 5 ?

  • Siddhartha Jonnalagadda


    I’m trying to check the md5 of the files (both in samples and the enron dataset). Neither of them are matching with the output of md5sum of the program. Would you kindly let us know how to reproduce it?


  • Siddhartha Jonnalagadda


    I am trying to check the compliance of my tool. However the xml validation tool that is needed doesn’t install in my machine. My machine is Windows 7 Home premium version.

  • Kirit Palsana


    I have few query in XML Template. i hope someone would help me to figureout same.
    1) How exactly it take care DeDuplicate Records. lets take example of Cust A, Cust B,Cust C. here Cust A is master document and others are Dedup respective to it.
    2) Setting up VOLUME Path,Do i have to cover absolute path always or i can provide VOLUME_PATH of each Batch and then define Relative_PATH. Right now its consider from XML Parent-Directory to relative path + FileName.

    I would greatly appreciate your help.

    Kirit Palsana

  • Any thought on using application agnostic XML representation of data and instruction set for interoperability and sharing?


  • Peter Glass

    Has EDRM considered the requirements of ISO-14721, Open Archive Information System (OAIS)? E-Discovery is not well served by simply migrating the ESI to an xml-tagged format. Even if the xml files are co-located with respect to the storage platform, it is a long way from satisfying the requirements of a managed archive. The FRCP demands that the records produced during discovery can be verifiably demonstrated to maintain clear chain of authority. Some records have retention requirements which span decades, maintaining chain of authority over extended periods requires long-term active management of the closed records. There must be auditable proof that the content has not suffered spoliation. And so on and so forth. The point being that transforming source information to xml-tagged files is a long way from supporting OAIS requirements. Although the original intent of OAIS was not to address the FRCP, it does a rather good job of it.

    • Hi Peter,
      OAIS did not come up for discussion within the XML group in the recent kickoff meeting last week. I just read up on it briefly, and can certainly see how it could help. For example, it does a good job of differentiating between the original data content, and the data representation, which is something we did discuss at length.
      I think we should keep this reference model in mind as we update the XML standard, but also keep in mind that the primary goal of the next revision of the EDRM XML standard (1.2) is to remove implementation barriers.
      I suggest you bring up OAIS with the new Information Management Reference Model (IMRM) group. They are doing for information management what EDRM does for E-discovery. I’ve just signed up as the liaison between the XML group and the IMRM group but have yet to catch up with their progress at the kickoff meeting last week. I’ll make it a point to ask them about OAIS.

    • Ranjan

      OAIS is more for information and managing information archives than e-discovery but I do agree that for XML standard in e-discovery to be more meaningful, it has to server the wider audience. Having said that, XML should be more on information representation and interchange, rather than archival.


  • Barbara Liberty

    Is anyone looking at extending the XML schema for SharePoint content, including content that has no on-disk format? Are any production vendors handling such content and what do they expect/require with respect to associated metadata?

Leave a Reply