semi合集-English.pdf - 第7871页

SEMI T13-1104 © SEMI 2004 31 List 4 XML Messagin g Envelope Example 1 <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope xmlns: SOAP-ENV= " http://schemas.xmlsoap.org/soap/envelop…

100%1 / 7923
SEMI T13-1104 © SEMI 2004 30
RELATED INFORMATION 2
AN EXAMPLE OF ENVELOP AND HEADERS FOR XML
COMMUNICATION
NOTICE: This related information is not an official part of SEMI T13 and was derived from the Japanese
Traceability Committee. This related information was approved for publication by full letter ballot on April 30,
2004.
R2-1 Message Encapsulation in Envelopes
R2-1.1 Message Envelope — Communicating messages for Die Trace Data in this document with eXtensible
Markup Language (XML) is one of effective choice. Such XML communication protocols as Simple Object Access
Protocol (SOAP) and XML-RPC (Remote Procedure Call) are very popular in this industry. In such protocols,
messages are structured and encapsulated in such lower level protocol as Hyper Text Transfer Protocol (HTTP). The
encapsulation is referred to as Envelope. Actual message header and body are filled in the envelop. This related
information introduces some example of the envelopes in the following sections.
R2-2 Placing Message Name in Header with Message Parameters in Body
R2-2.1 Regular SOAP or XML-RPC Messaging — If message has no possibility to have binary value as its
parameter, regular XML messaging is often used. It is typical to have message name in header and parameters in
body as shown in the following list.
R2-2.1.1 SEMI E128 Style Data Report — The following list shows an example of regular XML messaging
envelope in accordance with SEMI E128 “Specification for XML Message Structure” for the service ‘takeDTD’ of
Die Tracer. Service name is enclosed in element ‘Action’ of SOAP Header and message parameters are enclosed in
element ‘data’ of SOAP Body. SOAP Fault may be appended in the SOAP Body if SOAP communication error
happens.
SEMI T13-1104 © SEMI 2004 31
List 4 XML Messaging Envelope Example 1
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=
"http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<MessageHeader xmlns="urn:semi-org:schema:xmlmsg:E128:0703"
elementFormDefault="qualified">
<From>MdmAbc001</From>
<To>DtHalNykA012</To>
<MessageType>REQUEST</MessageType>
<RequestId>123456</RequestId>
<Action>takeDTD</Action>
<ReplyExpected>true</ReplyExpected>
</MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<data>
<
DeviceIdData xmlns="urn:semi-org:xsd.Doc3754.V0312.DeviceIdData">
<
SubstrateType>Strip</SubstrateType>
<
SubstrateId>MyStrip</SubstrateId>
<
LayoutId>Device</LayoutId>
<
OriginLocation>LowerLeftTop</OriginLocation>
<
RowColumnMajor>Column</RowColumnMajor>
<
D><Id></Id></D>
<
D><Id></Id></D>
<
D><Id></Id></D>
<
D><Id>Lot001-XXYY</Id></D>
<
D><Id>etc.</Id></D>
</
DeviceIdData>
</data>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
NOTE 1: The above list is just an example and some details may not be fully compliant to SEMI E128 or related documents.
SEMI T13-1104 © SEMI 2004 32
R2-3 Placing Message Name and Parameters in the Second MIME Block
R2-3.1 Messaging with Attachment — If message may have binary value in its parameter, an attachment may be
required. If transferred data is binary format, some contrivance to encode the data is necessary unless the data is
transferred separately by another means: e.g. binary file transfer. This case XML Message has an attached block for
the data.
R2-3.1.1 IPC-2501 Style Data Report — The following list shows an example of XML messaging envelope with
attachment in accordance with IPC 2501 “Definition of Web-Based Exchange of XML Data (Message Broker)” for
the service ‘takeDTD’ of Die Tracer. SOAP Envelope in the first MIME Block has just message’s information in
element ‘MessageInfo’ of SOAP Header and SOAP Fault in SOAP Body if it is required. Message name and
message parameters are encapsulated in the second MIME Block.
List 5 XML Messaging Envelope Example 2
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-
ENV="http://schemas.xmlsoap.org/soap/envelope/"
elementFormDefault="qualified">
<SOAP-ENV:Header>
<MessageInfo xmlns:IPC2501MI=
"http://webstds.gatech.edu/2501/MessageInfo.xsd"
elementFormDefault="qualified"
dateTime
= "2003-03-27T15:54:17.02-05:00"
sender= "MdmAbc001"
destination= "DtHalNykA012"
messageId= "123456"
messageSchema= "takeDTD">
</MessageInfo>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
- - - Second MIME Block
<?xml version="1.0" encoding="UTF-8"?>
<takeDTD xmlns:TxxxDtTD=
"urn:semi-org:TC-Schema:Txxx:0704:DTO-TDS"
elementFormDefault="qualified"
dateTime
= "2003-03-27T15:54:17.02-05:00">
<
DeviceIdData xmlns="urn:semi-org:xsd.Doc3754.V0312.DeviceIdData">
<
SubstrateType>Strip</SubstrateType>
<
SubstrateId>MyStrip</SubstrateId>
<
LayoutId>Device</LayoutId>
<
OriginLocation>LowerLeftTop</OriginLocation>
<
RowColumnMajor>Column</RowColumnMajor>
<
D><Id></Id></D>
<
D><Id></Id></D>
<
D><Id></Id></D>
<
D><Id>Lot001-XXYY</Id></D>
<
D><Id>etc.</Id></D>
</
DeviceIdData>
</takeDTD>
NOTE 2: Above list is just an example and some details may not be fully compliant to IPC-2501 or related documents.