semi合集-English.pdf - 第3146页

SEMI E125-0305 © SEMI 2003, 2005 54 R8-1.2.3 8 subclass — in a generalization relationship, the specializa tion of another class; t h e superclass. See: generalization . Contrast: superclass . R8-1.2.3 9 subtype — in a g…

100%1 / 7923
SEMI E125-0305 © SEMI 2003, 2005 53
R8-1.2.18 feature — a property, like operation or attribute, which is encapsulated within a classifier, such as an
interface, a class, or a datatype.
R8-1.2.19 generalization — a taxonomic relationship between a more general element and a more specific element.
The more specific element is fully consistent with the more general element and contains additional information.
An instance of the more specific element may be used where the more general element is allowed. See:
inheritance.
R8-1.2.20 inheritance — the mechanism by which more specific elements incorporate structure and behavior of
more general elements related by behavior. See: generalization.
R8-1.2.21 instance — an entity that has unique identity, a set of operations that can be applied to it, and state that
stores the effects of the operations. See: object.
R8-1.2.22 interface — a named set of operations that characterize the behavior of an element.
R8-1.2.23 interface inheritance — the inheritance of the interface of a more general element. Does not include
inheritance of the implementation. Contrast: implementation inheritance.
R8-1.2.24 message — a specification of the conveyance of information from one instance to another, with the
expectation that activity will ensue. A message may specify the raising of a signal or the call of an operation.
R8-1.2.25 method — the implementation of an operation. It specifies the algorithm or procedure associated with an
operation.
R8-1.2.26 model [MOF] — an abstraction of a physical system with a certain purpose. See: physical system.
Usage note: In the context of the MOF specification, which describes a meta-metamodel, for brevity the
metametamodel is frequently referred to as simply the model.
R8-1.2.27 multiple inheritance — a semantic variation of generalization in which a type may have more than one
supertype. Contrast: single inheritance.
R8-1.2.28 multiplicity — a specification of the range of allowable cardinalities that a set may assume. Multiplicity
specifications may be given for roles within associations, parts within composites, repetitions, and other purposes.
Essentially a multiplicity is a (possibly infinite) subset of the non-negative integers. Contrast: cardinality.
R8-1.2.29 object — an entity with a well-defined boundary and identity that encapsulates state and behavior. State
is represented by attributes and relationships, behavior is represented by operations, methods, and state machines.
An object is an instance of a class. See: class, instance.
R8-1.2.30 object diagram — a diagram that encompasses objects and their relationships at a point in time. An
object diagram may be considered a special case of a class diagram or a collaboration diagram. See:
class diagram,
collaboration diagram.
R8-1.2.31 operation — a service that can be requested from an object to effect behavior. An operation has a
signature, which may restrict the actual parameters that are possible.
R8-1.2.32 parent — in a generalization relationship, the generalization of another element, the child. See:
subclass, subtype. Contrast: child.
R8-1.2.33 package — a general purpose mechanism for organizing elements into groups. Packages may be nested
within other packages.
R8-1.2.34 qualifier — an association attribute or tuple of attributes whose values partition the set of objects related
to an object across an association.
R8-1.2.35 relationship — a semantic connection among model elements. Examples of relationships include
associations and generalizations.
R8-1.2.36 role — the named specific behavior of an entity participating in a particular context. A role may be static
(for example, an association end) or dynamic (for example, a collaboration role).
R8-1.2.37 single inheritance — a semantic variation of generalization in which a type may have only one
supertype. Synonym: multiple inheritance [OMA]. Contrast: multiple inheritance.
SEMI E125-0305 © SEMI 2003, 2005 54
R8-1.2.38 subclass — in a generalization relationship, the specialization of another class; the superclass. See:
generalization. Contrast: superclass.
R8-1.2.39 subtype — in a generalization relationship, the specialization of another type; the supertype. See:
generalization. Contrast: supertype.
R8-1.2.40 superclass — in a generalization relationship, the generalization of another class; the subclass. See:
generalization. Contrast: subclass.
R8-1.2.41 supertype — in a generalization relationship, the generalization of another type; the subtype. See:
generalization. Contrast: subtype.
R8-1.2.42 type — a stereotyped class that specifies a domain of objects together with the operations applicable to
the objects, without defining the physical implementation of those objects. A type may not contain any methods,
maintain its own thread of control, or be nested. However, it may have attributes and associations. Although an
object may have at most one implementation class, it may conform to multiple different types. See: implementation
class. Contrast: interface.
R8-1.2.43 visibility — an enumeration whose value (public, protected, or private) denotes how the model element
to which it refers may be seen outside its enclosing namespace.
NOTICE: SEMI makes no warranties or representations as to the suitability of the standards set forth herein for any
particular application. The determination of the suitability of the standard is solely the responsibility of the user.
Users are cautioned to refer to manufacturer's instructions, product labels, product data sheets, and other relevant
literature, respecting any materials or equipment mentioned herein. These standards are subject to change without
notice.
By publication of this standard, Semiconductor Equipment and Materials International (SEMI) takes no position
respecting the validity of any patent rights or copyrights asserted in connection with any items mentioned in this
standard. Users of this standard are expressly advised that determination of any such patent rights or copyrights, and
the risk of infringement of such rights are entirely their own responsibility.
Copyright by SEMI® (Semiconductor Equipment and Materials
International), 3081 Zanker Road, San Jose, CA 95134. Reproduction of
the contents in whole or in part is forbidden without express written
consent of SEMI.
SEMI E125.1-0305 © SEMI 2005 1
SEMI E125.1-0305
PROVISIONAL SPECIFICATION FOR SOAP BINDING FOR
EQUIPMENT SELF DESCRIPTION (EqSD)
This provisional specification was technically approved by the Global Information and Control Committee
and is the direct responsibility of the North American Information and Control Committee. Current edition
approved by the North American Regional Standards Committee on December 10, 2005. Initially available
at www.semi.org February 2005; to be published March 2005.
Table of Contents
1 Purpose....................................................................................................................................................................4
1.1 SOAP Implementation Mapping.......................................................................................................................4
2 Scope.......................................................................................................................................................................4
2.1 Specification Scope...........................................................................................................................................4
3 Limitations..............................................................................................................................................................4
3.1 Provisional Specification..................................................................................................................................4
4 Referenced Standards..............................................................................................................................................4
4.1 SEMI Standards................................................................................................................................................4
4.2 OMG Standards................................................................................................................................................4
4.3 W3C Standards.................................................................................................................................................4
4.4 Other Specifications .........................................................................................................................................5
5 Terminology............................................................................................................................................................5
5.1 Abbreviations and Acronyms............................................................................................................................5
5.2 Definitions ........................................................................................................................................................5
6 Conventions ............................................................................................................................................................5
6.1 Translating UML to XML Schema....................................................................................................................5
6.2 Documenting XML Schema and WSDL Files...................................................................................................6
6.3 Documenting XML Schema with Diagrams......................................................................................................7
6.4 XML Schema Sample........................................................................................................................................7
6.5 Translating UML to WSDL...............................................................................................................................9
7 Mapping of SEMI E125 UML to XML Schema and WSDL..................................................................................9
7.1 WSDL Organization .........................................................................................................................................9
7.2 EquipmentMetadataManager.........................................................................................................................10
7.3 MetadataClient...............................................................................................................................................42
List of Figures
Figure 1 XML Schema Example Diagram ....................................................................................................................8
Figure 2 XML for Sample .............................................................................................................................................8
Figure 3 XML Schema and WSDL File Organization ................................................................................................10
Figure 4 WSDL and XML Schema Files for SEMI E125...........................................................................................10
Figure 5 Mapping the EquipmentMetadataManager to a WSDL portType.................................................................12
Figure 6 GetUnitsRequest Global Element .................................................................................................................13
Figure 7 GetUnitsResponse Global Element...............................................................................................................13
Figure 8 GetTypeDefinitionsRequest Global Element................................................................................................15
Figure 9 GetTypeDefinitionsResponse Global Element..............................................................................................15
Figure 10 ParameterTypeDefinitionType Global complexType .................................................................................16
Figure 11 VariableTypeType Global complexType....................................................................................................20
Figure 12 ArrayTypeType Global complexType ........................................................................................................21
Figure 13 StructureTypeType Global complexType ...................................................................................................22
Figure 14 EnumeratedTypeType Global complexType...............................................................................................23
Figure 15 GetStateMachinesRequest Global Element.................................................................................................24
Figure 16 GetStateMachinesResponse Global Element ..............................................................................................25
Figure 17 StateMachineType Global complexType....................................................................................................25
Figure 18 GetSEMIObjTypesRequest Global Element...............................................................................................28
Figure 19 GetSEMIObjTypesResponse Global Element.............................................................................................28