BS ISO IEC 29500-3-2015 pdf free download – Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility.
4 Notational Conventions
The following typographical conventions are used in ISO/IEC 29500:
1) The first occurrence of a new term is written in italics. [Example: The text in ISO/IEC 29500 is divided into normative and informative categories. end example]
2) The tag name of an XML element is written using a distinct style and typeface. [Example: The bookmarkStart and bookmarkEnd elements specify … end example]
3) The name of an XML attribute is written using a distinct style and typeface. [Example: The dropCap attribute specifies … end example]
4) The value of an XML attribute is written using a constant-width style. [Example: The attribute value of auto specifies … end example]
Except for whole clauses or annexes that are identified as being informative, informative text that is contained within normative text is indicated in the following ways:
1) [Example: code fragment, possibly with some narrative … end example]
2) [Note: narrative … end note]
3) [Rationale: narrative … end rationale]
4) [Guidance: narrative … end guidance]
5General Description
This clause is informative
This Part of lSO/IEC 29500 is divided into the following subdivisions:
Front matter (Clauses 1-5);
Overview (Clause 6);
Main body (Clauses 7-9);.Annexes
Examples are provided to illustrate possible forms of the constructions described. References are used to referto related clauses.Notes are provided to give advice or guidance to implementers or programmers.
The following form the normative pieces of this Part of lSO/IEC 29500:
.Clauses 1-4, and 7-9
The following make up the informative pieces of this Part of lSO/IEC 29500:
Foreword
lntroduction.Clauses 5 and 6.All annexes
All notes and examplesEnd of informative text
6Overview
This clause is informative
This Part of ISO/IEC 29500 describes a set of XML elements and attributes, called MCE elements and attributes,the purpose of which is to enable producing applications to guide consuming applications in their handling ofany XML elements and attributes in namespaces not understood by the consuming applications.
MCE elements and attributes are intended to enable producing applications to use features added in newversions or extensions of a markup specification in the production of new documents, which neverthelessremain interoperable with consuming applications that do not understand these features.A producing
application includes MCE elements and attributes in documents to indicate to a consuming application how itcan adjust the content of the document to exclude those features that are not compatible with the version ofthe markup specification that it understands, while at the same time allowing consuming applications that dounderstand these features to make full use of them.
MCE elements and attributes define particular types of compatibility and extension constructs, as summarizedbelow:
.Namespaces can be declared to be ignorable, indicating that all elements and attributes in those
namespaces can be disregarded by consuming applications as if they were not present in the inputdocument, enabling graceful degradation of the document functionality.This allows implementationsto identify some markup as not core to the document content.
Elements in ignorable namespaces can be marked for their content to be processed that wouldotherwise be ignored.This allows producing applications to prevent loss of content nested within anelement in an ignorable namespace when processed by consuming applications that do not understand that namespace but do understand the namespace(s)of the nested content.
Namespaces can be declared that must be understood by consuming applications in order to processthe document.This allows producing applications to set minimum compatibility requirements forconsuming applications.
Alternative representations of document content can be specified.This allows producing applicationsto include content alternatives for consuming applications with differing sets of understood
namespaces and corresponding capabilities.
Application-defined extension elements enable producing applications to introduce additional featuresscoped to particular elements defined by a markup specification. Consuming applications might preserve application-defined extension elements even if they do not process them in any other way.Conceptually, a consuming application does not directly process input documents containing MCE elementsand attributes but rather uses an MCE processor to produce an output document understood by the
consuming application.BS ISO IEC 29500-3 pdf download.