[tei-council] [ tei-Bugs-1852100 ] nameLink element should not have @ref or @key attribute

[Lou's Laptop]

SourceForge.net wrote:
> Bugs item #1852100, was opened at 2007-12-17 04:09
> Message generated for change (Comment added) made by louburnard
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=644062&aid=1852100&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: nameLink element should not have @ref or @key attribute
>
> Initial Comment:
> It seems to me that att.personal should not be a
> member of att.naming, because this allows nameLink to be used with @key
> or @ref as an identifier for a person, something which seems highly
> improbable to me, to say the least.
>
> Because nameLink is a member of att.naming (via att.personal), it can
> have a @ref or @key to identify the entity being named by the nameLink -
> yet nameLink is not in fact a name. 
>
> "<nameLink> contains a connecting phrase or link used within a name but
> not regarded as part of it, such as van der or of."
> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-nameLink.html
>
> For example, this is valid, but, I submit, nonsensical:
>
> <persName>
>  <forename>Frederick</forename>
>  <nameLink key="frederick.van-der.tronk">van der</nameLink>
>  <surname>Tronck</surname>
> </persName>
>
> This glitch can be resolved by removing att.personal from att.naming,
> and instead explicitly including in att.naming every member of
> model.persNamePart EXCEPT nameLink.
>
> I also wonder whether persName itself needs @sort?
> http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.personal.html
>
>
> ----------------------------------------------------------------------
>
>   
>> Comment By: Lou Burnard (louburnard)
>>     
> Date: 2008-01-13 17:35
>
> Message:
> Logged In: YES 
> user_id=1021146
> Originator: NO
>
> I agree that it's wrong to have @key and @ref on nameLink. And I think
> your suggested fix would work. Do other Council members think this is in
> the category of egregious fixable errors?
>
>   
>
> ----------------------------------------------------------------------
>
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=644062&aid=1852100&group_id=106328
>