Validating xsd file
Of those languages, XDR and SOX continued to be used and supported for a while after XML Schema was published.
A number of Microsoft products supported XDR until the release of MSXML 6.0 (which dropped XDR in favor of XML Schema) in December 2006. supported its SOX schema language until declaring bankruptcy in late 2004.
Schema documents are organized by namespace: all the named schema components belong to a target namespace, and the target namespace is a property of the schema document as a whole.
A schema document may include other schema documents for the same namespace, and may import schema documents for a different namespace.
However, unlike most other schema languages, XSD was also designed with the intent that determination of a document's validity would produce a collection of information adhering to specific data types.
Such a post-validation infoset can be useful in the development of XML document processing software. It was the first separate schema language for XML to achieve Recommendation status by the W3C.
These components are usually created by processing a collection of schema documents, which contain the source language definitions of these components.
In popular usage, however, a schema document is often referred to as a schema.
(The latter mechanism requires the client invoking validation to trust the document sufficiently to know that it is being validated against the correct schema.
In its appendix of references, the XSD specification acknowledges the influence of DTDs and other early XML schema efforts such as DDML, SOX, XML-Data, and XDR.
It has adopted features from each of these proposals but is also a compromise among them.
In XSD 1.1, a complex type may be constrained by assertions — XPath 2.0 expressions evaluated against the content that must evaluate to true.
After XML Schema-based validation, it is possible to express an XML document's structure and content in terms of the data model that was implicit during validation.