I have been in this game for a looong time, and I have experienced first hand the emergence and maturation of the modern UX discipline as it applies to digital experiences.We (the UX community) have fought hard to prove the value of UX — to product management, engineering and businesses executives.Note: The material discussed in this section also applies to validating when using the SAX parser.
One of the things my teams are starting to consider is the idea of risk vs reward. I think that we need to shift the way we think about design validation.Whenever we feel the urge to validate with users, we first think about the amount of risk represented by the design at hand. The idea of validation is often flawed because it can be about affirmation rather than what it really should be, which is to try and Invalidate our ideas.Anne Hjortshoj — one of my very smart colleagues — always says…“UX is all about reducing risk, and revealing value.” We want to help our product teams ensure we are choosing the right problems to solve, and then make sure we are solving them in the right way.You also set a factory attribute to specify the parser language to use.
(For SAX parsing, on the other hand, you set a property on the parser generated by the factory.) Now that the program is ready to validate with an XML Schema definition, it is necessary only to ensure that the XML document is associated with (at least) one.
The (if one has been defined) to find a local copy of the schema.
If the schema definition does not define a target namespace, then it applies to the default (unnamed, or null) namespace.
Now that many of us have the power to do what we want…
we need to make sure we are doing the right things and not leaning too much on validation to the point of becoming counter productive.
We have have convinced those groups that we can reduce the risk associated with projects if only we can spend time up front validating our designs and our assumptions and we tend to do that by putting paper sketches, wireframes and prototypes in front of real users to understand whether our solutions are meeting their needs.