semi合集-English.pdf - 第7838页

SEMI T12.2-0704 © SEMI 2004 67 <enumeration value="GRANTED"/> <enumeration valie="REFUSED"/> </xsd:restriction> </xsd:simpleType> </xsd:schema>

100%1 / 7923
SEMI T12.2-0704 © SEMI 2004 66
<xsd:complexType name="HistoryIndexType">
<xsd:sequence>
<xsd:element name="Id" type="xsd:string"/>
<xsd:element name="Type" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<!-- Genaric Types - - - - Generic Types - - - - Generic Types - - -->
<xsd:complexType name="NamedValueType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="Value" type="xsd:anyType"/>
</xsd:sequence>
</xsd:complexType>
<!-- Service Status Type - - - - - Service Status Type - - -->
<xsd:complexType name="ServiceStatusType">
<xsd:sequence>
<xsd:element name="SvcAck" type="SvcAcktype"/>
<xsd:element name="SvcErr" type="SvcErrType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="SvcAckTye">
<xsd:restriction base="xsd:string">
<enumeration value="Successful"/>
<enumeration value="Wrong Service"/>
<enumeration value="Refused"/>
<enumeration value="Invalid Parameter"/>
<enumeration value="Has started"/>
<enumeration value="Unsuccessful"/>
<enumeration value="Wrong object"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexType name="SvcErrType">
<xsd:sequence>
<xsd:element name="SvcErrCode" type="xsd:integer"/>
<xsd:element name="SvcErrText" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<!-- Attributes - - - - - Attributes - - - - - - Attributes - - -->
<xsd:attributeGroup name="RegRequestAttr">
<xsd:attribute name="dateTime" type="xsd:dateTime" use="required"/>
<xsd:attribute name="sessionRef" type="xsd:string" use="required"/>
<xsd:attribute name="requestId" type="xsd:string" use="required"/>
</xsd:attributeGroup>
<xsd:attributeGroup name="RegResponseAttr">
<xsd:attribute name="dateTime" type="xsd:dateTime" use="required"/>
<xsd:attribute name="sessionRef" type="xsd:string" use="required"/>
<xsd:attribute name="requestRef" type="xsd:string" use="required"/>
<xsd:attribute name="status" type="RspStatus" use="required"/>
<xsd:attribute name="authority" type="xsd:string" use="optional"/>
<xsd:attribute name="linkId" type="xsd:string" use="optional"/>
<xsd:attribute name="linkCnt" type="xsd:integer" use="optional"/>
<xsd:attribute name="linkExp" type="xsd:duration" use="optional"/>
</xsd:attributeGroup>
<xsd:simpleType name="RspStatus">
<xsd:restriction base="xsd:string">
SEMI T12.2-0704 © SEMI 2004 67
<enumeration value="GRANTED"/>
<enumeration valie="REFUSED"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:schema>
SEMI T12.2-0704 © SEMI 2004 68
RELATED INFORMATION 1
IPC MESSAGING MECHANISM and STRUCTURE
NOTICE: This related information is not an official part of SEMI T12.2 and was derived from the Japanese
Traceability Committee. This related information was approved for publication by full letter ballot on April 30,
2004.
R1-1 HTTP and SOAP Envelope
R1-1.1 The following diagram illustrates HTTP message border and SOAP Envelope structure. SOAP Header
contains information of the message and SOAP body just contains SOAP Faults to make sure what happens when
something wrong. Intended message service and its parameters are contained in second MIME Block to make it
possible to allow mixture of non-XML data.
R1-2 Communication with Message Broker
R1-2.1 The following diagrams show client-server communications with Message Broker.
HT TP 1.1
SOAP wit h MI ME Envelope
MI ME Block
MI ME Block
Mess age N ame and Par amet er s
SOAP Envelope
SOAP Body
SOAP Header
SOAP Fault s
Me s s ag e I n f o r ma t i on
Figure R1-1
SOAP Envelope and MIME Blocks