I think their thinking was that if the attribute is not supplied, it should be assumed to take the default value, but that if the default value was not appropriate then an attribute must be supplied. Muddled, I agree, but that's not really the point here. Making it generate a warning rather than an error would be highly desirable. On 04/08/15 21:05, Syd Bauman wrote:
Inasmuch as there is such a thing as a "warning" in Schematron, we can certainly change the constraint (to use flag="warning"). But how on earth does it make sense to specify a default value (i.e., the value to assume when the attribute is not there) on a required attribute (i.e., one that will always be there)?
Well, Mr Smartypants Schematron, it may not make sense to you, but it did to the folks who defined this ODD, and making their ODD invalid is not going to win you any friends. Could we at least change this to a warning, so that the P5 test suite can run to completion?