On Feb 19, 2005, at 12:40 AM, Doug M-C wrote:
> Aren't we getting too complicated here?
> An XSLT processor can distinguish between one or more than one
> occurrence of a particular element and group the occurrences as
> appropriate, yes? Bruce?
> So, why not:
> <name type="personal">
> <namePart type="given" script="xx">John</namePart>
> <namePart type="family" script="xx">Doe</namePart>
> <namePart type="given" script="zz">XXX</namePart>
> <namePart type="family" script="zz">YYY</namePart>
I suppose it's possible, but I have a strong hunch the processing logic
is easier if you separately group them, with the alternateForm child
alternately being the simplest all around (in terms of markup, and in
terms of processing).
> That's from a purely MODS perspective.
> Adding MADS into the picture might make it more complicated.
Which is why I've complained about MADS in the past and about name
representation in general. I don't think it needs to be "more
> Are there plans to enable the use of MADS from within an
> OpenDocument, Bruce?
No. It would be a triumph to get them to include MODS; MADS is
It could be used within the bib plug-in that gets bundled with
OpenOffice though, in which case ...
> I would then guess that it is up to the
> particular processor (say, OpenOffice.org) as to how much
> information it transfers from a MADS record into the MODS record
> in a particular document. Just the authoritative name;
> authoritative name plus variants in other scripts, if present;
> authoritative plus all variants; etc.
Right; that's what I had in mind.