BLM 3160 XML Samples

The types of information supported by this specification include:

• Well Drilling Permits
• Drilling and Well Status Permits
• Sundry Well Activity Permits and Reports
• Completion Reports

This transaction set was constructed to carry the data required on a large number of regulatory forms defined by various U.S. states, the MMS and the BLM. The BLM forms used in these samples are typical of many regulatory reporting forms used throughout North America.

XML

The sample files presented here are based upon the Extensible Markup Language (XML) family of specifications from the W3C. The following components of XML are illustrated here:

• Document Type Definition (DTD) - a language that defines the structure and content rules for an XML file; this defines what the XML tags are, how the tag hierarchy is structured, and how the tags used
• Sample XML file - a file using the XML tags; these files contain the data values delimited by the tags defined in the DTD
• XSL Transformation (XSLT) - a language for transforming XML documents into other XML (and HTML) documents; this describes how to format and display the sample XML data file in these samples

These components illustrate how XML is designed to separate content from presentation for defined sets of structured data. 

BLM Forms

Notice of Staking (NOS)

A notice of staking (NOS) allows the operator to request an on-site inspection prior to filing an application for permit to drill (APD). This also initiates several informational procedures, including a 30 day public notification, which may result in a more rapid approval for a subsequent APD.

• Original NOS Form
• NOS Form XML DTD
• Sample XML file
• XSL Transformation file
• The result of applying the XSLT to the sample XML file
  [Note: appearance differs by browser]

3160-3 Application for Permit to Drill (APD)

BLM Form 3160-3 is an application for permit to drill (APD). Drilling operations or related construction activities may not be conducted without an BLM approved APD. A complete APD consists of a drilling plan (comprised of a surface use program and a drilling program), evidence of bond coverage, and such other information as may be required (e.g., H2S Contingency Plans where needed).

• Original Form 3160-3
• Form 3160-3 XML DTD
• Sample XML file
• XSL Transformation file
• The result of applying the XSLT to the sample XML file
  [Note: appearance differs by browser]

3160-4 Well Completion or Recompletion Report and Log

BLM Form 3160-4 is used for reporting initial well completions and recompletions. A Form 3160-4 is required to be filed within 30 days after completion of a well either for abandonment or production. The completion report is to reflect the mechanical and physical condition of the well. Geologic information and, when applicable, information on the completed interval and production is required.

• Original Form 3160-4
• Form 3160-4 XML DTD
• Sample XML file
• XSL Transformation file
• The result of applying the XSLT to the sample XML file
  [Note: appearance differs by browser]

Discussion

DTD vs. XML Schema

The specifications used to describe these three BLM forms were DTDs. The DTD is well suited to the "document-centered" description of data, such as illustrated here. From this base, the XML community is developing a more "information-centered" descriptions using XML Schema as a replacement for the DTD. While XML Schemas represents a significant improvement over DTDs, the basic architecture illustrated in these files are unchanged.

Local vs. General Specifications

Each of these DTDs represents a very specific expression of vocabulary and structure that is specific to a form. While some XML tags and structures are common to all three forms, some tags are unique to one form and others are used differently in each form. While many data values are identical between the forms, inevitable differences will result from the different ways these data values are used. These differences are greater as the uses are more diverse.

The BLM defines the content of each form based upon business processes that accomplish specific objectives. These XML files reflect these requirements indirectly. Additional, higher level requirements may be added to effect improved sharing of data between forms. This results in a generalization of the specifications, creating a more general specification like the ANSI X-12 625 transaction set.

The trade-off between local efficiency and general effectiveness is an issue of XML specification design. In XML, however, it is practical to create separate specifications at each level and move data between them using XSL Transformations. This allows very specific DTDs, like the ones for these forms, to be designed and used for specific uses (business processes) rather than forcing one specification for all uses.

The movement of data from a general to a specific structure removes some data which may not be recoverable later (this is "data rot"). This loss should be minimized when building XML specifications whenever possible. It is the role of standards to facilitate efforts towards this goal.