Hi Mark, Thank you for your feedback! Jing has an option for Relax NG validation that we expose in Options->Preferences -- XML / XML Parser / RELAX NG [ ] Check feasibly valid that does not mark anymore as validation errors the missing elements or attributes - in this mode a document is considered feasibly valid if all it takes to make it full valid is to add content, elements or attributes to it. Such a validation mode is useful indeed during authoring. AFAIK there is no similar support for XML Schema or DTDs. However, we do intercept all errors reported by Xerces to update the location information - oXygen changes the location information for many errors from the end of a start tag to the actual location of an attribute or of an attribute value the error actually refers to - so it may be possible to identify errors that refer to missing required content and change them to warnings, thus getting yellow markers instead of red markers, or remove them completely and getting a similar behavior with the check feasibly valid option from the Relax NG validation. This probably needs to be controlled by an option, because a validate action that returns only warnings is considered a successful validation, so the user should be aware that he decided to ignore some type of errors. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 4/26/13 10:15 PM, Mark Baker wrote:
I’m writing a book in DocBook. It is the first time I have used oXygen to write in a schema that I did not create myself, and I am therefore relying a lot more than I normally do on the cues that the editor gives me.
One of those cues are the validation errors. The problem is, they are all signaled with RED. That makes sense if you have entered something illegal, but most of the time they appear because you have begun to create a complex structure and that structure is currently incomplete. From an author’s point of view, that’s not an error, I just haven’t finished yet.
Where oXygen can generate the whole structure, it does, so no error is shown, but there are many cases where it can’t because what is required is one of one or more options. In these cases, the structured does not become legal until the author adds additional elements. The thing is, RED means stop, but the author, in this case should continue. RED means you did something wrong, but in these cases, the author simply hasn’t finished yet.
I find the editor is constantly slowing me down by throwing up these errors that I have to analyse each time to determine if I need to go on or if I need to back up. When I design a schema, I try to avoid creating these kinds of structures, for just this reason, but sometimes they cannot be avoided.
My question is, is there a way, and do folks think it is desirable, to present a different cue for incomplete structures than for erroneous ones. At minimum, use a different color, such as yellow, for incomplete. Ideally, find some way to indicate that the author is on the right track and needs to continue.
Thoughts?
Mark
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user