[tei-council] Use of <imprint> wrapper inside <bibl>-like-things

[Perry Willett]

Speaking for myself and not for the entire library profession, <imprint> (or
<docimprint> in <titlepage> for that matter) has always struck me as
unnecessary. Seems like a vestige of MARC or something.

Perry Willett
University of Michigan
pwillett at umich.edu


-----Original Message-----
From: tei-council-bounces at lists.village.Virginia.EDU
[mailto:tei-council-bounces at lists.village.Virginia.EDU] On Behalf Of Syd
Bauman
Sent: Thursday, November 17, 2005 6:53 AM
To: TEI Council
Subject: [tei-council] Use of <imprint> wrapper inside <bibl>-like-things

At the "class" sub-committee meeting in Oxford in September, it was
decided to drop the <imprint> element from <bibl> and <biblItem> (but
not from <monogr>). The effect of this change from the
sub-committee's point of view is to make the TEI class system a
little simpler and more coherent. That's a good thing. The result
from the encoder's point of view is that things that are encoded as

  <bibl xml:id="IMEV">
    <author>Carleton Brown</author> and <author>Rossell Hope
Robbins</author>
    <title level="m">The index of Middle English verse</title>
    <imprint>
      <pubPlace>New York</pubPlace>
      <date>1943</date>
    </imprint>
  </bibl>

in P4 would need to become

  <bibl xml:id="IMEV">
    <author>Carleton Brown</author> and <author>Rossell Hope
Robbins</author>
    <title level="m">The index of Middle English verse</title>
    <pubPlace>New York</pubPlace>
    <date>1943</date>
  </bibl>
  
in P5.

I am posting here just to double-check that this change is OK with
Council. While all of us at the meeting were convinced that the extra
level of nesting is not helpful, I think it would be a good idea to
ask some librarians, catalogers, bibliographers, etc.

_______________________________________________
tei-council mailing list
tei-council at lists.village.Virginia.EDU
http://lists.village.Virginia.EDU/mailman/listinfo/tei-council