Am 12.03.2012 16:43, schrieb Jon Stroop:
> Following up since there have been no comments about this; the MODS
> Editorial Committee is trying to figure out how to proceed and we would
> appreciate feedback. The proposed solution is as follows (pasted from
>> Embedding presentational markup within MODS records is out of scope of
>> what MODS--as a data format--intends to accomplish and contradicts the
>> widely followed best-practice of separating content from presentation.
>> Furthermore, adding support for (X)HTML elements in the MODS schema
>> would force all implementers to account for any and all elements in
>> the HTML namespace.
>> The committee has come up with a possible solution that involves the
>> definition of two new attributes, tentatively named altFormat and
>> Use the altFormat attribute to link out of the record to the same
>> content, formatted or marked up in a different way. Optionally,
>> include the contentType attribute with a media-type as its value (e.g.
>> text/html) to indicate the content type of the target. Where there are
>> multiple alternatives, use the already defined altRepGroup attribute
>> to bind the related instances of each element.
>> <abstract altRepGroup="A"
>> <abstract altRepGroup="A">l'histoire d'un cheval et un garçon qui
I could live with that solution but contentType should not imply the
usage of altForm.
<mods:titleInfo altRepGroup="1" contentType="text/html">
<mods:title>Understanding <acronym title="Metadata Object
In this case I have the HTML code escaped and no implementor is forced
to recognize it. They do have to recognize the contentType attribute of
You do not have to see this HTML as presentational markup, it is not
said how we present it to the user. We are just adding more semantic.
There has to be some kind of escaping/encoding of these things in the
text and choosing HTML seems to be natural here.
Thüringer Universitäts- und Landesbibliothek
Phone: ++49 3641 940027
FAX: ++49 3641 940022