semi合集-English.pdf - 第3398页
SEMI E132.1-0305 © SEMI 2005 25 8.2.11.1.3 AddACLEntry Response 8.2.11.1.3 .1 The service response is mapped to the XML Sc hema element AddACLE ntryResponse of type AddACLEntryR esponseType. Ta ble 30 shows how the ou tp…

SEMI E132.1-0305 © SEMI 2005 24
Table 26 GetACL Messages
Message Name
Schema
Element Name
E132HeaderMessage auth:E132Header
GetACLRequestMessage auth:GetACLRequest
GetACLResponseMessage auth:GetACLResponse
8.2.10.3 WSDL Operation
8.2.10.3.1 See the portType operation definition for “GetACL” in E132-SecurityAdmin-PortType.wsdl. Key
information is shown for convenience in Table 27.
Table 27 GetACL PortType Operation
Input Message Name
GetACLRequestMessage
Output Message Name GetACLResponseMessage
8.2.10.4 WSDL Operation Binding
8.2.10.4.1 See the operation binding for “GetACL” in E132-SecurityAdmin-Binding.wsdl. Key information is
shown for convenience in Table 28.
Table 28 GetACL Operation Binding
SOAPAction
urn:semi-org:ws.E132-1.V0305.secAdmin-binding:GetACL
Input Headers (WSDL Message, Required) E132HeaderMessage, required
Output Headers (WSDL Message, Required) E132HeaderMessage, required
8.2.11 AddACLEntry Operation
8.2.11.1 XML Schema Types
8.2.11.1.1 This section describes the XML mappings for the classes defined in SEMI E132 for the AddACLEntry
operation. See GetDefinedPrivileges operation regarding schema conventions used.
8.2.11.1.2 AddACLEntry Request
8.2.11.1.2.1 The service request is mapped to the XML schema element AddACLEntryRequest which is of type
AddACLEntryRequestType. Table 29 shows how the input parameters are mapped to XML. The XML
ACLEntryType is as described in ¶8.2.10.1.4, under Schema Types for GetACL operation.
Table 29 Translation Table for AddACLEntry Input Parameters
Argument Name Format XML Element or Attribute XML Name/Type
aclEntry Structured type Element ACLEntry: ACLEntryType
Figure 20
AddACLEntryRequest XML Schema Element

SEMI E132.1-0305 © SEMI 2005 25
8.2.11.1.3 AddACLEntry Response
8.2.11.1.3.1 The service response is mapped to the XML Schema element AddACLEntryResponse of type
AddACLEntryResponseType. Table 30 shows how the output parameters are mapped to XML. The XML Schema
diagram for AddACLEntryResponse is shown in Figure 21. Errors for this operation are returned using the XML
Schema element Error of type AddACLEntryErrorType, containing the common error element described in ¶8.2.6.1.
In addition, if the error is an operation not authorized error, the UnauthorizedOperationError element must also be
provided, of type UnauthorizedOperationType corresponding to the UnauthorizedOperationError class defined in
SEMI E132, UML mapping is as described in ¶8.2.6.2. If the error is an unrecognized privilege error, the
UnrecognizedPrivilegeError element must also be provided, of type UnrecognizedPrivilegeType corresponding to
the UnrecognizedPrivilegeError class, UML mapping for this class is described in ¶8.2.11.1.4.
Table 30 Translation Table for AddACLEntry Output Parameters
Argument Name Format XML Element or Attribute XML Name/Type
error Structured data Element Error: AddACLEntryErrorType
Figure 21
AddACLEntryResponse XML Schema Element
8.2.11.1.4 UnrecognizedPrivilegeError Class
8.2.11.1.4.1 The UnrecognizedPrivilegeError class is mapped to the XML UnrecognizedPrivilegeType. Table 31
shows how the attributes and associations of UnrecognizedPrivilegeError class are mapped to XML. The privileges
provided represent the list of privileges in input arguments that are not recognized by the equipment. Figure 22
shows the XML Schema diagram.
Table 31 Translation Table for UnrecognizedPrivilegeError Class
Attribute or Role Name UML Name/Type XML Element or Attribute XML Name/Type
description Text Element Description: xsd:string
unrecognizedPrivileges Association Element UnrecognizedPrivilege: PrivilegeType
(one or more)
Figure 22
UnrecognizedPrivilegeType XML Schema Type

SEMI E132.1-0305 © SEMI 2005 26
8.2.11.2 WSDL Message(s)
8.2.11.2.1 Three messages are defined for this operation corresponding to the SEMI E132 Header, Request and
Response messages. See the message definitions for “E132HeaderMessage”, “AddACLEntryRequestMessage”, and
“AddACLEntryResponseMessage” in E132-SecurityAdmin-PortType.wsdl. Key information is shown for
convenience in Table 32.
Table 32 AddACLEntry Messages
Message Name
Schema
Element Name
E132HeaderMessage auth:E132Header
AddACLEntryRequestMessage auth:AddACLEntryRequest
AddACLEntryResponseMessage auth:AddACLEntryResponse
8.2.11.3 WSDL Operation
8.2.11.3.1 See the portType operation definition for “AddACLEntry” in E132-SecurityAdmin-PortType.wsdl. Key
information is shown for convenience in Table 33.
Table 33 AddACLEntry PortType Operation
Input Message Name
AddACLEntryRequestMessage
Output Message Name AddACLEntryResponseMessage
8.2.11.4 WSDL Operation Binding
8.2.11.4.1 See the operation binding for “AddACLEntry” in E132-SecurityAdmin-Binding.wsdl. Key information
is shown for convenience in Table 34.
Table 34 AddACLEntry Operation Binding
SOAPAction
urn:semi-org:ws.E132-1.V0305.secAdmin-binding:AddACLEntry
Input Headers (WSDL Message, Required) E132HeaderMessage, required
Output Headers (WSDL Message, Required) E132HeaderMessage, required
8.2.12 DeleteACLEntry Operation
8.2.12.1 XML Schema Types
8.2.12.1.1 This section describes the XML mappings for the classes defined in SEMI E132 for the DeleteACLEntry
operation. See GetDefinedPrivileges operation regarding schema conventions used.
8.2.12.1.2 DeleteACLEntry Request
8.2.12.1.2.1 The service request is mapped to the XML Schema element DeleteACLEntryRequest which is of type
DeleteACLEntryRequestType. Table 35 shows how the input parameters are mapped to XML.
Table 35 Translation Table for DeleteACLEntry Input Parameters
Argument Name Format XML Element or Attribute XML Name/Type
subjectId Structured type Element SubjectID: xsd:string
Figure 23
DeleteACLEntryRequest XML Schema Element