Re: [tei-council] draft post to TEI-L re 299

Hi Syd— I wonder if <time> is likely to raise questions, and whether people might want a little more explanation: Can we provide a better explanation of why this set of attributes isn’t appropriate for time? (I think we must have been considering <time> as analogous to <date>, but in the Guidelines we do use it to express duration which certainly seems a matter of measurement, so I’m now puzzling over why we were so confident this set of attributes shouldn’t apply to <time>.) Also, just an annoying sidenote, but <persona> wasn’t on the list we reviewed on the ticket, though I don’t think it should be a problem to remove it. Perhaps that just merits a small sidenote in the explanation, as in: <persona> was not on the list of elements we originally discussed but discovered as Council investigated the issue. Cheers from back home in Greensburg! Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu mailto:ebb8@pitt.edu Development site: http://newtfire.org http://newtfire.org/

On Nov 19, 2017, at 7:47 PM, Syd Bauman wrote:

Here is draft language for your review before it is posted to TEI-L. Comments welcome.

--------- The TEI Technical Council plans to remove the following attributes:

atLeast=, atMost=, confidence=, extent=, max=, min=, precision=, quantity=, scope=, and unit=

from the following elements:

<affiliation>, <am>, <birth>, <climate>, <corr>, <date>, <death>, <education>, <event>, <expan>, <faith>, <floruit>, <geogName>, <langKnowledge>, <langKnown>, <location>, <name>, <nationality>, <occupation>, <org>, <orgName>, <origDate>, <origPlace>, <origin>, <persName>, <person>, <persona>, <place>, <placeName>, <reg>, <relation>, <residence>, <sex>, <socecStatus>, <terrain>, and <time>

These attributes (which are used for expressing a measurement or statistical information about a set) should never have been on these elements in the first place. Thus their presence is considered a corrigible error, and their removal is scheduled to take place at the next release (likely in Jan or Feb 2018) without a 2-year "deprecation" period, during which use of these attributes on these elements would cause a warning to occur.

If anyone is actually using one of these attributes on one of these elements, and its removal in future releases might be a hardship, please let us know by posting here or to the issue (https://github.com/TEIC/TEI/issues/299).

Thank you. --------- -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived