[MEI-L] revision of <bibl>

[Peter Stadler]

Dear Perry,

thank you for disseminating this issue. 
I have been discussing mei:bibl with Axel in the last weeks so I feel free to repeat my comments publicly:

First, TEI has the nice separation between tei:bibl and tei: biblStruct where the former is a "loosely-structured bibliographic citation" [1] and the latter a "structured bibliographic citation, in which only bibliographic sub-elements appear and in a specified order. "[2] 
If your use case is *creating* bibliographical citations, than the plain bibl can be used to store your citations already in the desired style (i.e. with punctuation etc.) which makes e.g. a later html output much easier.
So, my proposal would be to add a mei:biblStruct for at least three reasons:
1. MerMEId is using bibliographic citations in a highly structured way (cf. your examples)
2. It would not break backwards compatibility
3. a clear separation of structured and loosely-structured data which makes processing much easier since the processor knows what to expect. (Of course, the mei:biblStruct would need a clear structure with mandatory elements in a mandatory order)

Second, I don't understand the need for reinventing the wheel. There are a lot of schemata out there for bibliographic data which could be used, since it makes developing much easier as well as interchange. Here I'm not saying to use a different namespace (one could argue so, though) but to adopt the appropriate schemata from e.g. BibtexML[3], Zotero[4] or TEI[2].  For example I'd like to see the possibility to assign keywords/tags -- on the other hand I'm reluctant to introduce those special elements recipient and creation (the latter could go into mei:annot).

All the best
Peter

PS: By the way, mei:bibl is currently described as "Provides a citation for a published work." which should be amended to cover unpublished material as well.

[1] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-bibl.html
[2] http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-biblStruct.html
[3] http://bibtexml.sourceforge.net
[4] http://www.zotero.org/support/dev/data_model

Am 15.10.2012 um 20:50 schrieb "Roland, Perry (pdr4h)" <pdr4h at eservices.virginia.edu>:

> Hello,
> 
> Those of you subscribed to the developers list may have already seen a version of this message.  My apologies for cross-posting, but I think this is important enough to warrant soliciting a wide range of opinions, since some of the changes proposed will break backwards compatibility.
> 
> In order to better support bibliographic applications, such as MerMEId, the content model of <bibl> needs to be revised/expanded. The example below contains several new elements -- creator, editor, contributor, biblScope, genre, imprint, pubPlace, and publisher. These might also be useful at other points in addition to within <bibl>, say in the header, but that is not under consideration at the moment. A new <recipient> element may also be added for correspondence. <distributor> will also be allowed in <imprint>.
> 
> In addition, some existing elements, such as <creation>, should also be permitted within <bibl>.  This will allow the capture of non-bibliographic details of creation, such as the location where an item was created. 
> 
> Also, some existing elements, such as <physLoc> and <relatedItem>, should be allowed after re-definition; that is, <physLoc> will no longer function as the call number/shelf location. It will function as the wrapper for <repository> and <identifier>. In this context, <identifier> will hold the shelf number. With the FRBR changes, <relatedItem> will be replaced by <relation>, allowing <relatedItem> to be used as illustrated here.
> 
> The new element <biblList> will be a member of model.listLike, allowing it to be used wherever <list> is currently allowed. Other places where it might occur include <work>, <source> (will be called <item> after FRBR implementation, <event>, <eventList>, etc.
> 
> <biblList>
>  <bibl>
>    <!-- genre is preferred over @type on bibl so that authorizing info about the material designation can be captured. -->
>    <genre authority="marcgt"
>    authURI="http://www.loc.gov/standards/valuelist/marcgt.html">article</genre>
>    <creator>Daniel Grimley</creator>
>    <title level="a">Modernism and Closure: Nielsen's Fifth Symphony</title>
>    <title level="j">The Musical Quarterly</title>
>    <!-- The bibliographic unit values below can be added to the unit attribute defined in att.measurement. -->
>    <biblScope unit="vol">86</biblScope>
>    <biblScope unit="issue">1</biblScope>
>    <biblScope unit="pp">149-173</biblScope>
>    <imprint>
>      <pubPlace>London</pubPlace>
>      <date isodate="2002">2002</date>
>    </imprint>
>  </bibl>
>  <bibl>
>    <creator>Carl Nielsen</creator>
>    <recipient>William Behrend</recipient>
> 
>    <!-- Name with @role will still be possible, but the specific elements above are preferred. -->
>    <name role="author">Carl Nielsen</name>
>    <name role="recipient">William Behrend</name>
> 
>    <date isodate="1904-04-13">1904-04-13</date>
>    <genre>letter</genre>
>    <creation>
>      <geogName>Copenhagen</geogName>
>    </creation>
>    <physLoc>
>      <repository>DK-Kk</repository>
>      <identifier>NKS 5155 4°</identifier>
>    </physLoc>
>    <relatedItem rel="host">
>      <bibl>
>        <title>CNB</title>
>        <biblScope>II/333</biblScope>
>      </bibl>
>    </relatedItem>
>  </bibl>
> </biblList>
> 
> Comments are greatly appreciated, especially if this will break anything you're currently doing.
> 
> --
> p.
> 
> __________________________
> Perry Roland
> Music Library
> University of Virginia
> P. O. Box 400175
> Charlottesville, VA 22904
> 434-982-2702 (w)
> pdr4h (at) virginia (dot) edu
> _______________________________________________
> mei-l mailing list
> mei-l at lists.uni-paderborn.de
> https://lists.uni-paderborn.de/mailman/listinfo/mei-l