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 versioningpolicy, this schema document will persist athttp://www.w3.org/2007/08/xml.xsd.At the date of issue it can also be found athttp://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 Schemaitself, or with the XML namespace itself. In other words, if the XMLSchema or XML namespaces change, the version of this document athttp://www.w3.org/2001/xml.xsd will changeaccordingly; the version athttp://www.w3.org/2007/08/xml.xsd will not change.
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/ .
This schema document provides attribute declarations andattribute group, complex type and simple type definitions which can be used inthe construction of user schemas to define the structure of particular linkingconstructs, 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>
Compliance levels schema for Simple features GML 3.1.1 ProfileCopyright (c) 2006,2010 Open Geospatial Consortium.To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
Database handle for the object. It is of XML type ID,so is constrained to be unique in the XML document withinwhich it occurs. An external identifier for the objectin the form of a URI may be constructed using standard XMLand XPointer methods. This is done by concatenating theURI for the document, a fragment separator, and the valueof the id attribute.
<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>
Label for the object, normally a descriptive name. Anobject may have several names, typically assigned bydifferent authorities. The authority for a name isindicated by the value of its (optional) codeSpaceattribute. The name may or may not be unique, asdetermined by the rules of the organization responsiblefor the codeSpace.
<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>
In general this reference points to a CRS instance ofgml:CoordinateReferenceSystemType (seecoordinateReferenceSystems.xsd). For well knownreferences it is not required that the CRS descriptionexists at the location the URI points to.
Database handle for the object. It is of XML type ID,so is constrained to be unique in the XML document withinwhich it occurs. An external identifier for the objectin the form of a URI may be constructed using standard XMLand XPointer methods. This is done by concatenating theURI for the document, a fragment separator, and the valueof the id attribute.
Database handle for the object. It is of XML type ID,so is constrained to be unique in the XML document withinwhich it occurs. An external identifier for the objectin the form of a URI may be constructed using standard XMLand XPointer methods. This is done by concatenating theURI for the document, a fragment separator, and the valueof 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>
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 subsequenceversions.
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>
This string contains a name designed to provide some contextualizationto the data it contains. For example, it might include the name of thepipeline segment its data describes as well as a date. Another alternativeis to include the unique identifier from a database to associate thisdata package with transactional records in a relational database.
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>
This string contains a description of the data contained within thispackage that provides additional contextual meaning to it.
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>
This string contains additional information that may be relevant to thedata 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 thisdata package.
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>
This integer value is chosen from a domain reference code list thatspecifies what domain this PipelineML data package pertains to. Thereason for using a domain code is to provide a mechanism in the futurethat allows software applications to make more informed decisions onhow best to process this data package based on the context providedby this domain code value.
<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>
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 dataintegrity check to ensure the pair of values match.
<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>
This string defines the interchange standard being used in this datapackage. It is supported with a domain reference code list to ensureadherence to this standard. This value may be used in the future to support intelligent software application parsing based on the valueprovided.
<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>
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: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>
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 determinethe age of the data and to be able to make automated or manual decisionson the value of this data package based on its age.
<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>
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: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>
The server name is provided as a means of providing as much contextualizationas possible to the information. This data will help support the efforts toensure TVC (traecable, verifiable, and complete) records that meet regulatoryrequirements.
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>
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
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>
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
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>
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
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>
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 processingof this data.
<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>
Although all features described within this data package that could usea different unit of measure have a required UOM attribute, this value isdesigned 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 intendedto provide a high-level context of the data. Any feature attribute UOM wouldoverride this generic default value.
<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>
The current schema design allows for an unlimited number of companies to belisted here. The concept is that any organization that is involved in the development or processing of this data package would add a company entryand describe the activities they performed on the data. This helps provideadditional context to the data that could be used to help ensure TVC (traecable, verifiable, and complete) records that meet regulatory requirements.
<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>
This machine-readable value is a globally unique identifier such as one generated by a relational database management system. This GUID definesthe pipeline system being referenced by the data contained within thisdata package. This information helps ensure contextual integrity of the data.
<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>
This human-readable string provides the name of the pipeline system beingreferences by the data contained within this data package. Although thisinformation could be pulled from the data source of the pipelineID, it canoptionally be provided here for readability or as an integrity check.
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>
This machine-readable value is a globally unique identifier such as one generated by a relational database management system. This GUID definesthe 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: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>
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
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>
An appurtenant component involving the encasement of a section of pipeline components for the purposes of reinforcement, often used when a segment of pipeline componentscrosses or runs under a roadway or railway.
Database handle for the object. It is of XML type ID,so is constrained to be unique in the XML document withinwhich it occurs. An external identifier for the objectin the form of a URI may be constructed using standard XMLand XPointer methods. This is done by concatenating theURI for the document, a fragment separator, and the valueof 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>
<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>
A human-friendly integer value assigned to this specificinstance of a component.
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>
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 annulusmay by filled with a substance such as ashalt or concrete. It may alsobe left unfilled. This code value is constrained by a referenced code list for this domain.
<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>
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
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>
An integer code value representing the crossing type for this casing. A crossing type may be a roadway, railway, etc. under which the pipelinecrosses. This code value is constrained by a domain reference code list.
<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>
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
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>
<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>
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
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>
<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>
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
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>
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-- casingLinePipeDimensionNominalPipeSizeThe 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: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>
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
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>
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.
<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>
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.
<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>
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