Databases Reference
In-Depth Information
The simplest way to achieve this is to not specify the
form
and
attributeFormDefault
attributes. This will result in globally declared attributes
being prefixed with a namespace and locally declared attributes will have
unqualified names.
Namespace naming conventions
We also recommend defining a namespace naming convention, as this will provide
greater clarity as well as simplify the overall governance of assets. In the case of
oBay, our namespaces use the following convention:
http://<domain>/<sub-domain>/<namespace-type>/<subject_area>
Here,
obay
is a sub-domain within
rubiconred.com
. The
<namespace-type>
defines the type of component (for example, schema, service, and so on) to which
the namespace applies.
So within our canonical model, we have defined several namespaces, including:
http://rubiconred.com/obay/xsd/account
http://rubiconred.com/obay/xsd/auction
http://rubiconred.com/obay/xsd/common
As part of your naming standards, you should also define standard namespace
prefixes for each namespace in your canonical model.
Global versus local
A component (element, simple type, or complex type) is considered global if it's
defined as a child of the schema element. If defined within another component, it's
considered local. Consider the following fragment of XML:
<shipTo>
<name>
<title>Mr</title>
<firstName>James</firstName>
<lastName>Elliot</lastName>
</name>
<address>
<addressLine1>7PineDrive</addressLine1>
<addressLine2></addressLine2>
<city>Eltham<city>
<state>VIC</state>
<zip>3088</zip>
<country>Australia</country>
</address>
</shipTo>
