"John L. Clark" wrote: > In many cases, XMLmind XML Editor (XXE) provides validation error > messages with enough detail that a user can determine how to correct > the problem. For example, if you open an XHTML document with an `a` > tag in the `body`, XXE will correctly complain that 'element cannot > contain element "a" [cvc-complex-type]'. In some cases, though, the > error messages do not provide enough information. I ask that where > possible, some types of validation error messages provide more detail > as to the nature of the problem. I list two examples below. > > In one case, a schema restricts a particular element to only have > content of type `xsd:date`. If a user enters an incorrect date, XXE > will report the problem as 'bad character content for element'. I ask > that this be modified to something like 'bad character content for > element; expected xsd:date', possibly including a hyperlink to the XML > Schema Datatypes definition for `xsd:date`. If XXE wanted to take > extra steps, it could even provide a summary of the necessary lexical > format of the data. > > Another general case exists when an element is missing a required > child element. In such a case, XXE will report the problem as > 'required elements missing'. It would be very useful if a list of the > required elements could be included in this message.
We are well aware of these shortcomings and we haven't found a good way to improve the situation yet. Also, please remember that our goal is to be good at creating valid content, and not to be good at fixing invalid content. That's why, for example, we intend to implement a date/time picker (usable from the Attribute tool -- the icon which is at the right of the Value field -- or from a date-field() created using CSS generated content) in the near future (probably next version).
