I am very much in favor of this idea. I always felt uncomfortable not being able to indicate the version of the (now current) METS schema referenced in METS documents. When 1.3 will change to 1.4 but the URL to the schema stays the same my METS documents will reference a wrong version of the schema. In the worst case they will no longer be valid. This can be avoided by adding the version number to the URL of the current schema.
This matter is especially important if you look at long term preservation. Schema versions will probably differ more and more in the future from the now current one.
Dr. rer. nat. Helge Knüttel
Fachreferat Medizin, Informationsvermittlung Biomedizin
D-93042 Regensburg, Germany
email: [log in to unmask]
phone: ++49 941 944-5937; fax: ++49 941 944-5938
>>> [log in to unmask] 11/19/04 8:42 >>>
I think that in addition to having the URL for the current version of
METS ( http://www.loc.gov/standards/mets/mets.xsd) it would be useful to
have a working URL for the current version labelled by the version number.
That is, http://www.loc.gov/standards/mets/version13/mets.xsd should
lead to the 1.3 schema and not generate a 404 error, which it does
http://www.loc.gov/standards/mets/version11/mets.xsd (for v1.1) and
http://www.loc.gov/standards/mets/version12/mets.xsd (for v1.2) work.
Presumably, when we move to version 1.4,
http://www.loc.gov/standards/mets/version13/mets.xsd will come into
Is there a reason why
http://www.loc.gov/standards/mets/version13/mets.xsd will not exist
(presumably) until 1.4 becomes the official version? What do others think?
Raymond Yee 44 Barrows Hall, #3810
Technology Architect UC Berkeley
Interactive University Project Berkeley, CA 94720-3810
[log in to unmask] 510-642-0476 (work)
http://iu.berkeley.edu/rdhyee 413-541-5683 (fax)