The reusable email attribute simply contains an e-mail address.
A simpleType restriction should be added to this element so
that the parser can enforce the format of an email address with
a pattern.
The reusable uri="(anyURI)" attribute can be used in any element
definition that may refer to an external resource, e.g. a library
viewpoint or stakeholder document.
This is the root element for an ADX architectural description document. It conforms
to the schema's adType declaration, requiring a sequence of seven child elements:
<title>, <document-info>, >concerns<, <viewpoints>,
<views> <inconsistencies>, and <rationales>.
This is a placeholder concern element definition; the
concern element should eventually be defined as a type
with properties conforming to IEEE-1471 and substitutable
by a URL to an external stakeholder document (which must
still be in the adx:stakeholder format).
The entry element is defined for our glossary element. A glossary
contains a list of entries, each of which includes a term (type xs:string)
and a definition (type adx:richTextType).
This is a placeholder stakeholder element definition; the
stakeholder element should eventually be defined as a type
with properties conforming to IEEE-1471 and substitutable
by a URL to an external stakeholder document (which must
still be in the adx:stakeholder format).
The statement element is used in two subsections of the architectural
description (ad) element: the inconsistencies subsection, and the
rationales subsection.
The viewpoint-library element should be used as the root document
element for a standalone viewpoint library document. The library
document includes one or more viewpoint definitions and may also
include one or more stakeholder definitions. This element is not
used directly in a architectural description (ad) document.
The inline model is an abstract container for any
structured content. The concrete model data is expected
to be defined by an external XML schema. For now
this has a placeholder content type (adx:richText).
The view-model element is used in the definition of a view element;
a concrete view element may contain any sequence of child items, where each
item may either be a block of rich text, a model, or a model-list.
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
