Title: Theory / Unimportant / CS / Descriptive / XML / 1.0 W3/
Tags: fromMath mathToDef mathToSee

Name: Extensible Markup Language
Definition: Description of XML documents and partial description of computer programs which process them.
Notation: XML
Typ: GSML

Name: XML document
Typ: A list of entities.
Chapter: 1

Smaller0: Storage units
Greater0: parsed or unparsed data
Chapter: 1
Smaller to greater: contains
Hide middle: yes
Name: entities
Greater to smaller: belongs to
Suffix Smaller: . It

Name: Parsed data
Typ: Made up of characters.
Chapter: 1

Q: [...] and [...].
A: Some character data; some markups
Chapter: 1
Name: Characters

Name: XML processor
Definition: A software module used to read XML documents and provide access to their content and structure.
Chapter: 1

Name: The application
Definition: What uses the XML processor.
Chapter: 1

Name: Error
Definition: A violation of the rules of this specification; results are undefined.
Chapter: 1
Section: 2
Example: 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.

Name: Fatal error
Definition: An error which a conforming XML processor must detect and report to the application.
Chapter: 1
Section: 2

Q: If [...] is found [...].
A: an error; conforming software may detect and report an error and may recover from it
Chapter: 1
Section: 2

Q: [...] is found [...].
A: a fatal error; conforming software MUST detect and report an error and may recover from it. It may continue processing to report other errors. It must not continue to pass character data and information about the document's logical structure to the application in the normal way
Chapter: 1
Section: 2

Definition: Conforming software may or must (depending on the modal verb in the sentence) behave as described; if it does, it must provide users a means to enable or disable the behavior described.
Chapter: 1
Section: 2
Assuming: At user option

Definition: A rule which applies to all valid XML documents.
Chapter: 1
Section: 2
Assuming: Validity constraint

Q: Violations of validity constraints are [...]; they [...].
A: errors; must, at user option, be reported by validating XML processors
Chapter: 1
Section: 2

Name: well-formedness constraint
Definition: A rule which applies to all well-formed XML documents.
Chapter: 1
Section: 2

Question: Violations of well-formedness constraints are
Answer: fatal errors.
Chapter: 1
Section: 2

Definition: wo strings or names being compared are identical. Characters with multiple possible representations in ISO/IEC 10646 (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.
Chapter: 1
Section: 2
Assuming: Match of strings or names

Definition: If the strings belongs to the language generated by the production.
Chapter: 1
Section: 2
Assuming: Match of strings in the grammar

Definition: If the element conforms in the fashion described in the constraint.
Chapter: 1
Section: 2
Assuming: Match of content and content models

Name: for compatibility
Definition: Marks a sentence describing a feature of XML included solely to ensure that XML remains compatible with SGML..
Chapter: 1
Section: 2

Name: for interoperability
Definition: 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.
Chapter: 1
Section: 2