EpiDoc: Epigraphic Documents in TEI XML / Request Features / #126 Consider and document EpiDoc customization of unclear

#126 Consider and document EpiDoc customization of unclear

Milestone: 9.0

Status: done

Owner: Charlotte Tupman

Labels: guidelines (82) odd (3)

Priority: 5(medium)

Updated: 2018-02-20

Created: 2017-04-18

Creator: BODARD Gabriel

Private: No

The EpiDoc customization of <unclear>, which may only contain character data and <g> (since it closely reflects Leiden underdot), is a very tight subset of the semantics of tei:unclear, and therefore ought to be clearly documented as such, both in the Guidelines and the ODD.

Discussion

Hugh A. Cayless - 2017-05-16

EDAG agrees EpiDoc's use of <unclear> makes sense and agrees it should be more explicitly documented. <unclear> doesn't map perfectly to epigraphic practice in the use of underdot, but our use of the element is unambiguous.

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:

Scott DiGiulio - 2017-11-21

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

Charlotte Tupman - 2017-12-03

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

Charlotte Tupman - 2017-12-04

Added further explanatory prose to trans-ambiguous.xml on the default TEI usage of <unclear>, and emphasised EpiDoc's restricted usage. Also added prose on optional attribute. Not yet added further details to ODD.

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

Charlotte Tupman - 2017-12-04

Now added description to ODD.

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

Charlotte Tupman - 2017-12-04

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

Charlotte Tupman - 2017-12-04

status: done --> needs-feedback
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Charlotte Tupman - 2017-12-04

This is now ready for review.

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

BODARD Gabriel - 2018-02-20

status: needs-feedback --> done
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

BODARD Gabriel - 2018-02-20

This all looks fine to EDAG. Closing ticket as done for release 9.0.

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

Scott DiGiulio - 2018-02-20

Made slight tweaks, including removing the allowable TEI elements for clarity, as discussed at the Feb. 20 EDAG meeting, with commit r2721.

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

Consider and document EpiDoc customization of unclear

XML text markup for ancient documents

Group

Searches

Help

#126 Consider and document EpiDoc customization of unclear

Discussion