Hi, Martin --
First, I think your main point (of "cannot" being incongruous with
role="nonfatal") is a good one, worthy of a ticket.
But keep in mind when you look for these things, though, that some
are generated at build time. So if you look in p5.xml you find only
11 @roles (9 "nonfatal", 2 "warning"). But if you look in
Exemplars/tei_all.isosch you find there are 42 @roles (15 "nonfatal",
2 "warning", and 25 "error", out of a total of 99 <assert>s and
> Sorry if I misunderstood you Syd. There are currently 74 Schematron
> assertions and reports in the P5 source, of which only 9 have
> @role='nonfatal'; 4 of those relate to deprecations, so they are
> certainly advisory, but others are rather strange:
> <constraintSpec ident="att-datable-w3c-when" scheme="isoschematron">
> <sch:rule context="tei:*[@when]">
> <sch:report test="@notBefore|@notAfter|@from|@to"
> role="nonfatal">The @when attribute cannot be used with any other
> att.datable.w3c attributes.</sch:report>
> The report says "cannot be used", which is pretty categorical; I don't
> see how this could be both accurate ("cannot") and nonfatal/advisory.
> All five of the "nonfatal" rules which are not related to deprecation
> explicitly use the word "cannot". This just seems wrong to me. If
> they're really advisory, they should use different terminology, surely.