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:
We welcome any feedback you (or, of course, anyone on the list) might have.
Jon Stroop, on behalf of the MODS Editorial Committee
On 01/17/2012 06:16 AM, Thomas Scheffler wrote:
> 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.
> Thomas Scheffler