|
|
|
James P. Taylor |
|
GE Aircraft Engines |
|
|
|
|
This Working group was assigned the task of
applying XML tag identification and functionality to SPEC2000 messages. |
|
Also the XML “cross reference” is not to alter
the current definition and processes of SPEC2000. |
|
In addition the XML is to be neither a
conversion nor a translation to/from SPEC2000. |
|
|
|
|
|
|
|
|
|
|
A SPEC2000/XML Command Code is composed of a
series of identifiers which extend their specific meaning as defined in the
SPEC2000 standard. |
|
|
|
Identification is as follows: |
|
An 8 character identifier (Example 'Y1TTTAAA')
consisting of |
|
(pos.
1) 'Y' = Code identifying
function identifying 'S' =
Spares, 'R' =
Repair, ' W' = Warranty, |
|
(pos.2) '1' =
(constant value) |
|
(pos. 3-5)
'TTT' = Message Type (e.g.,
'INV' = invoice) |
|
(pos. 6-8)
'AAA' = Message Action
(e.g., 'XMT' = Transmission, "INQ" = Inquiry, “ACK” = ACK) |
|
The XML Command Code as described here is valid
for SPEC2000 messages only; it does not apply to SPEC2000 files (e.g., S/T
Files, V File, Procurement Planning files, etc.). |
|
|
|
|
|
S1BOOKED
==== S1CPOXMT. |
|
S1BOOKED Ack ==== S1CPOACK. |
|
|
|
|
The XML “TAG” or “TEI” in SPEC2000 ties to the
Common Support Data Dictionary DTD where a definition can be obtained. |
|
|
|
|
|
|
The SPEC2000 Header is provided for passing
Optional IATA addressing information and for Rejecting Documents. |
|
|
|
|
|
The XML Working group had a great deal of
discussion on the delivery of XML. |
|
There are many methods to deliver XML and today
there is no real leader. The group
decided to provide examples but not to make a recommendation at this time. |
|
Examples |
|
AS2 |
|
SOAP |
|
HTTPS – (GE provided a proprietary example) |
|
|
|
|
The XML working group Defined a XML
representation of SPEC2000 |
|
All current business rules in SPEC2000 are
transferred to this new standard. |
|
GE Aircraft Engines is currently doing XML with
some airlines. |
|
Other Suppliers have implemented certain
messages. |
|
|
|
|
|
Notes