semi合集-English.pdf - 第3009页

SEMI E121-0305 © SEMI 2003, 2005 5 8.7.3.4 The <NSS> syntax is limited to upp er or lower case c haracters followed by upper lower characters including a hyphen “-“ . The <NS S> is composed of more than on e …

100%1 / 7923
SEMI E121-0305 © SEMI 2003, 2005 4
8.4.1.3 Acronyms should be all in uppercase. Following a Three (or more) Letter Acronym (TLA), all in
uppercase, the next letter is lowercase, i.e.: TLAlowercase, not TLAUppercase.
8.5 Common XML Structures
8.5.1 When defining a list of elements where each has the same element name, nest the list of elements inside a
parent element. Form the parent’s element name by concatenating the name of the list elements with the word
“List”.
8.5.1.1 For example:
<SubstrateIDList>
<SubstrateID>Substrate1</SubstrateID>
<SubstrateID>Substrate2</SubstrateID>
:
<SubstrateID>Substrate25</SubstrateID>
</SubstrateIDList>
8.6 Schema Element Organization — The following recommendations apply only to the Primary and Secondary
Schemas.
8.6.1 With the purpose of readability of the schema and to aid in the understanding of the XML document, the
following guidelines are recommended when elements are defined in the XML document or schema:
8.6.1.1 Elements of type ID or KEY should be listed at the top of the schema, and elements of type IDREF or
KEYREF should be listed second.
8.6.1.2 Elements of simpleType should be declared first, followed by elements of complexType.
8.7 XML Namespaces
8.7.1 A namespace name is a URI (Universal Resource Identifier) that uniquely identifies the namespace. A
namespace is a group of names usually with a related purpose and context. The namespace is a globally unique
name. This is ensured by using a domain names as part of the namespace definition or a pre-determined identifier.
SEMI documents will use the URN (Universal Resource Naming) convention to define namespaces,
suppliers or
any other 3
rd
party suppliers can use either URN or URL (Universal Resource Locator) descriptions.
8.7.2 Each application or document definition is responsible for providing a namespace for the extension of its
vocabulary definition. A namespace must be unique and to ensure its uniqueness the definitions of namespaces must
follow the rules described below.
8.7.3 Namespace Syntax
8.7.3.1 SEMI Namespaces use Uniform Resource Names (URNs). All URNs have the following syntax:
<URN> ::= “urn:” <NID> “:”<NSS>
8.7.3.2 Where <NID> is the namespace identifier and <NSS> is the namespace specific string. The <NID> syntax
is limited to upper or lower characters followed by upper or lower characters including a hyphen “-“.
<NID> ::= <Letter> [<Letter-Number-Hyphen>]*
<Letter> ::= <upper> | <lower>
<Letter-Number-Hyphen> ::= <upper> | <lower> | <number> | “-“
8.7.3.3 The namespace identifier is case insensitive thus “ABC” and “abc” refer to the same namespace. All SEMI
defined namespaces will use <NID> ::= “semi-org”.
SEMI E121-0305 © SEMI 2003, 2005 5
8.7.3.4 The <NSS> syntax is limited to upper or lower case characters followed by upper lower characters including
a hyphen “-“ . The <NSS> is composed of more than one field and each field is separated by a period as shown
below. No other characters than the ones shown are allowed and should be considered reserved.
<NSS> ::= <XML Domain>”.”<SEMI Domain>”.”<Version>”.”<Name>
<XML domain> ::= <Letter> [ Letter-Number-Hyphen]
<SEMI Domain> ::= <Letter> [ Letter-Number-Hyphen]
<Version> ::= <Letter> [ Letter-Number-Hyphen]
<Name> ::= <Letter> [ Letter-Number-Hyphen]
8.7.3.5 <XML Domain> — A XML domain needs to be included to explain whether this is a schema (xsd) or a web
service (ws) by using the following format: <XML domain> = “xsd” for schema or “ws” for web service.
8.7.3.6 <SEMI Domain> or <Company Domain> — Include in the SEMI domain identifier the standard number as
assigned by SEMI. For example, Specification for Carrier Management = “E087”. In those cases where the standard
has not been approved but a formal document number has been assigned, use this number instead. For example,
Equipment Diagnostic Interface = “Doc3563”. When the definition is from a third party use the defined company
domain. For example, Etch equipment = “EtchTool” or “Model-3731-134”.
8.7.3.7 <Version> — Properly identifying the revision level of the schema and it is required when there is an
approved version of the standard the namespace definition should include the date that corresponds to the standard
release date or when it was approved. Dates are represented as month (mm) and year (yy) and use the “Vmmyy”
format. This field is not required when SEMI standards are non-existent. For third party applications it is
recommended that the “Vx-x” form be used. For example, 2001 Feb = “V0201” or for Version 2.1 = “V2-1”
8.7.3.8 <Name> — This label corresponds to the actual name of the document to which the namespace belongs.
For metadata definitions include the descriptive name of the schema using upper camel case. Ex.
CarrierManagement, EquipmentDiagnosticAcquisition, EquipmentMetadata, etc. For web services, the <Name>
includes the service or interface role and whether it corresponds to the “binding” or the “portType” definition. (See
UDDI Version 3 from OASIS for WSDL structure).
Examples of valid representations of namespaces are:
“urn:semi-org:xsd.E087.V0702.CarrierManagement”
“urn:semi-org:xsd.Doc3509.V12.DataCollectionManagement”
“urn:supplierXX-com:EtchTool.V07.Model123”
“urn:semi-org:ws.E132-1.V0305.SessionManager-binding”
“urn:semi-org:ws.E125-1.V1104.MetadataManager-portType”
Examples of invalid representation of namespaces are:
“urn:semi.org:xsd.Doc3509.V12.DataCollectionManagement” (Invalid use of period in <SEMI Domain>)
“urn:semi-org:xsd.E087.V7.22.CarrierManagement” (Invalid use of period in <Version>)
8.7.4 Multiple Default Namespaces
8.7.4.1 When more than one namespace is used in an XML document or schema, a prefix shall be defined for each
of the namespaces that uniquely identifies the elements that belong to each of the namespaces. This prefix is used to
specify that a local element or attribute name belongs to a particular namespace. These prefixes are used to override
attribute values and must be documented by the supplier of the application. The following rules apply to prefixes:
Rule 1: Prefixes should be defined in all uppercase or all lower case letters but not both.
Ex: <Definition xmlns: CMS=”urn:semi-org:xsd.E087.V0201.CarrierManagement”>
<CMS:Data> abcd </CMS:Data>
<CMS:Data> xyze </CMS:Data>
</Definition>
SEMI E121-0305 © SEMI 2003, 2005 6
Rule 2: Do not use the same prefix for more than one XML namespace. Prefixes defined with the same characters
and in the same order are considered the same even when defined in different letter case.
Ex. CMS and cms are equivalent.
8.7.5 Target Namespace
8.7.5.1 When more than one namespace is used in schema definition a target namespace should be defined using the
“targetNamespace” format definition. The target namespace definition should include the elementFormDefault =
“qualified” such that the elements defined within the target namespace are all qualified (in the namespace).
For example:
<schema targetNamespace="urn:semi-org:xsd.E125.V0303.Metadata"
xmlns:CEM = "urn:semi-org:xsd.E120.V0303.CommonEquipmentModel"
xmlns:CMS = "urn:semi-org:xsd.E087.V0304.CarrierManagement"
elementFormDefault="qualified">
</schema>
For web services:
<wsdl:definitions name="ESD" targetNamespace="urn:semi-org:ws.E125-1.V0305.Metadata-portType"
xmlns="urn:semi-org:ws.E125-1.V0305.Metadata-portType"
xmlns:auth="urn:semi-org:xsd.E132-1.V0305.auth"
xmlns:esd="urn:semi-org:xsd.E125-1.V0305.esd"
xmlns:eqmport="urn:semi-org:ws.E125-1.V0305.Metadata-portType"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
</wsdl:definitions>
8.8 Character Sets
8.8.1 Vocabularies (element and attribute names) should be restricted to the ASCII 7-bit character set (ISO-646) in
addition to restrictions imposed by XML and XML Schema on element and attribute names as defined in this
document.
8.8.2 XML Schema and instance documents should use the UTF-8 (ISO-10646) encoding; all other documents
should use the UTF-8 encoding (other encoding types may be used for documents whose intended use is restricted to
locales where the restriction to UTF-8 is inappropriate).
8.8.3 UTF-8 supports the ASCII 7-bit character set and the Unicode character set and is the current default
encoding for SOAP based documents.
8.9 Extensions to Enumeration Lists
8.9.1 As a general guideline fixed enumeration lists should not to be changed with additional values. Extendable
enumeration lists, on the other hand, are defined such that they allow the inclusion of supplier or application specific
choices.
8.9.2 Non-extendable Enumeration Lists
8.9.2.1 When an element or attribute has a fixed list of values it can be assumed that it is necessary to restrict the
list. The reasons for restriction to a fixed list are:
The implementation has a known set of cases to consider.
Variations in spelling, abbreviating, and case use need to be eliminated.
For example, an answer to a question may be either “yes” or “no”. A depth may be either “HI” or “LOW”. A unit of
measure may be one of a long, but finite list of ISO abbreviations.