semi合集-English.pdf - 第3016页
SEMI E121-0305 © SEMI 2003, 2005 12 R1-1.9 ISO R1-1.9.1 The Internat ional Orga nization for Standar dization (I S O) is a worldwide federati on of national st andards bodies from som e 140 countries, one from each count…
SEMI E121-0305 © SEMI 2003, 2005 11
R1-1.5 RossetaNet
R1-1.5.1 A consortium of more than 400 of the world’s leading Electronic Components (EC), Information
Technology (IT), Semiconductor Manufacturing (SM) and Solution Provider (SP) companies, RosettaNet is a self-
funded, non-profit organization dedicated to creating, implementing and promoting open e-business standards.
These standards form a common e-business language, aligning processes between trading partners on a global basis.
RosettaNet is named after the Rosetta stone, which, carved with the same message in three languages, led to the
understanding of hieroglyphics. RosettaNet, like the Stone, is breaking language barriers and making history.
RosettaNet drives collaborative development and rapid deployment of Internet-based business standards, creating a
common language and open e-business processes that provide measurable benefits and are vital to the evolution of
the global, high technology trading network. Developed with the collaboration and expertise of leading high-tech
companies, RosettaNet standards offer a robust nonproprietary solution, encompassing data dictionaries,
implementation framework, and business message schemas and process specifications, for e-business
standardization. RosettaNet standards include the RosettaNet Business Dictionary, RosettaNet Technical Dictionary,
RosettaNet Implementation Framework (RNIF) and RosettaNet Partner Interface Processes® (PIP®). Link
information: www.rosetta.org
R1-1.6 UN/CEFACT
R1-1.6.1 UN/CEFACT is the United Nations body whose mandate covers worldwide policy and technical
development in the area of trade facilitation and electronic business. Headquartered in Geneva, it has developed and
promoted many tools for the facilitation of global business processes including UN/EDIFACT, the international EDI
standard. Its current work “programme” includes such topics as “Simpl-edi” and “Object Oriented edi” and it
strongly supports the development and implementation of open interoperable, global standards and specifications for
electronic business. Link information: www.unece.org/cefact
R1-1.7 OASIS
R1-1.7.1 OASIS is the international, not-for-profit consortium that advances electronic business by promoting
open, collaborative development of interoperability specifications. The XML.ORG Registry provides as an open
community clearinghouse for distributing and locating XML application schemas, vocabularies and related
documents. OASIS serves as the home for industry groups and organizations interested in developing XML
specifications. OASIS is a not-for-profit, global consortium that drives the development, convergence and adoption
of e-business standards. OASIS produces worldwide standards for security, Web services, XML conformance,
business transactions, electronic publishing, topic maps and interoperability within and between market places.
OASIS has more than 400 corporate and individual members in 100 countries around the world. OASIS and the
United Nations jointly sponsor ebXML, a global framework for e-business data exchange. OASIS operates
XML.org, a community clearinghouse for XML application schemas, vocabularies and related documents. OASIS
hosts The XML Cover Pages, an online reference collection for interoperable markup language standards. The
OASIS Network includes CGM Open and LegalXML. Link information: http://www.oasis-open.org
R1-1.8 NIST
R1-1.8.1 Founded in 1901, NIST is a non-regulatory federal agency within the U.S. Commerce Department’s
Technology Administration. NIST’s mission is to develop and promote measurements, standards, and technology to
enhance productivity, facilitate trade, and improve the quality of life. NIST carries out its mission in four
cooperative programs: NIST Laboratories, conducting research that advances the nation’s technology infrastructure
and is needed by U.S. industry to continually improve products and services; the Baldrige National Quality
Program, which promotes performance excellence among U.S. manufacturers, service companies, educational
institutions, and health care providers; conducts outreach programs and manages the annual Malcolm Baldrige
National Quality Award which recognizes performance excellence and quality achievement; the Manufacturing
Extension Partnership, a nationwide network of local centers offering technical and business assistance to smaller
manufacturers; and the Advanced Technology Program, which accelerates the development of innovative
technologies for broad national benefit by co-funding R&D partnerships with the private sector. One program in
particular is SIMA. The SIMA Program seeks to provide U.S. manufacturers with capabilities enabling contextually
meaningful data to be shared among business activities such that reliable information is accessible when and where
it is needed. Link information: www.NIST.gov
SEMI E121-0305 © SEMI 2003, 2005 12
R1-1.9 ISO
R1-1.9.1 The International Organization for Standardization (ISO) is a worldwide federation of national standards
bodies from some 140 countries, one from each country. ISO is a non-governmental organization established in
1947. The mission of ISO is to promote the development of standardization and related activities in the world with a
view to facilitating the international exchange of goods and services, and to developing cooperation in the spheres of
intellectual, scientific, technological and economic activity. ISO’s work results in international agreements that are
published as International Standards. This guide may use some of the recommendations defined in ISO 11179
Document that defines a framework for the specification and standardization of data elements. Link information:
www.ISO.org.
R1-2 Glossary of Terms in XML
R1-2.1 Attribute — A qualifier on an XML tag that provides additional information. For example, in the tag <slide:
title="My Slide"/>, title is an attribute, and My Slide is its value.
R1-2.2 Binding — Construction of the code needed to process a well-defined bit of XML data.
R1-2.3 Comment — Text in an XML document that is ignored, unless the parser is specifically told to recognize it.
A comment is enclosed in a comment tag, like this:
<!-- This is a comment --> .
R1-2.4 Content — The part of an XML document that occurs after the prolog, including the root element and
everything it contains.
R1-2.5 CDATA — A predefined XML tag for “Character DATA” that says “don’t interpret these characters”, as
opposed to “Parsed Character Data” (PCDATA), in which the normal rules of XML syntax apply (for example,
angle brackets demarcate XML tags, tags define XML elements, etc.). CDATA sections are typically used to show
examples of XML syntax. Like this:
<![CDATA[ <slide>..A sample slide..</slide> ]]>
which displays as:
<slide>..A sample slide.. </slide>
R1-2.6 Data — The contents of an element generally used when the element does not contain any sub elements.
When it does, the more general term content is generally used. When the only text in an XML structure is contained
in simple elements, and elements that have sub elements have little or no data mixed in, then that structure is often
thought of as XML “data”, as opposed to an XML document.
R1-2.7 Declaration — The very first thing in an XML document, which declares it as XML. The minimal
declaration is <?xml version="1.0"?>. The declaration is part of the document prolog.
R1-2.8 Document — In general, an XML structure in which one or more elements contain text intermixed with sub
elements. See also: data.
R1-2.9 DOM — Document Object Model. A tree of objects with interfaces for traversing the tree and writing an
XML version of it, as defined by the W3C specification.
R1-2.10 Element — A unit of XML data, delimited by tags. An XML element can enclose other elements. For
example, in the XML structure, “<slideshow><slide>..</slide><slide>..</slide></slideshow>”, the
<slideshow> element contains two <slide> elements.
R1-2.11 Entity — A distinct, individual item that can be included in an XML document by referencing it. Such an
entity reference can name an entity as small as a character (for example, “<” , which references the less-than
symbol, or left-angle bracket (<). An entity reference can also reference an entire document, or external entity, or a
collection of element definitions (a parameter entity).
SEMI E121-0305 © SEMI 2003, 2005 13
R1-2.12 Entity Reference — A reference to an entity that is substituted for the reference when the XML document
is parsed. It may reference a predefined entity like < or it may reference one that is defined in the schema. In the
XML data, the reference could be to an entity that is defined in the local subset of the schema or to an external XML
file (an external entity). The schema can also carve out a segment of schema specifications and give it a name so that
it can be reused (included) at multiple points in the schema by defining a parameter entity.
R1-2.13 Error — A SAX parsing error is generally a validation error—in other words, it occurs when an XML
document is not valid, although it can also occur if the declaration specifies an XML version that the parser cannot
handle. See also: fatal error, warning.
R1-2.14 External Entity — An entity that exists as an external XML file, which is included in the XML document
using an entity reference.
R1-2.15 External Subset — That part of the schema that is defined by references to external .dtd or .xsd files.
R1-2.16 Fatal Error — A fatal error occurs in the SAX parser when a document is not well formed, or otherwise
cannot be processed. See also: error, warning.
R1-2.17 General Entity — An entity that is referenced as part of an XML document’s content, as distinct from a
parameter entity, which is referenced in the schema. A general entity can be a parsed entity or an unparsed entity.
R1-2.18 HTML — Hypertext Markup Language. The language of the Web. A system where every document has a
globally unique location, and documents can link to one another.
R1-2.19 Local Subset — That part of the schema that is defined within the current XML file.
R1-2.20 Namespace — A standard that lets you specify a unique label to the set of element names defined by a
schema. A document using that schema can be included in any other document without having a conflict between
element names. The elements defined in your schema are then uniquely identified so that, for example, the parser
can tell when an element called <name> should be interpreted according to your schema, rather than using the
definition for an element called “name” in a different schema.
R1-2.21 Normalization — The process of removing redundancy by modularizing, as with subroutines, and have
removing superfluous differences by reducing them to a common denominator. For example, reducing them to a
single NL normalizes line endings from different systems, and multiple white space characters are normalized to one
space.
R1-2.22 Notation — A mechanism for defining a data format for a non-XML document referenced as an unparsed
entity. This is a holdover from SGML that creaks a bit. The newer standard is to use MIME data types and
namespaces to prevent naming conflicts.
R1-2.23 OASIS — Organization for the Advancement of Structured Information Standards. Their home site is
http://www.oasis-open.org/. The schema repository they sponsor is at http://www.XML.org.
R1-2.24 Parsed Entity — A general entity which contains XML, and which is therefore parsed when inserted into
the XML document, as opposed to an unparsed entity.
R1-2.25 Parser — A module that reads in XML data from an input source and breaks it up into chunks so that your
program knows when it is working with a tag, an attribute, or element data. A no validating parser ensures that the
XML data is well formed, but does not verify that it is valid. See also: validating parser.
R1-2.26 Processing Instruction — Information contained in an XML structure that is intended to be interpreted by
a specific application.
R1-2.27 Prolog — The part of an XML document that precedes the XML data. The prolog includes the declaration
and an optional schema.
R1-2.28 Reference — See entity reference.
R1-2.29 RDF — Resource Description Framework. A standard for defining the kind of data that an XML file
contains. Such information could help ensure semantic integrity, for example by helping to make sure that a date is
treated as a date, rather than simply as text.