Give examples of @type on persName

XML text markup for ancient documents

Brought to you by: filosam, gabrielbodard, hcayless, paregorios, sdigiulio

#95 Give examples of @type on persName

Milestone: 9.6

Status: accepted

Owner: BODARD Gabriel

Labels: None

Priority: 5(medium)

Updated: 2023-06-15

Created: 2015-05-20

Creator: Pietro Maria Liuzzo

Private: No

more details requested for the use of @type in http://www.stoa.org/epidoc/gl/latest/idx-persnames.html

Discussion

BODARD Gabriel - 2015-12-08

The question was raised as to whether EpiDoc should be recommending "London" usage for persName and name--consensus is yes. We should revisit the guidelines to make it much more detailed and explicit. Suggestions are good because they help to encourage consistency (indexing in EFES will be more straightforward, for example); suggestions are also not obligatory, and more or less detail are both possible in individual cases. Further examples of Roman, Greek, Celtic and other types of names would all be useful.

(Linking to SNAP worth a mention?)

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2015-12-08

status: unread --> accepted

assigned_to: BODARD Gabriel

Priority: 3 --> 5(medium)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Pietro Maria Liuzzo - 2015-12-08

An example from Vernacular inscriptions project. They simply choose that there is no reason to distinguish at the moment and add @type. They simply mark names and persName and index those.

<persName><name>Branca</name> <name><w>d’</w><supplied reason="lost">Ur</supplied>so</name></persName>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2016-09-20

Group: future --> 8.23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simona Stoyanova - 2016-11-15

assigned_to: BODARD Gabriel --> Simona Stoyanova
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2016-11-16

summary: persName --> Give examples of @type on persName
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simona Stoyanova - 2017-01-17

The London usage of @type includes the values: attested, emperor, divine, consular, ruler, other; the distinction between 'ruler' and 'consular' being that we normally tag any local ruler/king mentioned in the text in any capacity as @type="ruler", and 'consular' is used only for consuls/archons/priests who are mentioned as part of the dating formula. It all depends on how we want to index the mentioned people and what we unltimatley want to do with them but that has been the categorisation used so far.

Now, 'consular' doesn't really apply to anything outside of Roman context, so Scott suggested changing it to 'eponymous'. (Also, it looks like only IRCyr uses it. IAph and IRT don't.)

Another option is to approach the concept differently, not as a type of person or of their name but as a person's role. So then we might have a reccommended list of values for @role instead of @type, which seems more rational for what these words signify in terms of their role in the text. For example:
@role=attestation
@role=political
@role=dating
@role=religious ("cult"?)
...

Thoughts?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Simona Stoyanova - 2017-03-07
  
  Gabby to write to Markup list with some history of past decisions and add current proposition.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Simona Stoyanova - 2017-03-07

status: accepted --> pending

assigned_to: Simona Stoyanova --> BODARD Gabriel

Group: 8.23 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2017-03-21

Group: future --> 8.24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2017-10-17

Group: 8.24 --> 9.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2017-12-04

status: pending --> accepted

Group: 9.0 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2018-04-17

Gabby will write to the Markup list summarising the London/USEP usage of persName and name, and ask if anyone objects to that becoming EpiDoc recommendation.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2019-01-22

Group: future --> 9.1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2019-10-15

Group: 9.1 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2019-10-15

Postponed until discussion on Markup.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2020-01-27

Discussion on Markup kicked off with an email at https://lsv.uky.edu/scripts/wa.exe?A2=MARKUP;9e906fd3.2001

Will report back if there is any useful consensus, and/or volunteers to help write the Guidelines.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2020-06-16

No objections. Gabby will implement in Guidelines.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2020-08-07

Group: future --> 9.2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2020-08-07

I intend to implement this in time for the next release. Assigning to milestone accordingly.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Scott Vanderbilt - 2020-10-20

Group: 9.2 --> future
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2022-01-18

Group: future --> 9.4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2023-06-15

Group: 9.4 --> 9.6
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.