Consider:

[error] Parse Error: Term('%CR;%LF;') - element.ContentType: Delimiter not found!

Schema context: element.ContentType Location line 16 column 99 in file:/C:/…/ContentType.xsd

Data location was preceding byte 23

UTF-8 text starting at byte 16 is: (age/jpg/png

)

Data (hex) starting at byte 16 is: (0x6167652F6A70672F706E670D0A)

The information is there if you start at byte 16, and count over to byte 23 you find /png.

But that is way too indirect.

Knowing that the delimiter was not found is helpful, as it knowing that it was looking for %CR;%LF; for a terminator. But I think this error could be improved by also telling me what value was found. Perhaps the error message could look a bit more like this:

[parsing error] While processing the ContentType element, the terminator ‘%CR;%LF;’ was expected,

but the value “/png” was found instead.

Location: line 16 column 99 in file:/C:/…/ContentType.xsd