LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  May 2013

TEI-L May 2013

Subject:

Re: teiHeader and CIP

From:

Matija Ogrin <[log in to unmask]>

Reply-To:

Matija Ogrin <[log in to unmask]>

Date:

Mon, 13 May 2013 23:49:45 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (56 lines)

Hello,

Thanks to all who shared their views on this topic. I don't know which 
encoding would be most appropriate ... Kevin's proposition about a <cip> 
element as a direct child of <publicationStmt> is the most clear, of 
course, and also Lou's suggestion to generalise the new element is to 
the point. Some further discussion will be needed, I guess.--

This way or another, the idea to include a CIP in the <teiHeader> has 
some reasonable grounds, I would think. Librarians maintain the view 
that a CIP record provides reliable data about the edition -- (even more 
reliable than those in the title page, they say). They argue that a CIP 
record confers a more authoritative status to the edition because it is 
controlled and catalogued in the OPAC. By means of a CIP, they say, a 
digital edition is more clearly distinguished from millions of other 
things "on the Internet", etc.

Dne 13. 05. 2013 06:27, piše Kevin Hawkins:
> So my preferred solution is still a new child of <publicationStmt>.  I
> almost put in a SourceForge feature request when I first replied to
> Matija's message, but then I realized that a project-specific
> customization will probably suffice.
A project-specific customization is something I would like to avoid 
here, if possible. After all, a CIP record is a very general thing, 
inserted in nearly every printed book and surely in every scholarly 
edition, dictionary, and other reference works.

After all, I find it unlikely any
> other national library would choose to issue CIP data for people's TEI
> documents,

Why not? Finally, the library doesn't issue a CIP to my private 
TEI-document, but to a "finished" digital edition, publicly available 
and used on the net. After all, digital edition is just a book ... 
Later, I may publish a new version of the edition, and librarians will 
modify the OPAC-record accordingly, this is a normal practice.

The inclusion of a new child-element in <publicationStmt> would resolve 
the issue, so I strongly support Kevin's idea.
Best,
Matija

>
> But if others have this same need, I would support creating this new
> element in P5.
>
> --Kevin


-- 
Matija Ogrin, dr.
Neznani rokopisi slovenskega slovstva 17. in 18. stoletja (NRSS)
<http://ezb.ijs.si/nrss/>
Inštitut za slovensko literaturo in literarne vede
ZRC SAZU

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager