semi合集-English.pdf - 第7884页

SEMI T13.2-1104 © SEMI 2004 4 Parameter Name Attribute/Element Type Remarks linkCnt Attribute integer extended for delayed response linkExp Attribute duration extended for delayed response 7.4 Example XML Message Fragmen…

100%1 / 7923
SEMI T13.2-1104 © SEMI 2004 3
Service Message Name Supporting Class Service Message Element
Name Base
Remarks
logException DieTraceManager LogException
planDTD DieTracer PlanDTD
registerTracer DieTraceMachine RegisterTracer
resign DieTraceManager Resign
setAlert DieTraceClient SetAlert
setForward DieTracer SetForward
setPlanningItems DieTraceMachine SetPlanningItems
showData DieTraceData ShowData
showDaughter CircuitModule ShowDaughter
showDTD DieTracer ShowDTD
showPhenomena DieTraceClient ShowPhenomena
showProperty CircuitModule, DieTraceData ShowProperty
takeDTD DieTracer TakeDTD
7.2 Service Parameter Mapping — Service parameter type mapping is shown in the following table.
Table 2 Service Parameter Type Mapping
Parameter Name Attribute/Element Type Remarks
Alert Element anyType Formatted Text
Clarifier Element string
DataName Element string
DataNameList Element string Repeating DataName
DataValue Element anyType Formatted Text
Designation Element string
Exceptions Element anyType Formatted Text
MachineType Element string
ManagingTracer Element string
Phenomena Element anyType Formatted Text
Property Element anyType Formatted Text
ServiceStatus Element complexType status+Rejection
Target Element string
TraceData Element anyType Formatted Text
Tracer Element string
Tracers Element string Repeating Tracer
7.3 Additional Parameters for Service Messages — Because this protocol mapping works for asynchronous HTTP
server-client communication on message broker, such additional parameters to give complementary information as
issued time and transaction identification are required to be attached to each message. The information may be
dependent to the role of the message. Type mapping of them are shown in the following table.
Table 3 Type Mapping of Additional Parameters
Parameter Name Attribute/Element Type Remarks
dateTime Attribute dateTime
sessionId Attribute string
sessionRef Attribute string
requestId Attribute string
requestRef Attribute string
linkId Attribute string extended for delayed response
SEMI T13.2-1104 © SEMI 2004 4
Parameter Name Attribute/Element Type Remarks
linkCnt Attribute integer extended for delayed response
linkExp Attribute duration extended for delayed response
7.4 Example XML Message Fragments — The following subsections give examples of some fragments of service
messages in XML. A full message is given with envelops and headers.
7.4.1 showProperty Request — The following XML description is an example of the principal part of service
request message for showProperty provided by CircuitModule objects. Because the Designation of parameters for a
CircuitModule is dependent to the circuit module and tracing objectives, they should be discussed between trace
data provider and consumer.
<ShowPropertyRequest dateTime=”2004-03-29T13:05:25.000-08:00”
SessionRef=”SemiDtQs-9876543210” RequestId=”123456”>
<Designation>Id</Designation>
<Designation>Type</Designation>
<Designation>ProductName</Designation>
<Designation>Lot</Designation>
</History>
</ShowPropertyRequest>
7.4.2 showPhenomena Response — The following XML description is an example of the principal part of service
response message for showPhenomena provided by DieTraceClient objects. Detail information of argument
“Phenomena” is not specified in the standard because it’s dependent to target product. Additional definition should
be exchanged in the system.
<ShowPhenomenaResponse dateTime=”2004-03-29T09:07:59.000-08:00”
SessionRef=”SemiDtQs-9876543123” RequestRef=”123443” status=”GRANTED”>
<Phenomena>
<Registered>2004-03-26T18:07:51.000-08:00<Registered>
<Product>meson689-4A</Product>
<Problem>Noise sensitive</Problem>
<Problem>Restarted Occasionally</Problem>
<Application>Office Computers</Application>
</Phenomena>
<ServiceStatus>
<SvcAck>Successful</SvcAck>
</ServiceStatus>
</ShowPhenomenaResponse>
SEMI T13.2-1104 © SEMI 2004 5
APPENDIX 1
APPENDIX TITLE
NOTICE: The material in this appendix is an official part of SEMI T13.2 and was approved by full letter ballot
procedures on July 23, 2004.
A1-1 XML Message Schema
A1-1.1 XML Schema — XML Schema is a kind of
template for documents. The following XML Schemas
shows how messages in this XML protocol are
represented.
A1-1.1.1 Message Schema — Each message in T12
has one XML Schema. Parsing with the schema,
application can understand what elements and attributes
mean. Also it can check syntax easily.
A1-1.1.2 Common Definitions — Common part of the
schema is separated and it is included in each message
schema.
A1-1.2 Enumeration — Attachment specific or
eqiopment specific enumeration may not be addressed
here. Corresponding part of the shema should be
extended or restricted with ‘redefine’ element, for
example, in application schema.
XML Message Schema Name: T13ShowDaughterRequestCmo.xsd for CircuitModule Class
<xsd:schema xmlns:xsd=”
http://www.w3.org/2001/XMLSchema”
xmlns:jit=”
http://www.semi.org/Traceability/T13.2-V01”
targetNamespace=”
http://www.semi.org/Traceability/T13.2-V01”
elementFormDefault="qualified" attributeFormDefault="qualified">
<xsd:include
schemaLocation="http://www.semi.org/Traceability/T13.2-V01/CommonDefinitions"/>
<!-- - - - - - - - Show Daughter Request - - - - - - - - - - - - - - -->
<xsd:element name="ShowDaughterRequest" type="ShowDaughterRequestType"/>
<xsd:complexType name="ShowDaughterRequestType">
<xsd:attributeGroup ref="RegRequestAttr"/>
</xsd:complexType>
</xsd:schema>
XML Message Schema Name: T13ShowDaughterResponseCmo.xsd for Circuit Module Class
<xsd:schema xmlns:xsd=”
http://www.w3.org/2001/XMLSchema
”
xmlns:jit=”
http://www.semi.org/Traceability/T13.2-V01”
targetNamespace=”http://www.semi.org/Traceability/T13.2-V01”
elementFormDefault="qualified" attributeFormDefault="qualified">
<xsd:include
schemaLocation="http://www.semi.org/Traceability/T13.2-V01/CommonDefinitions"/>
<!-- - - - - - - - - Show Daughter Response - - - - - - - - -->
<xsd:element name="ShowDaughterResponse" type="ShowDaughterResponseType"/>
<xsd:complexType name="ShowDaughterResponseType">
<xsd:sequence>
<xsd:element name="Clarifier" type="xsd:string" minOccurs="0"
maxOccurs="unbounded"/>
<xsd:element name="ServiceStatus" type="ServiceStatusType"/>
</xsd:sequence>
<xsd:attributeGroup ref="RegResponseAttr"/>
</xsd:complexType>
</xsd:schema>