The unique identifier of a container element. This attribute is generally required within the context of a WITSML server. There should be no assumption as to the semantic content of this attribute. This should only be used with recurring container types (i.e., maxOccurs greater than one). The value is only required to be unique within the context of the nearest recurring parent element. WITSML - Common Data Component Schema An identifier to indicate the data originator. This identifies the server that originally created the object and thus most of the uids in the object (but not necessarily the uids of the parents). This is typically a url. When the data was created at the persistent data store. Last change of any element of the data at the persistent data store. The change time is not updated for a growing object while it is growing. The item state for the data object. Comments and remarks. WITSML - Custom or User Defined Element and Attributes Component Schema. Specify custom element, attributes, and types in the custom data area. Any element or attribute in any namespace. It is strongly recommended that all custom data definitions be added to a unique namespace. A possibly temperature and pressure corrected desity value. The density of the product. The temperature to which the density has been corrected. If not given then the ambient temperature is assumed. If given, then a pressure should also be given. Common standard temperatures are: 0 degC, 15 degC, 60 degF. The pressure to which the density has been corrected. If not given then the ambient pressure is assumed. If given, then a temperature should also be given. Common standard pressures are: 1 atm and 14.696 psi (which are equivalent). A schema to capture a set of data that is relevant for many exchange documents. It includes information about the file that was created, and high-level information about the data that is being exchanged within the file. An identifier for the document. This is intended to be unique within the context of the NamingSystem. Zero or more alternate names for the document. These names do not need to be unique within the naming system. The date of the creation of the document. This is not the same as the date that the file was created. For this date, the document is considered to be the set of information associated with this document information. For example, the document may be a seismic binset. This represents the date that the binset was created. The FileCreation information would capture the date that the XML file was created to send or exchange the binset. A document class. Examples of classes would be a metadata classification or a set of keywords. The information about the creation of the exchange file. This is not about the creation of the data within the file, but the creation of the file itself. Information about the security to be applied to this file. More than one classification can be given. A free-form string that allows a disclaimer to accompany the information. A collection of events that can document the history of the data. The owner of the data. WITSML query parameters. An optional comment about the document. A structure for WITSML query parameters. The intent is to allow a query for all objects within an index range (whether or not the object is growing). These would typically be something like a daily report. The minimum start time for an object. This only applies to objects with a root level date and/or dateTime element(s). The objects may or not be growing objects but the See the API specification for behavior related to this query parameter. The maximum start time for an object. This only applies to objects with a root level date and/or dateTime element(s). See the API specification for behavior related to this query parameter. A block of information about the creation of the XML file. This is different than the creation of the data that is included within the file. The date and time that the file was created. If appropriate, the software that created the file. This is a free form string, and may include whatever information is deemed relevant. The person or business associate that created the file. Any comment that would be useful to further explain the creation of this instance document. Information about the security classification of the document. This is intended as a documentation of the security so that the file will not inadvertently be sent to someone who is not allowed access to the data. This block also carries a date that the security classification expires. For example, a well log is confidential for a period of time, and then becomes open. All security classes are characterized by their classification systems. The security class in which this document is classified. Examples would be confidential, partner confidential, tight. The meaning of the class is determined by the System in which it is defined. The security classification system. This gives context to the meaning of the Class value. The date on which this security class is no longer applicable. A general comment to further define the security class. The audit records what happened to the data, to produce the data that is in this file. It consists of one or more events. An event type captures the basic information about an event that has affected the data. The date on which the event took place. The party responsible for the event. A free form comment that can further define the event that occurred. A simple structure that allows an error report to be exchanged. The strucutre will allow for an error name, error id (generally a numerical code), and a description. A name of the error. A code, or other id, for the error. A description of the error. Unique identifier for the error report. Captures information about one processed wellLog. The kind of processing used to create the new log. The resultant wellLog. The wellLog which was the primary source for creating the derived log. A textual comment about the processing. Unique identifier for the node. A set of points recorded during the installation process. The information can include the length along the fiber, the measured depth, and a type of point. The measured depth of the installed point of the fiber. This is optional, because the sender may want to record points that are outside the well. The length along the fiber, from the zero point, for this particular point. The type of point that is being recorded. Unique identifier for the point. Product Volume Port Differential characteristics. A port on the other end of an internal connection. This should always be specified if a Product Flow Network is being referenced by this report. If this is not specified then there is an assumption that there is only one other port for the unit. For example, if this end of the connection represents an inlet port then the implied other end is the outlet port for the unit. The differential pressure between the ports. The differential temperature between the ports. The size of the choke. This characterizes the overall unit with respect to the flow restriction between the ports. The restriction might be implemented using a valve or an actual choke. The relative size of the choke restriction. This characterizes the overall unit with respect to the flow restriction between the ports. The restriction might be implemented using a valve or an actual choke. The unique identifier of the recurring element. Data that represents a foreign key to a wellbore. The wellbore may be defined within the context of another well. A pointer the wellbore with which there is a relationship. A pointer to the well that contains the wellboreReference. This is not needed unless the referenced wellbore is outside the context of a common parent well. A reference to a rig within a wellbore. The wellbore may be defined within the context of another well. This value represents a foreign key from one node to another. A pointer to the rig with which there is a relationship. A pointer to the wellbore that contains the rigReference. This is not needed unless the referenced rig is outside the context of a common parent wellbore. A pointer to the well that contains the wellboreParent. This is not needed unless the referenced wellbore is outside the context of a common parent well. A possibly temperature and pressure corrected volume value. The volume of the product. If the 'status' attribute is absent and the value is not "NaN", the data value can be assumed to be good with no restrictions. A value of "NaN" should be interpreted as null and should be not be given unless a status is also specified to explain why it is null. The amount of heat which would be released by the complete combustion in air of the above volume of product. The temperature to which the volume has been corrected. If not given then the ambient temperature is assumed. If given, then a pressure should also be given. Common standard temperatures are: 0 degC, 15 degC, 60 degF. The pressure to which the volume has been corrected. If not given then the ambient pressure is assumed. If given, then a temperature should also be given. Common standard pressures are: 1 atm and 14.696 psi (which are equivalent). Within the context of a WITSML Server, this data should duplicate the equivalent information in the well object. Name of the field in which the well is located. An alias name associated with the well. If the wellName is associated with a naming system then it should be included in this list. A datum to which elevations and depths are referenced. Defines the datums associated with elevation, vertical depth and measured depth coordinates within the context of a well. The human understandable contextual name of the reference datum. The code value that represents the type of reference datum. This may represent a point on a device (e.g., kelly bushing) or it may represent a vertical reference datum (e.g., mean sea level). The name of the vertical reference datum in a particular naming system. This should only be specified if the above 'code' represents some variation of sea level. An optional short name (code) can also be specified. Specifying a well known datum is highly desired if the above code is a variant of sea level because sea level varies over time and space. An example would be to specify a name of 'Caspian Sea' with a code of '5106' in the 'EPSG' naming system. Since various activities may use different points as measurement datums, it is useful to characterize the point based on its usage. A well reference datum may have more than one such characterization. For example, it may be the datum used by the driller and logger for measuring their depths. Example usage values would be 'permanent','driller', 'logger' 'WRP' (well reference point) and 'SRP' (site reference point). A pointer to the wellbore that contains the reference datum. This should be specified if a measured depth is given. A pointer to the rig that contains the device used as a reference datum. The rig may be associated with a wellbore in another well (e.g., pattern drilling using a rig on a track). The gravity based elevation coordinate of this reference datum as measured from another datum. Positive moving upward from the elevation datum. An elevation should be given unless this is a vertical reference datum (e.g., sea level). The measured depth coordinate of this reference datum as measured from another datum. The measured depth datum should either be the same as the elevation datum or it should be relatable to the elevation datum through other datums. Positive moving toward the bottomhole from the measured depth datum. This should be given when a local reference is "downhole", such as a kickoff point or ocean bottom template, and the borehole may not be vertical. If a Depth is given then an Elevation should also be given. A contextual description of the well reference datum. True indicates that this is the default reference datum for measured depth coordinates. False or not given indicates that this is not the default reference datum. Measured depth coordinates that do not specify a datum reference should be assumed to be measured relative to this default reference datum. Only one reference datum may be designated as the default measured depth datum for each well. Values are "true" (or "1") and "false" ( or "0"). True indicates that this is the default reference datum for vertical depth coordinates. False or not given indicates that this is not the default reference datum. Vertical depth coordinates that do not specify a datum reference should be assumed to be measured relative to the default reference datum. Only one reference datum may be designated as the default vertical depth datum for each well. Values are "true" (or "1") and "false" ( or "0"). True indicates that this is the default reference datum for elevation coordinates. False or not given indicates that this is not the default reference datum. Elevation coordinates that do not specify a datum reference should be assumed to be measured relative to the default reference datum. Only one reference datum may be designated as the default elevation datum for each well. Values are "true" (or "1") and "false" ( or "0"). The unique identifier of the reference datum. The information content of a DTS temperature run is captured in the following elements, and in the referenced dtsInstalledFiber (for context) and the reference well log (captures the table of data). The minimum time index contained within the object. The minimum and maximum indexes are server query parameters and will be populated with valid values in a "get" result. That is, all measurements for a well in the specified period defined by the min/max. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. The maximum time index contained within the object. The minimum and maximum indexes are server query parameters and will be populated with valid values in a "get" result. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. The definition of the "current time" index for this object. The current time index is a server query parameter which requests the selection of a single node from a recurring set (e.g., the data related to one point in a time series). That is, the "most recent" (at or before the specified time) measurement for a well. See the WITSML API Specification appendix on "Special Handling" of growing objects for a description of the behavior related to this parameter. Contextual data about the well that was tested. The date and time associated with the measurement. This will normally be the start of the run. The length of time that the instrument box was operating while collecting DTS data. A reference to the installed system that was used to make the measurements. A reference to the well log used to record the table of data. A reference to the fiber used to record the table of data. This is necessary only in the cases in which a dtsInstalledSystem has a multi-fiber installation. If there is only a single installed fiber, this element is unnecessary. A pointer to the fiber connection node. If more than one node is available for a well/wellbore, this element is used to specify which node is connected to the instrument box. This name should correspond to the fiberEndPoint/name that is recorded in the installed system object. A known point of the fiber. This point should correspond to one that is given in the wellboreFiberSchematic, so that the relationship between the length of fiber values in the wellboreFiberSchematic can be related to the values in the measurement table. An error that occurred during the measurement. A reference to a processed wellLog that represents this measurement. The WITSML API mandated plural root element which allows multiple singular objects to be sent. The plural name is formed by adding an "s" to the singular name. Information about the XML message instance. Main wrapper for all the distributed temperature survey information about the measurement. Note that this object must be accompanied by a wellLog object in order to be complete. Data object schema version. The fourth level must match the version of the schema constraints (enumerations and XML loader files) that are assumed by the document instance. The measurements of a DTS run are carried primarily in the wellLog object. The elements in this object are additional, defined parameters that are needed to capture the context of the DTS measurement. Human recognizable context for the well that contains the wellbore. Human recognizable context for the wellbore that contains the dts. Human recognizable context for the dts. The information content of a dts measurement object A container element that contains elements that are common to all data objects. A container element that can contain custom or user defined data elements. Unique identifier for the well. This uniquely represents the well referenced by the (possibly non-unique) nameWell. Unique identifier for the wellbore. This uniquely represents the wellbore referenced by the (possibly non-unique) nameWellbore. Unique identifier for the measurement. This type disallows an "empty" boolean value. This type should not be used directly except to derive another type. All boolean types should be derived from this type rather than using xsd:boolen. This type disallows an "empty" dateTime value. This type should not be used directly except to derive another type. All dateTime types should be derived from this type rather than using xsd:dateTime. This type disallows an "empty" date value. This type should not be used directly except to derive another type. All dateTime types should be derived from this type rather than using xsd:dateTime. This type disallows an "empty" double value. This type should not be used directly except to derive another type. The intended abstract supertype of all strings. This abstract type allows the control over whitespace for all strings to be defined at a high level. This type should not be used directly except to derive another type. Replace tab, line feed and carriage return with a space, collapse contiguous sequences of spaces to a single space and then remove leading and trailing spaces. The empty string is not allowed. This constraint conbined with the whiteSpace collapse constraint means that a blank value is not allowed. The intended abstract supertype of all quantities that have a value with a unit of measure. The unit of measure is in the uom attribute of the subtypes. This type allows all quantities to be profiled to be a 'float' instead of a 'double'. This defines the maximum acceptable length of a string that can be stored in a data base. This value should be the smallest "maximum size of a variable length character type" in commonly used DBMSs. This is the maximum size of a VARCHAR2 in Oracle 8. The intended abstract supertype of all singular data objects. The intended abstract supertype of all user assigned human recognizable contextual name types. There should be no assumption that (interoperable) semantic information will be extracted from the name by a third party. This type of value is generally not guaranteed to be unique and is not a candidate to be replaced by an enumeration. The intended abstract supertype of all locally unique identifiers. The value is not intended to convey any semantic content (e.g., it may be computer generated). The value is only required to be unique within a context in a document (e.g., defined via key and keyref). There is no guarantee that the same data in multiple documents will utilize the same uid value unless enforced by the source of the document (e.g., a document server). Spaces are not allowed. The intended abstract supertype of all comments or remarks intended for human consumption. There should be no assumption that semantics can be extracted from the field by a computer. Neither should there be an assumption that any two humans will interpret the information in the same way (i.e., it may not be interoperable). The intended abstract supertype of all enumerated "types". This abstract type allows the maximum length of a type enumeration to be centrally defined. This type should not be used directly except to derive another type. It should also be used for uncontrolled strings which are candidates to become enumerations at a future date. The intended abstract supertype of all "units of measure". This abstract type allows the maximum length of a UOM enumeration to be centrally defined. This type is abstract in the sense that it should not be used directly except to derive another type. The type of local or permanent reference datum for vertical gravity based (i.e., elevation and vertical depth) and measured depth coordinates within the context of a well. This list includes local points (e.g., kelly bushing) used as a datum and vertical reference datums (e.g., mean sea level). casing flange: A flange affixed to the top of the casing string used to attach production equipment. crown valve derrick floor ground level kelly bushing rotary bushing rotary table sea floor Lowest Astronomical Tide. The lowest tide level over the duration of the National Tidal Datum Epoch (19 years). Mean Sea Level - A tidal datum. The arithmetic mean of hourly heights observed over the National Tidal Datum Epoch (19 years). Mean Higher High Water - A tidal datum. The average of the higher high water height of each tidal day observed over the National Tidal Datum Epoch (19 years). Mean High Water - A tidal datum. The average of all the high water heights observed over the National Tidal Datum Epoch (19 years). Mean Lower Low Water - A tidal datum. The average of the lower low water height of each tidal day observed over the National Tidal Datum Epoch (19 years ). Mean Low Water - A tidal datum. The average of all the low water heights observed over the National Tidal Datum Epoch (19 years). Mean Tide Level - A tidal datum. The arithmetic mean of mean high water and mean low water. Same as half-tide level. kickoff point The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The meaning of the endpoint for min/max query parameters on "growing objects". The list of standard values is contained in the PRODML enumValues.xml file. The endpoint of the range is inclusive of the specified range value. hat is, a node index value which matches the specified range value is considered to be within the range. The endpoint of the range is exclusive of the specified range value. That is, a node index value which matches the specified range value is considered to be outside the range. The endpoint of the range may be extended to the first encountered value if an exact value match is not found. That is, if a node index value does not match the specified range value then the next smaller value (on minimum end) or larger value (on maximum end) in the index series should be used as the endpoint. Basically, this concept is designed to support interpolation across an undefined point. The endpoint of the range may be extended to the first encountered value if the interval is overlapped with the index interval. That is, if a node index value does not match the specified range value then the next smaller value (on minimum end) or larger value (on maximum end) in the index series should be used as the endpoint. This concept is designed to select ALL nodes whose index interval overlap with the query range. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. These values represent the state of a WITSML object. Actual data measured or entered at the well site. Model data used for "what if" calculations. A planned object. That is, one which is expected to be executed in the future. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. The type of Distributed Temperature Survey (DTS) fiber point. The list of standard values is contained in the PRODML enumValues.xml file. A point at which a fiber is physically, and semi-permanently, connected to another length of fiber. A point at which a cable connector is installed, which allows the fiber to be connected to another instrument or fiber length. The end of the fiber. If a U-geometry is used, and a connector is at both ends, the connector classification should be used rather than the end of fiber classification. The deepest point of the installed fiber in a well. This is a valid value for fiber installations that do NOT turn around at the bottom (J- and U-type installations). The point in the turn-around-sub at which measured depth stops increasing and begins decreasing. This is a valid value for fiber installations of the J- and U- type only. The start of the fiber. If appropriate, the connector classification should be used instead of this classification. The point on the fiber at which it enters the oven. The point on the fiber at which it exits the oven. The oven exit point should be closer to the wellbore than the oven entry point. A downhole point on the fiber at which a gauge is attached. The connector between the laser head and the optical fiber. The oven within or near the DTS instrument box which maintains a length of fiber at a reference temperature. Container in which ends of lengths of fiber are joined. The device at which a fiber originating at the instrument box is joined to a fiber installed in a wellbore. This is a recommended location at which LengthAlongFiber and measuredDepth in the wellbore are correlated The device at the base of the wellhead to which the production tubing is attached. This is a recommended location at which LengthAlongFiber and measuredDepth in the wellbore are correlated. The top-most point at which the fiber intersects the PBR (polished bore receptacle). For J- and U- installations, on the upward portion of the fiber, this is the point at which it leaves the pbf. The top of the electrical submersible pump (ESP). This is the minimum measured depth point of the pump. The base of the electrical submersible pump (ESP). This is the maximum measured depth point of the pump. Temperature measuring device at the wellhead independent of the optic fiber sensor. The point which is the minimum measured depth of a completion zone. The point which is the maximum measured depth of a completion zone. The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. An indicator of the quality of a value. This is designed for a SCADA or OPC style of value stasus. The token in parentheses are OPC's status string for the condition. The list of standard values is contained in the PRODML enumValues.xml file. The calibration status of the sensor is unknown. (Out of Calibration) The value is range limited, that is, at or near the end of range of the sensor. The value might be clamped. (Low Limited, High Limited) The value is just plain questionable. (Sub-Normal, Non-specific) The unit to which the sensor is attached is not running. (Device Failure) The field sensor itself is not working due to hardware failure or misconfiguration. (Sensor Failure) The communication to the field sensor is not working. That is, communcation cannot be established or maintained. (Comm Failure) Communication to the field sensor has timed out, that is, a connection exists, but a request for a field sensor data value has failed. (Last Known Value) The value is not known. This value should not be used in normal situations. All reasonable attempts should be made to determine the appropriate value. Use of this value may result in rejection in some situations. A timestamp value used for min/max query parameters related to "growing objects". The meaning of the endpoint of an interval can be modified by the endpoint attribute. The default is "inclusive". Values of "true" (or "1") and "false" (or "0"). A julian date. A date with the time of day and an optional time zone. While the time zone is optional, it is strongly advised that the zone always be specified in each date time value. A unitless quantity. This should not be confused with a dimensionless measure. A reference to a name in another node of the xml hierachy. This value represents a foreign key from one element to another. A reference to the unique identifier (uid attribute) in the node referenced by the name value. This attribute is required within the context of a WITSML server. A reference to a wellDatum in the current well. This value must match the uid value in a WellDatum. This value represents a foreign key from one element to another. This is an exception to the convention that a foreign key must utilize both a human contextual name and a uid value. For messages outside the context of a server then this value will commonly match the value of the name of the wellDatum (e.g., 'KB') if uids are not not used in that context. This was a compromise in order to allow the coordinate structures to be simple and still be usable both within the context of a server and outside the context of a server. A user assigned human recognizable contextual name of something. There should be no assumption that (interoperable) semantic information will be extracted from the name by a third party. This type of value is generally not guaranteed to be unique and is not a candidate to be replaced by an enumeration. A comment or remark intended for human consumption. There should be no assumption that semantics can be extracted from this field by a computer. Neither should there be an assumption that any two humans will interpret the information in the same way (i.e., it may not be interoperable). A community assigned human recognizable name. This type of value is intended to be unique and is generally a candidate to be constrained to an enumerated list. A locally unique identifier. The value is not intended to convey any semantic content (e.g., it may be computer generated). The value is only required to be unique within a context in a document (e.g., defined via key and keyref). There is no guarantee that the same data in multiple documents will utilize the same uid value unless enforced by the source of the document (e.g., a document server). A reference to the unique identifier of another element. This value represents a foreign key from one element to another. The value should match the value of an attribute of type uidString. The version of the schema. The first three levels are fixed. The fourth level can vary to represent the constraints defined in enumerations and XML loader files. The name of something within a naming system. The naming system within the name is (hopefully) unique. The name of something within a mandatory naming system with an optional code. The naming system within the name is unique. A unique (short) code associated with the name. A volume flow rate which may have a quality status. If the 'status' attribute is absent and the value is not "NaN", the data value can be assumed to be good with no restrictions. An indicator of the quality of the value. A volume flow rate which may have a quality status.. If the 'status' attribute is absent and the value is not "NaN", the data value can be assumed to be good with no restrictions. An indicator of the quality of the value. A measured depth coordinate in a wellbore. Positive moving from the reference datum toward the bottomhole. All coordinates with the same datum (and same uom) can be considered to be in the same Coordinate Reference System and are thus directly comparable. The unit of measure of the quantity value. A pointer to the reference datum for this coordinate value as defined in WellDatum. This value is assumed to match the uid value in a WellDatum. If not given then the default WellDatum must be assumed. The units of measure that are valid for measured depths in a wellbore. meter International Foot US Survey Foot A vertical (gravity based) elevation coordinate within the context of a well. Positive moving upward from the reference datum. All coordinates with the same datum (and same uom) can be considered to be in the same Coordinate Reference System and are thus directly comparable. The unit of measure of the quantity value. If not given then the default unit of measure of the explicitly or implicitly given datum must be assumed. A pointer to the reference datum for this coordinate value as defined in WellDatum. If not given then the default WellDatum must be assumed. The units of measure that are valid for vertical gravity based coordinates (i.e., elevation or vertical depth) within the context of a well. meter International Foot US Survey Foot British Foot 1865 A mass per mass measure that is constrained to a unit of percent. The number of moles as a proportion of the total number of moles measure that is constrained to a unit of percent.