On Wed, Jun 23, 2010 at 8:01 AM, Ashley Sanders
<a.sanders_at_manchester.ac.uk> wrote:
Actually, I'll be completely honest here, this looks like a horrible
idea. If you've ever had to try to parse and deal with formats that
do stuff like this (EAD, for example), they're excruciatingly
difficult to work with, simply because of all of the possible
variables that can appear when you're just, in this example, trying to
get the title string.
I'm also not entirely sure what this level of granularity buys you or
any reasonable way you would actually add data like this.
Trying to write applications to logically pull this data would be make
me want yank my hair out. We're not confined to 99,999 bytes in XML
-- it makes more sense to model things properly and explicitly and
consistently (the last being possibly the most important).
-Ross.
> <mods>
> <originInfo>
> <dateIssued encoding="marc">1840</dateIssued>
> </originInfo>
> <titleInfo>
> <title>Birmingham and Derby Junction Railway Time Tables.</title>
> </titleInfo>
> <name type="corporate">
> <namePart>BIRMINGHAM AND DERBY JUNCTION RAILWAY COMPANY.</namePart>
> <role>
> <roleTerm type="text">creator</roleTerm>
> </role>
> </name>
> <note>In : Midland Counties’ Railway. The Midland Counties’ Railway
> Companion, etc. 1840. 12º.</note>
> </mods>
>
> What would be nice is to be able to encode it something like this:
>
> <mods>
> <originInfo>
> <dateIssued encoding="marc">1840</dateIssued>
> </originInfo>
> <title><name type="corporate">Birmingham and Derby Junction Railway</name>
> Time Tables.</title>
> <name type="corporate">
> BIRMINGHAM AND DERBY JUNCTION RAILWAY COMPANY.
> <role type="text">creator</role>
> </name>
> <note>In : <name type="corporate">Midland Counties’ Railway</name>. <work
> relation="In"><title>The <name type="corporate">Midland Counties’
> Railway</name> Companion</title>, etc. <dateIssued>1840</dateIssued>.
> <format>12º</format></work>.</note>
> </mods>
>
> Ie, if we have mixed content in the XML we can drop the need for
> having a <titleInfo> tag as a parent for <title>. Likewise we can
> get rid of the <namePart> tag inside the <name> tag; and get
> rid of <roleTerm> inside <role>. (Actually I'd prefer to get rid
> <role> and replace it with an attribute of <name>.)
>
> We would be able to mark-up names, titles and other interesting info
> inside notes -- in fact, inside any other element.
>
> I think what we would end up with is the potential for much richer
> records, while simplifying the tag structure.
>
> Regards,
>
> Ashley.
> --
> Ashley Sanders a.sanders_at_manchester.ac.uk
> Copac http://copac.ac.uk A Mimas service funded by JISC
>
Received on Wed Jun 23 2010 - 08:36:36 EDT