Can we go ahead and do this please? I’m getting bored with the build failing constantly. The reason it’s throwing an error is because what was once enforced with Schematron (there being only one child node for <f>) is now enforced by the content model. The test expects the Schematron to fail, but the content model to be valid. But the content model is no longer valid. I don’t think we really need to test that invalid content is invalid, so I’d say remove the tests. They were testing Schematron that’s now gone. Hugh
On May 21, 2016, at 18:16 , Syd Bauman
wrote: The Jenkins build of P5 is failing because of the following test in .../P5/Test/testbasic.xml:
<fLib xmlns="http://www.tei-c.org/ns/1.0"> <f name="xxx">A feature may have untyped content</f> <f name="yyy"> <string>or typed</string> </f> <f name="notgood"> <string>multiple types</string> <symbol value="doubleplusungood"/> </f> <f name="alsonotgood">mixed content <symbol value="doubleplusungood"/> </f> </fLib>
I think these are tests that are *supposed* to fail, and thus should be in the detest/ suite, not here in testbasic.xml.
1) Can someone (Martin?) affirm for me that testbasic.xml is supposed to be valid?
2) Can someone (Laurent?, Lou?, Piotr?) affirm for me that an <f> is supposed to have at most 1 child element (from class model.featureVal, i.e. one of <fs>, <vColl>, <vMerge>, <vNot>, <binary>, <default>, <numeric>, <string>, <symbol>, <vAlt>, or <vLabel>)?
If I've got this right, I'll just move these tests out of testbasic, and we'll be up and running again. -- 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