semi合集-English.pdf - 第3523页
SEMI E134.1-0305 © SEMI 2005 10 <xs:element name =" Parent "> < xs:complexType > < xs:sequence > < xs:element name =" Child1 "/> < xs:complexType > < xs:sequence minOc…
SEMI E134.1-0305 © SEMI 2005 9
Figure 1
XML Schema Example Diagram
6.4 XML Schema Sample
6.4.1 The sample XML Schema for the example shown in Figure 1, is presented below. Refer to the XML
documentation referenced in ¶4.3 for a complete description of the syntax and semantics of XML Schema.
SEMI E134.1-0305 © SEMI 2005 10
<xs:element name="Parent">
<xs:complexType>
<xs:sequence>
<xs:element name="Child1"/>
<xs:complexType>
<xs:sequence minOccurs="0">
<xs:element name="Child1a"/>
<xs:element name="Child1b" maxOccurs="unbounded"/>
<xs:element name="Child1c" minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Child2">
<xs:complexType>
<xs:choice maxOccurs="2">
<xs:element name="Child2a"/>
<xs:element name="Child2b"/>
<xs:element name="Child2c"/>
</xs:choice>
</xs:complexType>
</xs:element>
<xs:element name="Child3">
<xs:complexType>
<xs:all>
<xs:element name="Child3a"/>
<xs:element name="Child3b"/>
</xs:all>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
Figure 2
XML for Sample
6.5 Translating UML to WSDL
6.5.1 In general, UML interface classes defined in the abstract specification are translated into WSDL as portType
definitions, and each portType definition has a corresponding WSDL binding definition. The following tables show
the convention used for documenting the WSDL port type and binding definitions for a given UML interface class.
Table 5 Example Interface WSDL Port Type Table
Class Name <UML interface name from abstract specification>
WSDL Port Type Name <port type name used in WSDL>
SEMI E125 Operation
WSDL Operation
<operation name from UML interface> <WSDL port type operation name>
Table 6 Example Interface WSDL Binding Table
SEMI E125 Class Name <UML interface name from abstract specification>
WSDL Binding Name <binding name used in WSDL>
SOAP Binding Style <RPC or document>
SOAP Transport <transport identifying URI>
SEMI E134.1-0305 © SEMI 2005 11
6.5.2 Each operation defined for a given UML interface class has a corresponding operation definition and binding.
Operations are described using a table format illustrated by Table 7 and Table 8.
Table 7 Example Operation Binding Table
SOAPAction <the SOAPAction HTTP header value to be used for this operation>
Input Headers (WSDL Message, Required)
<the name of the WSDL message providing input headers, and whether
or not the headers are required>
Output Headers (WSDL Message, Required)
<the name of the WSDL message providing output headers, and
whether or not the headers are required>
Table 8 Example PortType Operation Table
Input Message Name <WSDL message name used as input for the WSDL port type operation>
Output Message Name <WSDL message name used as output for the WSDL port type operation>
7 Mapping of E134 UML to XML Schema and WSDL
7.1 WSDL Organization
7.1.1 Each interface definition in SEMI E134 is mapped to a WSDL portType and binding definition. WSDL
portType definitions are named after the interface and its operations as they appear in SEMI E134. WSDL binding
definitions for each portType are used to specify the SOAP 1.1 envelope contents for each operation, and to define
the corresponding XML encoding styles and HTTP header usage. All SEMI E134 WSDL interfaces use
document/literal encoding, with the complete SOAP header and body contents defined in XML Schema file(s) via
global element definitions.
7.1.2 Figure 3 shows the relationship between the WSDL binding and portType definitions and the XML Schema
types used for each interface. The portType definition imports XML Schema type definitions used in each operation
via the XML Schema “import” statement. The WSDL binding definition imports the portType definition via the
WSDL “import” statement. Figure 4 shows the specific XML Schema and WSDL files defined for SEMI E134.
Figure 3
XML Schema and WSDL File Organization
con
E134 DataCollectionManager Interface
E134-1-
V
XXXX-Equipment-PortType.wsdl
E134-1-
V
XXXX-Client-PortType.wsdl
E134-1-
V
XXXX-Equipment-Binding.wsdl
E134-1-
V
XXXX-Schema.xsd
E134-1-
V
XXXX-Client-Binding.wsdl
E134 DPCConsumer Interface
Equipment
E134 Client
Figure 4
WSDL and XML Schema Files for SEMI E134