[tei-council] Proposal <idno> coverage -SF 2493417

[Laurent Romary]

Hi all,
Whether or not it is a major semantic shift, the  proposal has the  
property not to break existing usage and integrate smoothly in the  
encoding practices that lay behind the use of <idno> for other  
bibliographical component (note that an ISSN reference does not sit  
around on a shelf either: its an abstract entity allowing one to  
identify groups of publications ) one culd use the same argument to  
mean that an author identifier groups all papers from one author).
Anyhow, I fully support Peter's argumentation.
Laurent

Le 21 janv. 09 à 23:11, Lou Burnard a écrit :

> Peter Boot wrote:
>> This does not involve, as Syd wrote on the TEI in Libraries
>> mailing list
>> (https://listserv.indiana.edu/cgi-bin/wa-iub.exe?A2=ind0901B&L=TEILIB-L&T=0&F=&S=&P=2774 
>> ),
>> a ‘semantic shift’: <idno> would have the same meaning it always  
>> had, it
>> would just be applied to new elements.
>
> That is *precisely* what I would consider to be a semantic shift!
> We have an element called "persName" which has the semantics of "name
> applied to a person". If we redefine it to mean "name applied to a
> vegetable", it's still a name, but its semantics have changed.
>
> Similarly the current meaning of <idno> is that it's "an identifier  
> for
> a bibliographic item". Authors are not bibliographic items. They do  
> not
> (usually) sit around on shelves, and you cannot ask for a copy of one!
> By all means let's expand its semantics to include authors (etc), if  
> we
> want to do that, but let's not pretend we're not making a major change
> in the meaning of this element.
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council