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 http://bit.ly/AtfaIZ): > 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 > contentType. > > 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. > > Example: > <abstract altRepGroup="A" altForm="http://foo.edu/alternate-markup.html" contentType="application/xhtml+xml"/> > <abstract altRepGroup="A">l'histoire d'un cheval et un garçon qui aimait</abstract> All best, Jon On 02/27/2012 01:21 PM, Jon Stroop wrote: > Thomas, > The MODS Editorial Committee has been discussing your proposal, and > while we don't feel comfortable with the idea of allowing for HTML (or > other markup) to be embedded within MODS elements, we think we may > have come up with a solution. Please see the details on the MODS E.C. > wiki: > > http://bit.ly/AtfaIZ > > We welcome any feedback you (or, of course, anyone on the list) might > have. > > Best, > Jon Stroop, on behalf of the MODS Editorial Committee > > On 01/17/2012 06:16 AM, Thomas Scheffler wrote: >> Hi, >> >> currently we are developing a MODS support component in our open >> source framework MyCoRe. >> >> During implementation we noticed a nice feature is missing. For >> accessibility of the presentation platform we like to add some hints >> for screen readers etc.. We want use what the HTML standard provides >> us, as this is our primary presentation platform. So whenever a title >> or an abstract is entered we provide an additional field with the >> same text HTML-encoded. The proper way to link both together is to >> use the altRepGroup attribute as HTML is another representation of >> the normal plain text field. >> >> Sadly there is no way of tagging which variant is plain text and >> which is HTML. There are three more attributes allowed: xml:lang, >> transliteration and script. Neither of them fits. I would like to >> suggest an "encoding" attribute that would enable this use case. >> >> regards >> >> Thomas Scheffler