[tei-council] Requests 1925125 and 1933198

[Gabriel Bodard]

Thanks for this useful summary, James.

I have two minor questions for Council:

(1) Is there some way to embed one attribute class within another? I am 
thinking of the (provisionally named) att.ranging class (@min, @max, 
@atLeast, @atMost) to which *all* elements that are members of 
att.dimensions should be added, but which should also be able to apply 
to elements that do not need @quantity, @unit, @precision (such as the 
new <precision/> element). To put the question another way, do we just 
have to remember to make all members of att.dimensions also members of 
att.ranging, or can att.dimensions itself be made a member of att.ranging?

(2) I can come up with some examples using <precision/> and/or 
<certainty/> to qualify dates of incriptions. Does anyone have any other 
examples to offer? Does this proposal need more explanation?

Cheers,

Gabby

James Cummings a écrit :
> While discussing feature request tickets number 1721365, and especially
> 1925125 and 1933198, Gabby (with stupid questions from me) fleshed out
> some proposals on some new attribute classes and a new element.  Since
> they are all related I cut-and-paste with minor edits from the feature
> requests so that Council can decide these.
> 
> The proposals are:
> 
> Request 1925125
> (1) we need to define the four new attributes, (@min, @max, at atLeast,
> @atMost) in a new attribute class, as previously discussed, perhaps
> "att.ranging" or similar. (The <precision> element mentioned below will
> then be a member of att.ranging but not att.dimensions.)
> 
> (2) the existing @precision attribute should be defined within
> att.dimensions __but **not** att.editLike or att.ranging__. It is really
> a bug that many of the members of att.editLike currently have @precision.
> 
> 
> Request 1933198
> (1) We should create a new element, <precision/> basically in parallel
> with <certainty/> but recording precision.
> 
> (2) This element is a member of "att.ranging" (newly defined class, see
> #1925125; contains @min, @max, @atLeast, @atMost)
> 
> (3) This element is also a member of a newly defined class
> (?"att.qualifier") containing @degree, @locus, @target (to which
> <certainty/> will now also belong)
> 
> (4) define one new attribute, @stdDeviation, for recording the standard
> deviation of a number, range, or approximation. (data.numeric is
> probably appropriate for this attribute, but prose at least should
> indicate that value should be positive.)
> 
> If council could have a quick look at these tickets and comment here or
> on SF then these could maybe be upgraded to GREEN.
> 
> Gabby: Did I forget to mention anything? Would you like to explain more?
> 
> -James
>

-- 
Dr Gabriel BODARD
(Epigrapher & Digital Classicist)

Centre for Computing in the Humanities
King's College London
26-29 Drury Lane
London WC2B 5RL

Email: gabriel.bodard at kcl.ac.uk
Tel: +44 (0)20 7848 1388
Fax: +44 (0)20 7848 2980

http://www.digitalclassicist.org/
http://www.currentepigraphy.org/