[From nobody Sun Jan 13 12:58:01 2008
Envelope-to: lou@herald.ox.ac.uk
Delivery-date: Sun, 13 Jan 2008 17:44:24 +0000
Received: from rx2.herald.ox.ac.uk ([163.1.0.236])
	by imap211.herald.ox.ac.uk with esmtp (Exim 4.63)
	(envelope-from <nobody@sourceforge.net>) id 1JE6si-00075p-GP
	for lou@herald.ox.ac.uk; Sun, 13 Jan 2008 17:44:24 +0000
Received: from relay4.mail.ox.ac.uk (relay4.mail.ox.ac.uk [129.67.1.163])
	by rx2.herald.ox.ac.uk (Postfix) with ESMTP id 7068038040
	for <lou@herald.ox.ac.uk>; Sun, 13 Jan 2008 17:44:24 +0000 (GMT)
Received: from lists.sourceforge.net ([66.35.250.206]
	helo=mail.sourceforge.net)
	by relay4.mail.ox.ac.uk with esmtp (Exim 4.68)
	(envelope-from <nobody@sourceforge.net>) id 1JE6sh-0006RA-FA
	for lou.burnard@oucs.ox.ac.uk; Sun, 13 Jan 2008 17:44:24 +0000
Received: from sc8-sf-web22-b.sourceforge.net ([10.3.1.212]
	helo=sc8-sf-web22.sourceforge.net)
	by mail.sourceforge.net with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.44) id 1JE6sg-00066o-O7; Sun, 13 Jan 2008 09:44:22 -0800
Received: from nobody by sc8-sf-web22.sourceforge.net with local (Exim 4.43)
	id 1JE6sg-0007ep-C9; Sun, 13 Jan 2008 09:44:22 -0800
To: noreply@sourceforge.net
From: "SourceForge.net" <noreply@sourceforge.net>
Subject: [ tei-Bugs-1852101 ] title element should be a member of att.naming
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-SourceForge-Tracker-unixname: tei
X-SourceForge-Tracker-trackerid: 644062
X-SourceForge-Tracker-itemid: 1852101
X-SourceForge-Tracker-itemstatus: Open
X-SourceForge-Tracker-itemassignee: louburnard
X-SourceForge-Tracker-itemupdate-reason: Comment added
X-SourceForge-Tracker-itemupdate-username: louburnard
Message-Id: <E1JE6sg-0007ep-C9@sc8-sf-web22.sourceforge.net>
Sender: Nobody <nobody@sc8-sf-web22.sourceforge.net>
Date: Sun, 13 Jan 2008 09:44:22 -0800
X-Oxmail-Spam-Status: score=0.0 tests=none
X-Oxmail-Spam-Level: 

Bugs item #1852101, was opened at 2007-12-17 04:13
Message generated for change (Comment added) made by louburnard
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=644062&aid=1852101&group_id=106328

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Conal Tuohy (conal_tuohy)
>Assigned to: Lou Burnard (louburnard)
Summary: title element should be a member of att.naming

Initial Comment:
Clearly a <title> is a name of a thing, and I think to be consistent we should treat it like other kinds of names, where we've allowed encoders to identify precisely which thing is named, by reference to an entry in an authority file or similar (using @key or @ref). Adding <title> to att.naming would allow that.

I guess <lang> is a similar case.

See thread on Council list:
http://lists.village.virginia.edu/pipermail/tei-council/2007/009215.html

----------------------------------------------------------------------

>Comment By: Lou Burnard (louburnard)
Date: 2008-01-13 17:44

Message:
Logged In: YES 
user_id=1021146
Originator: NO

I have two problems with this. 
(1) when <title> appears inside a bibliographic record it really is the
canonical title, and so @key and @ref shouldn't be permitted there. 
(2) @key and @ref usually point to a <person>, <place>, or <org> or other
"named entity". If we are going to treat canonical titles in the same way,
won#'t we need to have a special place for them, a <listTitle> as it were?
or is the idea that you'd point to a <bibl> containing the canonical title?
What happens if two distinct bibliographic items happen to have the same
canonical title?

 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=644062&aid=1852101&group_id=106328
]