[tei-council] class struggle continues

[James Cummings]

Lou Burnard wrote:
> I've just fallen over what looks to be a mistake in the way a couple of
> classes are defined. The two are:
> 
> att.personal  "common attributes for those elements which form part of a
> personal name" which gives you @type @full and @sort
> 
> att.naming    "provides attributes common to elements which refer to
> named persons, places, organizations etc." which just gives you @key
> (and will also shortly give you @nymKey)
> 
> Members of att.personal: addName  forename  genName  nameLink  roleName
>  surname
> 
> Members of att.naming: affiliation  birth  bloc  collection  country
> death  district  education  geog  geogName  institution  name
> nationality  occupation  persEvent  persName  persState  persTrait
> placeName  pubPlace  region  relation  repository  residence  rs
> settlement  socecStatus
> 
> Seems to me that
> * persName ought to be a member of att.personal (definitely)
agreed
> * @full and @sort ought to be separated from @type (maybe)
Is there anything special about @type here compared to that provided by
att.typed?  Or maybe I should be asking, what is the difference?

> * att.naming is a silly name if all it does is give you @key, especially
> as some of its members are not by any stretch of the imagination names
> at all

If we rename it, is it really the right place for @nymKey?  I have no
suggestions for better names, but agree that one isn't really right.

> * att.personal ought to be a member of att.naming (definitely)

agreed.

-- 
Dr James Cummings, Oxford Text Archive, University of Oxford
James dot Cummings at oucs dot ox dot ac dot uk