Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Australian Standard
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
INFORMATION PROCESSING—
TEXT AND OFFICE SYSTEMS—
STANDARD GENERALIZED
MARKUP LANGUAGE (SGML)
This Australian Standard was prepared by Committee IS/1, Information Processing
Systems. It was approved on behalf of the Council of the Standards Association of
Australia on 27 October 1987 and published on 1 December 1987.
Review of Australian Standards. To keep abreast of progress in industry, Australian Standards are subject
to periodic review and are kept up to date by the issue of amendments or new edit ions as necessary. It is
important therefore that Standards users ensure that they are in possession of the latest editi on, and any
amendments thereto.
Full detail s of all Australi an Standards and related publications will be found in the Standards Australi a
Catalogue of Publications; this information is supplemented each month by the magazine ‘The Australi an
Standard’, which subscribing members receive, and which gives details of new publications, new editi ons
and amendments, and of withdrawn Standards.
Suggesti ons for improvements to Australi an Standards, addressed to the head off ice of Standards Australia,
are welcomed. Notif ication of any inaccuracy or ambiguit y found in an Australi an Standard should be made
without delay in order that the matter may be investigated and appropriate action taken.
AS 3514—1987
Australian Standard
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
INFORMATION PROCESSING—
TEXT AND OFFICE SYSTEMS—
STANDARD GENERALIZED
MARKUP LANGUAGE (SGML)
Incorporating:
Amdt 1—1996
PREFACE
This Standard was prepared by the Association’s Committee on Information
Processing Systems. It is identical with and has been reproduced from International
Standard ISO 8879—1986;drawn up by ISO TC 97, Information Processing Systems.
This Standard:
— specifies an abstract syntax known as the Standard Generalized Markup Language
(SGML). The language expresses the description of a document’s structure and
other attributes, as well as other information that makes the markup interpretable.
— specifies a reference concrete syntax that binds the abstract syntax to specific
characters and numeric values, and criteria for defining variant concrete syntaxes.
— defines conforming documents in terms of their use of components of the
language.
— defines conforming systems in terms of their ability to process conforming
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
Contents
0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
0.1 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
0.2 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
0.3 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2 Field of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
3 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5 Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
5.1 Syntactic Tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.2 Ordering and Selection Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
6 Entity Structure . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. . . . . . . . . . . . . . . . . . . . . 33
6.1 SG ML Document . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. . . .. . . . . . . . . . . . . . . . . 33
6.2 SG ML Entities . . . . . . . . . . . . . . . . . . . . . . . . .. .. .. .. . . .. . . . . . . . . . . . . . . . . 33
6.2.1 S Separator . . . . . . . . . . . . . . . . . . . . .. .. .. .. . . .. . . . . . . . . . . . . . . . . 34
6.2.2 Entity End . . . . . . . . . . . . . . . . . . . . . . .. .. .. . . . . .. . . . . . . . . . . . . . . . . 34
6.2.3 Implied SG ML Declaration . . . . . . . . . . . . .. .. .. . . .. . . . . . . . . . . . . . . . . 34
6.3 Non-SG ML Data Entity . . . . . . . . . . . . . . . . . . .. .. .. .. . . .. . . . . . . . . . . . . . . . . 34
8 Processing Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.1 Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Annexes
A.5 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . 77
A.6 Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . 77
B Basic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figures
9 Element Markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
COPYRIGHT
AS 3514—1987 14
a) Descriptive markup predominates and is — Markup declarations that allow the user to define
distinguished from processing instructions. a specific vocabulary of generic identifiers and
attributes for different document types.
Descriptive markup includes both generic
identifiers and other attributes of document — Provision for arbitrary data content. In
elements that motivate processing instructions. generalized markup, “data” is anything that is
The processing instructions, which can be in any not defined by the markup language. This can
language, are normally collected outside of the include specialized “data content notations”
document in procedures. that require interpretation different from general
As the source file is scanned for markup and text: formulas, images, non-Latin alphabets,
the various elements are recognized, the previously formatted text, or graphics.
processing system executes the procedures
associated with each element and attribute for — Enti ty references : a non-system-specific
that process. For other processes, different technique for referring to content located outside
procedures can be associated with the same the mainstream of the document, such as
elements and attributes without changing the separately-written chapters, pi characters,
document markup. photographs, etc.
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
When a processing instruction must be entered — Special delimiters for processing instructions to
directly in a document, it is delimited differently distinguish them from descriptive markup.
from descriptive markup so that it can easily be Processing instructions can be entered when
located and changed for different processes. needed for situations that cannot be handled by
the procedures, but they can easily be found
b) Markup is formally defined for each type of and modified later when a document is sent to
document. a different processing system.
A generalized markup language formalizes
document markup by incorporating “document For a generalized markup language to be an
type definitions”. Type definitions include a acceptable standard, however, requires more than
specification (like a formal grammar) of which just providing the required functional capabilities.
elements and attributes can occur in a The language must have metalinguistic properties,
document and in what order. With this in order to satisfy the constraints imposed by the
information it is possible to determine whether need to use it in a multiplicity of environments. The
the markup for an individual document is correct major constraints, and the means by which the
(that is, complies with the type definition) and Standard Generalized Markup Language addresses
also to supply markup that is missing, because them, can be summarized as follows:
it can be inferred unambiguously from other
markup that is present. a) Documents “marked up” with the language must
be processable by a wide range of text
NOTE — A more detailed introduction to the concepts of processing and word processing systems.
generic coding and the Standard Generalized Markup Language
can be found in annex A.
The full form of the language, with all optional
features, offers generality and flexibility that can
0.2 Objectives be exploited by sophisticated systems; less
powerful systems need not support the features.
The Standard Generalized Markup Language To facilitate interchange between dissimilar
standardizes the application of the generic coding systems, an “SGML declaration” describes any
and generalized markup concepts. It provides a markup features or concrete syntax variations
coherent and unambiguous syntax for describing used in a document.
whatever a user chooses to identify within a
document. The language includes:
b) The millions of existing text entry devices must
— An “abstract syntax” for descriptive markup of be supported.
document elements.
SGML documents, with the reference concrete
— A “reference concrete syntax” that binds the syntax, can easily be keyboarded and
abstract syntax to particular delimiter characters understood by humans, without machine
and quantities. Users can define alternative assistance. As a result:
concrete syntaxes to meet their requirements.
COPYRIGHT
15 AS 3514—1987
— Use of SGML need not await the development g) The language must not depend on a particular
and acceptance of a new generation of data stream or physical file organization.
hardware — just software to process the
documents on existing machines. The markup language has a virtual storage
model in which documents consist of one or
— Migration to such a new generation (when it more storage entities, each of which is a
comes) will be easier, as users will already be sequence of characters. All real file access is
familiar with SGML. handled by the processing system, which can
decide whether the character sequence should
c) There must be no character set dependency, as be viewed as continuous, or whether it should
documents might be keyed on a variety of reflect physical record boundaries.
devices. h) “Marked up” text must coexist with other data.
The language has no dependency on a A processing system can allow text that
particular character set. Any character set that conforms to this International Standard to occur
has bit combinations for letters, numerals, in a data stream with other material, as long as
space, and delimiters is acceptable. the system can locate the start and end of the
conforming text.
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
The concrete syntax can be changed with the However, it is recognized that many
SGML declaration to accommodate any implementers will want to take advantage of the
reserved system characters. language’s information capture capabilities to
provide intelligent editing or to create SGML
e) There must be no national language bias. documents from a word processing front-end
environment. SGML accommodates such uses
The characters used for names can be by providing the following capabilities:
augmented by any special national characters. — Element content can be stored separately
Generic identifiers, attribute names, and other from the markup.
names used in descriptive markup are defined
by the user in element and entity declarations. — Control characters can be used as
delimiters.
The declaration names and keywords used in
markup declarations can also be changed. — Mixed modes of data representation are
permitted in a document.
Multiple character repertoires, as used in — Multiple concurrent logical and layout
multi-lingual documents, are supported. structures are supported.
f) The language must accommodate familiar
typewriter and word processor conventions. 0.3 Organization
The organization of this International Standard is as
The “short reference” and “data tag” capabilities
follows:
support typewriter text entry conventions.
Normal text containing paragraphs and a) The physical organization of an SGML
quotations is interpretable as SGML although it document as an entity structure is specified in
is keyable with no visible markup. clause 6.
COPYRIGHT
AS 3514—1987 16
h) The logical organization of an SGML document b) Specifies a reference concrete syntax that binds
as an element structure, and its representation the abstract syntax to specific characters and
with descriptive markup, is specified in clause 7. numeric values, and criteria for defining variant
concrete syntaxes.
c) Processing instructions are discussed in
clause 8. c) Defines conforming documents in terms of their
use of components of the language.
d) Common markup constructs, such as
characters, entity references, and processing
instructions are covered in clause 9. d) Defines conforming systems in terms of their
ability to process conforming documents and to
e) Markup declarations with general applicability recognize markup errors in them.
(comment, entity, and marked section) are
specified in clause 10. e) Specifies how data not defined by this
International Standard (such as images,
f) Markup declarations that are used primarily to graphics, or formatted text) can be included in a
specify document type definitions (document conforming document.
type, element, notation, short reference
This is a free 17 page sample. Access the full version at http://infostore.saiglobal.com.
p) Markup declarations that are used primarily to a) Identify or specify “standard” document types, document
architectures, or text structures.
specify link process definitions (link type, link
attribute, link set and link set use) are defined in
b) Specify the implementation, architecture, or markup error
clause 12. handling of conforming systems.
COPYRIGHT
This is a free preview. Purchase the entire publication at the link below: