semi合集-English.pdf - 第7777页

SEMI T12.2-0704 © SEMI 2004 6 APPENDIX 1 XML SCHEMA NOTICE : The material in this appendix is an official part of SEMI T12.2 and was approved by full letter b allot procedur es on April 30 , 2004. A1-1 XML Message Schema…

SEMI T12.2-0704 © SEMI 2004 5

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

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 envelopes and headers.

7.4.1 addEvent Request — The following XML description is an example of the principal part of service request

message for addEvent provided by HistoryRecord objects. Because the structure of parameter ‘History’ is dependent

to event, attachment type and equipment, the standard doesn’t define it. Suppliers are required to define the structure

or negotiate with specific user. Users need to discuss with suppliers or interpret their structures.

<AddEventRequest dateTime=”2004-03-29T13:05:25.000-08:00”

SessionRef=”SemiJitQs-9876543210” RequestId=”123456”>

</ HistoryIndex>

<Event>

<EventClass>Milestone</EventClass>

</NamedValue>

<Event>

</History>

</AddEventRequest>

7.4.2 showTypes Response — The following XML description is an example of the principal part of service

response message for showTypes provided by Invoice objects.

<ShowTypesResponse dateTime=”2004-03-29T09:07:59.000-08:00”

SessionRef=”SemiJitQs-9876543123” RequestRef=”123443” status=”GRANTED”>

<SvcAck>Successful</SvcAck>

</ServiceStstus>

</ShowTypesResponse>

SEMI T12.2-0704 © SEMI 2004 6

APPENDIX 1

XML SCHEMA

NOTICE: The material in this appendix is an official part of SEMI T12.2 and was approved by full letter ballot

procedures on April 30, 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: T12ChangeNameRequestAtt.xsd for Attachment Class

<xsd:schema xmlns:xsd=

http://www.w3.org/2001/XMLSchema

xmlns:jit=

http://www.semi.org/Traceability/T12.2-V01

targetNamespace=

http://www.semi.org/Traceability/T12.2-V01

elementFormDefault="qualified" attributeFormDefault="qualified">

<xsd:include

schemaLocation="http://www.semi.org/Traceability/T12.2-V01/CommonDefinitions"/>

<xsd:element name="ChangeNameRequest" type="ChangeNameRequestType"/>

<xsd:complexType name="ChangeNameRequestType">

<xsd:sequence>

<xsd:element name="AttachmentName" type="xsd:string"/>

</xsd:sequence>

<xsd:atributeGroup ref="RegRequestAttr"/>

</xsd:complexType></xxx>

</xsd:schema>

XML Message Schema Name: T12ChangeNameResponseAtt.xsd for Attachment Class

<xsd:schema xmlns:xsd=

http://www.w3.org/2001/XMLSchema

xmlns:jit=http://www.semi.org/Traceability/T12.2-V01

targetNamespace=http://www.semi.org/Traceability/T12.2-V01

elementFormDefault="qualified" attributeFormDefault="qualified">

<xsd:include

schemaLocation="http://www.semi.org/Traceability/T12.2-V01/CommonDefinitions"/>

<xsd:element name="ChangeNameResponse" type="ChangeNameResponseType"/>

<xsd:complexType name="ChangeNameResponseType">

<xsd:sequence>

<xsd:element name="AttachmentName" type="xsd:string" minOccurs="0" maxOccurs="1"/>

SEMI T12.2-0704 © SEMI 2004 7

<xsd:element name="ServiceStatus" type="ServiceStatusType"/>

</xsd:sequence>

<xsd:atributeGroup ref="RegResponseAttr"/>

</xsd:complexType>

</xsd:schema>

XML Message Schema Name: T12ShowHistoryRequestAtt.xsd for Attachment Class

<xsd:schema xmlns:xsd=

http://www.w3.org/2001/XMLSchema

xmlns:jit=

http://www.semi.org/Traceability/T12.2-V01

targetNamespace=

http://www.semi.org/Traceability/T12.2-V01

elementFormDefault="qualified" attributeFormDefault="qualified">

<xsd:include

schemaLocation="http://www.semi.org/Traceability/T12.2-V01/CommonDefinitions"/>

<xsd:element name="ShowHistoryRequest" type="ShowHistoryRequestType"/>

<xsd:complexType name="ShowHistoryRequestType">

<xsd:sequence>

<xsd:element name="Items" type="xsd:string" minOccurs="0" maxOccurs="unbounded”

<xsd:element name="Restriction" type="xsd:string" minOccurs="0"

maxOccurs="unbounded"/>

xsd:sequence>

<xsd:atributeGroup ref="RegRequestAttr"/>

</xsd:complexType>

</xsd:schema>

XML Message Schema Name: T12ShowHistoryResponseAtt.xsd for Attachment Class

<xsd:schema xmlns:xsd=

http://www.w3.org/2001/XMLSchema

xmlns:jit=

http://www.semi.org/Traceability/T12.2-V01

targetNamespace=

http://www.semi.org/Traceability/T12.2-V01

elementFormDefault="qualified" attributeFormDefault="qualified">

<xsd:include

schemaLocation="http://www.semi.org/Traceability/T12.2-V01/CommonDefinitions"/>

<xsd:element name="ShowHistoryResponse" type="ShowHistoryResponseType"/>

<xsd:complexType name="ShowHistoyResponseType">

<xsd:sequence>

<xsd:element name="History" type="HistoryType" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element name="ServiceStatus" type="ServiceStatusType"/>

</xsd:sequence>

<xsd:atributeGroup ref="RegResponseAttr"/>

</xsd:complexType>

</xsd:schema>

XML Message Schema Name: T12ShowIdRequestAtt.xsd for Attachment Class

<xsd:schema xmlns:xsd=

http://www.w3.org/2001/XMLSchema

xmlns:jit=http://www.semi.org/Traceability/T12.2-V01