This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.
This document was written by Manoj Srivastava
This guideline is intended to be intepreted as SGML sub-policy (not official policy). While this document does not carry the weight of official policy, it is sufficient basis for the submission of bugs against a package. This may change at a latter date.
Entity Management is generally left up to the implementation, and hence there are no extant Standards that cover this. However, lack of an established convention would prevent different segments of the SGML subsystem from co-operating with each other, hence it is important that a policy be established so that SGML package maintainers may depend on other parts of the system behaving consistently.
SGML can refer to an external file (really an entity) with an external identifier: this is a public identifier or a system identifier, or both.
A typical public identifier looks like
A system identifier looks like
To map external identifiers to file names, one should first try the system identifier, as a file name, and then search entity catalog files and then search the list of file names derived from the public identifier. The catalog format is according to SGML/Opens resolution on entity management. The catalog consists of a series of entries and comments. A comment is delimited by -- like in a markup declaration.
The fallback derivation of the file name is modelled after the
Contiguous white space is compacted to a single space and replaced with an underscore (_); the characters / to % are also replaced with _. The text class is down-cased. The language specifier (i.e., //EN) and anything following it should be removed.
There are a number of other files, though not entities
referenced by Document instances, are still required by the
SGML subsytem to parse or validate the document. These files
are also covered by this document.
Declaration Files: Any declaration file should be put
in /usr/lib/sgml/declaration
Notations: These files go in
/usr/lib/sgml/notation.
A few public and system identifiers pairings are shown below.
The first four actually exist in Debian.
This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version.
This document was written by Manoj Srivastava
This guideline is intended to be intepreted as SGML sub-policy (not official policy). While this document does not carry the weight of official policy, it is sufficient basis for the submission of bugs against a package. This may change at a latter date.
Entity Management is generally left up to the implementation, and hence there are no extant Standards that cover this. However, lack of an established convention would prevent different segments of the SGML subsystem from co-operating with each other, hence it is important that a policy be established so that SGML package maintainers may depend on other parts of the system behaving consistently.
SGML can refer to an external file (really an entity) with an external identifier: this is a public identifier or a system identifier, or both.
A typical public identifier looks like
A system identifier looks like
To map external identifiers to file names, one should first try the system identifier, as a file name, and then search entity catalog files and then search the list of file names derived from the public identifier. The catalog format is according to SGML/Opens resolution on entity management. The catalog consists of a series of entries and comments. A comment is delimited by -- like in a markup declaration.
The fallback derivation of the file name is modelled after the
Contiguous white space is compacted to a single space and replaced with an underscore (_); the characters / to % are also replaced with _. The text class is down-cased. The language specifier (i.e., //EN) and anything following it should be removed.
There are a number of other files, though not entities
referenced by Document instances, are still required by the
SGML subsytem to parse or validate the document. These files
are also covered by this document.
Declaration Files: Any declaration file should be put
in /usr/lib/sgml/declaration
Notations: These files go in
/usr/lib/sgml/notation.
A few public and system identifiers pairings are shown below.
The first four actually exist in Debian.