Closed jamescummings closed 3 years ago
Jenkins can be told to ignore it, but that should only happen if we're sure it's the right thing to do.
I'm not sure it is, hence assigning @sydb since I think the XSLT producing this schematron is his.
F2F: We think this might not be an issue any more, but @sydb will check more closely.
No warnings noticed in latest TEI-dev build on Jenkins. (Given that TEI_to_odd4odds is now TEI-to-tei_customization …)
When Jenkins builds TEI-dev it gives a couple of warnings:
Which, if I've followed them back correctly, refer to the schematron rule surrounding
@xml:id
needing to be unique in the document for the tei_customization ODD. This is generated by https://github.com/TEIC/TEI/blob/dev/P5/Utilities/TEI_to_odd4odds.xslt#L1397 and it is complaining because of its lack of specific context.Is there: a) A way to fix this so the schematron doesn't complain? b) A way for Jenkins to be told to ignore it? c) A real need for this? Doesn't any normal xml schema validation also do xml:id uniqueness testing?