Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by

Table of Contents

Group by:

http://www.pipelineml.org/pml

Complex Types
Simple Types

http://www.opengis.net/gml

Attributes

http://www.opengis.net/gmlsf

http://www.w3.org/XML/1998/namespace

Attribute Groups

Resource hierarchy:

Main schema componentry.xsd
Namespace http://www.pipelineml.org/pml
Properties
attribute form default unqualified
element form default qualified
version 0.1.1
[ top ]
Imported schema xml.xsd
Namespace http://www.w3.org/XML/1998/namespace
Annotations
See http://www.w3.org/XML/1998/namespace.html and
   http://www.w3.org/TR/REC-xml for information about this namespace.

    This schema document describes the XML namespace, in a form
    suitable for import by other schema documents.  

    Note that local names in this namespace are intended to be defined
    only by the World Wide Web Consortium or its subgroups.  The
    following names are currently defined in this namespace and should
    not be used with conflicting semantics by any Working Group,
    specification, or document instance:

    base (as an attribute name): denotes an attribute whose value
         provides a URI to be used as the base for interpreting any
         relative URIs in the scope of the element on which it
         appears; its value is inherited.  This name is reserved
         by virtue of its definition in the XML Base specification.

    id   (as an attribute name): denotes an attribute whose value
         should be interpreted as if declared to be of type ID.
         This name is reserved by virtue of its definition in the
         xml:id specification.

    lang (as an attribute name): denotes an attribute whose value
         is a language code for the natural language of the content of
         any element; its value is inherited.  This name is reserved
         by virtue of its definition in the XML specification.
  
    space (as an attribute name): denotes an attribute whose
         value is a keyword indicating what whitespace processing
         discipline is intended for the content of the element; its
         value is inherited.  This name is reserved by virtue of its
         definition in the XML specification.

    Father (in any context at all): denotes Jon Bosak, the chair of 
         the original XML Working Group.  This name is reserved by 
         the following decision of the W3C XML Plenary and 
         XML Coordination groups:

             In appreciation for his vision, leadership and dedication
             the W3C XML Plenary on this 10th day of February, 2000
             reserves for Jon Bosak in perpetuity the XML name
             xml:Father
This schema defines attributes and an attribute group
        suitable for use by
        schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
        attributes on elements they define.

        To enable this, such a schema must import this schema
        for the XML namespace, e.g. as follows:
        <schema . . .>
         . . .
         <import namespace="http://www.w3.org/XML/1998/namespace"
                    schemaLocation="http://www.w3.org/2001/xml.xsd"/>

        Subsequently, qualified reference to any of the attributes
        or the group defined below will have the desired effect, e.g.

        <type . . .>
         . . .
         <attributeGroup ref="xml:specialAttrs"/>
 
         will define a type which will schema-validate an instance
         element with any of those attributes
In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2007/08/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself, or with the XML namespace itself.  In other words, if the XML
Schema or XML namespaces change, the version of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2007/08/xml.xsd will not change.
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Imported schema gmlsf.xsd
Namespace http://www.opengis.net/gml
Annotations
GML 3.1.1 Simplified Features profile Levels 0 and 1.
         
Copyright (c) 2006,2010 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
Properties
attribute form default unqualified
element form default qualified
version 1.0.0.2
[ top ]
Imported schema xlink.xsd
Namespace http://www.w3.org/1999/xlink
Annotations
This schema document provides attribute declarations and
attribute group, complex type and simple type definitions which can be used in
the construction of user schemas to define the structure of particular linking
constructs, e.g.<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
           xmlns:xl="http://www.w3.org/1999/xlink">

 <xs:import namespace="http://www.w3.org/1999/xlink"
            location="http://www.w3.org/1999/xlink.xsd">

 <xs:element name="mySimple">
  <xs:complexType>
   ...
   <xs:attributeGroup ref="xl:simpleAttrs"/>
   ...
  </xs:complexType>
 </xs:element>
 ...
</xs:schema>
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Imported schema gmlsfLevels.xsd
Namespace http://www.opengis.net/gmlsf
Annotations
Compliance levels schema for Simple features GML 3.1.1 Profile
         
Copyright (c) 2006,2010 Open Geospatial Consortium.
To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
Properties
attribute form default unqualified
element form default qualified
version 1.0.0.2
[ top ]
Element pml:ComponentCollection
Namespace http://www.pipelineml.org/pml
Diagram
Diagram componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractGMLType componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractFeatureBaseType componentry.tmp#boundedBy componentry.tmp#AbstractFeatureType componentry.tmp#ComponentCollectionType_featureMember componentry.tmp#ComponentCollectionType componentry.tmp#_GML
Type pml:ComponentCollectionType
Type hierarchy
Properties
content complex
Substitution Group Affiliation
Model
Children gml:boundedBy, gml:description, gml:name, pml:featureMember
Instance
<pml:ComponentCollection gml:id="" xmlns:pml="http://www.pipelineml.org/pml" xmlns:gml="http://www.opengis.net/gml">
  <gml:description>{0,1}</gml:description>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <gml:boundedBy>{0,1}</gml:boundedBy>
  <pml:featureMember>{1,1}</pml:featureMember>
</pml:ComponentCollection>
Attributes
QName Type Use Annotation
gml:id ID required
Database handle for the object.  It is of XML type ID,
so is constrained to be unique in the XML document within
which it occurs.  An external identifier for the object
in the form of a URI may be constructed using standard XML
and XPointer methods.  This is done by concatenating the
URI for the document, a fragment separator, and the value
of the id attribute.
Source
<xsd:element name="ComponentCollection" type="pml:ComponentCollectionType" substitutionGroup="gml:_GML"/>
[ top ]
Element gml:description
Namespace http://www.opengis.net/gml
Annotations
Contains a simple text description of the object.
Restricted to only allow a text string, as done in GML 3.2.
Diagram
Diagram
Type string
Properties
content simple
Used by
Source
<element name="description" type="string">
  <annotation>
    <documentation>Contains a simple text description of the object.</documentation>
    <documentation>Restricted to only allow a text string, as done in GML 3.2.</documentation>
  </annotation>
</element>
[ top ]
Element gml:name
Namespace http://www.opengis.net/gml
Annotations
Label for the object, normally a descriptive name. An
object may have several names, typically assigned by
different authorities.  The authority for a name is
indicated by the value of its (optional) codeSpace
attribute.  The name may or may not be unique, as
determined by the rules of the organization responsible
for the codeSpace.
Diagram
Diagram componentry.tmp#CodeType_codeSpace componentry.tmp#CodeType
Type gml:CodeType
Properties
content complex
Used by
Attributes
QName Type Use
codeSpace anyURI optional
Source
<element name="name" type="gml:CodeType">
  <annotation>
    <documentation>Label for the object, normally a descriptive name. An object may have several names, typically assigned by different authorities. The authority for a name is indicated by the value of its (optional) codeSpace attribute. The name may or may not be unique, as determined by the rules of the organization responsible for the codeSpace.</documentation>
  </annotation>
</element>
[ top ]
Element gml:boundedBy
Namespace http://www.opengis.net/gml
Diagram
Diagram componentry.tmp#Envelope componentry.tmp#BoundingShapeType
Type gml:BoundingShapeType
Properties
content complex
Used by
Model
Children gml:Envelope
Instance
<gml:boundedBy xmlns:gml="http://www.opengis.net/gml">
  <gml:Envelope srsName="">{1,1}</gml:Envelope>
</gml:boundedBy>
Source
<element name="boundedBy" type="gml:BoundingShapeType"/>
[ top ]
Element gml:Envelope
Namespace http://www.opengis.net/gml
Diagram
Diagram componentry.tmp#EnvelopeType_srsName componentry.tmp#EnvelopeType_lowerCorner componentry.tmp#EnvelopeType_upperCorner componentry.tmp#EnvelopeType
Type gml:EnvelopeType
Properties
content complex
Used by
Complex Type gml:BoundingShapeType
Model
Children gml:lowerCorner, gml:upperCorner
Instance
<gml:Envelope srsName="" xmlns:gml="http://www.opengis.net/gml">
  <gml:lowerCorner>{1,1}</gml:lowerCorner>
  <gml:upperCorner>{1,1}</gml:upperCorner>
</gml:Envelope>
Attributes
QName Type Use Annotation
srsName anyURI required
In general this reference points to a CRS instance of
gml:CoordinateReferenceSystemType (see
coordinateReferenceSystems.xsd). For well known
references it is not required that the CRS description
exists at the location the URI points to.
Source
<element name="Envelope" type="gml:EnvelopeType"/>
[ top ]
Element gml:EnvelopeType / gml:lowerCorner
Namespace http://www.opengis.net/gml
Diagram
Diagram componentry.tmp#doubleList componentry.tmp#DirectPositionType
Type gml:DirectPositionType
Type hierarchy
Properties
content complex
Source
<element name="lowerCorner" type="gml:DirectPositionType"/>
[ top ]
Element gml:EnvelopeType / gml:upperCorner
Namespace http://www.opengis.net/gml
Diagram
Diagram componentry.tmp#doubleList componentry.tmp#DirectPositionType
Type gml:DirectPositionType
Type hierarchy
Properties
content complex
Source
<element name="upperCorner" type="gml:DirectPositionType"/>
[ top ]
Element pml:ComponentCollectionType / pml:featureMember
Namespace http://www.pipelineml.org/pml
Diagram
Diagram componentry.tmp#_Feature
Properties
content complex
Model
Children gml:_Feature
Instance
<pml:featureMember xmlns:pml="http://www.pipelineml.org/pml" xmlns:gml="http://www.opengis.net/gml">
  <gml:_Feature gml:id="">{1,1}</gml:_Feature>
</pml:featureMember>
Source
<xsd:element name="featureMember">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="gml:_Feature"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element gml:_Feature
Namespace http://www.opengis.net/gml
Diagram
Diagram componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractGMLType componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractFeatureBaseType componentry.tmp#boundedBy componentry.tmp#AbstractFeatureType componentry.tmp#Casing componentry.tmp#Coating componentry.tmp#Compressor componentry.tmp#Elbow componentry.tmp#Flange componentry.tmp#Joint componentry.tmp#LauncherReceiver componentry.tmp#LinePipe componentry.tmp#Meter componentry.tmp#PackageMetadata componentry.tmp#Pump componentry.tmp#Reducer componentry.tmp#Sleeve componentry.tmp#Tap componentry.tmp#Tee componentry.tmp#Valve componentry.tmp#_GML
Type gml:AbstractFeatureType
Type hierarchy
Properties
content complex
abstract true
Substitution Group
Substitution Group Affiliation
Used by
Model
Children gml:boundedBy, gml:description, gml:name
Instance
<gml:_Feature gml:id="" xmlns:gml="http://www.opengis.net/gml">
  <gml:description>{0,1}</gml:description>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <gml:boundedBy>{0,1}</gml:boundedBy>
</gml:_Feature>
Attributes
QName Type Use Annotation
gml:id ID required
Database handle for the object.  It is of XML type ID,
so is constrained to be unique in the XML document within
which it occurs.  An external identifier for the object
in the form of a URI may be constructed using standard XML
and XPointer methods.  This is done by concatenating the
URI for the document, a fragment separator, and the value
of the id attribute.
Source
<element name="_Feature" type="gml:AbstractFeatureType" abstract="true" substitutionGroup="gml:_GML"/>
[ top ]
Element pml:PackageMetadata
Namespace http://www.pipelineml.org/pml
Annotations
This feature only contain metadata defining the information contained
within this data package.
Diagram
Diagram componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractGMLType componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractFeatureBaseType componentry.tmp#boundedBy componentry.tmp#AbstractFeatureType componentry.tmp#PackageMetadataType_packageVersion componentry.tmp#PackageMetadataType_packageName componentry.tmp#PackageMetadataType_packageDescription componentry.tmp#PackageMetadataType_packageNote componentry.tmp#PackageMetadataType_packageDomainCode componentry.tmp#PackageMetadataType_packageDomainName componentry.tmp#PackageMetadataType_interchangeStandard componentry.tmp#PackageMetadataType_interchangeStandardVersion componentry.tmp#PackageMetadataType_beginCreationDateTime componentry.tmp#PackageMetadataType_endCreationDateTime componentry.tmp#PackageMetadataType_serverName componentry.tmp#PackageMetadataType_dbName componentry.tmp#PackageMetadataType_systemUser componentry.tmp#PackageMetadataType_appName componentry.tmp#PackageMetadataType_languageCode componentry.tmp#PackageMetadataType_unitOfMeasure componentry.tmp#PackageMetadataType_company componentry.tmp#PackageMetadataType_pipelineID componentry.tmp#PackageMetadataType_pipelineName componentry.tmp#PackageMetadataType_pipelineSubsystemID componentry.tmp#PackageMetadataType_pipelineSubsystemName componentry.tmp#PackageMetadataType componentry.tmp#_Feature
Type pml:PackageMetadataType
Type hierarchy
Properties
content complex
Substitution Group Affiliation
Model
Children gml:boundedBy, gml:description, gml:name, pml:appName, pml:beginCreationDateTime, pml:company, pml:dbName, pml:endCreationDateTime, pml:interchangeStandard, pml:interchangeStandardVersion, pml:languageCode, pml:packageDescription, pml:packageDomainCode, pml:packageDomainName, pml:packageName, pml:packageNote, pml:packageVersion, pml:pipelineID, pml:pipelineName, pml:pipelineSubsystemID, pml:pipelineSubsystemName, pml:serverName, pml:systemUser, pml:unitOfMeasure
Instance
<pml:PackageMetadata gml:id="" xmlns:pml="http://www.pipelineml.org/pml" xmlns:gml="http://www.opengis.net/gml">
  <gml:description>{0,1}</gml:description>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <gml:boundedBy>{0,1}</gml:boundedBy>
  <pml:packageVersion>{0,1}</pml:packageVersion>
  <pml:packageName>{0,1}</pml:packageName>
  <pml:packageDescription>{0,1}</pml:packageDescription>
  <pml:packageNote>{0,1}</pml:packageNote>
  <pml:packageDomainCode>{0,1}</pml:packageDomainCode>
  <pml:packageDomainName>{0,1}</pml:packageDomainName>
  <pml:interchangeStandard>{0,1}</pml:interchangeStandard>
  <pml:interchangeStandardVersion>{0,1}</pml:interchangeStandardVersion>
  <pml:beginCreationDateTime>{0,1}</pml:beginCreationDateTime>
  <pml:endCreationDateTime>{0,1}</pml:endCreationDateTime>
  <pml:serverName>{0,1}</pml:serverName>
  <pml:dbName>{0,1}</pml:dbName>
  <pml:systemUser>{0,1}</pml:systemUser>
  <pml:appName>{0,1}</pml:appName>
  <pml:languageCode>{0,1}</pml:languageCode>
  <pml:unitOfMeasure>{0,1}</pml:unitOfMeasure>
  <pml:company>{0,unbounded}</pml:company>
  <pml:pipelineID>{0,1}</pml:pipelineID>
  <pml:pipelineName>{0,1}</pml:pipelineName>
  <pml:pipelineSubsystemID>{0,1}</pml:pipelineSubsystemID>
  <pml:pipelineSubsystemName>{0,1}</pml:pipelineSubsystemName>
</pml:PackageMetadata>
Attributes
QName Type Use Annotation
gml:id ID required
Database handle for the object.  It is of XML type ID,
so is constrained to be unique in the XML document within
which it occurs.  An external identifier for the object
in the form of a URI may be constructed using standard XML
and XPointer methods.  This is done by concatenating the
URI for the document, a fragment separator, and the value
of the id attribute.
Source
<xsd:element name="PackageMetadata" type="pml:PackageMetadataType" substitutionGroup="gml:_Feature">
  <xsd:annotation>
    <xsd:documentation>This feature only contain metadata defining the information contained within this data package.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageVersion
Namespace http://www.pipelineml.org/pml
Annotations
This numeric value is intended to be used to facilitate a 
light-weight versioning control mechanism. If changes are 
needed to a data package that has been previously distributed 
but is intended to provide an newer representation of the data, 
this value should be increased incrementally with subsequence
versions.
Diagram
Diagram
Type xsd:float
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="packageVersion" type="xsd:float" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This numeric value is intended to be used to facilitate a light-weight versioning control mechanism. If changes are needed to a data package that has been previously distributed but is intended to provide an newer representation of the data, this value should be increased incrementally with subsequence versions.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageName
Namespace http://www.pipelineml.org/pml
Annotations
This string contains a name designed to provide some contextualization
to the data it contains. For example, it might include the name of the
pipeline segment its data describes as well as a date. Another alternative
is to include the unique identifier from a database to associate this
data package with transactional records in a relational database.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="packageName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This string contains a name designed to provide some contextualization to the data it contains. For example, it might include the name of the pipeline segment its data describes as well as a date. Another alternative is to include the unique identifier from a database to associate this data package with transactional records in a relational database.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageDescription
Namespace http://www.pipelineml.org/pml
Annotations
This string contains a description of the data contained within this
package that provides additional contextual meaning to it.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="packageDescription" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This string contains a description of the data contained within this package that provides additional contextual meaning to it.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageNote
Namespace http://www.pipelineml.org/pml
Annotations
This string contains additional information that may be relevant to the
data package. This may include notes from the individual who exported 
the data package. It may include information about various activities,
procedures, policies, etc. that were involved in the production of this
data package.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="packageNote" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This string contains additional information that may be relevant to the data package. This may include notes from the individual who exported the data package. It may include information about various activities, procedures, policies, etc. that were involved in the production of this data package.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageDomainCode
Namespace http://www.pipelineml.org/pml
Annotations
This integer value is chosen from a domain reference code list that
specifies what domain this PipelineML data package pertains to. The
reason for using a domain code is to provide a mechanism in the future
that allows software applications to make more informed decisions on
how best to process this data package based on the context provided
by this domain code value.
Diagram
Diagram componentry.tmp#PackageDomainCodeType
Type pml:PackageDomainCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration 1
enumeration 2
Source
<xsd:element name="packageDomainCode" type="pml:PackageDomainCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This integer value is chosen from a domain reference code list that specifies what domain this PipelineML data package pertains to. The reason for using a domain code is to provide a mechanism in the future that allows software applications to make more informed decisions on how best to process this data package based on the context provided by this domain code value.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:packageDomainName
Namespace http://www.pipelineml.org/pml
Annotations
This string is a human-readable value that matches the previous element.
It is optional. It may be provided to enhance readability or as a data
integrity check to ensure the pair of values match.
Diagram
Diagram componentry.tmp#PackageDomainNameType
Type pml:PackageDomainNameType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration Componentry
enumeration Survey
Source
<xsd:element name="packageDomainName" type="pml:PackageDomainNameType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This string is a human-readable value that matches the previous element. It is optional. It may be provided to enhance readability or as a data integrity check to ensure the pair of values match.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:interchangeStandard
Namespace http://www.pipelineml.org/pml
Annotations
This string defines the interchange standard being used in this data
package. It is supported with a domain reference code list to ensure
adherence to this standard. This value may be used in the future to 
support intelligent software application parsing based on the value
provided.
Diagram
Diagram componentry.tmp#InterchangeStandardType
Type pml:InterchangeStandardType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration PipelineML
Source
<xsd:element name="interchangeStandard" type="pml:InterchangeStandardType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This string defines the interchange standard being used in this data package. It is supported with a domain reference code list to ensure adherence to this standard. This value may be used in the future to support intelligent software application parsing based on the value provided.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:interchangeStandardVersion
Namespace http://www.pipelineml.org/pml
Annotations
This value defines the version of the interchange standard being used 
in this data package. It is supported with a domain reference code list 
to ensure adherence to this standard. This value may be used in the 
future to support intelligent software application parsing based on 
the value provided.
Diagram
Diagram componentry.tmp#InterchangeStandardVersionType
Type pml:InterchangeStandardVersionType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration 0.0.17
enumeration 0.0.18
enumeration 0.1.0
enumeration 0.1.1
enumeration 0.1.2
enumeration 0.1.3
enumeration 0.1.4
enumeration 0.1.5
Source
<xsd:element name="interchangeStandardVersion" type="pml:InterchangeStandardVersionType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This value defines the version of the interchange standard being used in this data package. It is supported with a domain reference code list to ensure adherence to this standard. This value may be used in the future to support intelligent software application parsing based on the value provided.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:beginCreationDateTime
Namespace http://www.pipelineml.org/pml
Annotations
This concept behind including the start date and time for the creation of 
the data package is to be able to leverage this information to determine
the age of the data and to be able to make automated or manual decisions
on the value of this data package based on its age.
Diagram
Diagram componentry.tmp#DateTimeType
Type pml:DateTimeType
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="beginCreationDateTime" type="pml:DateTimeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This concept behind including the start date and time for the creation of the data package is to be able to leverage this information to determine the age of the data and to be able to make automated or manual decisions on the value of this data package based on its age.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:endCreationDateTime
Namespace http://www.pipelineml.org/pml
Annotations
This concept behind including the end date and time for the creation of 
the data package is to know how long it took to generate this information.
It also helps support additional business decisions based on the age of 
the data.
Diagram
Diagram componentry.tmp#DateTimeType
Type pml:DateTimeType
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="endCreationDateTime" type="pml:DateTimeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This concept behind including the end date and time for the creation of the data package is to know how long it took to generate this information. It also helps support additional business decisions based on the age of the data.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:serverName
Namespace http://www.pipelineml.org/pml
Annotations
The server name is provided as a means of providing as much contextualization
as possible to the information. This data will help support the efforts to
ensure TVC (traecable, verifiable, and complete) records that meet regulatory
requirements.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="serverName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>The server name is provided as a means of providing as much contextualization as possible to the information. This data will help support the efforts to ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:dbName
Namespace http://www.pipelineml.org/pml
Annotations
The source database name is provided as a means of providing as much 
contextualization as possible to the information. This data will help support 
the efforts to ensure TVC (traecable, verifiable, and complete) records that 
meet regulatory requirements.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="dbName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>The source database name is provided as a means of providing as much contextualization as possible to the information. This data will help support the efforts to ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:systemUser
Namespace http://www.pipelineml.org/pml
Annotations
The system user who originally exported the database is provided as a means 
of providing as much contextualization as possible to the information. This 
data will help support the efforts to ensure TVC (traecable, verifiable, and 
complete) records that meet regulatory requirements.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="systemUser" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>The system user who originally exported the database is provided as a means of providing as much contextualization as possible to the information. This data will help support the efforts to ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:appName
Namespace http://www.pipelineml.org/pml
Annotations
The software application name that was used to originally export the data 
is provided as a means of providing as much contextualization as possible 
to the information. This data will help support the efforts to ensure TVC 
(traecable, verifiable, and complete) records that meet regulatory requirements.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="appName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>The software application name that was used to originally export the data is provided as a means of providing as much contextualization as possible to the information. This data will help support the efforts to ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:languageCode
Namespace http://www.pipelineml.org/pml
Annotations
The 2-digit language code provided here is pulled from a domain reference 
code list that originated from the ISO 639-1. This information can be 
utilized by software applications to assist in the parsing and processing
of this data.
Diagram
Diagram componentry.tmp#LanguageCodeType
Type pml:LanguageCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration aa
enumeration ab
enumeration ae
enumeration af
enumeration ak
enumeration am
enumeration an
enumeration ar
enumeration as
enumeration av
enumeration ay
enumeration az
enumeration ba
enumeration be
enumeration bg
enumeration bh
enumeration bi
enumeration bm
enumeration bn
enumeration bo
enumeration br
enumeration bs
enumeration ca
enumeration ce
enumeration ch
enumeration co
enumeration cr
enumeration cs
enumeration cs
enumeration cu
enumeration cv
enumeration cy
enumeration da
enumeration de
enumeration dv
enumeration dz
enumeration ee
enumeration el
enumeration el
enumeration en
enumeration eo
enumeration es
enumeration et
enumeration eu
enumeration fa
enumeration ff
enumeration fi
enumeration fj
enumeration fo
enumeration fr
enumeration fy
enumeration ga
enumeration gd
enumeration gl
enumeration gn
enumeration gu
enumeration gv
enumeration ha
enumeration he
enumeration hi
enumeration ho
enumeration hr
enumeration ht
enumeration hu
enumeration hy
enumeration hz
enumeration ia
enumeration id
enumeration ie
enumeration ig
enumeration ii
enumeration ik
enumeration io
enumeration is
enumeration it
enumeration iu
enumeration ja
enumeration jv
enumeration ka
enumeration kg
enumeration ki
enumeration kj
enumeration kk
enumeration kl
enumeration km
enumeration kn
enumeration ko
enumeration kr
enumeration ks
enumeration ku
enumeration kv
enumeration kw
enumeration ky
enumeration la
enumeration lb
enumeration lg
enumeration li
enumeration ln
enumeration lo
enumeration lt
enumeration lu
enumeration lv
enumeration mg
enumeration mh
enumeration mi
enumeration mk
enumeration ml
enumeration mn
enumeration mr
enumeration ms
enumeration mt
enumeration my
enumeration na
enumeration nb
enumeration nd
enumeration ne
enumeration ng
enumeration nl
enumeration nn
enumeration no
enumeration nr
enumeration nv
enumeration ny
enumeration oc
enumeration oj
enumeration om
enumeration or
enumeration os
enumeration pa
enumeration pi
enumeration pl
enumeration ps
enumeration pt
enumeration qu
enumeration rm
enumeration rn
enumeration ro
enumeration ru
enumeration rw
enumeration sa
enumeration sc
enumeration sd
enumeration se
enumeration sg
enumeration si
enumeration sk
enumeration sl
enumeration sm
enumeration sn
enumeration so
enumeration sq
enumeration sr
enumeration ss
enumeration st
enumeration su
enumeration sv
enumeration sw
enumeration ta
enumeration te
enumeration tg
enumeration th
enumeration ti
enumeration tk
enumeration tl
enumeration tn
enumeration to
enumeration tr
enumeration ts
enumeration tt
enumeration tw
enumeration ty
enumeration ug
enumeration uk
enumeration ur
enumeration uz
enumeration ve
enumeration vi
enumeration vo
enumeration wa
enumeration wo
enumeration xh
enumeration yi
enumeration yo
enumeration za
enumeration zh
enumeration zu
Source
<xsd:element name="languageCode" type="pml:LanguageCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>The 2-digit language code provided here is pulled from a domain reference code list that originated from the ISO 639-1. This information can be utilized by software applications to assist in the parsing and processing of this data.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:unitOfMeasure
Namespace http://www.pipelineml.org/pml
Annotations
Although all features described within this data package that could use
a different unit of measure have a required UOM attribute, this value is
designed to provide a high-level picture of a default UOM of measure that 
is used. This might be US Feet, UK Meters, etc. This value is only intended
to provide a high-level context of the data. Any feature attribute UOM would
override this generic default value.
Diagram
Diagram componentry.tmp#UnitOfMeasureType
Type pml:UnitOfMeasureType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration Barrels
enumeration Barrels Per Day
enumeration Barrels Per Hour
enumeration Centimeters
enumeration Count
enumeration Cubic Centimeters
enumeration Cubic Feet
enumeration Cubic Feet Per Second
enumeration Days
enumeration Decimal Degrees
enumeration Degrees (Angle)
enumeration Degrees Celsius
enumeration Degrees Fahrenheit
enumeration Degrees-Minutes-Seconds
enumeration Feet
enumeration Feet Per Second
enumeration Gallons
enumeration Gallons Per Minute
enumeration Horsepower
enumeration Hour
enumeration Inch
enumeration Kilowatt
enumeration Kilowatt Hour
enumeration Mile
enumeration Miles Per Hour
enumeration Mils
enumeration Minute
enumeration Nautical Mile
enumeration Not Applicable
enumeration Percentage
enumeration Pound
enumeration Pounds Per Square Inch
enumeration Radians
enumeration Rank
enumeration Rods
enumeration Seconds
enumeration Sequence
enumeration US Dollars
enumeration Ampere
enumeration Volt
enumeration Ratio
Source
<xsd:element name="unitOfMeasure" type="pml:UnitOfMeasureType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>Although all features described within this data package that could use a different unit of measure have a required UOM attribute, this value is designed to provide a high-level picture of a default UOM of measure that is used. This might be US Feet, UK Meters, etc. This value is only intended to provide a high-level context of the data. Any feature attribute UOM would override this generic default value.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:company
Namespace http://www.pipelineml.org/pml
Annotations
The current schema design allows for an unlimited number of companies to be
listed here. The concept is that any organization that is involved in the 
development or processing of this data package would add a company entry
and describe the activities they performed on the data. This helps provide
additional context to the data that could be used to help ensure TVC 
(traecable, verifiable, and complete) records that meet regulatory requirements.
Diagram
Diagram componentry.tmp#CompanyType_companyName componentry.tmp#CompanyType_companyRole componentry.tmp#CompanyType_companyDepartment componentry.tmp#CompanyType_contactName componentry.tmp#CompanyType_contactPhone componentry.tmp#CompanyType_contactPhoneType componentry.tmp#CompanyType_contactEmail componentry.tmp#CompanyType_contactAddress componentry.tmp#CompanyType
Type pml:CompanyType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children pml:companyDepartment, pml:companyName, pml:companyRole, pml:contactAddress, pml:contactEmail, pml:contactName, pml:contactPhone, pml:contactPhoneType
Instance
<pml:company xmlns:pml="http://www.pipelineml.org/pml">
  <pml:companyName>{0,1}</pml:companyName>
  <pml:companyRole>{0,1}</pml:companyRole>
  <pml:companyDepartment>{0,1}</pml:companyDepartment>
  <pml:contactName>{0,1}</pml:contactName>
  <pml:contactPhone>{0,1}</pml:contactPhone>
  <pml:contactPhoneType>{0,1}</pml:contactPhoneType>
  <pml:contactEmail>{0,1}</pml:contactEmail>
  <pml:contactAddress>{0,1}</pml:contactAddress>
</pml:company>
Source
<xsd:element name="company" type="pml:CompanyType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>The current schema design allows for an unlimited number of companies to be listed here. The concept is that any organization that is involved in the development or processing of this data package would add a company entry and describe the activities they performed on the data. This helps provide additional context to the data that could be used to help ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CompanyType / pml:companyName
Namespace http://www.pipelineml.org/pml
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="companyName" type="xsd:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:companyRole
Namespace http://www.pipelineml.org/pml
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="companyRole" type="xsd:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:companyDepartment
Namespace http://www.pipelineml.org/pml
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="companyDepartment" type="xsd:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:contactName
Namespace http://www.pipelineml.org/pml
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="contactName" type="xsd:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:contactPhone
Namespace http://www.pipelineml.org/pml
Diagram
Diagram componentry.tmp#PhoneNumberType
Type pml:PhoneNumberType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
pattern [0-9\-\+\(\)]{4,}
Source
<xsd:element name="contactPhone" type="pml:PhoneNumberType" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:contactPhoneType
Namespace http://www.pipelineml.org/pml
Diagram
Diagram componentry.tmp#PhoneNumberTypeType
Type pml:PhoneNumberTypeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
enumeration work
enumeration home
enumeration mobile
enumeration fax
enumeration voice/fax
enumeration voicemail
Source
<xsd:element name="contactPhoneType" type="pml:PhoneNumberTypeType" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:contactEmail
Namespace http://www.pipelineml.org/pml
Diagram
Diagram componentry.tmp#EmailType
Type pml:EmailType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
pattern ([A-z0-9_\.\-\+])[email protected](([A-z0-9_\-]{2,})\.)+[A-z0-9_\-]{2,}
Source
<xsd:element name="contactEmail" type="pml:EmailType" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:CompanyType / pml:contactAddress
Namespace http://www.pipelineml.org/pml
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="contactAddress" type="xsd:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element pml:PackageMetadataType / pml:pipelineID
Namespace http://www.pipelineml.org/pml
Annotations
This machine-readable value is a globally unique identifier such as one 
generated by a relational database management system. This GUID defines
the pipeline system being referenced by the data contained within this
data package. This information helps ensure contextual integrity of the 
data.
Diagram
Diagram componentry.tmp#GUIDType
Type pml:GUIDType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
pattern [a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}
Source
<xsd:element name="pipelineID" type="pml:GUIDType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This machine-readable value is a globally unique identifier such as one generated by a relational database management system. This GUID defines the pipeline system being referenced by the data contained within this data package. This information helps ensure contextual integrity of the data.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:pipelineName
Namespace http://www.pipelineml.org/pml
Annotations
This human-readable string provides the name of the pipeline system being
references by the data contained within this data package. Although this
information could be pulled from the data source of the pipelineID, it can
optionally be provided here for readability or as an integrity check.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="pipelineName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This human-readable string provides the name of the pipeline system being references by the data contained within this data package. Although this information could be pulled from the data source of the pipelineID, it can optionally be provided here for readability or as an integrity check.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:pipelineSubsystemID
Namespace http://www.pipelineml.org/pml
Annotations
This machine-readable value is a globally unique identifier such as one 
generated by a relational database management system. This GUID defines
the subsection of the pipeline system being referenced by the data 
contained within this data package. This information helps ensure 
contextual integrity of the data.
Diagram
Diagram componentry.tmp#GUIDType
Type pml:GUIDType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
pattern [a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}
Source
<xsd:element name="pipelineSubsystemID" type="pml:GUIDType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This machine-readable value is a globally unique identifier such as one generated by a relational database management system. This GUID defines the subsection of the pipeline system being referenced by the data contained within this data package. This information helps ensure contextual integrity of the data.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:PackageMetadataType / pml:pipelineSubsystemName
Namespace http://www.pipelineml.org/pml
Annotations
This human-readable string provides the name of the pipeline subsystem 
being references by the data contained within this data package. Although 
this information could be pulled from the data source of the pipelineID, 
it can optionally be provided here for readability or as an integrity 
check.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="pipelineSubsystemName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This human-readable string provides the name of the pipeline subsystem being references by the data contained within this data package. Although this information could be pulled from the data source of the pipelineID, it can optionally be provided here for readability or as an integrity check.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:Casing
Namespace http://www.pipelineml.org/pml
Annotations
An appurtenant component involving the encasement of a section of pipeline components 
for the purposes of reinforcement, often used when a segment of pipeline components
crosses or runs under a roadway or railway.
Diagram
Diagram componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractGMLType componentry.tmp#id componentry.tmp#description componentry.tmp#description componentry.tmp#name componentry.tmp#name componentry.tmp#StandardObjectProperties componentry.tmp#AbstractFeatureBaseType componentry.tmp#boundedBy componentry.tmp#AbstractFeatureType componentry.tmp#CasingType_componentID componentry.tmp#CasingType_componentCode componentry.tmp#CasingType_casingAnnulusTypeCode componentry.tmp#CasingType_casingAnnulusTypeName componentry.tmp#CasingType_casingCrossingTypeCode componentry.tmp#CasingType_casingCrossingTypeName componentry.tmp#CasingType_casingInsulatorTypeCode componentry.tmp#CasingType_casingInsulatorTypeName componentry.tmp#CasingType_casingSealTypeCode componentry.tmp#CasingType_casingSealTypeName componentry.tmp#CasingType_casingLinePipeDimensionBoundCode componentry.tmp#CasingType_casingLinePipeDimensionBoundName componentry.tmp#CasingType_casingLinePipeDimensionOutsideDiameter componentry.tmp#CasingType_casingLinePipeDimensionNominalWallThickness componentry.tmp#CasingType_casingLinePipeDimensionNominalPipeSize componentry.tmp#CasingType_casingLinePipeSpecificationBoundCode componentry.tmp#CasingType_casingLinePipeSpecificationBoundName componentry.tmp#CasingType_casingLinePipeSpecificationSpecification componentry.tmp#CasingType_casingLinePipeSpecificationGrade componentry.tmp#CasingType_casingLinePipeSpecificationMaterial componentry.tmp#CasingType_casingLinePipeSpecificationYieldStrength componentry.tmp#CasingType_casingPipeMillLocation componentry.tmp#CasingType_casingVentCount componentry.tmp#CasingType_description componentry.tmp#CasingType_comment componentry.tmp#CasingType_installDate componentry.tmp#CasingType_removeDate componentry.tmp#CasingType_manufactureDate componentry.tmp#CasingType_manufacturerCode componentry.tmp#CasingType_manufacturerName componentry.tmp#CasingType_geometry0D componentry.tmp#CasingType_geometry1D componentry.tmp#CasingType componentry.tmp#_Feature
Type pml:CasingType
Type hierarchy
Properties
content complex
Substitution Group Affiliation
Model
Children gml:boundedBy, gml:description, gml:name, pml:casingAnnulusTypeCode, pml:casingAnnulusTypeName, pml:casingCrossingTypeCode, pml:casingCrossingTypeName, pml:casingInsulatorTypeCode, pml:casingInsulatorTypeName, pml:casingLinePipeDimensionBoundCode, pml:casingLinePipeDimensionBoundName, pml:casingLinePipeDimensionNominalPipeSize, pml:casingLinePipeDimensionNominalWallThickness, pml:casingLinePipeDimensionOutsideDiameter, pml:casingLinePipeSpecificationBoundCode, pml:casingLinePipeSpecificationBoundName, pml:casingLinePipeSpecificationGrade, pml:casingLinePipeSpecificationMaterial, pml:casingLinePipeSpecificationSpecification, pml:casingLinePipeSpecificationYieldStrength, pml:casingPipeMillLocation, pml:casingSealTypeCode, pml:casingSealTypeName, pml:casingVentCount, pml:comment, pml:componentCode, pml:componentID, pml:description, pml:geometry0D, pml:geometry1D, pml:installDate, pml:manufactureDate, pml:manufacturerCode, pml:manufacturerName, pml:removeDate
Instance
<pml:Casing gml:id="" xmlns:pml="http://www.pipelineml.org/pml" xmlns:gml="http://www.opengis.net/gml">
  <gml:description>{0,1}</gml:description>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <gml:boundedBy>{0,1}</gml:boundedBy>
  <pml:componentID>{0,1}</pml:componentID>
  <pml:componentCode>{0,1}</pml:componentCode>
  <pml:casingAnnulusTypeCode>{0,1}</pml:casingAnnulusTypeCode>
  <pml:casingAnnulusTypeName>{0,1}</pml:casingAnnulusTypeName>
  <pml:casingCrossingTypeCode>{0,1}</pml:casingCrossingTypeCode>
  <pml:casingCrossingTypeName>{0,1}</pml:casingCrossingTypeName>
  <pml:casingInsulatorTypeCode>{0,1}</pml:casingInsulatorTypeCode>
  <pml:casingInsulatorTypeName>{0,1}</pml:casingInsulatorTypeName>
  <pml:casingSealTypeCode>{0,1}</pml:casingSealTypeCode>
  <pml:casingSealTypeName>{0,1}</pml:casingSealTypeName>
  <pml:casingLinePipeDimensionBoundCode>{0,1}</pml:casingLinePipeDimensionBoundCode>
  <pml:casingLinePipeDimensionBoundName>{0,1}</pml:casingLinePipeDimensionBoundName>
  <pml:casingLinePipeDimensionOutsideDiameter uom="">{0,1}</pml:casingLinePipeDimensionOutsideDiameter>
  <pml:casingLinePipeDimensionNominalWallThickness uom="">{0,1}</pml:casingLinePipeDimensionNominalWallThickness>
  <pml:casingLinePipeDimensionNominalPipeSize uom="">{0,1}</pml:casingLinePipeDimensionNominalPipeSize>
  <pml:casingLinePipeSpecificationBoundCode>{0,1}</pml:casingLinePipeSpecificationBoundCode>
  <pml:casingLinePipeSpecificationBoundName>{0,1}</pml:casingLinePipeSpecificationBoundName>
  <pml:casingLinePipeSpecificationSpecification>{0,1}</pml:casingLinePipeSpecificationSpecification>
  <pml:casingLinePipeSpecificationGrade>{0,1}</pml:casingLinePipeSpecificationGrade>
  <pml:casingLinePipeSpecificationMaterial>{0,1}</pml:casingLinePipeSpecificationMaterial>
  <pml:casingLinePipeSpecificationYieldStrength uom="">{0,1}</pml:casingLinePipeSpecificationYieldStrength>
  <pml:casingPipeMillLocation>{0,1}</pml:casingPipeMillLocation>
  <pml:casingVentCount>{0,1}</pml:casingVentCount>
  <pml:description>{0,1}</pml:description>
  <pml:comment>{0,1}</pml:comment>
  <pml:installDate>{0,1}</pml:installDate>
  <pml:removeDate>{0,1}</pml:removeDate>
  <pml:manufactureDate>{0,1}</pml:manufactureDate>
  <pml:manufacturerCode>{0,1}</pml:manufacturerCode>
  <pml:manufacturerName>{0,1}</pml:manufacturerName>
  <pml:geometry0D>{0,1}</pml:geometry0D>
  <pml:geometry1D>{0,1}</pml:geometry1D>
</pml:Casing>
Attributes
QName Type Use Annotation
gml:id ID required
Database handle for the object.  It is of XML type ID,
so is constrained to be unique in the XML document within
which it occurs.  An external identifier for the object
in the form of a URI may be constructed using standard XML
and XPointer methods.  This is done by concatenating the
URI for the document, a fragment separator, and the value
of the id attribute.
Source
<xsd:element name="Casing" type="pml:CasingType" substitutionGroup="gml:_Feature">
  <xsd:annotation>
    <xsd:documentation>An appurtenant component involving the encasement of a section of pipeline components for the purposes of reinforcement, often used when a segment of pipeline components crosses or runs under a roadway or railway.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:componentID
Namespace http://www.pipelineml.org/pml
Annotations
A machine-friendly globally unique identity value assigned to 
this specific instance of a component.
Diagram
Diagram componentry.tmp#GUIDType
Type pml:GUIDType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
pattern [a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{12}
Source
<xsd:element name="componentID" type="pml:GUIDType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A machine-friendly globally unique identity value assigned to this specific instance of a component.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:componentCode
Namespace http://www.pipelineml.org/pml
Annotations
A human-friendly integer value assigned to this specific
instance of a component.
Diagram
Diagram
Type xsd:integer
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="componentCode" type="xsd:integer" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A human-friendly integer value assigned to this specific instance of a component.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingAnnulusTypeCode
Namespace http://www.pipelineml.org/pml
Annotations
An integer code value representing the annulus type of this casing. The 
annulus of a pipeline casing is any void between any piping, tubing or 
casing and the piping, tubing, or casing immediately surrounding it. 
It is named after the corresponding geometric concept. The annulus
may by filled with a substance such as ashalt or concrete. It may also
be left unfilled. This code value is constrained by a referenced code 
list for this domain.
Diagram
Diagram componentry.tmp#CasingAnnulusTypeCodeType
Type pml:CasingAnnulusTypeCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
maxInclusive 99999
minInclusive 0
Source
<xsd:element name="casingAnnulusTypeCode" type="pml:CasingAnnulusTypeCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>An integer code value representing the annulus type of this casing. The annulus of a pipeline casing is any void between any piping, tubing or casing and the piping, tubing, or casing immediately surrounding it. It is named after the corresponding geometric concept. The annulus may by filled with a substance such as ashalt or concrete. It may also be left unfilled. This code value is constrained by a referenced code list for this domain.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingAnnulusTypeName
Namespace http://www.pipelineml.org/pml
Annotations
This human-readable string provides the name of the casing annulus type 
being references by the data contained within this data package. Although 
this information could be pulled from the data source of the 
casingAnnulusTypeCode, it can optionally be provided here for readability 
or as an integrity check.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="casingAnnulusTypeName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>This human-readable string provides the name of the casing annulus type being references by the data contained within this data package. Although this information could be pulled from the data source of the casingAnnulusTypeCode, it can optionally be provided here for readability or as an integrity check.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingCrossingTypeCode
Namespace http://www.pipelineml.org/pml
Annotations
An integer code value representing the crossing type for this casing. 
A crossing type may be a roadway, railway, etc. under which the pipeline
crosses. This code value is constrained by a domain reference code list.
Diagram
Diagram componentry.tmp#CasingCrossingTypeCodeType
Type pml:CasingCrossingTypeCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
maxInclusive 99999
minInclusive 0
Source
<xsd:element name="casingCrossingTypeCode" type="pml:CasingCrossingTypeCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>An integer code value representing the crossing type for this casing. A crossing type may be a roadway, railway, etc. under which the pipeline crosses. This code value is constrained by a domain reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingCrossingTypeName
Namespace http://www.pipelineml.org/pml
Annotations
A string value representing the name of the crossing type for this casing. 
This code value is constrained by a referenced code list. This value is 
optional as this name directly corresponds to the casingCrossingTypeCode. 
It may be used as an integrity check and/or human-readability.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="casingCrossingTypeName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A string value representing the name of the crossing type for this casing. This code value is constrained by a referenced code list. This value is optional as this name directly corresponds to the casingCrossingTypeCode. It may be used as an integrity check and/or human-readability.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingInsulatorTypeCode
Namespace http://www.pipelineml.org/pml
Annotations
An integer code value representing the insulator type for this casing. 
This code value is constrained by a domain reference code list.
Diagram
Diagram componentry.tmp#CasingInsulatorTypeCodeType
Type pml:CasingInsulatorTypeCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
maxInclusive 99999
minInclusive 0
Source
<xsd:element name="casingInsulatorTypeCode" type="pml:CasingInsulatorTypeCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>An integer code value representing the insulator type for this casing. This code value is constrained by a domain reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingInsulatorTypeName
Namespace http://www.pipelineml.org/pml
Annotations
A string value representing the name of the insulator type for this casing. 
This code value is constrained by a domain reference code list. This value 
is optional as this name directly corresponds to the casingInsulatorTypeCode. 
It may be used as an integrity check and/or human-readability.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="casingInsulatorTypeName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A string value representing the name of the insulator type for this casing. This code value is constrained by a domain reference code list. This value is optional as this name directly corresponds to the casingInsulatorTypeCode. It may be used as an integrity check and/or human-readability.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingSealTypeCode
Namespace http://www.pipelineml.org/pml
Annotations
An integer code value representing the seal type for this casing. This 
code value is constrained by a referenced code list.
Diagram
Diagram componentry.tmp#CasingSealTypeCodeType
Type pml:CasingSealTypeCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
maxInclusive 99999
minInclusive 0
Source
<xsd:element name="casingSealTypeCode" type="pml:CasingSealTypeCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>An integer code value representing the seal type for this casing. This code value is constrained by a referenced code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingSealTypeName
Namespace http://www.pipelineml.org/pml
Annotations
A string value representing the name of the seal type for this casing. This 
code value is constrained by a referenced code list. This value is optional 
as this name directly corresponds to the casingSealTypeCode. It may be used 
as an integrity check and/or human-readability.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="casingSealTypeName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A string value representing the name of the seal type for this casing. This code value is constrained by a referenced code list. This value is optional as this name directly corresponds to the casingSealTypeCode. It may be used as an integrity check and/or human-readability.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeDimensionBoundCode
Namespace http://www.pipelineml.org/pml
Annotations
An integer code value that represents a bound combination of values that 
identify casing linePipe dimension attribution. This code value represents 
the combination of the following casing linePipe dimension attributes:
--    casingLinePipeDimensionOutsideDiameter
--    casingLinePipeDimensionNominalWallThickness
--    casingLinePipeDimensionNominalPipeSize
The utilization of bound type codes represents the highest level of data 
integrity because the unique combination of codes have been vetted by 
pipeline industry SMEs and determined to be valid combinations. This is 
an optional implementation of PipelineML and considered a best practice. 
This value shall be constrained by a reference code list.
Diagram
Diagram componentry.tmp#CasingLinePipeDimensionBoundCodeType
Type pml:CasingLinePipeDimensionBoundCodeType
Properties
content simple
minOccurs 0
maxOccurs 1
Facets
maxInclusive 99999
minInclusive 0
Source
<xsd:element name="casingLinePipeDimensionBoundCode" type="pml:CasingLinePipeDimensionBoundCodeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>An integer code value that represents a bound combination of values that identify casing linePipe dimension attribution. This code value represents the combination of the following casing linePipe dimension attributes: -- casingLinePipeDimensionOutsideDiameter -- casingLinePipeDimensionNominalWallThickness -- casingLinePipeDimensionNominalPipeSize The utilization of bound type codes represents the highest level of data integrity because the unique combination of codes have been vetted by pipeline industry SMEs and determined to be valid combinations. This is an optional implementation of PipelineML and considered a best practice. This value shall be constrained by a reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeDimensionBoundName
Namespace http://www.pipelineml.org/pml
Annotations
A string containing the name of the bound combination of casing linePipe 
dimension attribution. This value is optional as this name directly 
corresponds to the linePipeDimensionBoundCode. It may be used as an 
integrity check and/or human-readability.
Diagram
Diagram
Type xsd:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
<xsd:element name="casingLinePipeDimensionBoundName" type="xsd:string" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A string containing the name of the bound combination of casing linePipe dimension attribution. This value is optional as this name directly corresponds to the linePipeDimensionBoundCode. It may be used as an integrity check and/or human-readability.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeDimensionOutsideDiameter
Namespace http://www.pipelineml.org/pml
Annotations
A numeric value containing the linePipe outside diameter for this type 
of casing. The utilization of unbound attributes without use of bound 
type is considered substandard but permissible. Such substandard data 
may be permissible for cases in which new attribute combinations are 
utilized but not yet vetted into the bound code list. They may be 
provided in addition to the bound type code as an integrity checking 
and/or human-readability. This value shall be constrained by a 
reference code list.
Diagram
Diagram componentry.tmp#CasingLinePipeDimensionOutsideDiameterType_uom componentry.tmp#CasingLinePipeDimensionOutsideDiameterType
Type pml:CasingLinePipeDimensionOutsideDiameterType
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use
uom xsd:string required
Source
<xsd:element name="casingLinePipeDimensionOutsideDiameter" type="pml:CasingLinePipeDimensionOutsideDiameterType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A numeric value containing the linePipe outside diameter for this type of casing. The utilization of unbound attributes without use of bound type is considered substandard but permissible. Such substandard data may be permissible for cases in which new attribute combinations are utilized but not yet vetted into the bound code list. They may be provided in addition to the bound type code as an integrity checking and/or human-readability. This value shall be constrained by a reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeDimensionNominalWallThickness
Namespace http://www.pipelineml.org/pml
Annotations
A numeric value containing the linePipe nominal wall thickness for this 
type of casing. The utilization of unbound attributes without use of bound 
type is considered substandard but permissible. Such substandard data may 
be permissible for cases in which new attribute combinations are utilized 
but not yet vetted into the bound code list. They may be provided in 
addition to the bound type code as an integrity checking and/or human-
readability. This value shall be constrained by a reference code list.
Diagram
Diagram componentry.tmp#CasingLinePipeDimensionNominalWallThicknessType_uom componentry.tmp#CasingLinePipeDimensionNominalWallThicknessType
Type pml:CasingLinePipeDimensionNominalWallThicknessType
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use
uom xsd:string required
Source
<xsd:element name="casingLinePipeDimensionNominalWallThickness" type="pml:CasingLinePipeDimensionNominalWallThicknessType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A numeric value containing the linePipe nominal wall thickness for this type of casing. The utilization of unbound attributes without use of bound type is considered substandard but permissible. Such substandard data may be permissible for cases in which new attribute combinations are utilized but not yet vetted into the bound code list. They may be provided in addition to the bound type code as an integrity checking and/or human- readability. This value shall be constrained by a reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeDimensionNominalPipeSize
Namespace http://www.pipelineml.org/pml
Annotations
A numeric value containing the linePipe nominal wall thickness for this 
type of casing. The utilization of unbound attributes without use of bound 
type is considered substandard but permissible. Such substandard data may 
be permissible for cases in which new attribute combinations are utilized 
but not yet vetted into the bound code list. They may be provided in 
addition to the bound type code as an integrity checking and/or human-
readability. This value shall be constrained by a reference code list.
Diagram
Diagram componentry.tmp#CasingLinePipeDimensionNominalPipeSizeType_uom componentry.tmp#CasingLinePipeDimensionNominalPipeSizeType
Type pml:CasingLinePipeDimensionNominalPipeSizeType
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use
uom xsd:string required
Source
<xsd:element name="casingLinePipeDimensionNominalPipeSize" type="pml:CasingLinePipeDimensionNominalPipeSizeType" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
    <xsd:documentation>A numeric value containing the linePipe nominal wall thickness for this type of casing. The utilization of unbound attributes without use of bound type is considered substandard but permissible. Such substandard data may be permissible for cases in which new attribute combinations are utilized but not yet vetted into the bound code list. They may be provided in addition to the bound type code as an integrity checking and/or human- readability. This value shall be constrained by a reference code list.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element pml:CasingType / pml:casingLinePipeSpecificationBoundCode
Namespace http://www.pipelineml.org/pml
Annotations