About xsd:schema Properties

The root element of every XML Schema document is the xsd:schema element. The xsd:schema element has the properties described in Table 42. Click the Tree tab, and then click the Schema node to view the properties for the xsd:schema element.

Table 42. xsd:schema Properties
Property	Description
`Type`	The type is always `Schema`.
`Namespace`	The namespace for the `Schema` node is usually `xsd`, but you can change it.
`Target Namespace`	This is the namespace that elements and attributes defined in an instance document belong to. For example, suppose you define the following: <xsd:schema ... targetNamespace="http://myNS"> <xsd:element name="myelement"/> In an instance document, the following declarations conform with the target namespace: <myelement xmlns="http://myNS"/> <myns:myelement xmlns:myns="http://myNS"/> However, the following declaration does not conform: <myns:myelement xmlns:myns="http://anotherNS"/>
`Version`	Use this property as a convenient way to track the revisions of your XML Schema document.
`Default Element Form`	An element or attribute's form is either `qualified` or `unqualified`. A form of `qualified` means that each time an element or attribute is referenced in the schema document, you must specify the prefix of its namespace. Every element and attribute has a `form` attribute. If it is not explicitly defined, the schema processor checks the default attribute form specified for the `Schema` node. For example: <xs:schema elementFormDefault="qualified" targetNamespace="http://myNs" xmlns:myns="http://myNS"> <xs:element name="topElem"> .... </xs:element> <xs:element name="anElem"> <xs:complexType> <xs:sequence> <xs:element ref="myns:topElem"> ... If the form for the element `topElem` (or, the default form for elements) was defined to be unqualified, the reference could have used `ref="topElem"`.
`Default Attribute Form`
`Default Blocked Definitions`	If an element does not have its own blocked or final definition, the schema processor uses the default blocked or final definition you specify here.
`Default Final Definitions`

< Previous | Next >

Converting Custom EDI Message Types to XML

Vital and valuable legacy data locked in proprietary EDI files? See how to use DataDirect XML Converters™ custom EDI message type tools to convert nonconformant EDI to XML.

XQuery Tutorial

This XQuery Tutorial is about "BUILDING XQUERY BASED WEB SERVICE AGGREGATION AND REPORTING APPLICATIONS".

WYSIWYG XSLT Designer

Stylus Studio's powerful and easy-to-use WYSIWYG ("What you see is what you get") XSLT Designer lets you create XSLT stylesheets without writing any code! Go from a blank slate to solid, robust XSLT in minutes, using simple drag-and-drop operations.

XML Schema Validator, DTD Validator

Stylus Studio lets you validate XML documents using integrated XML Schema or DTD validators. Use the Stylus Studio built-in validator, or any number of supported XML parsers and XML validators like MSXML SAX and DOM, Xerces, .NET, and more!

About xsd:schema Properties

Converting Custom EDI Message Types to XML

XQuery Tutorial

WYSIWYG XSLT Designer

XML Schema Validator, DTD Validator

Stylus Most Wanted