This is the final XSD specification for the EDRM 1.0 interchange format The root element of the EDRM XML file is the parent for all documents being transmitted The Major Version of this EDRM XML file (currently 1). If omitted, default will be 1 The Minor Version of this EDRM XML file (currently 0). If omitted, default will be 0 Description of the XML file to describe the overall contents being transmitted The Data Interchange Type between systems: Update or Delete. If not specified, will default to Update. A string used to identify the case that the XML data is associated with. The Root File Path where the documents reside which need to be loaded using this XML file. If blank, relative pathing will be used. The locale for the data represented in the XML file. This should be a two-letter code that matches an ISO-3166 locale. The default is US (United States). Every batch contains one or more documents identified by a complext document type defined below Every batch may contain relationship between documents contained withing the XML file identified by a complext Related document type defined below Every batch may contain folders identified by Folder type defined below CustomBatchInfo is where all non-EDRM data related to a batch can be placed The optional name of the batch. Within Documents element, there are one or more documents each document may contains several different parts identified by a Document Type defined below Every document may contain tag information identified by a generic name/value pair identified by Tag Type. This is a high level element which contains tag elements Every document may have 0 or more files associated with it. Every document may contain Review information identified by a ReviewType. This is a high level element which contains Review elements. Reviewes contain annotation information, which are really just sets of tags that are associated with a single review operation. Every document may contain Location information identified by a LocationType. This is a high level element which contains Location elements. Locations are information about particular occurrences of a document in the original data source(s) Custom document information not compliant with the EDRM spec The DocID is a unique identifier for the document within the context of the case "Message" for message-type documents or "File" for all others. This can be used in parsing the message and file specific EDRM-defined metadata tags The MIME type of the document (see http://www.w3schools.com/media/media_mimeref.asp) TagName is a required field specifying the name of this tag. It can either be an EDRM-compliant standard tag name (such as "#CC" for the cc'ed recipients of an email message) or a custom tag name. TagDataType is a required field specifying the data type of this tag (Text, Integer, DateTime, Decimal, Boolean, LongInteger, LongText). TagValue is a required field specifying the value of this tag. Its data type should match the TagDataType of the tag. If the information is known, this attribute tracks when (datetime) the tag was modified. If the information is known, populate the name of the user that modified the tag value. This element represents a single file associated with the containing document. Document Text File are of 2 types Raw text embedded withing XML OR text contained in a text file. The attributes of Text File are further identified by File Attributes Binary file content can be embedded directly within the XML file using this element. In EDRM XML 1.0 it is proposed that this only be supported for files whose FileType is "Text." An ExternalFile is defined if the source of the file content is external to the XML file. The path to the file, either relative to the XML file or absolute. If not specified, same as the path to the XML file. The size of the file. The hash of the file in hex string format to use for checksumming and ensuring no changes have been made to the external file. MD5 is the default. Other hash algorithms may be supported in the future; these will have a documented prefix code before the hash (e.g. "SHA1:{SHA-1 hash}). For the MD5 default, no prefix is required. Use this sequence number associated with the file name in conjunction with FileName and MergeFileCount to merge contents of several files into a single file. The assumption is that the name of the merged file will be the same as the name of the first file in the sequence. Use the sequence number associated with the file name in conjunction with FileName and MergeFileCount to merge contents of several files into a single file. The type of the file. Valid values in EDRM 1.0 are Native, Image, Text, or Redacted. The name of the custodian who owned the document at this particular location The URI of the document at the location (including filename) This is the type of the document relationships. Valid values are "Attachment" (for email attachments), "Container" (for ZIP/PST files, etc.) "NearDupe" (for near duplications", "Embedded" for embedded objects, or "Discussion" (for threads)