semi合集-English.pdf - 第3017页
SEMI E121-0305 © SEMI 2003, 2005 13 R1-2.12 En tity Reference — A reference to an entity that is sub stitu ted for the reference when the XML documen t is parsed. It may reference a predefined entity like < o r it…
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.
SEMI E121-0305 © SEMI 2003, 2005 14
R1-2.30 RDF Schema — A standard for specifying consistency rules (for example, price must be greater than zero,
discount must be less than 15%) that apply to the specifications contained in an RDF.
R1-2.31 Root — The outermost element in an XML document. The element that contains all other elements.
R1-2.32 SAX — “Simple API for XML”. An event-driven interface in which the parser invokes one of several
methods supplied by the caller when a “parsing event” occurs. “Events” include recognizing an XML tag, finding an
error, encountering a reference to an external entity, or processing a schema specification.
R1-2.33 Schema — A database-inspired method for specifying constraints on XML documents using an XML-
based language. Schemas address deficiencies in DTDs, such as the inability to put constraints on the kinds of data
that can occur in a particular field (for example, all numeric). Since schemas are founded on XML, they are
hierarchical, so it is easier to create an unambiguous specification, and possible to determine the scope over which a
comment is meant to apply.
R1-2.34 SGML — Standard Generalized Markup Language. The parent of both HTML and XML. However, while
HTML shares SGML’s propensity for embedding presentation information in the markup, XML is a standard that
allows information content to be totally separated from the mechanisms for rendering/displaying that content.
R1-2.35 Tag — A piece of text that describes a unit of data, or element, in XML. The tag is distinguishable as
markup, as opposed to data, because it is surrounded by angle brackets (< and >). For example, the element
<name>My Name</name> has the start tag <name>, the end tag </name>, which enclose the data “My Name”.
To treat such markup syntax as data, you use an entity reference or a CDATA section.
R1-2.36 Unicode — A standard defined by the Unicode Consortium that uses a 16-bit “code page” which maps
digits to characters in languages around the world. Because 16 bits covers 32,768 codes, Unicode is large enough to
include all the world’s languages, with the exception of ideographic languages that have a different character for
every concept, like Chinese. For more info, see http://www.unicode.org/.
R1-2.37 Unparsed Entity — A general entity that contains something other than XML. By its nature, then, an
unparsed entity contains binary data.
R1-2.38 URI — A “Universal Resource Identifier”. A URI is either a URL or a URN. (URLs and URNs are
concrete entities that actually exist. A “URI” is an abstract superclass -- it’s a name we can use when we know we
are dealing with either an URL or an URN, and we don’t care which.
R1-2.39 URL — Universal Resource Locator. A pointer to a specific location (address) on the Web that is unique in
the entire world. The first part of the URL defines the type of address. For example, http:/ identifies a Web location.
The ftp:/ prefix identifies a downloadable file. Other prefixes include file:/ (a file on the local disk system) and
mailto:/ (an email address).
R1-2.40 URN — Universal Resource Name. A unique identifier that identifies an entity, but doesn’t tell where it is
located. That lets the system look it up to see if a local copy exists before going out to find it on the Web. It also
allows the web location to change, while still allowing the object to be found.
R1-2.41 Valid — A valid XML document, in addition to being well formed, conforms to all the constraints imposed
by a schema. In other words, it does not contain any tags that are not permitted by the schemas, and the order of the
tags conforms to the or schema’s specifications.
R1-2.42 Validating Parser — A validating parser is a parser that ensures that an XML document is valid, as well as
well formed. See also: parser.
R1-2.43 w3c — The World Wide Web Consortium. The international body that governs Internet standards.
R1-2.44 Warning — A SAX parser warning is generated when the document’s schema contains duplicate
definitions, and similar situations that are not necessarily an error, but which the document author might like to
know about, since they could be. See also: fatal error, error.
R1-2.45 Well-formed — A well-formed XML document is syntactically correct. It does not have any angle brackets
that are not part of tags. (The entity references < and > are used to embed angle brackets in an XML