(Imported from Google Code)
DDMS 4.0.1 will likely be out before the ISM files are marked for Public Release.
4.0.1 is a bug fix patch to 4.0 which, although it will share the same XML namespace, will not necessarily be backwards compatible. The ddmsOCType will be removed from the ContactInfoType and the ismocType will be added instead. Because of this irregularity, it would probably be best to support 4.0.1 and NOT 4.0.
Update documentation to 4.0.1. Mention why 4.0 is not supported.
Update codebase to 4.0.1.
Add ismocType validation to the validate() method of the producers.
Rev 737 alters all of the code to use 4.0.1 instead of 4.0, and mentions in the docs why 4.0 is not supported:
<p>DDMS 4.0 was released in September 2011 with an oversight on the technical implementation of the <code>pocType</code> attribute on producer roles. DDMS 4.0
contained a <code>ddmsOCType</code> attribute for this, but it was soon determined by the IC that this would break IRM instances. DDMS 4.0.1 was quickly released a month
later and employs <code>ISMocType</code> instead.</p>
<p>Although this change (removing the old attribute and adding a new one) breaks backwards compatibility, the decision was made to reuse the DDMS 4.0
XML namespace, given that the adoption of DDMS 4.0 was assumed to be relatively low. Because DDMS 4.0 is considered to be "broken", and because
DDMS 4.0.1 was released before I released DDMSence 2.0.0, I have elected not to support DDMS 4.0.</p>
<p><b>How to Upgrade:</b></p>
<p>There are no upgrade steps required. "4.0" is not a valid supported DDMS version in DDMSence. If your organization is upgrading from an earlier
version of DDMS, the DDMS team is strongly encouraging that you go directly to 4.0.1 anyhow.</p>
Complete in Rev 738, which converts the pocType accessor into a List<String> vs. a String, and does ISMVocabulary checking on token values.