[tei-council] Feature request 1933198: 'precision' element needed

[David Sewell]

I'm just back from France and catching up on things (took 3 days holiday
in Paris after the Council meeting).

As Tim Finney was quite involved in the discussions with this proposal
I've invited him to provide feedback on the SF ticket, but won't be
hearing from him before around midnight tonight London/central Europe
time as he's in Perth. Can we extend the deadline by a day in case he
raises any issues that we might want to consider?

David

On Wed, 8 Apr 2009, Arianna Ciula wrote:

> If I remember well today was the deadline the council gave itself in
> Lyon to express any doubt about this proposal. I think is well
> expressed and it makes a very good case for dates also recalled by the
> recent debate on TEI-L.
>
> So I am for it: green for me.
>
> Arianna
>
>
> ==
> Dr. Arianna Ciula
> Science Officer
>
> European Science Foundation
> Humanities Unit
> 1 quai Lezay Marnésia
> BP 90015
> F-67080 Strasbourg
> France
>
> Email: aciula at esf.org
> Tel: +33 (0) 388767104
>
>
>
> -----Original Message-----
> From: tei-council-bounces at lists.village.Virginia.EDU [mailto:tei-council-bounces at lists.village.Virginia.EDU] On Behalf Of Gabriel Bodard
> Sent: mardi 31 mars 2009 20:16
> To: TEI Council
> Subject: [tei-council] Feature request 1933198: 'precision' element needed
>
> Proposal:
>
> This FR proposed the creation of a new element, <precision/> for use in
> those cases where the precision of a date or dimension or other
> measurement is more complicated that can be expressed by the simple
> @precision attribute. (This is a direct parallel to the <certainty/>
> element, which handles cases that are too complicated for simple @cert.)
>
> This was first discussed by the group in Galway, and since taken further
> by James C. and myself, and the recommendation is as follows:
>
> (1) Creation of a new element, <precision/> (empty element);
>
> (2) element inherits global attributes and those from att.dimensions
> (@min, @max, @atLeast, @atMost are the essential ones);
>
> (3) Create a new attribute class (“att.qualifier” vel sim.) with the
> attributes @degree, @locus, @target (currently defined ad hoc for
> <certainty/>;
>
> (4) define new attribute @stdDeviation for <precision/>, with datatype
> numeric.
>
> Examples of usage:
>
> (A)
> <date xml:id=”d00001” notBefore=”0014” notAfter=”0064”>Within approx 50
> years of the death of Augustus</date>
> <precision target=”#d001” locus=”notAfter” degree=”low”/>
> <precision target=”#d001” locus=”notBefore” degree=”high”/>
>
> (B)
> John Smith (bishop <date xml:id=”d002” from=”1753”
> to=”1795”>1753-c.1795</date>)
> <precision target=”#d002” locus=”to” degree=”low”/>
>
> (C)
> Each column has a minimum of 10 characters width and a maximum of c.25
> (I know this is clumsy, but people do say this sort of thing):
> <measure type=”count” min=”10” max=”25” xml:id=”m001”>10-c.25</measure>
> <precision target=”#m001” locus=”max” degree=”low”/>
>
> (The dates are the really compelling use-case for this... partly because
> you used to be able to do something similar in Master with @notBefore,
> @notAfter, and @exact=’both|notAfter|notBefore|none’.)
>
> ((Someone more comfortable with statistics than me can probably come up
> with an example using @stdDeviation. Possibly James, who I think
> convinced me when we discussed this.))
>
> Let me know if any questions about this arise--I may be online part of
> Thursday on the train.
>
> Best,
>
> Gabby
>
>

-- 
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: dsewell at virginia.edu   Tel: +1 434 924 9973
Web: http://rotunda.upress.virginia.edu/