• Updated EDRM XML compliance load file, Jan 23 2008 version
  • 6 KB
  • .zip file containing .xml file

The changes address some issues recently raised. There are three changes:

1. The Tag #To fields are correctly formatted for multiple email address situations
2. Hash codes are consistently lower case
3. There should be no hash code errors during validation

The compliance data set does not change. Just replace the load file in the existing zip with the load file inside this zip.

The changes most likely will not affect whether anyone passes compliance.

Please post comments about the EDRM XML materials on the EDRM Bulletin Board (registration required) or send them to mail@edrm.net

Thank you.

• EDRM XML Interchange Format Schema Documentation, Jan 23 2008 version
  • 47 KB
  • PDF file

Please post comments about the EDRM XML materials on the EDRM Bulletin Board (registration required) or send them to mail@edrm.net

Thank you.

• EDRM XML XSD, Jan 11 2008 version
  • 17 KB
  • Updated EDRM XML XSD file
  • Corrects a bounding issue

During validation testing, we found there is a “bounding” on the <Tag> record within a <Review> that limits you to one <Tag> record per <Review>. That was not the intention of the schema… the group intended that you could have multiple tags contained within the same review.

The schema has been patched to address this issue. The patch is a one-field change in the “ReviewType” complex type.

Old:

<xs:complexType name=”ReviewType”>

    <xs:sequence>

        <xs:element name=”Tag” type=”TagType” minOccurs=”0″ maxOccurs=”1“/>

    </xs:sequence>

    <xs:attribute name=”ReviewId” type=”xs:long”/>

</xs:complexType>

New:

<xs:complexType name=”ReviewType”>

    <xs:sequence>

        <xs:element name=”Tag” type=”TagType” minOccurs=”0″ maxOccurs=”unbounded“/>

    </xs:sequence>

    <xs:attribute name=”ReviewId” type=”xs:long”/>

</xs:complexType>

Note: This will not affect compliance of anyone who already has successfully validated their XML using the validation tool. If you have done your implementation with the one-tag-per-review limitation you will still check out fine with the updated schema.

The updated schema can be dropped into the root directory of your EDRM validation tool install in place of the existing EDRM.xsd file.

Please post comments about the EDRM XML materials on the EDRM Bulletin Board (registration required) or send them to mail@edrm.net

Thank you.

• EDRM XML Validation Tool, Version 1.0.6, Jan 9 2008
  zip file containing XMLValidationTool.msi
  • 6,712 KB
  • Executable file
  • The install package has been updated to include the latest XML schema
  • The program expects the schema (xsd) to exist in the C:\Program Files\EDRM\XMLValidationTool folder for validation
  • Developed by the EDRM XML 2 Validation Tool Working Group

The revised package includes the latest EDRM XML schema.

If you downloaded the Jan. 8 package, please replace it with the Jan. 9 package.

Comments about the EDRM XML materials can be posted on the EDRM Bulletin Board (registration required) or sent to mail@edrm.net

Thank you.

• EDRM XML Validation Tool, Version 1.0.6, Jan 8 2008
  zip file containing XMLValidationTool.msi
  • 6,712 KB
  • Executable file
  • Developed by the EDRM XML 2 Validation Tool Working Group

We welcome your comments and suggestions. Please send feedback to us at mail@edrm.net

Thank you.

• EDRM XML materials Dec 18 2007
  .zip file containing:
  • Updated EDRM-XMLSchema.xsd
  • EDRM-MetadataTags.xls
  • Compliance data set folder containing edocs, email and TIFF
  • 20071218tree.xls listing contents of compliance data set folder
  • readme.txt

Please note that with the current schema and data set, 8 hash codes do not match.  We are working on correcting that.

These materials should replace any previously downloaded materials.

We welcome your comments and suggestions. Please send feedback to us at mail@edrm.net

Thank you.