Petroleum Industry Data Exchange (PIDX) Committee
GCIMT IT Security Forum PIDX Telecommunications Finance & Accounting

  API Staff Contact:

  Desiree Burnley
  American Petroleum Institute
  1220 L Street, NW
  Washington, DC 20005-4070
  P: 202-682-8504
  F: 202-682-8207
  E: burnleyd@api.org
   My API Committees  |  Business and Information Technology Committees  
    |  Updated: 7/27/05 12:21 PM [Image: Printer Friendly version.] Print version

  PIDX Standards

  PIDX Organization
  PIDX Members
  Upcoming Events
  Latest News
  Past Events & Results
  Issues/Documents
  PIDX Standards
  Rosters
  PIDX Subcommittees
  Specific Interest Groups

 
 


Click here to Download the Feb 2006 PIDX 3901 Publication.


===================================
PIDX 3901 Publication Release Notes
===================================

The following materials are included with the February, 2006 Publication of the PIDX 3901 Specification:

------------------------------------
This contains the PIDX XML Schema files which are the core of the PIDX XML specification. These XML Schema files define the data structures that PIDX implementers share via XML messages. Each XML Schema file is suffixed with a '.xsd' file extension (xsd stands for 'XML Schema Definition'). XML instance documents created to conform to these XML Schema will have the extension '.xml'

------------------------------------
PIDX_XMLUsageGuideline_InvoiceResponse_v1.pdf

This document provides guidelines regarding how the new version of the InvoiceResponse.xsd file should be used. The XML Schema was modified to meet some of the shortcomings previously identified, namely:
- Invoice acceptance or rejection should be flagged at the Invoice Response Properties (i.e. header) level.
- The schema should support the reporting of errors identified in the original invoice header.
- Line item status reporting should be optional and not mandatory.
- InvoiceResponseNumber usage needs to be clarified.

------------------------------------
PIDX_3901_VersioningTable.pdf

This document provides a snapshot of each XML Schema file in the PIDX 3901 specification and its associated version. This document will be maintained going forward with all future PIDX 3901 specification release(s). Each XML Schema file contains a version specific to that file. As of the February, 2006 release XML Schema version information is no longer captured in XML Schema namespace(s).

PIDX AS2 Usage Guideline v1.2

In addition to developing and maintaining standards for XML business document payloads, BMWG is responsible for Transport, Routing, and Packaging (TRP) protocols. The RosettaNet Implementation Framework (RNIF) version 2.0 was the first TRP to be approved for use in PIDX recommended practices. While fully-featured, RNIF has proven to be too costly and complex for smaller enterprises in the oil and gas industry to adopt. The AS2 protocol provides a more lightweight protocol for these smaller organizations and wraps business message payloads in a lightweight envelope, and transports them using HTTP or HTTPS. This document outlines the suggested use of the AS2 protocol within PIDX implementations.

------------------------------------
Summary of Modifications

- The InvoiceResponse XML Schema was redesigned to indicate acceptance or rejection at the invoice response properties level. Also, line item status. Several other minor modifications were included.

- The BillOfLadingCreate and BillOfLadingResponse XML Schema files are new with this release and have been developed within the PIDX Downstream subcommittee.

- The PIDXLib and PIDXCodeLists XML Schema files have been modified to support these changes and additions.

=======
Note(s)
=======

Excerpts from the W3C XML Schema Primer:

"In an instance document, the attribute xsi:schemaLocation provides hints from the author to a processor regarding the location of schema documents. The author warrants that these schema documents are relevant to checking the validity of the document content, on a namespace by namespace basis."

"The schemaLocation attribute contains pairs of values: The first member of each pair is the namespace for which the second member is the hint describing where to find to an appropriate schema document. The presence of these hints does not require the processor to obtain or use the cited schema documents, and the processor is free to use other schemas obtained by any suitable
means, or to use no schema at all."

PIDX RP3901 Transaction Standards Click here to view PIDX RP3901 Transaction Standards


PIDX Classification Standards
Access the PIDX Product Classification Codes & Service component Standards Website
.
PIDX EDI Standards
Download PDF files of PIDX EDI Standards.


The Petroleum Industry Data Dictionary (PIDD)

The dictionary of common industry terms to facilitate eBusiness.


Common Industry Material Identification Standards (CIMIS)

CIMIS codes are common identifiers and standard descriptions for commodity materials utilized in maintenance, operations, construction, and OEM activities.

Proposed Standards/Proposed Standards Revisions
Check out proposed PIDX standards and proposed revisions to existing PIDX standads.


API Standards, Publications and Services
This link takes you to a copy of the API Publication Catalog. API eBusiness standards are described in the Subscriptions, Software, and Information Technology Section (Electronic Data Exchange subsection). To order publications, visit the site of API's primary distributor - Global Engineering.


PIDX Standards Subcommittee

This link takes you to the PIDX Standards Committee home page. It provides information on the committee and PIDX standards.

API Procedures for Standards Development
As API's ebusiness Standards body, PIDX must comply with API procedures for standards development (pdf/file size = 150kb).



Back to Top

 
       
Helping You Get The Job Done Right.    Get Adobe Acrobat Reader  

  Antitrust Guidelines | Privacy Policy | Terms and Conditions | Copyright

  © 2005 - American Petroleum Institute. All rights reserved.
  1220 L Street, NW • Washington, DC 20005-4070 USA • 202-682-8000