Documentation for WITSML_Composite

Table of Contents

Master schema documentation file: WITSML_Composite.xsd.html


Schema Document Properties

Target Namespace
Version 1.3.1
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations belong to this schema's target namespace.
  • By default, local attribute declarations have no namespace.
Schema Composition

Declared Namespaces

Prefix Namespace
Schema Component Representation
<xsd:schema elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="" version="1.3.1">
<xsd:include schemaLocation="cs_productFlowExternalReference.xsd"/>
<xsd:include schemaLocation="cs_productFlowNetwork.xsd"/>

Global Definitions

Model Group: grp_productFlowModel

Name grp_productFlowModel
Documentation The non-contextual content of a WITSML Product Flow Model object.
XML Instance Representation
<witsml:installation> witsml:facilityIdentifierStruct </witsml:installation> [0..1]

'The name of the facility which is represented by this model. The name can be qualified by a naming system. This also defines the kind of facility.'

<witsml:contextFacility> witsml:facilityIdentifierStruct </witsml:contextFacility> [0..*]

'The name and type of a facility whose context is relevant to the represented installation.'

<witsml:dTimStart> witsml:timestamp </witsml:dTimStart> [0..1]

'The date and time of the start of validity for this model.'

<witsml:dTimEnd> witsml:timestamp </witsml:dTimEnd> [0..1]

'The date and time of the termination of validity for this model.'

<witsml:externalConnect> witsml:cs_productFlowExternalReference </witsml:externalConnect> [0..*]

'Defines the external port in another Product Flow Model to which an external port in this model is connected. An external port should be connected to an external port with the opposite direction. The connected external port must be in another Product Flow Model. These connections should always be defined on a one-to-one basis. For example, if a facility may receive input from multiple other facilities then a separate input port should be defined for each of those facilities. This allows any question about mass balancing to be contained within each individual model. The external port name must match the name of an external port on the network that represents this model.'

<witsml:network> witsml:cs_productFlowNetwork </witsml:network> [1..*]

'The description of one named network within this model. Each model is self contained but may reference other newtorks for defining internal detail. One of the networks must represent this model.'

<witsml:comment> witsml:commentString </witsml:comment> [0..1]

'A descriptive remark about the model.'

h970983430 h970983430 h-622169519 h-622169519 h1457553133 h-215126629 h-793122037
Schema Component Representation
<xsd:group name="grp_productFlowModel">
<xsd:element name="installation" type=" witsml:facilityIdentifierStruct " minOccurs="0" maxOccurs="1"/>
<xsd:element name="contextFacility" type=" witsml:facilityIdentifierStruct " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="dTimStart" type=" witsml:timestamp " minOccurs="0" maxOccurs="1"/>
<xsd:element name="dTimEnd" type=" witsml:timestamp " minOccurs="0" maxOccurs="1"/>
<xsd:element name="externalConnect" type=" witsml:cs_productFlowExternalReference " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="network" type=" witsml:cs_productFlowNetwork " minOccurs="1" maxOccurs="unbounded"/>
<xsd:element name="comment" type=" witsml:commentString " minOccurs="0" maxOccurs="1"/>


Complex Type:

Schema Component Type


Schema Component Name
Super-types: Address < AusAddress (by extension)
  • QLDAddress (by restriction)
If this schema component is a type definition, its type hierarchy is shown in a gray-bordered box.
Name AusAddress
Abstract no
The table above displays the properties of this schema component.
XML Instance Representation
<... country="Australia" >
<unitNo> string </unitNo> [0..1]
<houseNo> string </houseNo> [1]
<street> string </street> [1]
Start Choice [1]
<city> string </city> [1]
<town> string </town> [1]
End Choice
<state> AusStates </state> [1]
<postcode> string <<pattern = [1-9][0-9]{3}>> </postcode> [1] ?

The XML Instance Representation table above shows the schema component's content as an XML instance.

Schema Component Representation
<complexType name="AusAddress">
<extension base=" Address ">
<element name="state" type=" AusStates "/>
<element name="postcode">
<restriction base=" string ">
<pattern value="[1-9][0-9]{3}"/>
<attribute name="country" type=" string " fixed="Australia"/>
The Schema Component Representation table above displays the underlying XML representation of the schema component. (Annotations are not shown.)


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.

All Model Group Child elements can be provided in any order in instances. See:

Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See:

Collapse Whitespace Policy Replace 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.

Key Constraint Like Uniqueness Constraint, but additionally requires that the specified value(s) must be provided. See:

Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See:

Model Group Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See:

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 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.

Notation A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See:

Preserve Whitespace Policy Preserve whitespaces exactly as they appear in instances.

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 Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32).

Sequence Model Group Child elements and model groups must be provided in the specified order in instances. See:

Substitution Group Elements 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 Namespace The 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.

Uniqueness Constraint Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See: