On Mar 30, 2005, at 7:57 PM, Andrew E Switala wrote:
> There's still the issue of displaying unrecognized markup.
I had posted the note in part because while I had earlier been
concerned that people that do math couldn't get by without MathML in
titles, David pointed out there are workarounds.
However, he is clear of the need for it in abstracts, which is what
I've heard elsewhere as well.
In any case ...
> Three possibilities that come to mind for dealing with that are
> 1. Displaying the text content without the markup, with instructions in
> the users' guidelines to the effect that any inline markup scheme
> leave intelligible text when the tags are removed.
So do as XML parsers and XSLT processor do by default?
> 2. Converting the markup to text and displaying it, e.g.
> <title><x:y xmlns:x="http://blahblah">z</x:y></title>
> is converted to
> <x:y xmlns:x="http://blahblah">z</x:y>
> for display on a Web page.
I confess I don't quite understand #2. You're proposing escaped
> 3. Alternate text.
Not following here.
> I'm partial to #2, which is the simplest to implement (no new
> attributes/elements for denoting the alternate text, and no
> outside of schema validity). It's also more or less what people have
> been doing all along with BibTeX--putting the records on the Web with
> embedded TeX markup unmodified.
Well, if inline markup were allowed, it should obviously be with the
idea in mind that it be flexible,
I see a number of levels of possibility for the markup. Starting with
the simplest and most tightly-controlled, to the most complex,
1) Define a single new inline element. In the Endnote XML format it's
called (problematically) "style", in XHTML it's called "span" (better
because it's more generic, and because you can assign semantic classes
to it), in DocBook it's "phrase." In any case, it's a single element
you can load with flexible semantic information.
<title>Some Title with <span class="emphasis">Emphasis</span> and a
<span class="title monographic">Title</span></title>
The advantage of this is it's flexible, it's simple, and it maps really
easily to the web.
2) Allow a handful of MODS elements to be children of certain key
element; most notably title and subTitle. This is the sort of thing
<title><name>Joe</name> and <title>Title</title></title>
3) Allow foreign namespace content in certain elements (titles,
abstracts, etc.). This then makes the math people happy, but could
open up problems.
There are other possibilities too, of course.
BTW, on a related note, I've settled on an annotation markup language
that is more-or-less a very simple version of XHTML. I markup quotes
with page numbers and such. However, I can't actually include any of
that in a MODS record, except in the extension element.