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_productFlowUnit.xsd"/>
<xsd:include schemaLocation="cs_productFlowlExternalPort.xsd"/>
<xsd:include schemaLocation="attgrp_uid.xsd"/>

Global Definitions

Complex Type: cs_productFlowNetwork

Super-types: None
Sub-types: None
Name cs_productFlowNetwork
Abstract no
Documentation The non-contextual content of a WITSML Product Flow Network object.
XML Instance Representation
uid=" witsml:uidString [0..1]

'The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element.'

<witsml:name> witsml:nameString </witsml:name> [1]

'The name of the Product Flow Network. This must be unique within the context of the overall Product Flow Model.'

<witsml:representedUnit> witsml:refNameString </witsml:representedUnit> [0..1]

'A pointer to the Flow Unit that this network represents. The Unit must exist in a different Network. If a unit is not specified then the network represents the model. A model should only be represented by one network. The model network represents the overall installation. All other networks represent internal detail and should not be referenced from outside this model. The external ports on the model network represent the external ports to the overall Product Flow Model. A pointer to an external port on the Product Flow Model does not require the name of the model network because it is redundant to knowledge of the model name (i.e., there is a one-to-one correspondence). A unit model defines the internal behavior of a Flow Unit.'

<witsml:port> witsml:cs_productFlowlExternalPort </witsml:port> [0..*]

'An external port. This exposes an internal node for the purpose of allowing connections to the internal behavior of the network. Networks that represent a Flow Unit should always have external ports. If this network represents a Unit then the name of the external port must match the name of a port on the Unit (i.e., they are logically the same port).'

<witsml:unit> witsml:cs_productFlowUnit </witsml:unit> [1..*]

'A flow behavior for one unit. Within this context, a unit represents a usage of equipment for some purpose. The unit is generally identified by its function rather than the actual equipment used to realize the function. A unit might represent something complex like a field or separator or something simple like a valve or pump.'

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

'A descriptive remark about the network.'

h-269201247 h65068842 h529433413 h-482327241 h-793122037 h-1931220815
Schema Component Representation
<xsd:complexType name="cs_productFlowNetwork">
<xsd:element name="name" type=" witsml:nameString " minOccurs="1" maxOccurs="1"/>
<xsd:element name="representedUnit" type=" witsml:refNameString " minOccurs="0" maxOccurs="1"/>
<xsd:element name="port" type=" witsml:cs_productFlowlExternalPort " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element name="unit" type=" witsml:cs_productFlowUnit " minOccurs="1" maxOccurs="unbounded"/>
<xsd:element name="comment" type=" witsml:commentString " minOccurs="0" maxOccurs="1"/>
<xsd:attributeGroup ref=" witsml:attgrp_uid "/>


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: