A Introduction Of XML Schema

Hi there, my name is Michael Dupre. You are welcome to my '5 minute XML' guides the place where I offer you daily byte size tutorials.

Our present-day topic is designed for folks who happen to be new to XML.

An XML schema definition language serves as a apparatus for generating schemas. A schema is a file suitable for defining the structure, content along with semantics of one's XML document.

Numerous schema definition languages are available for use. The DTD (or Document Type Definition) language appeared to be popular via the XML community but has generally been outmoded by XSD (or XML Schema Definition) language.

XSD is recommended and even looked after by means of the web standards body, W3C. Not like DTD, XSD is actually itself written in XML (accordingly, extensible), provides support for data-types plus namespaces and is generally a lot more extensive.

An XML schema identifies the elements and also attributes that go into your XML file, their data-types and default values (if any). It defines which elements are child elements, the order and volume of them.

Additionally it specifies whether an element is in fact empty or might include text. An XML file is not needed to have a schema declaration but when one is included it will likely be used to validate the XML document against all of the above criteria.

Schemas are created from a number of organizations and professional bodies to represent a common method with regard to data interchange within a given industry, profession or other specialist domain.

Schemas are created with the intention that they will realise wide spread adoption by their community and then in so doing, improve marketplace cohesion. I have listed a very few samples from a persistantly escalating volume of schemas available today:

•    RSS (Really Simple Syndication) intended for news syndication,

•    FpML (Financial products Mark-up language)

and FIXML (Financial Information eXchange Markup Language) for the financial markets,

•    XBRL (Extensible Business Reporting Language) for the Business markets,

•    SDMX-ML (Statistical Data and Metadata eXchange Markup Language) for the purpose of sharing statistical data.

•    RDF (Resource Description Language) for Metadata,

•    MathML (Mathematical mark-up language) for specialised mathematicians and

•    SVG (Scalable Vector Graphics) language for vector images.

A substantial repository of schemas can be obtained from this XML Standards Library.

XML Editors

Being familiar with all the intricacies of XSD is really a struggle but quite a few XML editors (of different functionality) are around to enable you to simplify the job of constructing XML documents and schemas.

An <a href="http://www.liquid-technologies.com/xml-editor.aspx">xml editor</a> may usually provide code completion and even assist with syntax whilst in design process. It has to also be able to get a sample XML document from a finished schema.

A few will seek to produce a schema from the sample XML document. Many will supply you a graphical rendering of your schemas and XML files and can even generate some other documentation to suit your needs, also.

XML editors assists you to fully grasp XML technology plus assist you cope with enormous, complicated schemas and XML documents.

The fundamental syntax for including a schema namespaces definition within your XSD file is as follows:

<xsd:schema targetNamespace="http://www.myschema.com" xmlns="http://www.myschema.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

The targetNamespace is an attribute of schema. On this illustration it defines the URI: http://www.myschema.com. This URI identifies the current schema’s namespace. It is additionally defined as the default namespace by the xmlns=http://www.myschema.com (note the absence of a prefix).

Which means any element or attribute in the XML instance document(s) don't have to be prefixed to be able to define which schema they belong to.

Unless of course specifically prefixed, all elements and attributes in the instance record(s) are part of this namespace. A different URI is in addition defined in your schema header: xmlns:xsd="http://www.w3.org/2001/XMLSchema".

Remember that this one is prefixed :xsd. This at this time signifies that if an element or attribute within our instance file has a prefix belonging to the same URI, then this schema resource has to be referenced in place of our default schema.

Notice that this prefix in its self is without question immaterial. What is also important is the fact both the XSD prefix and XML instance document prefix should match the same URI.

When we prefixed our example schema document’s URI xmlns=http://www.myschema.com with say xmlns:ms=http://www.myschema.comt, the instance document will likely be expected to prefix it's elements and attributes using a prefix associated with that same URI.

We can easily after that get rid off our W3C URI xmlns:xsd=http://www.w3.org/2001/XMLSchema prefix like so, xmlns=http://www.w3.org/2001/XMLSchema and this would most likely instead become our default schema. This specific arrangement is normal and frequently makes wise practice.

Namespaces help for XSD schema facilitates the use of any prefix in an instance document to just accept unknown elements and attributes out of acknowledged or not known namespaces. This is simply not possible for DTDs.

For you to take out the ‘targetNamespace’ would be work free of namespaces. The function of the ‘targetNamespace’ is generally to bind a namespace to a W3C XML schema file. In the above instance we bound the URI http://www.myschema.com to symbolise our default namespace.

The sole area of the schema namespace definition example I haven’t included up to this point is the opening <xsd:schema...> part. The prefix here simply suggests that this particular line need to be processed using the namespace URI bound to the xsd prefix (i.e. http://www.w3.org/2001/XMLSchema ).

You will run into the schema attribute <xs:schema elementFormDefault="qualified" ...> I am going to take care of this in another 5 Minute XML tutorial.

A wealth of facts are available about XML if you happen to want to learn more. For the definitive guide, visit www.W3.org.

I am hoping the aforementioned is beneficial to anyone out there. Much more content can be on its way in the near future.

Additional articles about xml editor

About the author

Michael Dupre is truly an knowledgeable authority in XML programming and even XML standards and possesses loads of working understanding of XML Editor as well as functional know how with XML Schema Editor.

Please Rate This Article

Select Rating Excellent Very Good Interesting Fair Could Use Improvement

Number of ratings: 0
Rating: 0