[tei-council] DCR alignment inside ODD

[Piotr Bański]

I'm working on the ISO DCR / ISOcat issues.[1] Got stuck at the point of
adding the relevant pieces of text to the Guidelines.

The enlightened way to align grammatical categories with the values of
the DCR is to put the appropriate references into the ODD, and I guess
<equiv> is the ideal place for that.

I imagine, and please correct me if I am wrong, that for elements such
as <pos>, this action may be trivial:

<elementSpec ident="pos" mode="change">
   <equiv dcr:datcat="http://www.isocat.org/datcat/DC-1345"/>
</elementSpec>

(I'm skipping several issues to try to focus on the main one [2])

The above makes it possible for us to happily realize that whenever we
do e.g.

<gramGrp><pos>...</pos></gramGrp>

all the machines in the world may know that by <pos>, we mean
http://www.isocat.org/datcat/DC-1345 .

However, there is also the content of <pos> to be handled, and it is not
so obvious to me how to represent this in the ODD. Intuitively, I'm
thinking of

<elementSpec>
...
<content>
 {list of values with their DCR references}
</content>
...

except I can't pull this off in the TEI -- I need to use RNG (and it's
not so obvious to me right now, how exactly). But this is not the idea
of the exercise, is it: the idea was to make the creation of DCR
references available to an average hum... well, say, electronic
lexicographer or corpus linguist. Actually, to encourage the creation of
such references.

Do I misunderstand something?
(at this point, I'm adding a CC to Laurent, and will relay his reply if
he finds the time to provide any)

In Zadar, I presented a solution whereby I encoded this sort of
information inside the header. I was told no no no, it belongs in the
ODD. Now I'm wondering if we're not back to the header, after all.[3]

I'll be grateful for any hints you can offer.

Thanks and good night,

  Piotr


[1]:
https://sourceforge.net/tracker/index.php?func=detail&aid=3432520&group_id=106328&atid=644065

[2]: One such issue is: but do we modify the TEI Spec for <pos> thus or
do we let each encoder do it on their own? My answer would be the
latter, because there is no single reference for POS.

[3]: And in some cases, I actually still firmly believe that the header
is the only place to do that efficiently; I may actually have a topic
for the next TEI-MM...