semi合集-English.pdf - 第3189页

SEMI E125.1-0305 © SEMI 2005 43 Table 87 Metada taClient PortType Definitions File Name E125-1-V0305-MetadataCl ient-PortTy pe.wsdl Target Namespace urn:semi-org:ws.E125-1.V0305.esdMetaClt-portType Imported/Referenced Na…

100%1 / 7923
SEMI E125.1-0305 © SEMI 2005 42
Table 84 Translation Table for Input Arguments for the NotifyOnRevisions Operation
Argument Name Format XML Element or Attribute XML Name/Type
notification boolean attribute enable: xsd:boolean
Figure 32
NotifyOnRevisionsResponse Global Element
7.2.16.8.2 NotifyOnRevisionsResponse — This global element acts as a top-level container entity representing the
SOAP body of the response to an SEMI E125 NotifyOnRevisions request. It contains an optional element named
“Error” of complexType “ErrorType”, defined in SEMI E138. As defined in SEMI E125, this operation returns no
arguments, so there is no other content defined for this response.
Table 85 Translation Table for Output Arguments for the GetUnits Operation
Argument Name Format XML Element or Attribute XML Name/Type
error Structured data, of type
Error, defined in the
SEMI Specification for
Semicondoctor
Common Components
Element Error: ccs:ErrorType
No SEMI E125-specific error codes are
defined for this operation.
7.3 MetadataClient
7.3.1.1 This section is provisional, pending approval of SEMI E132.1 and SEMI E138.
7.3.1.2 Application of SEMI E132 Sessions
7.3.1.3 Operations defined by the SEMI E125 MetadataClient interface shall be exchanged via HTTP and shall not
be exchanged via HTTPS. The equipment shall include a hash of the client’s SEMI E132 session identifier in the
SOAP envelope header provided with the operation using the E132HashHeader element, as specified by
SEMI E132.1
7.3.1.4 The equipment shall only send SEMI E125 notifications to instances of the MetadataClient interface if the
corresponding SEMI E132 Session(s) for that client are in the “Established” state. The equipment shall use the URL
provided with the HTTPEndpoint information included in the SEMI E132 EstablishSession request to send all
SEMI E125 notifications to the MetadataClient interface.
7.3.2 XML Schema and WSDL Files
7.3.2.1 The XML Schema and WSDL defined by this specification for the MetadataClient interface is contained in
the following documents:
Table 86 XML Schema
File Name E125-1-V0305-Schema.xsd
Target Namespace urn:semi-org:xsd.E125-1.V0305.esd
Imported/Referenced
Namespaces
urn:semi-org:xsd.E120-1.V1104.CommonEquipmentModel
urn:semi-org:xsd.CommonComponents.V0305.ccs
http://www.w3.org/2001/XMLSchema
Description
This file defines all of the E125 data types and elements used by both the
EquipmentMetadataManager and MetadataClient interfaces.
SEMI E125.1-0305 © SEMI 2005 43
Table 87 MetadataClient PortType Definitions
File Name E125-1-V0305-MetadataClient-PortType.wsdl
Target Namespace urn:semi-org:ws.E125-1.V0305.esdMetaClt-portType
Imported/Referenced
Namespaces
urn:semi-org:xsd.E132-1.V0305.auth
urn:semi-org:xsd.E125-1.V0305.esd
http://schemas.xmlsoap.org/wsdl/
http://www.w3.org/2001/XMLSchema
Description
This file defines all of the input/output messages and operations for the MetadataClient interface,
based on the data types defined in the SEMI E125 XML Schema.
Table 88 EquipmentMetadataManager Binding Definitions
File Name E125-1-V0305-MetadataClient-Binding.wsdl
Target Namespace urn:semi-org:ws.E125-1.V0305.esdMetaClt-binding
Imported/Referenced
Namespaces
urn:semi-org:ws.E125-1.V0305.esdMetaClt-portType
http://schemas.xmlsoap.org/wsdl/soap/
http://schemas.xmlsoap.org/wsdl/
Description
This file binds the abstract portType definition to HTTP and SOAP, specifying required SOAP
and HTTP headers for each operation and the XML encoding style.
7.3.3 WSDL Port Type Overview
7.3.3.1 The MetadataClient WSDL portType definition organizes the SEMI E125.1 XML Schema data types into a
collection of named operations with inputs and outputs that correspond to the UML operations that are defined for
the MetadataClient interface in SEMI E125. The WSDL portType itself is named after the SEMI E125 interface,
and each WSDL portType operation is named after the corresponding UML operation defined for the interface.
Each WSDL operation consists of two WSDL message definitions corresponding to the input and output (request
and response) for the UML operation defined in SEMI E125. The MetadataClient interface defines only one
operation with no outputs (one-way).
Table 89 EquipmentMetadataManager Port Type
SEMI E125 Class Name MetadataClient
WSDL Port Type Name MetadataClient
SEMI E125 Operation
WSDL Operation
MetadataRevised MetadataRevised
7.3.4 WSDL Binding Overview
7.3.4.1 The WSDL MetadataClient binding definition specifies a message and transport protocol to use for a given
portType (SOAP and HTTP for SEMI E125.1), the interface style used (document style for SEMI E125.1). These
setting are shown in Table 13. For each WSDL portType operation, the binding defines any SOAP headers used and
whether or not they are required, the HTTP SOAPAction header value to use for that operation, and the XML
encoding to use (literal). The binding definitions for each portType operation are described in ¶¶7.2.8 through
7.2.16.
Table 90 EquipmentMetadataManager Binding
SEMI E125 Class Name MetadataClient
WSDL Binding Name MetadataClient Binding
SOAP Binding Style document
SOAP Transport http://schemas.xmlsoap.org/soap/http
7.3.5 WSDL Service Overview
7.3.5.1 This specification does not provide a WSDL service definition for the MetadataClient interface. WSDL
service definitions define the address(es) at which a given interface can be accessed by a client. Such information is
SEMI E125.1-0305 © SEMI 2005 44
provided dynamically to the equipment during SEMI E132 Session establishment, using the EstablishSession
message.
7.3.6 MetadataRevised
7.3.6.1 WSDL Operation Binding
7.3.6.1.1 See the operation binding for “MetadataRevised” in E125-1-V0305-MetadataClient-Binding.wsdl. Key
information is shown for convenience in the following table.
Table 91 MetadataRevised Operation Binding
SOAPAction
urn:semi-org:ws.E125-1.V0305.esdMetaEqp-
binding:MetadataRevised
Input Headers (WSDL Message, Required) E132HashHeaderMessage, required
Output Headers (WSDL Message, Required) E132HashHeaderMessage, required
7.3.6.2 WSDL PortType Operation
7.3.6.2.1 See the portType operation definition for “MetadataRevised” in SEMI E125- MetadataClient -
PortType.wsdl. Key information is shown for convenience in the following table.
Table 92 MetadataRevised PortType Operation
Input Message Name MetadataRevisedNotificationMessage
7.3.6.3 WSDL Message(s)
7.3.6.3.1 See the message definitions for “E132HashHeaderMessage” and “MetadataRevisedNotificationMessage”
in E125-1-V0305-MetadataClient-PortType.wsdl. Key information is shown for convenience in the following table.
Table 93 EquipmentMetadataManager Binding
Message Name
Schema
Element Name
E132HashHeaderMessage auth:E132HashHeader
NotifyOnRevisionsRequestMessage esd: MetadataRevisedNotification
7.3.6.4 XML Schema Types
Figure 33
MetadataRevisedNotification Global Element
7.3.6.4.1 MetadataRevisedNotification — This global element acts as a top-level container entity representing the
SOAP body of a MetadataRevised notification. As defined in SEMI E125, this operation has one input argument:
the current revision of the equipment metadata. This argument is modeled as a single element named “Revision” of
built-in type “xsd:dateTime”.
Table 94 Translation Table for Input Arguments for the NotifyOnRevisions Operation
Argument Name Format XML Element or Attribute XML Name/Type
revision Structured data of type
RevisionNotice
element Revision: xsd:dateTime.
7.3.6.4.2 Revision — This global element is the XML Schema representation of the SEMI E125 RevisionNotice
class.