<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"Formateret HTML Tegn";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.FormateretHTMLTegn
{mso-style-name:"Formateret HTML Tegn";
mso-style-priority:99;
mso-style-link:"Formateret HTML";
font-family:Consolas;
color:black;}
p.FormateretHTML, li.FormateretHTML, div.FormateretHTML
{mso-style-name:"Formateret HTML";
mso-style-link:"Formateret HTML Tegn";
margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
font-variant:normal !important;
color:black;
text-transform:none;
position:relative;
top:0pt;
mso-text-raise:0pt;
letter-spacing:0pt;
text-shadow:none;
font-weight:normal;
font-style:normal;
text-decoration:none none;
vertical-align:baseline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:3.0cm 2.0cm 3.0cm 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="DA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Hi Benjamin, Perry, & all<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">I notice that <provenance> is a child of the manuscript description’s <history> element in TEI. That does make sense to me, as the manuscript’s history may roughly
be divided into its creation and its transmission. However I see your point, Perry, that in our case, making <provenance> available within <history> would be nonsense in the context of work and expression (and possibly even in source, but only when using the
FRBR module, in which case <provenance> belongs at item level). <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">Provenance is related to both history and physical location, as it may be regarded as the item’s historical record of physical locations or owners. That is why
I brought it up in this <history> discussion, and also why I brought it up a couple of years ago in a discussion about <physLoc>. I am not sure I can see any can of worms hidden here, but of course I don’t know what has been discussed elsewhere. My reason
for starting the discussion back in December 2012 was that I noticed that <physLoc> was moved out of <physDesc> but <provenance> was not. I never understood why <provenance> was left in <physDesc>.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">I am perfectly aware, of course, that <physLoc> only describes an item’s current location, not previous ones. I have no particular preferences whether <provenance>
should be a child of <history>, <physLoc>, or be their sibling. The latter option may very well be the best solution, making <physLoc> and <provenance> siblings as they were originally, but now in the context of <source> or <item> instead of <physDesc>. In
the physical description of an item, where it is now, provenance information appears – at least to me – even more out of place than the information on the item’s current location.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif"">I am sorry if this opens some unwanted discussions, but actually I don’t see this as very problematic, just as something we forgot :-)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Axel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif""><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:65.2pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext">Fra:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext"> mei-l [mailto:mei-l-bounces@lists.uni-paderborn.de]
<b>På vegne af </b>Benjamin Wolff Bohl<br>
<b>Sendt:</b> 4. april 2014 11:04<br>
<b>Til:</b> mei-l@lists.uni-paderborn.de<br>
<b>Emne:</b> Re: [MEI-L] history of sources / items<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:65.2pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Dear all,<br>
<br>
not that I have too much experience in cataloguing sources or writing verbose source description, but it might help to have a look at the TEI way of doing things. Some nice example applications concerning manuscripts were presented during the Edirom-Summer-School
2013 by Torsten Schaßan.<br>
<br>
The Herzog August Bibliothek has their TEI code available on-line, see for example:<br>
</span><a href="http://diglib.hab.de/?db=mss&list=ms&id=27-2-aug-2f&catalog=Lesser&mode=xml"><span lang="EN-US">http://diglib.hab.de/?db=mss&list=ms&id=27-2-aug-2f&catalog=Lesser&mode=xml</span></a><span lang="EN-US"><br>
<br>
Just my to code-points ;-)<br>
Benjamin<br>
<br>
<o:p></o:p></span></p>
<pre style="margin-left:65.2pt"><span lang="DE">***********************************************************<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">Musikwissenschaftliches Seminar Detmold/Paderborn<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">BMBF-Projekt "Freischütz Digital"<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">Benjamin Wolff Bohl<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">Gartenstraße 20<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">D–32756 Detmold<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE"><o:p> </o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">Tel. +49 (0) 5231 / 975-669<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">Fax: +49 (0) 5231 / 975-668<o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">E-Mail: </span><a href="mailto:bohl@edirom.de"><span lang="DE">bohl@edirom.de</span></a><span lang="DE"><o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE"><o:p> </o:p></span></pre>
<pre style="margin-left:65.2pt"><a href="http://www.freischuetz-digital.de"><span lang="DE">http://www.freischuetz-digital.de</span></a><span lang="DE"><o:p></o:p></span></pre>
<pre style="margin-left:65.2pt"><span lang="DE">***********************************************************<o:p></o:p></span></pre>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="DE">Am 03.04.2014 21:32, schrieb Joachim Veit:<o:p></o:p></span></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Dear Perry, <br>
thank you very much for these details and <annot type="naive">excuse my misunderstanding of the possibilities of "annotation"</annot>!!
<br>
Indeed your proposal to transfer the possibiliies of <annot> to <history> would be excellent in my eyes because - at least in our case - the history will be so detailed that <annot> seems to be semantically inadequate (at least if we consent that the content
of an essay should not be hidden in the footnotes but in the main text...;-) ). <br>
And with <div> we should have the opportunity to squeeze al things in which are hidden in the 27 corners of our project...
<br>
Waiting for the discussion with Kristina and Johannes tomorrow, <br>
meanwhile with cordial thanks and best greetings, <br>
Joachim <br>
<br>
<br>
Am 03.04.14 17:59, schrieb Roland, Perry D. (pdr4h): <br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Johannes and Joachim,
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Sometimes you have a copy, and you would like to tell the story behind it – why it has been copied, under which conditions it happened, etc. Basically, I want to get hold of <creation> for source
(and maybe item, even though I think this might be less important). Of course, people may confuse the histories of works and sources, but this doesn't explain why there shouldn't be a source history in MEI…
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">I understand your motivation better, but <creation> is not the thing you're looking for (ala Obi-wan Kenobi). <creation> is intended to hold a *brief* statement of the circumstances of creation.
That's why it's content model is very restrictive: <br>
<br>
<rng:zeroOrMore> <br>
<rng:choice> <br>
<rng:text/> <br>
<rng:ref name="date"/> <br>
<rng:ref name="geogName"/> <br>
</rng:choice> <br>
</rng:zeroOrMore> <br>
<br>
It's nothing more than a string with <date> and <geogName> thrown in to capture important dates and places. You could think of <creation> as the "quick and dirty" or "headline" version of the content that follows it.
<br>
<br>
For more "essay-like" content, you can use the other possible children of history; i.e., eventList and p.
<br>
<br>
<rng:optional> <br>
<rng:ref name="model.headLike"/> <br>
</rng:optional> <br>
<rng:optional> <br>
<rng:ref name="creation"/> <br>
</rng:optional> <br>
<rng:zeroOrMore> <br>
<rng:choice> <br>
<rng:ref name="eventList"/> <br>
<rng:ref name="p"/> <br>
</rng:choice> <br>
</rng:zeroOrMore> <br>
<br>
But contrary to what Joachim said, the most "book-like" and least restrictive model is actually that of <annot>:
<br>
<br>
<rng:zeroOrMore> <br>
<rng:choice> <br>
<rng:text/> <br>
<rng:ref name="model.textcomponentLike"/> <br>
<rng:ref name="model.textphraseLike"/> <br>
<rng:ref name="model.editLike"/> <br>
<rng:ref name="model.transcriptionLike"/> <br>
</rng:choice> <br>
</rng:zeroOrMore> <br>
<br>
This allows just about everything under the sun! <br>
<br>
On the issue of <history>, what I hear you saying is that you'd like its content model to be more like that of <annot>, something like:
<br>
<br>
<rng:optional> <br>
<rng:ref name="model.headLike"/> <br>
</rng:optional> <br>
<rng:optional> <br>
<rng:ref name="creation"/> <br>
</rng:optional> <br>
<rng:zeroOrMore> <br>
<rng:choice> <br>
<rng:ref name="model.textcomponentLike"/> <br>
</rng:choice> <br>
</rng:zeroOrMore> <br>
<br>
where the members of model.textcomponentLike are: <br>
<br>
lgLike - lg <br>
listLike - biblList, eventList, list <br>
pLike -p <br>
quoteLike - quote <br>
tableLike - table <br>
<br>
or perhaps <br>
<br>
<rng:optional> <br>
<rng:ref name="model.headLike"/> <br>
</rng:optional> <br>
<rng:optional> <br>
<rng:ref name="creation"/> <br>
</rng:optional> <br>
<rng:zeroOrMore> <br>
<rng:ref name="model.divLike"/> <br>
</rng:zeroOrMore> <br>
<br>
where the membership of model.divLike is just <div> and members of model.divLike and model.textcomponentLike are permitted as content of <div>
<br>
<br>
or <br>
<br>
<rng:optional> <br>
<rng:ref name="model.headLike"/> <br>
</rng:optional> <br>
<rng:optional> <br>
<rng:ref name="creation"/> <br>
</rng:optional> <br>
<rng:zeroOrMore> <br>
<rng:choice> <br>
<rng:ref name="model.divLike"/> <br>
<rng:ref name="model.textcomponentLike"/> <br>
</rng:choice> <br>
</rng:zeroOrMore> <br>
<br>
making <history> into a more div-Like container that can wrap other components and divs (which is how you can get section headings).
<br>
<br>
These modifications will also address your need to include a list of bibliographic citations within <history>.
<br>
<br>
Going farther, we could even drop <creation> from <history>, moving any content in former versions of MEI to subordinate <p> elements. This would eliminate the privileging of data-like uses of <creation>.
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">I still think that <history> might be a better parent for <provenance> than <physDesc>. We agree that the provenance of an item is not part of the physical description, do we? I'm not saying
we must move it to history, but I wonder if we could, possibly with additional means to prevent it from showing up on work and expression…
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US"><physDesc> was a convenient place to locate <provenance> since in library land, as Joachim confirms, "provenance> often has clear connections with <physDesc> because stamps and librarian's or
auctioneer's entries are often mentioned in this context." But there's no reason why it should remain there if there's a compelling reason to move it.
<br>
<br>
We could move <provenance> up a level into <item> itself rather than placing it inside <history> and then making <history> available inside <item>. Taking this approach would put <provenance> where it needs to be (on <item>) and not everywhere <history> can
occur; that is, <work>, <expression>, and <source> (should we decide to allow <history> there too). It also maintains separation between the history of "handing down" (quoting Joachim) of the item and the production history of the item, which is the proper
content for <item>/<history>. <br>
<br>
Does this help? <br>
<br>
-- <br>
p. <br>
<br>
__________________________ <br>
Perry Roland <br>
Music Library <br>
University of Virginia <br>
P. O. Box 400175 <br>
Charlottesville, VA 22904 <br>
434-982-2702 (w) <br>
pdr4h (at) virginia (dot) edu <br>
________________________________________ <br>
From: mei-l [</span><a href="mailto:mei-l-bounces@lists.uni-paderborn.de"><span lang="EN-US">mei-l-bounces@lists.uni-paderborn.de</span></a><span lang="EN-US">] on behalf of Johannes Kepper [</span><a href="mailto:kepper@edirom.de"><span lang="EN-US">kepper@edirom.de</span></a><span lang="EN-US">]
<br>
Sent: Thursday, April 03, 2014 9:26 AM <br>
To: Music Encoding Initiative <br>
Subject: Re: [MEI-L] history of sources / items <br>
<br>
Am 03.04.2014 um 15:10 schrieb Roland, Perry D. (pdr4h) </span><a href="mailto:pdr4h@eservices.virginia.edu"><span lang="EN-US"><pdr4h@eservices.virginia.edu></span></a><span lang="EN-US">:
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Johannes, <br>
<br>
Sorry for arriving late to the party. :-) <br>
<br>
The <history> element wasn't provided in source (manifestation) and item in order to encourage the use of work/history or expression/history. The assumption was that what folks often have to say about a manifestation or item is really about the work and expression
anyway. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Sometimes you have a copy, and you would like to tell the story behind it – why it has been copied, under which conditions it happened, etc. Basically, I want to get hold of <creation> for source
(and maybe item, even though I think this might be less important). Of course, people may confuse the histories of works and sources, but this doesn't explain why there shouldn't be a source history in MEI…
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">A notesStmt/annot element (perhaps with a label of "history" in this case) can be used as a "catch all" to capture any information not easily shoe-horned into the other available elements in
work, expression, source, and item. But, since the models of source and item are essentially lists of optional children, it's also not difficult to add <history> in all these places without creating any backwards compatibility problems. Before doing so,
however, I'd like to know more about what you'd like to say about source and/or item history that makes this necessary.
<br>
<br>
I'm not in favor of moving <provenance> inside <history> because doing this would mean breaking compatibility. It would also make provenance available inside work, expression, and source (e.g., work/history/provenance) where its presence could lead to abuse.
What exactly is the provenance (that is, the custodial history) of a work or expression? I don't there is such a thing.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">Well, I see your point, and I agree with that. There is certainly no provenance of a work or expression. The kind of information someone would be looking for is about the transmission of the
work, which should go into history. However, I still think that <history> might be a better parent for <provenance> than <physDesc>. We agree that the provenance of an item is not part of the physical description, do we? I'm not saying we must move it to history,
but I wonder if we could, possibly with additional means to prevent it from showing up on work and expression…
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">I don't understand what problem you're having with <bibl> inside <source>. Are you looking to provide bibliographic citations for whatever arguments you present in <history>? I need more information,
please. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">I have no problem with bibl inside source, except that it isn't allowed. I'd like to be able to put in literature about a specific source (like a review of a printed edition etc.), that's it.
The current means to get a bibl into source seem to be too complicated… <br>
<br>
Hth, <br>
Johannes <br>
Ceterum censeo, don't forget to discuss the MEI organization, either here on MEI-L or at
</span><a href="http://bit.ly/1hDyq4X"><span lang="EN-US">http://bit.ly/1hDyq4X</span></a><span lang="EN-US">.
<br>
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">-- <br>
p. <br>
<br>
__________________________ <br>
Perry Roland <br>
Music Library <br>
University of Virginia <br>
P. O. Box 400175 <br>
Charlottesville, VA 22904 <br>
434-982-2702 (w) <br>
pdr4h (at) virginia (dot) edu <br>
________________________________________ <br>
From: mei-l [</span><a href="mailto:mei-l-bounces+pdr4h=virginia.edu@lists.uni-paderborn.de"><span lang="EN-US">mei-l-bounces+pdr4h=virginia.edu@lists.uni-paderborn.de</span></a><span lang="EN-US">] on behalf of Johannes Kepper [</span><a href="mailto:kepper@edirom.de"><span lang="EN-US">kepper@edirom.de</span></a><span lang="EN-US">]
<br>
Sent: Thursday, April 03, 2014 5:16 AM <br>
To: Music Encoding Initiative <br>
Subject: Re: [MEI-L] history of sources / items <br>
<br>
I was hoping to get a reply from Perry, especially since I think this dates back to the days before FRBR, when there were work and source elements. expression and item just inherited their standard models with little modifications, so I'm not surprised about
their behavior. <br>
<br>
However, I also prefer to add a history element to source and item, and moving provenance in there seems like a logical modification then. I wouldn't worry too much about backward compatibility. I think we're past the point where we'd have to make huge changes
to the model, and little modifications should require only little modifications in software. Also, providing a XSLT to go back and forth between MEI2013 and MEI201x is not an issue, so that people could use whatever is most appropriate to them. This might
result in putting the history somewhere nested into a notesStmt when going back to 2013, but so be it…
<br>
<br>
I remember discussions about structured vs. prose-based content models for a number of elements, among them bibl and annot. Does this relate to the initial question, and should we revise it as well?
<br>
<br>
<br>
Johannes <br>
Ceterum censeo, don't forget to discuss the MEI organization, either here on MEI-L or at
</span><a href="http://bit.ly/1hDyq4X"><span lang="EN-US">http://bit.ly/1hDyq4X</span></a><span lang="EN-US">.
<br>
<br>
<br>
<br>
Am 03.04.2014 um 02:50 schrieb Eleanor Selfridge-Field </span><a href="mailto:esfield@stanford.edu"><span lang="EN-US"><esfield@stanford.edu></span></a><span lang="EN-US">:
<br>
<br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US">"Provenance" is a standard item in catalogues of works in manuscript, but
<br>
it has a range of meanings, all of which might comfortable fit within <br>
"history". It sometimes identifies previously owners but equally often it <br>
refers to a physical location (city, institution, performing group et <br>
al.). <br>
<br>
Eleanor <br>
<br>
Eleanor Selfridge-Field <br>
Consulting Professor, Music (and, by courtesy, Symbolic Systems) <br>
Braun Music Center #129 <br>
Stanford University <br>
Stanford, CA 94305-3076, USA <br>
</span><a href="http://www.stanford.edu/~esfield/"><span lang="EN-US">http://www.stanford.edu/~esfield/</span></a><span lang="EN-US"> +1/ 650 725-9242
<br>
<br>
<br>
-----Original Message----- <br>
From: mei-l [</span><a href="mailto:mei-l-bounces@lists.uni-paderborn.de"><span lang="EN-US">mailto:mei-l-bounces@lists.uni-paderborn.de</span></a><span lang="EN-US">] On Behalf Of
<br>
Johannes Kepper <br>
Sent: Wednesday, April 02, 2014 2:39 AM <br>
To: Music Encoding Initiative <br>
Subject: [MEI-L] history of sources / items <br>
<br>
Dear list, <br>
<br>
while discussing the upcoming Weber Werkverzeichnis (Weber's work <br>
catalogue) with Kristina Richts and Joachim Veit, I can't remember why we <br>
dropped the <history> element from sources and items? We have it on works <br>
and expressions, but not on these two. However, it might be interested to <br>
write something about the creation of a source (which is not the same as <br>
the provenance, which is available). Can someone please remind me of our <br>
argument to drop it? Otherwise, it would be a fault that we might want to <br>
correct. <br>
<br>
Btw., <bibl> seems to be equally hidden (you can get it from source at <br>
source/physDesc/physMedium/bibl.). <br>
<br>
Best, <br>
Johannes <br>
<br>
_______________________________________________ <br>
mei-l mailing list <br>
</span><a href="mailto:mei-l@lists.uni-paderborn.de"><span lang="EN-US">mei-l@lists.uni-paderborn.de</span></a><span lang="EN-US">
<br>
</span><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l"><span lang="EN-US">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</span></a>
<span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US"><br>
_______________________________________________ <br>
mei-l mailing list <br>
</span><a href="mailto:mei-l@lists.uni-paderborn.de"><span lang="EN-US">mei-l@lists.uni-paderborn.de</span></a><span lang="EN-US">
<br>
</span><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l"><span lang="EN-US">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</span></a>
<span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US"><br>
_______________________________________________ <br>
mei-l mailing list <br>
</span><a href="mailto:mei-l@lists.uni-paderborn.de"><span lang="EN-US">mei-l@lists.uni-paderborn.de</span></a><span lang="EN-US">
<br>
</span><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l"><span lang="EN-US">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</span></a>
<span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:65.2pt"><span lang="EN-US"><br>
<br>
<br>
<br>
<o:p></o:p></span></p>
<pre style="margin-left:65.2pt">_______________________________________________<o:p></o:p></pre>
<pre style="margin-left:65.2pt">mei-l mailing list<o:p></o:p></pre>
<pre style="margin-left:65.2pt"><a href="mailto:mei-l@lists.uni-paderborn.de">mei-l@lists.uni-paderborn.de</a><o:p></o:p></pre>
<pre style="margin-left:65.2pt"><a href="https://lists.uni-paderborn.de/mailman/listinfo/mei-l">https://lists.uni-paderborn.de/mailman/listinfo/mei-l</a><o:p></o:p></pre>
</blockquote>
<p class="MsoNormal" style="margin-left:65.2pt"><o:p> </o:p></p>
</div>
</body>
</html>