com.sun.xml.bind.v2.schemagen.xmlschema.xmlschema-for-jaxb.rng Maven / Gradle / Ivy
The newest version!
RELAX NG schema for XML Schema by Jeni Tennison . Based on
XML
Schema Part I: Structures Recommendation and XML Schema Part
II: Datatypes .
Amended to comply with 10 August 2001 Tutorial.
Removed key attributes.
Replaced not element with except elements.
Replaced multiple consecutive optional attributes to use the
zeroOrMore/choice pattern.
Removed interleave elements inside list elements (which are no longer
permitted).
This allows any number of attributes that are not in the XML Schema
namespace or are in no namespace. This is somewhat more complicated than
the XML Schema anyAttribute equivalent.
This allows any number of attributes that are not in the XML Schema
namespace or are in no namespace, an optional id attribute of type ID,
and an optional annotation element. This is used as the basis for many
element content models.
This gives the content model of the top level of the schema.
This gives the components that can be redefined within the redefine
element. They also occur at the top level of the schema.
This gives the values for the various form attributes:
elementFormDefault and attributeFormDefault on the schema element, and
the form attributes on the element and attribute elements.
qualified
unqualified
This gives the values that can be taken in the lists used to control
derivation by extension or restriction (this is 'reduced' derivation
because some derivation can involve substitution). This RELAX NG schema,
like the XML Schema Recommendation here, allows the keywords 'extension' and
'restriction' to be repeated any number of times.
extension
restriction
This specifies the possible values for attributes that control derivation.
#all
This is the beginning point for the schema, and defines the schema
element.
This gives the value type for the maxOccurs attribute, which may be a
non-negative number or the keyword 'unbounded'.
unbounded
This specifies the occurs attributes, minOccurs and maxOccurs, as they
are normally used.
This gives the possible content of complex types.
This gives the particles that can make up a model group.
This specifies the relationship between fixed and default attributes on
element and attribute elements - if one is present, then the other cannot
be. This is a constraint that cannot be specified using XML Schema.
This specifies the relationship between the type attribute and the
simpleType element child of attribute elements - if one is present, then
the other cannot be, although it is possible for neither to be allowed.
This describes attribute elements when used in a local context. They
have an optional use attribute, possibly a fixed or default attribute,
and then can either have a ref attribute (referring to a top-level
attribute) or a name attribute with an optional form attribute and
specifying an attribute type.
optional
prohibited
required
This describes attribute elements when used at the top level of the
schema. They must have a name, may have a fixed or default attribute,
and specify their type through a type attribute or child simpleType
element. The name attribute of each attribute element that appears at
the top level of the schema is unique.
This gives the model group for specifying the attributes in a complex
type, an extension or restriction.
This specifies the anyAttribute wildcard.
This specifies the content of a complexType element. As children, it can
have a simpleContent, a complexContent or a model group. Only if it has
one of the latter two, may it have a mixed attribute. This latter
constraint is something that cannot be specified in XML Schema.
This specifies the basic content of a complexType element.
This describes a restriction element within a complexContent element
(i.e. one that restricts a complex type). It has a base attribute, may
contain a model group and may contain attribute declarations of various
sorts.
This specifies the basic model for an extension element: adding a
required base attribute to the model used for most components.
This describes an extension element within a complexContent element
(i.e. one that restricts a complex type). It may contain a model group
and may contain attribute declarations of various sorts.
This describes a complexContent element. It may have a mixed attribute,
and either a restriction or extension element as content.
This describes a restriction element that appears within a simpleContent
or simpleType element (i.e. one that restricts a simple type). Its
content follows the simple restriction model that is detailed below, and
may include attribute declarations.
This describes an extension element that appears within a simpleContent
element (i.e. one that extends a simple type). Like other extensions, it
has a base type, but it can only be used to add attributes.
This describes a simpleContent element, whose content can either hold a
restriction or extension element.
This gives the possible values for block attributes on element elements,
which includes substitution amongst the list of possible values. This
RELAX NG schema, like the XML Schema Recommendation, allows each of the
keywords 'extension', 'restriction' and 'substitution' to occur more than
once within the list.
#all
extension
restriction
substitution
This describes the basic content model of an element element. It is
annotated, may have a fixed or default attribute, and may have nillable
and/or block attributes. Its type may be specified through a type
attribute, a local simple type or a local complex type - the choice
between these methods is something that cannot be indicated with XML
Schema. This content is optionally followed by some identify constraints.
This describes an element element that appears at the top level of the
schema. On top of the basic content for an element element, it has to
have a name, which is a unique identifier in the element symbol space. It
may have substitutionGroup, abstract and/or final attributes.
This describes an element element that appears locally, within a
complexType or group element. It may have minOccurs and/or maxOccurs
attributes. If it has a ref attribute, then that's all it can
have. Otherwise, it must have a name and specifies its type in the same
way as the basic element content model described above. It may in this
case also have a form element. These constraints on local elements
cannot be described within XML Schema.
This gives the content of a model group (not a group element) in the
normal run of things. It has occurrence attributes and any number of
particles within it.
This gives the content of a model group (not a group element) within a
named group - it differs from the above in that it doesn't have any
occurrence attributes.
This describes an all element that appears outside a named group (i.e. as
the content of a complexType element). It has the standard model for an
all element, but adds minOccurs and maxOccurs attributes which can only
take certain values.
This describes a choice element that appears outside a named group.
This describes a sequence element that appears outside a named group.
This describes a wildcard element (i.e. any or anyAttribute). The
namespace attribute can take a list URIs interspersed with the keywords
'##targetNamespace' and/or '##local'. This RELAX NG schema, like the XML
Schema Recommendation, allows the keywords to be specified more than once
each within the list, if they're given. This model also specifies the
processContents attribute.
##any
##other
##targetNamespace
##local
lax
skip
strict
This describes an any element as a wildcard.
This describes an import element that's used when its parent schema
element specifies a targetNamespace. In these cases, the namespace
attribute on the import element is optional.
This is designed to describe the content of the appinfo elements in the
schema. At the moment this allows any mixed content without validation.
Note that this is fairly complex compared to the XML Schema equivalent,
which would be a single any element.
This describes an appinfo element. It has an optional source attribute
and can currently contain anything at all.
This is designed to describe the content of the documentation elements in
the schema. At the moment this allows any mixed content without
validation. Note that this is fairly complex compared to the XML Schema
equivalent, which would be a single any element.
This describes a documentation element. It has optional source
and xml:lang attributes and can currently contain anything at all.
This describes an annotation element. It can have any attributes, may
have an id attribute, and contains any number of documentation or appinfo
elements.
This gives the various types of derivation of simple types.
This specifies the values of the final attribute for simple types. This
RELAX NG schema for XML Schema, like the XML Schema Recommendation, allows
the keywords 'list', 'union' and 'restriction' to appear more than once
within the list.
#all
list
union
restriction
This gives the basic content of a simple type.
This specifies the types of facets that are valid in restrictions on the
built-in data types. This can only perform rudimentary checking, but
should be enough in most circumstances. Note that for xs:anySimpleType
and xs:string, the whiteSpace facet can take any value, for
xs:normalizedString it can be 'replace' or 'collapse', and for all other
built-in types it has to be 'collapse'.
This describes a list element. It can either specify a local simple type
or have a itemType attribute. This constraint cannot be expressed in XML
Schema.
This describes a union element. If the memberTypes attribute is missing
or empty, then it must contain one or more simpleType elements; if
it's present, then it can contain simpleType elements or list simple
types in the memberTypes attribute. This constraint cannot be expressed
in XML Schema.
This is the basic content of a facet. It has an optional fixed attribute.
This is the content of a facet that cannot be fixed (enumeration or
pattern). It has a value attribute that can take any kind of value.
This describes an enumeration element.