-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to properly delete a <constraintSpec>
#541
Comments
With @sydb @HelenaSabel and @npcole : We found that if we change line 2018 or odd2odd.xsl from:
to:
we get a change in behaviour -- processing does find the constraintSpecs -- but the original problem is not solved by this alone. |
We (the Stylesheets group) have just discovered the problem (thanks to @HelenaSabel :-) — the key
So we suggest those 13 just get re-named, so we can use just |
Blocked until the discussion on TEI ticket 2223 is closed. |
See TEI issue 2223 and the corresponding PR. Hmmm … is it better to write that as See /TEIC/TEI/issues/2223 and the corresponding PR, /TEIC/TEI/pull/2224. ? The former looks nicer, but the latter gives you pop-ups. |
One would think this would be easy. Just
<constraintSpec module="[module]" ident="[ident]" sceme="schematron" mode="delete"/>
should do it, eh? A bit weird that@scheme
is required, but no big deal.No such luck. The big deal is that it does not work. Nor does most any other method I tried. According to my little test ODD (which is attached to this ticket with an extra .txt extension), one can delete a
<constraintSpec>
from a class by specifying the deletion or change (to an empty<constraintSpec>
or<constraint>
) in a<classSpec mode="change">
; and one can delete a<constraintSpec>
from an element only if"replace"
ed with an empty one.I do not think this is the right state of affairs. I think that the whole point of being in att.identifiable is to be deleted or over-ridden.
The text was updated successfully, but these errors were encountered: