Glossary of "Extensible Markup Language (XML) 1.1"

Term entries in the "Extensible Markup Language (XML) 1.1" glossary

W3C Glossaries

Showing results 21 - 40 of 70

empty

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An element with no content is said to be empty.
empty-element tag

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An empty-element tag takes a special form:
end-tag

From Extensible Markup Language (XML) 1.1 (2004-02-04)

The end of every element that begins with a start-tag MUST be marked by an end-tag containing a name that echoes the element's type as given in the start-tag:
entities

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An XML document may consist of one or many storage units. These are called entities; they all have content and are all (except for the document entity and the external DTD subset) identified by entity name.
entity reference

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An entity reference refers to the content of a named entity.
enumerated attributes

From Extensible Markup Language (XML) 1.1 (2004-02-04)

Enumerated attributesMUST take one of a list of values provided in the declaration
error

From Extensible Markup Language (XML) 1.1 (2004-02-04)

A violation of the rules of this specification; results are undefined. Unless otherwise specified, failure to observe a prescription of this specification indicated by one of the keywords MUST, REQUIRED, MUST NOT, SHALL and SHALL NOT is an error. Conforming software MAY detect and report an error and MAY recover from it.
escape

From Extensible Markup Language (XML) 1.1 (2004-02-04)

Entity and character references MAY both be used to escape the left angle bracket, ampersand, and other delimiters. A set of general entities (amp, lt, gt, apos, quot) is specified for this purpose. Numeric character references MAY also be used; they are expanded immediately when recognized and MUST be treated as character data, so the numeric character references < and &MAY be used to escape < and & when they occur in character data.
external entity

From Extensible Markup Language (XML) 1.1 (2004-02-04)

If the entity is not internal, it is an external entity, declared as follows:
external markup declaration

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An external markup declaration is defined as a markup declaration occurring in the external subset or in a parameter entity (external or internal, the latter being included because non-validating processors are not required to read them).
fatal error

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An error which a conforming XML processorMUST detect and report to the application. After encountering a fatal error, the processor MAY continue processing the data to search for further errors and MAY report such errors to the application. In order to support correction of errors, the processor MAY make unprocessed data from the document (with intermingled character data and markup) available to the application. Once a fatal error is detected, however, the processor MUST NOT continue normal processing (i.e., it MUST NOT continue to pass character data and information about the document's logical structure to the application in the normal way).
for compatibility

From Extensible Markup Language (XML) 1.1 (2004-02-04)

Marks a sentence describing a feature of XML included solely to ensure that XML remains compatible with SGML.
for interoperability

From Extensible Markup Language (XML) 1.1 (2004-02-04)

Marks a sentence describing a non-binding recommendation included to increase the chances that XML documents can be processed by the existing installed base of SGML processors which predate the WebSGML Adaptations Annex to ISO 8879.
general entities

From Extensible Markup Language (XML) 1.1 (2004-02-04)

General entities are entities for use within the document content. In this specification, general entities are sometimes referred to with the unqualified term entity when this leads to no ambiguity.
included

From Extensible Markup Language (XML) 1.1 (2004-02-04)

An entity is included when its replacement text is retrieved and processed, in place of the reference itself, as though it were part of the document at the location the reference was recognized.
internal entity

From Extensible Markup Language (XML) 1.1 (2004-02-04)

If the entity definition is an EntityValue, the defined entity is called an internal entity. There is no separate physical storage object, and the content of the entity is given in the declaration.
literal entity value

From Extensible Markup Language (XML) 1.1 (2004-02-04)

For an external entity, the literal entity value is the exact text contained in the entity.
For an internal entity, the literal entity value is the quoted string actually present in the entity declaration, corresponding to the non-terminal EntityValue.
markup

From Extensible Markup Language (XML) 1.1 (2004-02-04)

Markup takes the form of start-tags, end-tags, empty-element tags, entity references, character references, comments, CDATA section delimiters, document type declarations, processing instructions, XML declarations, text declarations, and any white space that is at the top level of the document entity (that is, outside the document element and not inside any other markup).
markup declaration

From Extensible Markup Language (XML) 1.1 (2004-02-04)

A markup declaration is an element type declaration, an attribute-list declaration, an entity declaration, or a notation declaration.
match

From Extensible Markup Language (XML) 1.1 (2004-02-04)

(Of strings or names:) Two strings or names being compared MUST be identical. Characters with multiple possible representations in Unicode (e.g. characters with both precomposed and base+diacritic forms) match only if they have the same representation in both strings. No case folding is performed. (Of strings and rules in the grammar:) A string matches a grammatical production if it belongs to the language generated by that production. (Of content and content models:) An element matches its declaration when it conforms in the fashion described in the constraint .

The Glossary System has been built by Pierre Candela during an internship in W3C; it's now maintained by Dominique Hazael-Massieux

Copyright © 2000-2003W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements.