Hi! Wrapping up my tickets, I came across two issues which would require some input: a) https://github.com/TEIC/TEI/issues/1702, I think the proposal on making <pc> and <lbl> a member of model.entryPart.top for encoding print dictionaries looks reasonable to me. Could you take a look at this and tell me your thoughts? b) https://github.com/TEIC/TEI/issues/1420 I didn't manage to adjust the content model of <valItem> to reflect that the <remarks> element is only allowed if the <desc> element is present as well. Can anyone help me with that? This is the current content model: <content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.descLike"/> <classRef key="model.glossLike"/> </alternate> <!-- to be added : <elementRef key="remarks" minOccurs="0" maxOccurs="unbounded"> --> <elementRef key="paramList" minOccurs="0" maxOccurs="1"/> </sequence> </content> Best, Martina Martina Scholger Centre for Information Modelling Austrian Centre for Digital Humanities University of Graz Elisabethstraße 59/III 8010 Graz
1 seems reasonable and will only affect dictionary encoding. We discussed, but I don't remember the outcome at a F2F. November minutes imply that it was finished on the morning of Nov 18 after not being completed by the group(s) to which it was assigned. --elli [Elli Mylonas Senior Digital Humanities Librarian and Center for Digital Scholarship University Library Brown University library.brown.edu/cds] On Wed, Jan 17, 2018 at 4:21 PM, Scholger, Martina ( martina.scholger@uni-graz.at) <martina.scholger@uni-graz.at> wrote:
Hi!
Wrapping up my tickets, I came across two issues which would require some input:
a) https://github.com/TEIC/TEI/issues/1702, I think the proposal on making <pc> and <lbl> a member of model.entryPart.top for encoding print dictionaries looks reasonable to me. Could you take a look at this and tell me your thoughts?
b) https://github.com/TEIC/TEI/issues/1420 I didn't manage to adjust the content model of <valItem> to reflect that the <remarks> element is only allowed if the <desc> element is present as well. Can anyone help me with that? This is the current content model:
<content> <sequence> <alternate minOccurs="0" maxOccurs="unbounded"> <classRef key="model.descLike"/> <classRef key="model.glossLike"/> </alternate> <!-- to be added : <elementRef key="remarks" minOccurs="0" maxOccurs="unbounded"> --> <elementRef key="paramList" minOccurs="0" maxOccurs="1"/> </sequence> </content>
Best, Martina
Martina Scholger Centre for Information Modelling Austrian Centre for Digital Humanities University of Graz Elisabethstraße 59/III 8010 Graz
-- 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
b) https://github.com/TEIC/TEI/issues/1420 I didn't manage to adjust the content model of <valItem> to reflect that the <remarks> element is only allowed if the <desc> element is present as well. Can anyone help me with that?
I think the following would do the trick for RELAX NG, but will be ambiguous in DTD-land. Will be working on re-factoring it unambiguously soon, but if anyone else wants to take a stab, please feel free. --------- | <content> | <sequence> | <alternate minOccurs="0" maxOccurs="1"> | <sequence> | <!-- with <desc> and optional <remarks> --> | <classRef key="model.glossLike" minOccurs="0" maxOccurs="unbounded"/> | <classRef key="model.descLike" minOccurs="1" maxOccurs="unbounded"/> | <sequence minOccurs="0" maxOccurs="unbounded"> | <classRef key="model.glossLike" minOccurs="1" maxOccurs="unbounded"/> | <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <elementRef key="remarks" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <sequence> | <!-- with optional <desc>, no <remarks> --> | <alternate minOccurs="0" maxOccurs="unbounded"> | <classRef key="model.descLike"/> | <classRef key="model.glossLike"/> | </alternate> | </sequence> | </alternate> | <elementRef key="paramList" minOccurs="0" maxOccurs="1"/> | </sequence> | </content> --------- If we can't get this working, would could of course resort to: --------- | <constraintSpec ident="no-remarks-without-desc" scheme="schematron"> | <constraint> | <sch:rule context="tei:valItem[tei:remarks]"> | <sch:assert test="tei:desc">A value item should only have a remarks section if it also has a description</sch:assert> | </sch:rule> | </constraint> | </constraintSpec> --------- :-)
Got it: --------- | <!-- Do not allow <remarks> unless <desc> is present: --> | <!-- ( gloss*, ( desc+, ( gloss, desc* )*, remarks* )?, paramList? ) --> | <!-- | Note that the optional clause $2 that contains the only reference | to <remarks> has a required <desc>. | --> | <content> | <sequence> | <classRef key="model.glossLike" minOccurs="0" maxOccurs="unbounded"/> | <sequence minOccurs="0"> | <classRef key="model.descLike" minOccurs="1" maxOccurs="unbounded"/> | <sequence minOccurs="0" maxOccurs="unbounded"> | <classRef key="model.glossLike" minOccurs="1" maxOccurs="1"/> | <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <elementRef key="remarks" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <elementRef key="paramList" minOccurs="0" maxOccurs="1"/> | </sequence> | </content> --------- It works when I build locally (although lots of other things go wrong). Try it, Martina, and see what Mr. Jenkins thinks.
I think the following would do the trick for RELAX NG, but will be ambiguous in DTD-land. Will be working on re-factoring it unambiguously soon, but if anyone else wants to take a stab, please feel free. --------- | <content> | <sequence> | <alternate minOccurs="0" maxOccurs="1"> | <sequence> | <!-- with <desc> and optional <remarks> --> | <classRef key="model.glossLike" minOccurs="0" maxOccurs="unbounded"/> | <classRef key="model.descLike" minOccurs="1" maxOccurs="unbounded"/> | <sequence minOccurs="0" maxOccurs="unbounded"> | <classRef key="model.glossLike" minOccurs="1" maxOccurs="unbounded"/> | <classRef key="model.descLike" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <elementRef key="remarks" minOccurs="0" maxOccurs="unbounded"/> | </sequence> | <sequence> | <!-- with optional <desc>, no <remarks> --> | <alternate minOccurs="0" maxOccurs="unbounded"> | <classRef key="model.descLike"/> | <classRef key="model.glossLike"/> | </alternate> | </sequence> | </alternate> | <elementRef key="paramList" minOccurs="0" maxOccurs="1"/> | </sequence> | </content> ---------
If we can't get this working, would could of course resort to:
--------- | <constraintSpec ident="no-remarks-without-desc" scheme="schematron"> | <constraint> | <sch:rule context="tei:valItem[tei:remarks]"> | <sch:assert test="tei:desc">A value item should only have a remarks section if it also has a description</sch:assert> | </sch:rule> | </constraint> | </constraintSpec> --------- :-)
It works when I build locally (although lots of other things go wrong). Try it, Martina, and see what Mr. Jenkins thinks.
That seems silly ... Martina won't be awake for another few hours. May as well see what Mr. Jenkins thinks now. I've just checked in that new content model at 4bd02ee.
Thank you, Syd! The local test looks good to me (also the DTD). -----Ursprüngliche Nachricht----- Von: tei-council-bounces@lists.tei-c.org [mailto:tei-council-bounces@lists.tei-c.org] Im Auftrag von Syd Bauman Gesendet: Donnerstag, 18. Jänner 2018 04:22 An: tei-council@lists.tei-c.org Betreff: Re: [tei-council] Comments needed
It works when I build locally (although lots of other things go wrong). Try it, Martina, and see what Mr. Jenkins thinks.
That seems silly ... Martina won't be awake for another few hours. May as well see what Mr. Jenkins thinks now. I've just checked in that new content model at 4bd02ee. -- 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
participants (3)
-
Mylonas, Elli -
Scholger, Martina (martina.scholger＠uni-graz.at) -
Syd Bauman