[Announce] DDMSence 2.1.0 released
20 views
Skip to first unread message
Brian Uri!
Jan 19, 2013, 2:07:39 PM1/19/13
to ddms...@googlegroups.com
Hello everyone,
DDMSence v2.1.0 is now available for download. This is a stable, minor release which adds support for the latest version of the DoD Discovery Metadata Specification (4.1). It is backwards compatible with v2.0.0, and an upgrade guide exists for migrating from any 1.x versions.
There are two "under the hood" changes to be aware of:
First, the DDMS specification is no longer available for Public Release, and this retroactively applies to old versions. Now that a DoD Data Services Environment account is required to download DDMS schemas, those schemas are no longer bundled with DDMSence. Instead, DDMSence now uses its own generated schemas which are sufficient for equivalent validation. (The Public Release versions of DDMS dependencies, such as XLink/ISM/NTK, are still bundled in). There should be no impact on end users, and the DDMSence library should work exactly as it did before.
Second, DDMS 4.1 is the first version which shares an XML namespace with a prior version (both 4.0.1 and 4.1 have the same namespace). Any XML instance that uses this XML namespace will be treated as a 4.1 record, and validated accordingly. An XML instance that uses a new 4.1 element (such as ddms:approximableStart) will generate a warning during validation to show that the record might not be understandable to a system that is using 4.0.1 instead of 4.1.
Looking ahead, DDMS 5.0 is already being finalized. 5.0 will be the first version of DDMS to be recast into the IC's Trusted Data Format (IC-TDF) specification. In the cloud-oriented world, the concept of a DDMS metacard goes away, and DDMS data is broken up across various structures and assertions in a TDF. More details about this recasting can be found on the DDMS homepage.
Because DDMSence has always been a library for handling metacards, it is currently unclear how I will support DDMS 5.0 in DDMSence. If you have any suggestions or use cases to share, I always welcome the feedback. Thank you for your continued support!
Regards,
BU
DDMSence v2.1.0 is now available for download. This is a stable, minor release which adds support for the latest version of the DoD Discovery Metadata Specification (4.1). It is backwards compatible with v2.0.0, and an upgrade guide exists for migrating from any 1.x versions.
There are two "under the hood" changes to be aware of:
First, the DDMS specification is no longer available for Public Release, and this retroactively applies to old versions. Now that a DoD Data Services Environment account is required to download DDMS schemas, those schemas are no longer bundled with DDMSence. Instead, DDMSence now uses its own generated schemas which are sufficient for equivalent validation. (The Public Release versions of DDMS dependencies, such as XLink/ISM/NTK, are still bundled in). There should be no impact on end users, and the DDMSence library should work exactly as it did before.
Second, DDMS 4.1 is the first version which shares an XML namespace with a prior version (both 4.0.1 and 4.1 have the same namespace). Any XML instance that uses this XML namespace will be treated as a 4.1 record, and validated accordingly. An XML instance that uses a new 4.1 element (such as ddms:approximableStart) will generate a warning during validation to show that the record might not be understandable to a system that is using 4.0.1 instead of 4.1.
Looking ahead, DDMS 5.0 is already being finalized. 5.0 will be the first version of DDMS to be recast into the IC's Trusted Data Format (IC-TDF) specification. In the cloud-oriented world, the concept of a DDMS metacard goes away, and DDMS data is broken up across various structures and assertions in a TDF. More details about this recasting can be found on the DDMS homepage.
Because DDMSence has always been a library for handling metacards, it is currently unclear how I will support DDMS 5.0 in DDMSence. If you have any suggestions or use cases to share, I always welcome the feedback. Thank you for your continued support!
Regards,
BU
Reply all
Reply to author
Forward
0 new messages