This bug report is a follow-up on the discussion found in https://listserv.brown.edu/archives/cgi-bin/wa?A2=tei-l;fc2bf4f.1307.
Bug #585 contains a proposal to deal with fuzzy dates:
<state from="1382" to="1477"> <precision match="@from" atLeast="1382" atMost="1430"/> <precision match="@to" atLeast="1444" atMost="1477"/> <p>Catholicos-Patriarch of the Church of the East.</p> </state>
That report only covers the addition of att.ranging
to precision
. But in addition to implement that proposal, it is also necessary to allow state
to contain precision
. In order to cover all possible uses of state-like elements, I propose to add precision
to all of model.orgStateLike
, model.persStateLike
and model.placeStateLike
.
Pending council agreement, making green and assigning to Peter Stadler at F2F Raleigh 2014-11-17
Council agrees.
The request is to add "precision to all of model.orgStateLike, model.persStateLike and model.placeStateLike". The elements in question are:
The most already allow for
precision
viamacro.phraseSeq.limited
ormacro.phraseSeq
. The elements with a more complex content model are:My thoughts so far:
model.headLike
. Shouldprecision
be added before?precision
be added before the choice as an option?precision
be added as a possible first child?precision
rather bemodel.certLike
to also allow for <certainty> and <respons>?Should't the path of @match be different? According to http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.scoping.html the context (node I hope) in which the @match is evaluated is defined to be the element bearing this attribute (not implicitly its parent). I haven't found a hint in tei:precision that this is in this case different.
Is this just a flaw in this example or is this a general issue with the interpretation of "context"?
According to the example and note on the page you cite, the “context” is
indeed the parent element, unless the @target attribute specifies
something different:
We are talking about two contexts.
1 the context referring to the interpretation of tei:precision. That
appears to be clearly the parent element of tei:precision. I completely
agree with you on that.
2 the context the @match, in the meaning defined by xpath, is interpreted
with. That was wrong and does not align to the attribute's definition.
As only the latter is problematic, and wrongly used at other places in the
guidelines' examples, Martin moved this to a separate ticket. A clearer
wording might help, though
Am 31.05.2015 11:15 schrieb "Frederik" freedo@users.sf.net:
Related
Feature Requests: #518
There was a definite confusion between the definition of the attribute:
supplies an arbitrary XPath expression using the syntax defined in Kay (ed.) (2007) which identifies a set of nodes, selected within the context identified by the target attribute if this is supplied, or within the context of the element bearing this attribute if it is not.
which says it's the element bearing the @match attribute, and the remark:
he expression of certainty applies to the nodeset identified by the
value of the target attribute, possibly modified additionally by the
value of the match attribute. If neither attribute is present, the
expression of certainty applies to the context of the certainty
element itself, i.e. its parent element.
We noticed this yesterday, and I'll submit a bug for it if I haven't done so already -- can't remember. :-)
New ticket here:
https://sourceforge.net/p/tei/bugs/761/
This is a bit of a mess.
implemented in [r13242] without complaints by Mr. Jenkins; tested briefly (precision in state and climate); closing!