#398 <name> should be a member of att.datable

AMBER
closed-fixed
Martin Holmes
5
2014-07-31
2012-04-20
Martin Holmes
No

This issue arose in the following short thread on TEI-L:

http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind1204&L=tei-l&F=&S=&P=47703

Since <persName>, <orgName> and <placeName> are all members of att.datable, it seems odd that the more generic <name> is not, and the discussion provides one use-case where this would be useful.

Discussion

  • Lou Burnard
    Lou Burnard
    2012-09-16

    I suppose the thinking is that the datability of persName etc has to do with the application of the name to some entity (person, place etc.) -- its the date this thing was called whatever. Whereas the generic <name> isn't necessarily applied to anything. Fairly weak as an argument, I agree.

     
  • Lou Burnard
    Lou Burnard
    2012-09-16

    • milestone: --> AMBER
     
  • since the Guidelines state that <persName> may be regarded "synonymous" with <name type="person">, <placeName> may be regarded as "an abbreviation for" <name type="place"> , and <orgName> "equivalent to" <name type="org"> I think we must allow <name> to also be a member of att.datable (or else clearly explain and justify this difference in the prose.

     
  • Martin Holmes
    Martin Holmes
    2013-01-07

    • status: open --> closed-fixed
     
  • Martin Holmes
    Martin Holmes
    2013-01-07

    This seems to have been completed already, I think by James in October. Setting to Accepted and closing the ticket.