Energistics PRODML v1.3 Data Schema Files

This version represents redefinition of the Distributed Temperature Survey (DTS) model to the v1.2.2 Data Schema. This version is backward-compatible except for DTS components.

This file and all of the files associated with this version of the PRODML Data Schema can be downloaded via a Zip file. This document describes the file content of folder ./prodml_v1.3_data/ in the zip structure. Folder ./abstract_v1.0/ contains a required abstract schema which is used across multiple Energistics domains. Folder ./aggregate_1.0/ contains an optional schema which can be used to collect data from multiple Energistics domains.

File ./doc/PRODML_schema_overview.html represents the browsable overview documentation.

Normative Files

The normative data schema specification consists of the following files.

• ./xsd_schemas/*.xsd

and the content of files:

• ./ancillary/enumValuesProdml.xml [PRODML standard instance values (enumeration loader file)]
• ./ancillary/enumValues.xml [WITSML standard instance values (enumeration loader file)]
• ./ancillary/witsmlUnitDict.xml [Unit of measure acronyms and their conversion factors.]

The schema files assume that the Energistics abstract schema is copied into the proper relative folder structure. The above zip file will include a copy of the abstract schema in the proper location.

Variant Schemas

The following files represent generated variants of the normative data schemas. These files are only normative when used within the context of a web service. The PRODML GDA should use the read schemas while the WITSML API will use the read, write and update schemas.

• ./generated_read_schemas/*.xsd
• ./generated_write_schemas/*.xsd
• ./generated_update_schemas/*.xsd
• ./generated_delete_schemas/*.xsd

Read Schemas

The generated read schema files are a copy of the normative files except that all elements and attributes are optional. Just as in SQL, mandatory data is not required to be requested. If used within a WITSML web service, these schema files must represent the XMLout response from the WITSML WMLS_GetFromStore method.

Write Schemas

The generated write schema files are a copy of the normative files except that some unique identifier attributes have had their optionality changed. If used within a WITSML web service, these schema files must represent the XMLin input to the WITSML WMLS_AddToStore method.

Update Schemas

The generated update schema files are a copy of the normative files with all elements and attributes optional except that all unique identifier attributes and uom attributes are mandatory. If used within a WITSML web service, these schema files must represent the XMLin input to the WITSML WMLS_UpdateInStore method.

Delete Schemas

The generated delete schema files are a copy of the normative files with all elements and attributes optional except that all object and parentage uids are mandatory. If used within a WITSML web service, these schema files must represent the QueryIn input to the WITSML WMLS_DeleteFromStore method.

Non-normative files

The following files are informative and are not part of the normative specification.

• ./index_prodml_schema.html [This file.]
• CHANGE_DETAIL_PRODML.TXT [A detailed change history within this release cycle. A change summary is available from the browsable overview.]
• ./doc/*.*
• ./doc/schema/*.html [Represent browsable versions of the ./xsd_schemas/*.xsd files and are referenced from the browsable overview file.]
• ./xml_examples/*.* [An example XML file for each data object. These examples do not represent a best-practice.]
• ./ancillary/PRODML_V1.3_content.xlsx [A spreadsheet representing the content of the XSD files.]
• ./ancillary/witsmlUnitDict.html [A browsable version of witsmlUnitDict.xml]
• ./ancillary/WITSML_Abbreviations.html [A list of abbreviations contained in the schema names.]
• ./ancillary/cs_enumValues.xsd [A schema for the enumValues files.]
• ./ancillary/Units.xsl [A stylesheet for the witsmlUnitDict.xml file.]
• ./xsd_schemas/sub_objectMemberProdml.xsd [An example file for use with the Energistics aggregate specification.]