Dear MODS implementers,
The MODS/MADS Editorial Committee is considering changing how the version attribute on the root <mods> element is implemented. Since incremental versions within a major release version are intended to be backwards compatible, there is a feeling that the version attribute should be looser than it currently is. Right now, MODS 3.3 requires version="3.3", making it more difficult to validate a 3.2 document against the 3.3 schema that it could be. The proposal we're considering now involves making the data type of the version attribute a string so that any value would be valid. An alternative would be to enumerate the version attribute values with all the previous incremental versions, for example MODS 3.3 would allow 3.3, 3.2, 3.1, and 3.0 as allowed values.
Would making this change for MODS 3.4 break any processes implementers have in place? Please let us know if you do any processing that relies on specific values in the MODS version attribute.
Chair, MODS/MADS Editorial Committee
Digital Library Program
Indiana University - Bloomington
Wells Library W501
Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com