Hi,
Jenkins is back to normal. I’ve undone the changes in <pc> for the moment.
But my question from my previous email still remains. Are there any thoughts on that?
Best,
Martina
Hi all,
The reason is that there is an ambiguous content model. <sense> and <re> both already use model.phrase, which has <pc> provided by model.segLike (thanks to James and Peter for helping me with this).
Eg. the content model for <sense> is
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<classRef key="model.gLike"/>
<elementRef key="sense"/>
<classRef key="model.phrase"/>
<classRef key="model.global"/>
</alternate>
</content>
I think the content model for <entry> should be (see addition in bold):
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<textNode/>
<elementRef key="hom" />
<elementRef key="sense" />
<elementRef key="pc" />
<classRef key="model.global"/>
<classRef key="model.ptrLike"/>
</alternate>
</content>
And for <hom> this should be (see addition in bold):
<content>
<alternate minOccurs="0"
maxOccurs="unbounded">
<elementRef key="sense" />
<elementRef key="pc" />
<classRef key="model.global"/>
</alternate>
</content>
And for <pc>:
delete <memberOf key=”model.entryPart.top” /> which I added today and which caused the problem.
Jenkins didn’t complain when I added <memberOf key=”model.entryPart.top” /> to <lbl>, so I wouldn’t change that.
My question is now – is that the way to go or is there a better way?
Best,
Martina
Mag. Dr. Martina Scholger
Zentrum für Informationsmodellierung
Austrian Centre for Digital Humanities
Universität Graz
A-8010 Graz | Elisabethstraße 59/III
+43 316 380 2291