STANDARD ST.32
RECOMMENDATION FOR THE MARKUP OF PATENT DOCUMENTS USING SGML
(STANDARD GENERALIZED MARKUP LANGUAGE)
Revision adopted by the PCIPI Executive Coordination
Committee
at its seventeenth session on November 24, 1995
TABLE OF CONTENTS
................................................................
INTRODUCTION.......................................................................................................................................................................
DEFINITIONS...........................................................................................................................................................................
CHARACTER SETS.................................................................................................................................................................
REFERENCES..........................................................................................................................................................................
REQUIREMENTS OF THE RECOMMENDATION........................................................................................................................
PART 1: SGML MARKUP FOR
COMMON TEXT.......................................................................................................................
GENERAL TEXT.....................................................................................................................................................................
TABLE OF SGML TAGS...................................................................................................................................................
SGML TAGS: DESCRIPTION AND USAGE....................................................................................................................... 9
DOCUMENT STRUCTURE......................................................................................................................................... 9
<PATDOC> : PATent
DOCument.............................................................................................................................. 9
<SDOxx> : Sub‑DOcument
tags............................................................................................................................ 10
<CHG> :
CHanGe....................................................................................................................................................
<BCHG> :
Beginning of a CHanGe.........................................................................................................................
<ECHG> :
End of CHanGe......................................................................................................................................
<H> :
Headings.......................................................................................................................................................
<P> :
Paragraphs................................................................................................................................................... 11
<PC> :
Paragraph Continuation.............................................................................................................................. 11
<BR> :
BReak.........................................................................................................................................................
<FOO> :
FOOtnotes................................................................................................................................................
<FOR> :
FOotnote Reference................................................................................................................................
TEXT ‘HIGHLIGHTING’
MARKUP...........................................................................................................................
<B> :
Bold...............................................................................................................................................................
<BAI> : BAIkaku.................................................................................................................................................... 11
<HAN> : HANkaku.................................................................................................................................................. 11
<I> : Italic............................................................................................................................................................... 11
<O> :
‘Over’ embellishments...................................................................................................................................
<U> :
Under embellishments...................................................................................................................................
<SB> :
SuBscript....................................................................................................................................................
<SP>:
SuPerscript..................................................................................................................................................
MISCELLANEOUS..................................................................................................................................................
<CHF> :
CHaracter Fraction constructs................................................................................................................
<CHFBR> :
CHaracter Fraction BReak...................................................................................................................
<FLA> :
FLoating Accents.....................................................................................................................................
<FLAC> :
FLoating ACcent....................................................................................................................................
<LTL> :
LiTeraL text..............................................................................................................................................
PAGE STRUCTURE TAGS......................................................................................................................................
<TXF> :
TeXt Frame...............................................................................................................................................
<DP> :
Document Page..........................................................................................................................................
<PCL> :
Page CoLumn...........................................................................................................................................
<PLN> :
Page LiNe.................................................................................................................................................
LISTS...................................................................................................................................................................................
TABLE OF SGML TAGS AND ATTRIBUTES...................................................................................................................
SGML TAGS: DESCRIPTION
AND USAGE.....................................................................................................................
<DL> :
Definition List..............................................................................................................................................
<DT> :
Definition Term............................................................................................................................................
<DD> :
Definition Description..................................................................................................................................
<OL> :
Ordered List...............................................................................................................................................
<SL> :
Simple List..................................................................................................................................................
<UL> :
Unordered List............................................................................................................................................
<LI> :
List Item......................................................................................................................................................
IMAGES...............................................................................................................................................................................
TABLE OF SGML TAGS AND ATTRIBUTES...................................................................................................................
SGML TAGS: DESCRIPTION
AND USAGE.....................................................................................................................
<EMI> :
EMbedded Image......................................................................................................................................
<ELE> :
Embedded image LEgend.........................................................................................................................
<EMR> :
EMbedded image Reference....................................................................................................................
<RTI> :
Replacement of Text by Image.................................................................................................................
<GAI> :
GAIji..........................................................................................................................................................
TABLES...............................................................................................................................................................................
TABLE OF SGML TAGS AND ATTRIBUTES...................................................................................................................
SGML TAGS: DESCRIPTION
AND USAGE.....................................................................................................................
<TAB> :
TABular material.......................................................................................................................................
<TTI> :
Table TItle.................................................................................................................................................
<TCH> :
Table Column Header...............................................................................................................................
<TSH> :
Table Sub‑Header....................................................................................................................................
<TSB> :
Table StuB line.........................................................................................................................................
<ROW> :
ROW.........................................................................................................................................................
<CEL> :
CELl..........................................................................................................................................................
CHEMICAL FORMULAE......................................................................................................................................................
TABLE OF TAGS AND ATTRIBUTES..............................................................................................................................
SGML TAGS: DESCRIPTION
AND USAGE.....................................................................................................................
<CHE> :
CHEmical formula.....................................................................................................................................
<CHR> :
CHemical Reaction...................................................................................................................................
<CRF> :
Chemical ReFerence................................................................................................................................
MATHEMATICAL FORMULAE...........................................................................................................................................
TABLE OF SGML TAGS AND ATTRIBUTES...................................................................................................................
TABLE OF SGML TAGS AND ATTRIBUTES...................................................................................................................
SGML TAGS: DESCRIPTION
AND USAGE.....................................................................................................................
FORMULA AND FORMULA
REFERENCE...............................................................................................................
<F> :
inline Formula................................................................................................................................................
<DF> :
Display Formula..........................................................................................................................................
<DFG> :
Display Formula Group.............................................................................................................................
<DFREF> :
mathematical Formula REFerence.......................................................................................................
FORMULA CONTENT............................................................................................................................................. 11
<MARK> : MARK..................................................................................................................................................... 11
<MARKREF> :
MARK REFerence........................................................................................................................... 11
<BREAK> :
BREAK.................................................................................................................................................
<BOX> :
BOXes......................................................................................................................................................
<OV> :
‘OVer’ embellishments................................................................................................................................
<TENSOR> :TENSORs............................................................................................................................................ 11
<ITALIC> : ITALIC................................................................................................................................................ 11
<ROMAN> : ROMAN................................................................................................................................................ 11
<FRAC> :
FRACtions..............................................................................................................................................
<OVER> :
OVER (fraction denominator)................................................................................................................
<SUP> :
SUPerscript..............................................................................................................................................
<SUB> :
SUBscript.................................................................................................................................................
<PILE> :
PILEs......................................................................................................................................................
<ABOVE> :
ABOVE................................................................................................................................................
<FENCE> :
FENCEs................................................................................................................................................
<MIDDLE> :
MIDDLE (post)...................................................................................................................................
<PLEX> :
PLEX and <OPERATOR>:
OPERATOR................................................................................................
<SUM> :
SUMmation...............................................................................................................................................
<INTEGRAL> :
INTEGRAL.....................................................................................................................................
<PRODUCT> : PRODUCT........................................................................................................................................
<FROM> :
Operator for “limits\................................................................................................................................
<OF> :
Operator for “limits\....................................................................................................................................
<TO> :
Operator for “limits\....................................................................................................................................
<SQRT> :
SQuare RooT.........................................................................................................................................
<SQUARE> :
SQUARE............................................................................................................................................
<ROOT> :
ROOT.....................................................................................................................................................
<POWER> :
POWER................................................................................................................................................
<VEC> :
VECtors....................................................................................................................................................
<MATRIX> :
MATRIces..........................................................................................................................................
<COL> :
COLumn(s) in a matrix.............................................................................................................................
CITATIONS, NAMES AND
ADDRESSES.............................................................................................................................
TABLE OF SGML TAGS.................................................................................................................................................
CIT........................................................................................................................................................................... 11
Citation..................................................................................................................................................................... 11
Patent Document
Citations....................................................................................................................................... 11
Non‑Patent
Document Citations............................................................................................................................... 11
ARTCIT................................................................................................................................................................... 11
Article information, citation......................................................................................................................................
BOOKCIT.................................................................................................................................................................
Book Information, citation.........................................................................................................................................
DBASECIT...............................................................................................................................................................
Database Information Group, citation......................................................................................................................
Author Group...........................................................................................................................................................
BOOKID...................................................................................................................................................................
Book Identification....................................................................................................................................................
Document Identification............................................................................................................................................
Individual or Organization Data................................................................................................................................
General Name..........................................................................................................................................................
ADR.........................................................................................................................................................................
Address...................................................................................................................................................................
DATE.......................................................................................................................................................................
Date.........................................................................................................................................................................
PART 2: SGML MARKUP FOR
PATENT BIBLIOGRAPHIC DATA..........................................................................................
PATENT BIBLIOGRAPHIC DATA...........................................................................................................................................
TABLE OF SGML TAGS..............................................................................................................................................
B000 Office Specific System/File Information......................................................................................................
B100 Document Identification...............................................................................................................................
B200 Domestic Filing Data....................................................................................................................................
B300 Priority Data.................................................................................................................................................
B400 Public Availability Dates...............................................................................................................................
B500 Technical Information..................................................................................................................................
B600 References to other legally or procedurally
related domestic patent documents.......................................
B700 Parties Concerned with the Document........................................................................................................
B800 International Convention Data other than the
Paris Convention..................................................................
B900 Miscellaneous data......................................................................................................................................
INDEX OF ELEMENTS AND ATTRIBUTES..............................................................................................................................
ELEMENTS......................................................................................................................................................................
ATTRIBUTES..................................................................................................................................................................
ANNEX A: SGML DECLARATION FOR PATENT
DOCUMENTS.................................................................................
ANNEX B: DOCUMENT TYPE DEFINITION FOR
PATENT DOCUMENTS....................................................................
ANNEX C: PATENT CHARACTER ENTITY
REFERENCES (NON-ISO).........................................................................
ANNEX D: EXAMPLE PATENT DOCUMENT AND SGML
MARKUP...........................................................................
STANDARD ST.32
RECOMMENDATION FOR THE MARKUP OF PATENT
DOCUMENTS USING SGML
(STANDARD GENERALIZED
MARKUP LANGUAGE)
Revision adopted by the PCIPI Executive Coordination
Committee
at its seventeenth session on November 24, 1995
INTRODUCTION
1 This Recommendation is an application
of International Standard ISO 8879:1986, Information
Processing - Text and Office Systems - Standard Generalized Markup Language
(SGML); which is under review.
2 This
Recommendation provides for the exchange of patent documents in
machine-readable form on any exchange medium in a hardware-, software- and layout-independent format. Such independence of the representation of
the contents of a document from their intended uses is achieved by using International
Standard ISO 8879:1986, Information processing ‑ Text and office systems ‑
Standard Generalized Markup Language (SGML), to define generic identifiers
which are in turn used to mark the logical structure of each patent document.
3 International
Standard ISO 8879:1986 cannot be used per
se as the basis for document processing.
That is not the intention of the standard. Instead, ISO 8879 “standardizes the
application of generic coding and generalized markup concepts. It provides a coherent and unambiguous syntax for describing whatever a user
chooses to identify within a document”
(ISO 8879:1986 page 2). The
choice of tags, that is, the semantics
to which the syntax applies, is left to the user.
4 Therefore,
this Recommendation defines generic identifiers or “tags” for marking the
logical elements of a patent document.
The logical elements of a patent document are of two types: common text and patent-specific content.
5 Under
the terms of International Standard ISO 8879:1986 any tags may be used in a
particular document so long as the semantics are defined in an accompanying
document type definition (DTD). It is
conceivable that a patent issuing authority may choose different tags than
those specified in this Recommendation.
So long as the tags were defined in the accompanying DTD, the document
could be presented to a user on a system designed to read SGML documents. However, documents which use a DTD that
differs from that specified below cannot be considered to be in compliance with
this Recommendation even if they are in compliance with ISO 8879:1986.
6 Markup
in compliance with this Recommendation is independent of layout and
formatting. Decisions regarding layout
and formatting must be made at the time a document is presented for reading,
either on a display screen or on paper.
It is at the time of presentation that, for example, text which has been
marked as emphasized (bold, italic, etc.) is rendered in an available font
which has more or less the desired appearance.
It is at the time of presentation that the size of the display page
(screen or paper) is determined. Many
such decisions which map the generic identifiers in a document to the capabilities
of a particular physical display device (whether screen or paper) determine,
for example, how many characters will fit on one line or how much text will fit
on a display page. As a result, the
document may not have exactly the same physical appearance when it is presented
on different display devices. This
Recommendation does not address issues concerned with mapping generic
identifiers to a particular display device.
It can be expected that in the future two standards may be applied in
this area: Standard Page Description
Language (SPDL) ISO/IEC DIS 10180 and Document Style Semantics and
Specification Language (DSSSL) ISO/IEC
DIS 10179.
7 Markup
in compliance with this Recommendation should facilitate importing large sets
of documents into a database. In fact,
the extensive list of tags for patent bibliographic data will make it possible
for database vendors to more easily distinguish various information elements
with higher precision than has been possible in the past. This Recommendation does not address issues
concerned with mapping generic identifiers to database fields.
8 This
revision of ST.32 shall be referenced as version 3 (1995). This is to distinguish it from previous versions, which may still be
used for data exchange but, if so, must
be referenced as: version 1 (October
1987) or version 2 (September 1990). The
relevant DTD may then be applied to a specific version for processing, parsing,
etc. In addition it is possible to
reference the DTD to be used as an attribute to any patent document, the
default being the latest version of ST.32.
It is, of course, recommended to update files to this latest version of
ST.32 for data exchange.
DEFINITIONS
9 The
expression patent document includes
patents for invention, plant patents, design patents, utility certificates,
utility models, documents of addition thereto and published applications
therefor. (Refer also to WIPO ST.16: Recommended Standard Code for the
Identification of Different Kinds of Patent Documents)
10 Common text refers to
logical elements that could occur in any type of industrial property
information or in any kind of document, for example, paragraphs, footnotes,
subscripts, special characters, lists, embedded images, tables, chemical
formulae, mathematical formulae, etc.
Tags for common text data are specified and described in Part 1(the DTD
is in Annex B).
11 Patent-specific content
refers to logical elements that ordinarily occur only in patent documents, for
example, inventor’s name, patent number, issuing authority, priority data,
classification symbols, etc. In short,
any of the information elements identified in WIPO Standard ST.9, Recommendation
Concerning Bibliographic Data on and Relating to Patents and SPCs, as well
as some others. Tags for patent
bibliographic data are specified and described in Part 2 (the DTD is in Annex
B).
12 Markup is defined as
text that is added to the content of a document and that describes the structure and other
attributes of the document in a non-system-specific manner, independently of
any processing that may be performed on it.
Markup includes document type definitions (DTDs), entity references, and
descriptive markup (tags).
13 A document type
definition (DTD) formally defines:
·
the names of all the logical elements that are
allowed in documents of a particular type;
·
how often each logical element may appear;
·
the permissible contents for each logical
element;
·
attributes (parameters) that may be used with
each logical element;
·
the correct sequence of logical elements;
·
the names of all external and pre-defined
entities that may be referenced in a document;
·
the hierarchical structure of a document;
·
the features used from the SGML standard.
A DTD defines
the vocabulary of the markup for which SGML defines the syntax. The complete set of tags that may be found in
a particular document are listed and formally defined in its DTD which must
accompany the document. Each document in
a large set of documents which share the same DTD, that is, documents which are
of the same type, usually incorporates the DTD by reference.
14 An entity is
content that is not part of the text stream in a document but which is
incorporated into the text stream by reference to its name. In patent documents, for example, images are
external entities. Entity references can
also be used to code instances of characters not found in the ‘declared’
character set (see Character Sets below).
15 Tags define a
document’s logical structure by labelling elements of the document’s content
using the generic identifiers declared in the DTD.
16 The hierarchy of
SGML tags used in this Recommendation follows the general structure of a patent
document. The level in the hierarchy is
indicated by the appropriate SGML tag describing a generic logical
element. A generic logical element is a
component of the text such as the entire document, a specific sub‑document,
a paragraph, a list, etc. Each generic
logical element is described by a start tag and end tag.
level sgml
tag (example)
Document <PATDOC>
. Sub‑document <SDOXX>
. . Text
Component (Paragraph) <P>
. . . Text Element (Subscript) <SB>
. . . . Character
. . . End </SB>
. . End </P>
. End </SDOXX>
End </PATDOC>
17 International Standard ISO 8879:1986
defines an abstract syntax and a reference concrete syntax. The reference concrete syntax for SGML tags
is as follows:
Start End
Tag Tag
This
is <B> text </B> that will appear emphasized as
bold ...
Where
< is
the opening delimiter for Start Tags (1 character)
</ is
the opening delimiter for End Tags (2 characters)
> is
the closing delimiter for both Start Tags and End Tags (1 character)
B is the generic identifier of this
particular tag, defined in the DTD
A generic
identifier is a name that identifies a generic logical element. The text between the start tag and the end
tag is a specific instance of the generic logical element. Depending upon the generic identifier,
parameters may be required. In the
description of the various tags in this Recommendation, parameters are referred
to as “attributes” in conformance with ISO practice. For an explanation of the relationship
between reference concrete syntax and abstract syntax, see International
Standard ISO 8879:1986.
18 The following is a brief example of SGML markup:
<PATDOC>
<SDOBI
LA=EN>
<B100>
(Minimum bibliographic tags would need to be added here)
</SDOBI>
<SDODE
LA=EN>
<H LVL=0>FABRIC SOFTENER
COMPOSITION</H>
<H LVL=1>TECHNICAL
FIELD</H>
...
<H LVL=1>SUMMARY OF THE
INVENTION</H>
<P N=11>The present
invention relates to an aqueous fabric softener composition comprising:
<SL>
<LI>(A) from 1% to 50% by
weight of ... cyclic amines of the formula
<EMI FILE=“92102108”
wherein n is 2 or 3,
R<SB>1</SB> and
...
<LI>(B) from 3% to 20% by
weight of (A)
...
</SL>
</SDODE>
</PATDOC>
In the example
above <EMI FILE=“92102108” <PATDOC> and </PATDOC> mark the
beginning and end of a patent respectively.
The other tags in the example are explained below and there are more
extensive examples in Annex D.
CHARACTER SETS
19 The data content of the majority of documents, including
patents, consists of data characters.
The data characters could be in any language consisting of many types of
character (‘character’ is used in its broadest sense here to include graphical
symbols). In this recommendation only
one coded character set is referenced:
ISO 646. This is probably the
most common system independent
character set in use today. Characters not
in this code set should be represented by public entity references - preferably
those contained in ISO 8879 - these are referenced in the DTD in Annex B. Note that other character sets and character
entity references are possible. It is
not recommended to use the code pages contained in WIPO ST.31 since these can lead to problems in data
interchange, are not easily maintained and are not as commonly used and
accepted as the ISO 646 code page.
REFERENCES
20 The following documents are of
fundamental importance to this Recommendation:
International Standard ISO 8879:1986, Information processing ‑ Text and office systems ‑
Standard Generalized Markup Language (SGML);
Technical Report ISO/IEC/TR 9573:1988(E) Information processing ‑ SGML support facilities ‑
Techniques for using SGML;
International Standard ISO 639:1988, Code for the Representation of Names of Languages.
International Standard ISO 646:1991, Information Processing ‑ ISO 7‑bit coded character set
for information interchange.
WIPO Standard ST.3,
Recommended Standard Two-Letter Code for
the Representation of States, Other Entities and Intergovernmental
Organizations;
WIPO Standard ST.9,
Recommendation Concerning Bibliographic
Data on and Relating to Patents and SPCs;
WIPO Standard ST.16,
Recommended Standard Code for the
Identification of Different Kinds of Patent Documents.
21 For additional information concerning SGML the following
publications may be of interest (please note there is now a considerable amount
of literature, books and periodicals, on SGML, as well as many user groups, the
list below is only a small selection):
American National Standards Institute. Electronic
manuscript preparation and markup. (Z39.59). Transaction Publishers : New Brunswick
(USA) and London, 1991.
ISBN 0887389457.
Association of American Publishers. Electronic Manuscript Series : Author’s
guide to electronic manuscript preparation and markup; Reference
manual on electronic manuscript preparation and markup; Markup
of mathematical formulas; Markup of tabular material. Dublin,
Ohio : Electronic Publishing Special Interest Group
(EPSIG), 1989.
Bryan, Martin. SGML :
an author’s guide to the Standard Generalized Markup Language (SGML). Wokingham :
Addison‑Wesley, 1988. ISBN
0201175355.
Goldfarb, Charles F. The SGML handbook. Oxford
: OxfordUniversity
Press, 1990. ISBN 0 19 853737 9.
Van Herwijnen,
Eric. Practical SGML. 2nd.ed. Dordrecht : Kluwer Academic Publishers, 1994. ISBN 0792394348
REQUIREMENTS OF THE RECOMMENDATION
22 Documents which conform to this Recommendation shall be
marked up in conformance with:
·
International Standard ISO 8879:1986,
Information Processing ‑ Text and Office
Systems ‑ Standard Generalized Markup Language (SGML);
·
the DTD contained in Annex B.
23 Documents which conform to this Recommendation shall use the reference concrete syntax defined in
International Standard ISO 8879:1986.
See also Annex A: SGML Declaration for Patent Documents.
24 The DTD contained in Annex B shall be provided separately
from the individual documents in the collection of documents to which it
applies.
25 Each document to which the DTD in Annex B applies will
incorporate the DTD by reference.
26 Reference to the DTD contained in Annex B shall be made by
use of its “public name” which has been [will be] registered with the
appropriate international authority and is declared below in Annex B.
27 No document in conformance with this Recommendation shall
refer to or incorporate by reference a DTD 1) for which a public name has not
been registered with the appropriate international authority; 2) which does not
appear in this Recommendation.
28 It may happen that some particularly unusual document
contains some text or image portion(s) which cannot be rendered for the end
user with adequate fidelity, in the judgement of the issuing authority, without
the introduction of one or more logical elements not contained in Annex B. In that event:
281 The issuing authority shall provide
constructive notice to end users that some documents contain exceptional
elements. Where possible, the exact
identification of such documents shall be provided, either as a list of
document numbers or contiguous ranges of document numbers.
282 The issuing authority shall make every
attempt to have the required logical element(s) introduced into the appropriate
DTD contained in the appropriate section of this Recommendation, so that other
issuing authorities may take advantage of them, and so that presentation system
vendors may take account of them in preparing presentation software and hardware.
283 The issuing authority may, at its
discretion, include the required logical element(s) in a supplementary DTD
which is incorporated by reference into the DTD(s) that apply to the
document(s) in question until such time as the elements are incorporated into
this Recommendation.
2831 A supplementary DTD shall not be incorporated
directly into the document(s) to which it applies.
2832 A supplementary DTD shall not contain any
duplicate logical elements included in the DTD contained in ST.32, Annex B.
2833 If a supplementary DTD is provided,
constructive notice shall be given to the end user to that effect.
PART 1: SGML MARKUP FOR COMMON TEXT
The tags described in this part of ST.32 indicate text portions
that are not specific to any one type of industrial property information and
may therefore be used in any document conforming to ST.32.
GENERAL TEXT
|
TABLE OF SGML TAGS
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<B>
|
Bold
|
Indicates the beginning of text to be highlighted at the
time of presentation by using a bold typestyle. An end tag is required.
|
|
<BAI>
|
BAIkaku
|
Indicates Japanese text portion to be highlighted using
an expanded font. An end tag is
required.
|
|
<BCHG>
|
Beginning of a CHanGe
|
Indicates the beginning of a change in bibliographic data
only. Attributes required. It is an empty element which should be
followed by <ECHG>.
|
|
<BR>
|
line BReak
|
Indicates the position in the text at which a line break
occurs. No end tag is necessary.
|
|
<CHF>
|
CHaracter Fraction
|
Indicates a character construct consisting of two or more
characters in a ‘fraction type’ construct.
Use with the <CHFBR>
tag. An end tag is required.
|
|
<CHFBR>
|
CHaracter Fraction BReak
|
Indicates the break point in a character ‘fraction’
construct consisting of two or more characters in a ‘fraction type’
construct. No end tag is necessary.
|
|
<CHG>
|
CHanGe
|
Indicates the beginning of a change (not in bibliographic
data). Attributes required. An end tag is required
|
|
<DP>
|
Document Page
|
Indicates the beginning of a new page. The attribute N=
is required. No end tag is necessary.
|
|
<ECHG>
|
End of a CHanGe
|
Indicates the end of a change in bibliographic data
only. Attributes required. It is an empty element which should be
preceded by <BCHG>.
|
|
<FLA>
|
FLoating Accents
|
This indicates a character enhanced with a particular
attributing feature. An end tag is
required.
|
|
<FLAC>
|
FLoating ACcents
|
This indicates the attributing feature in a floating
accent construct. No end tag is
necessary.
|
|
<FOO>
|
FOOtnote
|
Indicates a footnote.
Attributes required. An end tag
is required.
|
|
<FOR>
|
FOotnote Reference
|
Indicates a reference to a previous footnote. Attributes required. An end tag is required.
|
|
<H>
|
Heading level
|
Indicates a separate text portion that precedes text
parts, for example, paragraphs. An end
tag is required.
|
|
<HAN>
|
HANkaku
|
Indicates Japanese text portion to be highlighted using a
compressed font. An end tag is
required.
|
|
<I>
|
Italic
|
Indicates the beginning of text to be highlighted at the
time of presentation by using an italic typestyle. An end tag is required.
|
|
<LTL>
|
LiTeraL
|
Indicates the beginning of text in which the space,
indents, line endings, etc., should be preserved as keyed in the original
document. An end tag is required.
|
|
<O>
|
‘Over’ embellishments
|
Indicates the beginning of text to be covered by an over,
or mid, embellishment of a particular designated style (attribute) at the
time of presentation. An end tag is
required.
|
|
<P>
|
Paragraph
|
Indicates a text portion known as a paragraph and implies
that the text will begin on a new line.
No end tag is necessary.
|
|
<PATDOC>
|
PATent DOCument
|
Indicates the beginning of a patent document instance
(file). An end tag is required.
|
|
<PC>
|
Paragraph
Continuation
|
Indicates a continuation of an interrupted
paragraph. No end tag is necessary.
|
|
<PCL>
|
Page CoLumn
|
Indicates the beginning of a new column. The attribute N=
is required. No end tag is necessary.
|
|
<PLN>
|
Page LiNe
|
Indicates the beginning of a new line. The attribute N=
is required. No end tag is necessary.
|
|
<SB>
|
SuBscript
|
Indicates the beginning of text which is to be placed as
a subscript to the preceding text outside mathematical formulae. An end tag is required.
|
|
<SDOxx>
|
Sub-DOcument
|
Indicates the beginning of a sub-document whose identity
(xx) is included in the tag. An end
tag is recommended.
|
|
<SP>
|
SuPerscript
|
Indicates the beginning of text which is to be placed as
a superscript to the preceding text outside mathematical formulae. An end tag is required.
|
|
<TXF>
|
TeXt Frame
|
This indicates a rectangular area of text of a page. No end tag is necessary.
|
|
<U>
|
Under embellishment
|
Indicates the beginning of text to be highlighted with an
under embellishment of a particular style (attribute) at the time of
presentation. An end tag is required.
|
|
TABLE OF
ATTRIBUTES
|
|
ATTRIBUTE
|
NAME
|
DESCRIPTION
|
|
ALIGN
|
ALIGN
|
Alignment of data.
|
|
CY
|
CountrY code
|
Indicates country code based on ST.3
|
|
DATE
|
DATE
|
Date : in the
format YYYYMMDD
|
|
DNUM
|
Document Number
|
Identifier of document (publication or application
number)
|
|
DTD
|
Document Type Definition
|
Version number of the DTD.
|
|
FILE
|
File name
|
The file name of a patent document or image file.
|
|
FN
|
Footnote Number
|
Unique identification for a footnote
|
|
FNREF
|
Foot Note REFerence
|
Unique identification for a footnote reference
|
|
FONT
|
FONT
|
Font used in text frames
|
|
FR
|
FRame
|
Frame number within a page
|
|
HE
|
HEight
|
Height of images in mm
|
|
ID
|
IDentifier
|
Has various parameters depending on tag
|
|
KIND
|
KIND
|
Kind of document based on ST.16
|
|
LA
|
LAnguage
|
Indicates sub-document language
|
|
LS
|
Line Spacing
|
Line spacing in text frames
|
|
LVL
|
LeVeL
|
Indicates the level of a heading
|
|
LX
|
X coordinate
|
X coordinate of image in 1/10mm
|
|
LY
|
Y coordinate
|
Y coordinate of image in 1/10mm
|
|
N
|
Number
|
Indicates numbers for
paragraphs, pages, etc.
|
|
POS
|
POSition
|
Indicates various parameters depending on the tag
|
|
SIZE
|
SIZE
|
Font size in text frames
|
|
STATUS
|
STATUS
|
Indicates status of patent document and/or change
|
|
STYLE
|
STYLE
|
Indicates the style of various attributes, for example,
over characters, etc.
|
|
TYPE
|
TYPE
|
Type of embellishment
|
|
WI
|
WIdth
|
Width of images in mm
|
SGML TAGS: DESCRIPTION AND USAGE
DOCUMENT STRUCTURE
1 <PATDOC> : PATent DOCument
This is the mandatory identifier with which every patent
document must start. An end tag is
required.
Required Attribute(s):
None.
Optional Attribute(s):
FILE=name Where
‘name’ is the name of the patent
document file, which contains the document instance.
STATUS= Status
of the patent document, eg. contains changes, republished, deleted, withdrawn,
etc.
Note: It
is recommended that the following optional attributes should be used only when
the mandatory tags, giving document identification, contained in the
<SDOBI> sub-document, are not used.
This may be the case, for example, when only partial information is
exchanged between offices.
CY=xx Where
xx is the country or organisation, according to WIPO ST.3, publishing or issuing the patent
document. <B190>
DATE=YYYYMMDD Date of
publication. <B140>
DNUM=n Where
n is the document number, usually the publication number but may also be the
application number. <B110> or
<B210>
KIND=xx Where
xx is the kind of patent document code taken from WIPO ST.16.
<B130>
DTD=n Where
n is the version number of the DTD applied to a particular patent
document. The default is ST.32 Version 3
(1995).
DTD Syntax:
<!ELEMENT patdoc ‑ ‑
(sdobi,(sdoab*&sdode?&sdocl*&sdodr?&sdosr?))
+(%floats;)
>
<!ATTLIST patdoc cy
CDATA #IMPLIED ‑‑ Country, organis. St.3 ‑‑
dnum CDATA
#IMPLIED ‑‑
Identification number ‑‑
date NUMBER
#IMPLIED ‑‑ date of
publication ‑‑
file CDATA
#IMPLIED ‑‑ file
identification ‑‑
kind CDATA
#IMPLIED ‑‑ Kind of
patent St.16 ‑‑
status CDATA
#IMPLIED ‑‑ Status
of the patent doc. ‑‑
dtd NUTOKEN #IMPLIED ‑‑ Version NUMBER of DTD ‑‑>
Examples:
<PATDOC><SDOBI>Here is a WIPO Patent
Document (other tags would normally be included)</SDOBI></PATDOC>
<PATDOC FILE92101123 CY=EP DATE=19921212 DNUM=0500111
KIND=A1>
<SDOBI>Here
is a European Patent Office application with a search report (A1)(other
tags would normally be included)</SDOBI></PATDOC>
2 <SDOxx> : Sub‑DOcument tags
This is the mandatory identifier with which every sub‑document
must start. An end tag, although
optional, is recommended.
Where xx = sub‑document identifier
Possible sub‑documents are:
<SDOAB> ABstract
<SDOBI> BIbliographic data
<SDOCL> CLaims
<SDODE> DEscription
<SDODR> DRawings
<SDOSR> Search Report
Required Attribute(s):
None.
Optional Attribute(s):
CY=country
code Indicates the country where
the sub‑document “CLAIMS” especially relate to, abbreviated in accordance
with WIPO Standard ST.3 country code.
LA=language
code Indicates language of the sub‑document
in accordance with International Standard ISO 639:1988.
STATUS= Status
of the patent sub-document, eg. contains changes, republished, deleted,
withdrawn, etc.
DTD Syntax:
<!ELEMENT sdobi ‑ o
(B000?,B100,B200?,B300?,B400?,B500?,B600?,B700?,B800?,
B900?)
+(bchg|echg) ‑‑ Bibliographic data ‑‑>
<!ELEMENT sdoab ‑ o
((h|p|pc|%img;)+) ‑‑
Abstract ‑‑>
<!ELEMENT sdodr ‑ o (emi+) ‑‑ Drawings ‑‑>
<!ELEMENT sdode ‑ o
(h|p|pc|%img;)+ ‑‑
Description ‑‑>
<!ELEMENT sdocl ‑ o (h|p|%lst;)+ ‑‑ Claims ‑‑>
<!ELEMENT sdosr ‑ o ((B510?,B520?,B560?,B580?)|(emi)+) --
Search report -->
<!ATTLIST (sdobi|sdoab|sdode|sdocl|sdodr|sdosr)
la NAME #IMPLIED
‑‑ language(ISO 639)
‑‑
cy NAME #IMPLIED
‑‑ country code
‑‑
status CDATA #IMPLIED -- Status of the sub-doc. -->
Examples:
<SDOBI>
<B500><B542>Here
is bibliographic data - it should contain other tags also</B500>
</SDOBI>
<SDOCL LA=F>
<OL>
<LI>Dispositif de reséquencement (RU) pour un
noeud d’un système de commutation de cellules, chaque cellule étant constituée
d’un nombre variable de sous‑cellules ayant une longueur fixe, ce noeud
comportant .....
<LI> ...
</OL>
</SDOCL>
<SDOAB LA=D>
<P>Die
vorliegende Erfindung betrifft Impfstoffe auf Basis von Bovinen Herpesviren des
Typs 1 (BHV‑1) die Änderungen in Bereichen ihres Genoms enthalten, die
für nicht‑essentielle Teile essentieller Proteine kodieren. Mit Hilfe dieser Impfstoffe können geimpfte
von nicht‑geimpften Rindern unterschieden werden. Die Erfindung betrifft ferner Verfahren zur
Isolierung und Herstellung der geänderten BHV‑1 Stämme, Isolierung und
Herstellung der geänderten Proteine und Peptide.
</SDOAB>
<SDOCL LA=D CY=AT>
<OL>
<LI>Mikroorganismus DSM 7329 und DSM 7330.
<LI>Verfahren zur Herstellung von L‑¡‑Aminosäuren
durch enzymatische Umsetzung eines D‑, L‑ und/oder D,L‑5‑monosubstituierten
Hydantoins und/oder einer D‑, L‑ und/oder D,L‑N‑Carbamoyl‑¡‑aminosäure,<BR>
</OL>
</SDOCL>
3 <CHG> : CHanGe
This indicates data which has been ‘changed’ (it could also
indicate the original text). An end tag
is required.
Required Attribute(s):
DATE=YYYYMMDD Indicates the date on which the text was
changed.
STATUS= Indicates the status of the
change, the value of this attribute has been left open but one letter codes are
recommended, eg. A = amended text, D = deleted text, O = Original text.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT chg ‑ ‑
(h|p|pc|(%ptext;))* ‑‑
Change text ‑‑>
<!ATTLIST chg date
NUMBER #REQUIRED ‑‑ Date of change text ‑‑
status
CDATA #REQUIRED ‑‑ Status of the change ‑‑>
Example:
<P><CHG DATE=19950321 STATUS=A>This data was
amended on 21 March 1995</CHG>
4 <BCHG> : Beginning of a CHanGe
This indicates bibliographic data which has been ‘changed’
(it could also indicate the original text).
It is an empty element - it should be followed by <ECHG>.
Required Attribute(s):
DATE=YYYYMMDD Indicates the date on which the text was
changed.
STATUS= Indicates the status of the
change, the value of this attribute has been left open but one letter codes are
recommended, eg. A = amended text, D = deleted text, O = Original text.
Optional Attribute(s):
None
DTD Syntax:
<!ATTLIST bchg date
NUMBER #REQUIRED ‑‑ Date data changed ‑‑
status
CDATA #REQUIRED ‑‑ Status of the change ‑‑>
Example:
<B235><BCHG DATE=19960321
STATUS=A><DATE>19960321</DATE><ECHG></B235>
5 <ECHG> : End of CHanGe
This indicates the end of data which has been ‘changed’ in
bibliographic data (it could also indicate the original text). It is an empty element - it should be
preceded by <BCHG>.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT echg ‑
o EMPTY ‑‑ End of
changed bibliographic data -->
Example:
<B235><BCHG DATE=19960321
STATUS=A><DATE>19960321</DATE><ECHG></B235>
6 <H>
: Headings
This indicates levels of headings which may be treated
differently. An end tag is required.
Required Attribute(s):
None.
Optional Attribute(s):
LVL=n Indicates the level of the heading
ALIGN= Indicates the alignment
of the header which may be centre, left, right - left is the default.
DTD Syntax:
<!ELEMENT h ‑ -
(%ptext;)+ -‑ Header ‑‑>
<!ATTLIST h lvl NUMBER
#IMPLIED ‑‑ Header
level --
align (%align;) “left” -- alignment ‑‑>
Examples:
<H>This is a default heading</H>
<H LVL=0>This is the title heading</H>
<H LVL=1>This is a sub‑section heading</H>
7 <P>
: Paragraphs
This indicates a text portion commonly known as a
paragraph. No end tag is necessary.
Required Attribute(s):
None.
Optional Attribute(s):
N=nnnnnn Consisting of a 6‑digit sequence number
indicating every paragraph in a document or sub‑document. Leading zeros may be dropped.
ALIGN= Indicates
the alignment of the paragraph which may be centre, left, right - left is the
default.
Example:
<P>First text paragraph.<P>Second
text paragraph.
<P N=1>First text paragraph.<P
N=2>Second text paragraph.
DTD Syntax:
<!ELEMENT p - o (%ptext;)+ ‑‑ Paragraph
elements ‑‑>
<!ATTLIST p n NUMBER #IMPLIED ‑‑ Reference number --
align
(%align;) “left” -- alignment ‑‑>
8. <PC> : Paragraph
Continuation
This indicates an interruption in a paragraph, for example,
by a figure, table, etc. The existing
paragraph should be continued. No end
tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT pc ‑ o (%ptext;)+ ‑‑ Paragraph
continuation ‑‑>
Example:
<P N=12>Here starts a new text paragraph, it
contains an EMI:
<EMI ID=‘2.1’ HE=10 WI=20 TI=CF>
<PC>and continues without paragraph formatting
...
9 <BR> : BReak
This indicates a line break in general text. No end tag is necessary. Whether and how the break tag is interpreted
at the time of presentation is not specified in this Recommendation. Note that this tag should not be used in
mathematical formulae where <BREAK>
is used.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT br ‑ o
EMPTY ‑‑
Line break ‑‑>
Example:
|
This line must break here
and also break here
but that’s all for this paragraph.
|
<P>This line must
break here<BR>and
also break here<BR>but
that’s all for this paragraph.
|
Note: the
above example assumes that the break tag is interpreted at the time of
presentation as forcing a line break in the text. Other interpretations are possible.
10 <FOO> : FOOtnotes
This tag identifies a text portion which is the contents of
a footnote. The footnote should be
inserted in the text stream at the point where it is first referred to. The presentation software will cause the
footnote to appear, usually, at the bottom of the page. An end tag is required.
Required Attribute(s):
FN=nnnn.nn Consisting of a 4‑digit
sequence number indicating the page number of the original document on which
the footnote occurred and a 2‑digit sequence number indicating the
sequence of footnotes on that particular page.
Optionally, it may be replaced by a sequential numbering of footnotes
within a document, in which case use Either form is valid. It must be a unique reference in the
document. Leading zeros may be dropped.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT foo ‑ ‑
(%ptext;)+ ‑‑ Footnotes ‑‑>
<!ATTLIST foo fn NUTOKEN
#REQUIRED ‑‑
Footnote id. ‑‑>
Example:
... text *<FOO FN=‘10.1’>* This is the text of the
footnote - to be placed at the foot of a page - note that the asterisk “*” is
also part of this footnote</FOO> ....
Note: The
indicator, in this case “*”, is NOT inserted by application software, as is
normal, because in patent documentation it is often not possible to change data
submitted by a patent applicant.
11 <FOR> : FOotnote Reference
This indicates from which point(s) in a document a footnote
is referenced. An end tag is required.
Required Attribute(s):
FNREF=nnnn.nn Consisting of a 4‑digit
sequence number indicating the original page number on which the footnote
occurred and a 2‑digit sequence number indicating the sequence of footnotes on that particular page. This attribute should contain exactly the
same value as the attribute of the referenced footnote (FN=). Optionally, it may be
replaced by a sequential numbering within a document, in which case use FNREF=nnnnnn. Either form is
valid. Leading zeros may be dropped.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT for ‑ ‑
(%ptext;)+ ‑‑
Footnote reference ‑‑>
<!ATTLIST for fnref NUTOKEN
#REQUIRED ‑‑
Footref id. ‑‑>
Example:
text<FOR FNREF=‘10.1’>*</FOR> ...
Note:
At the time of presentation this
should result in the SAME footnote as first appeared on page 10 of the original
document being produced on the page where <FOR> is used. This may occur, for example, if there is a
page break during processing between the two footnote references which were
originally on the same page.
TEXT ‘HIGHLIGHTING’
MARKUP
Note: The
following codes: <B>, <BAI>,
<HAN>, <I>, <O>, <U>, <SB> and <SP> may be
regarded as tags which can be used to mark characters, words, phrases, etc. as
‘highlighted’, that is emphasised in some way.
In other instances they may be replaced by a ‘pure’ SGML tag such as <HPn>,
highlighted phrase, where n is the numeric value assigned to a particular form
of highlighting which is determined at the time of presentation ( bold, italic,
etc.). However, for patent documents,
for the purposes of readability, it is recommended that the codes below be used
instead. (Highlighted phrase identifiers
are not contained in the DTD).
12 <B> : Bold
This indicates a text portion to be highlighted as
bold. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT b ‑ ‑
(%ptext;)+ ‑(b) ‑‑
Bold typeface ‑‑>
Example:
|
This text is bold
|
<B>This
text is bold</B>
|
13 <BAI> : BAIkaku
This indicates a Japanese text portion to be highlighted
using an expanded font. An end tag is
required.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT bai ‑ ‑
(%ptext;)+ ‑(bai|han) ‑‑
Expanded font ‑‑>
14 <HAN> : HANkaku
This indicates a Japanese text portion to be highlighted
using a compressed font. An end tag is
required.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT han ‑ ‑
(%ptext;)+ ‑(han|bai) ‑‑
Compressed font ‑‑>
15 <I> : Italic
This indicates a text portion to be highlighted as
italic. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT i ‑ ‑
(%ptext;)+ ‑(i) ‑‑ Italics ‑‑>
Example:
|
This text is italic
|
<I>This
text is italic</I>
|
16 <O> : ‘Over’ embellishments
The over-character tag is used to identify parts of text over
which special accents or diacritical marks are to be placed.
Note: the
‘mark’ could also be placed mid character.
In mathematical formulae use <OV>.
An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
POS= The position attribute defines the
position of the mark and takes one of the values: above or mid. The default value is above.
STYLE= The style attribute defines the style of the
mark. It takes one of the values: single, double, triple, dash, dots, or
bold. The default value is single.
TYPE= The type attribute defines the type of the
mark to be used. It takes one of the
values: dot, dotdot, dot3, dot4, tie,
tiebrace, hat, hacek, acute, grave, cedil, ring, macron, ogonek, dblac, breve,
tilde, vec, rvec, dyad, circle, caret, prime, dprime, plus, none, bar. The default value is bar.
Note: Not
all combinations of type and style attribute values would normally be used, eg
typetilde, style=dots.
DTD Syntax:
<!ELEMENT o ‑ ‑
(%ptext;)+ ‑(o|ov) ‑‑
‘Over’ embellishment ‑‑>
<!ATTLIST o pos (above|mid) “above” ‑‑ position of ‘over’
embellishment ‑‑
type (%type;)
“bar” ‑‑ types of
embellishment(default bar) ‑‑
style
(%style;) “single” ‑‑ Line
style (default single) ‑‑>
Examples:
|
|
<O>This
text has a single continuous bar over the whole sentence</O>
|
|
-----------
The word example is covered by a
dashed bar
|
The word <O STYLEDASH>example</O>
is covered by a dashed bar.
|
17 <U> : Under embellishments
The under-character tag is used to identify parts of text
under which special accents or diactrical marks may be placed - typically an
underscore. In mathematical formulae use
<OV POS=BELOW>. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
STYLE= The style attribute
defines the style of the mark. It takes
one of the values: single, double,
triple, dash, dots, or bold. The default
value is single.
TYPE= The type attribute
defines the type of the mark to be used.
It takes one of the values: dot,
dotdot, dot3, dot4, tie, tiebrace, hat, hacek, acute, grave, cedil, ring,
macron, ogonek, dblac, breve, tilde, vec, rvec, dyad, circle, caret, prime,
dprime, plus, bar. The default value is
bar.
Note: Not
all combinations of type and style attribute values would normally be used, eg
typetilde, styledots.
DTD Syntax:
<!ELEMENT u ‑ ‑
(%ptext;)+ ‑(u|ov) ‑‑
Underscore embellishment ‑‑>
<!ATTLIST u type
(%type;) “bar” ‑‑ types
of embellishment(default bar) ‑‑
style(%style;)”single” -- Line style
(default single) ‑‑>
Examples:
|
This text has a single
continuous underscore for the whole sentence.
The word example is underscored with a double bar.
|
<U>This
text has a single continuous underscore (bar) for the whole sentence.</U>
The word <U STYLE=DOUBLE>example</U>
is underscored with a double bar.
|
18. <SB> : SuBscript
This indicates a text portion to be placed as a subscript
(inferior) to the immediately preceding character. An end tag is required. See also the <SUB> tag used in
mathematical formulae.
Required Attribute(s):
None
Optional Attribute(s):
POS= The position
attribute takes one of the values: pre,
mid or post, post being the default.
DTD Syntax:
<!ELEMENT sb ‑ ‑
((%hil;)|(#PCDATA))* ‑(fla) ‑‑ Subscript ‑‑>
<!ATTLIST (sp|sb) pos (PRE|MID|POST) “POST” ‑‑ Position (default
post) ‑‑>
Example:
H2O H<SB>2</SB>O
19 <SP>: SuPerscript
This indicates a text portion to be placed as a superscript
(superior) to the immediately preceding character. An end tag is required. See also the <SUP> tag used in
mathematical formulae.
Required Attribute(s):
None
Optional Attribute(s):
POS= The position
attribute takes one of the values: pre,
mid or post, post being the default.
DTD Syntax:
<!ELEMENT sp ‑ ‑
((%hil;)|(#PCDATA))* ‑(fla) ‑‑ Superscript ‑‑>
<!ATTLIST (sp|sb) pos (PRE|MID|POST) “POST” ‑‑ Position (default
post) ‑‑>
Example:
Xn‑1 X<SP>n‑1</SP>
MISCELLANEOUS
20 <CHF> : CHaracter Fraction
constructs
This indicates ‘fraction’ constructs in general text. The alignment of ‘numerator’ and
‘denominator’ is centred by default. It should be used only in general
text. An end tag is required.
See also the ‘true’ fraction tag, <FRAC>, used
in mathematical formulae.
Required Attribute(s):
None
Optional Attribute(s):
ALIGN= Indicates the alignment
of the numerator and/or denominator, which
may be centre, left, right - centre is the default.
Example: (See below)
21 <CHFBR> : CHaracter Fraction BReak
This identifies the start of a character fraction
‘denominator’. No end tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
STYLE= The style attribute
defines the style of the mark preceding the character fraction
denominator. It takes one of the
values: single, double, triple, dash,
dots, or bold. The default value is
single.
TYPE= The type attribute
defines the type of the mark to be used preceding the character fraction
denominator. It takes one of the
values: dot, dotdot, dot3, dot4, tie,
tiebrace, hat, hacek, acute, grave, cedil, ring, macron, ogonek, dblac, breve,
tilde, vec, rvec, dyad, caret, circle, plus, prime, dprime, bar, none. The default value is bar.
Note: Not
all combinations of type and style attribute values would normally be used, eg
typetilde, styledots.
DTD Syntax:
<!ELEMENT chf ‑ ‑
(((#PCDATA)|(%hil;))+, chfbr) ‑‑ character fraction ‑‑>
<!ATTLIST chf align (%align;) “centre” ‑‑ alignment ‑‑
<!ELEMENT chfbr ‑
o ((#PCDATA)|(%hil;))+ ‑‑
character fraction break ‑‑>
<!ATTLIST chfbr type
(%type;) “bar” ‑‑
types of embellishment(default bar) ‑‑
style (%style;) “single” --
Line style (default single) ‑‑>
Examples:
20 <CHF>20<CHFBR TYPE=NONE>D</CHF>
D
22. <FLA> : FLoating Accents
This indicates a character, or characters,
enhanced with a particular attributing feature(s). It enables “composite” characters not in a
character set to be composed from characters and character entity
references. It should be used in
combination with the <FLAC>
tag. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
fla ‑ ‑
(((#PCDATA)|(%hil;))+, flac) ‑‑
Floating accent construct -->
23. <FLAC> :
FLoating ACcent
This indicates the start of a floating accent to
be placed above, mid, or below a base character, or characters, above is the
default. It enables “composite”
characters not in a character set to be composed from characters and character
entity references. It should be used in
combination with the <FLA>
tag. No end tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
POS= The
position attribute takes one of the values:
above, mid or below, above being the default.
DTD Syntax:
<!ELEMENT
flac ‑ o ((#PCDATA)|(%hil;))+
‑‑ Floating accent (upper part) -->
<!ATTLIST
flac pos (ABOVE|MID|BELOW) “ABOVE” ‑‑
Position (default above) ‑‑>
Examples:
Å <FLA>A<FLAC>ˆ</FLA>
a <FLA>a<FLAC>•</FLA>
24. <LTL> : LiTeraL text
Indicates the beginning of text in which the
space, indents, line endings, etc., should be preserved as keyed in the
original layout. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
WI=nnn Width: 3‑digit expression in millimetres.
DTD Syntax:
<!ELEMENT
ltl ‑ - CDATA ‑‑ Literal
text -->
<!ATTLIST
ltl wi
NUMBER #IMPLIED ‑‑ Width in mm ‑‑>
Example:
|
This text
has a special
layout
which
must be
preserved
exactly
as entered.
|
<LTL>
This text
has a special
layout
which
must be
preserved
exactly
as entered.
</LTL>
|
PAGE
STRUCTURE TAGS
The following tags are specific to patent
document processing and are to be used to indicate page structure in order to allow exact
citation of pages, page numbers, columns and lines. For post processing of the data these tags
can, of course, be ignored if required.
25. <TXF> : TeXt Frame
This indicates an area of text within a page of
a document. An end tag is not allowed -
it is an EMPTY element.
Required Attribute(s):
FR=nnnn Consisting
of a 4‑digit sequence number within a page.
HE=nnn Height: 3‑digit expression in millimetres.
WI=nnn Width: 3‑digit expression in millimetres.
Optional Attribute(s):
LX=nnnn 4‑digit
X‑coordinate expressed in 1/10 millimetres referencing to the top left
corner of the page.
LY=nnnn 4‑digit
Y‑coordinate expressed in 1/10 millimetres referencing to the top left
corner of the page.
FONT=name The font
used in the text frame, eg Courier, Helvetica, etc.
SIZE=nn A 2
digit number for the point size of the font.
LS=n Where
n is the number (may be decimal) of the line spacing within the text frame.
DTD Syntax:
<!ELEMENT
txf ‑ o EMPTY ‑‑ Text
frame ‑‑>
<!ATTLIST
txf fr NUTOKEN #REQUIRED ‑‑ Txf identity ‑‑>
he NUMBER
#REQUIRED ‑‑
Height in mm ‑‑>
wi NUMBER
#REQUIRED ‑‑
Width in mm ‑‑>
lx NUMBER
#IMPLIED ‑‑
X‑coord 1/10 mm ‑‑>
ly NUMBER
#IMPLIED ‑‑
Y‑coord 1/10 mm ‑‑>
font CDATA #IMPLIED ‑‑ Font name ‑‑>
size NUMBER #IMPLIED ‑‑ Font point
size ‑‑>
ls NUTOKEN #IMPLIED ‑‑ Line spacing ‑‑>
Example:
<PATDOC CY=JP>
<SDOAB>
<TXF FR=0001 HE=080 WI=080 LX=0200 LY=1800>
<P>Japanese Patent Office abstract...
</SDOAB></PATDOC>
26. <DP>
: Document Page
This indicates the beginning of a page. No end tag is necessary.
Note: The use of this tag is
optional since it is a formatting tag.
It may be discarded at the time of presentation. However, it may be useful for patent
documents where page citation is common and may need to be preserved in
electronic document systems.
Required Attribute(s):
N=nnnn 4‑digit
number being the page number per document.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
dp ‑ o EMPTY ‑‑ Document
page break ‑‑>
<!ATTLIST
dp n
NMTOKEN #REQUIRED ‑‑ Document page
number ‑‑>
Example:
<DP N=6>This
is the start of page 6
27. <PCL> : Page CoLumn
This indicates the beginning of a column in a
page. It should always be preceded by
<TXF> tag. No end tag is
necessary.
Note: The use of this tag is
optional since it is a formatting tag.
It may be discarded at the time of presentation. However, it may be useful for patent
documents, where column citation is used, and may need to be preserved in
electronic document systems.
Required Attribute(s):
N=nnnn 4‑digit
number being the column number.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
pcl ‑ o EMPTY ‑‑ Page
column ‑‑>
<!ATTLIST
pcl n
NMTOKEN #REQUIRED ‑‑ Page column number ‑‑>
Example:
<PCL N=2>This
is the start of column 2
28. <PLN> : Page LiNe
This indicates the beginning of a line within a
page. It should always be preceded by a
<TXF> tag. No end tag is
necessary.
Note: The use of this tag is
optional since it is a formatting tag.
It may be discarded at the time of presentation. However, it may be useful for patent
documents, where line number citation is common, and may need to be preserved
in electronic document systems.
Required Attribute(s):
N=nnnn 4‑digit
number being the line number.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
pln ‑ o EMPTY ‑‑ page
line ‑‑>
<!ATTLIST
pln n
NMTOKEN #REQUIRED ‑‑ page line number ‑‑>
Example:
<PLN N=15>This
is the start of line 15
LISTS
|
TABLE
OF SGML TAGS AND ATTRIBUTES
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<DD>
|
Definition Description
|
Indicates a text portion which is the description of a tagged
item in a definition list. No end tag
is necessary.
|
|
<DL>
|
Definition List
|
Indicates a text portion to be displayed as a list, each item
comprising a term followed by a description.
An end tag is required.
|
|
<DT>
|
Definition Term
|
Indicates a text portion which is the term in a definition
list. No end tag is necessary.
|
|
<LI>
|
List Item
|
Indicates the beginning of an item which forms part of a simple,
ordered or unordered list. No end tag
is necessary.
|
|
<OL>
|
Ordered List
|
Indicates a text portion to be displayed as a list, each item
being identified by a sequential number or letter. An end tag is required.
|
|
<SL>
|
Simple List
|
Indicates a text portion to be displayed as a simple list. An end tag is required.
|
|
<UL>
|
Unordered List
|
Indicates a text portion to be displayed as a list, each item
identified by a symbol which is defined in a required attribute (ST). An end tag is required.
|
|
ATTRIBUTE
|
NAME
|
DESCRIPTION
|
|
COMPACT
|
COMPACT
|
Indicates if lists should be processed as compact
|
|
LEVEL
|
LEVEL
|
Nesting level of a list
|
|
NUMSTYLE
|
NUMSTYLE
|
Numeric style of a list
|
|
PREFIX
|
PREFIX
|
Prefix for each list item
|
|
ST
|
STyle
|
Style (character or graphic) of an unordered list item
|
|
TSIZE
|
Term SIZE
|
Indicates the horizontal space allowed for definition terms plus
gutter space
|
SGML
TAGS: DESCRIPTION AND USAGE
29. <DL> : Definition List
This indicates a text portion known as a
definition or glossary list. A
definition list contains one or more items, each followed by its
description. The items are identified by
the <DT> identifier and the
description by the <DD>
identifier. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
TSIZE= This
attribute is used to specify the indent to be used for the definition
description. It is normally larger than
the maximum width of the terms.
COMPACT= Used to
indicate when no blank lines are to be left between definition items at the
time of presentation.
DTD Syntax:
<!ELEMENT
dl ‑ ‑ (dt,dd)+ ‑‑ Definition
list ‑‑>
<!ATTLIST
dl tsize NUMBER #IMPLIED ‑‑ Term size attribute ‑‑
compact (compact) #IMPLIED ‑‑ Spacing between items ‑‑>
Example:
(see below)
30. <DT> : Definition Term
This indicates a term in a definition list. No end tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
dt ‑ o (%ptext;) ‑‑ Definition
term ‑‑>
Example:
(see below)
31. <DD> : Definition Description
This indicates the description of an item (term)
marked <DT> in a definition
list. No end tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
dd ‑ o ((%ptext;)|p)+ ‑‑ Definition
description ‑‑>
Example: In
this example it is assumed that none of the terms exceed the length that may
have been specified as default for such lists.
EPO European
Patent Office <DL>
<DT>EPO
JPO Japanese
Patent Office <DD>European Patent Office
<DT>JPO
USPTO United
States Patent and Trademark Office <DD>Japanese Patent Office
<DT>USPTO
<DD>United States Patent and Trademark Office
</DL>
32. <OL> : Ordered List
This indicates a portion of structured text
known as a list. An ordered list will
have a sequence of numbers or letters generated at the time the document is
created, not at the time of presentation, to indicate the relative position in
the list of each item. Lists may be
nested. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
COMPACT= Used to
indicate when no blank lines are to be left between items at the time of
presentation.
LEVEL= Used
to indicate the nesting level of a list.
NUMSTYLE= Used to
indicate the numeric style of a list.
PREFIX= Used to
indicate prefix for each list item.
DTD Syntax:
<!ELEMENT ol ‑ ‑ (li)+ ‑‑ Ordered
list ‑‑>
<!ATTLIST
ol compact (compact) #IMPLIED ‑‑
Spacing between items ‑‑
level NUMBER
#IMPLIED ‑‑
Nesting level of list ‑‑
numstyle CDATA #IMPLIED ‑‑ Numbering style ‑‑
prefix CDATA
#IMPLIED ‑‑ Prefix
for each list item ‑‑>
Example:
(see below)
33. <SL> : Simple List
This indicates a portion of structured text
known as a list. A simple list will not
have anything preceding the list items to indicate them as such. Lists may be nested. An end tag is required.
Required Attribute(s):
None
Optional Attribute(s):
COMPACT= Used to
indicate when no blank lines are to be left between items at the time of
presentation.
LEVEL= Used
to indicate the nesting level of a list.
DTD Syntax:
<!ELEMENT
sl ‑ ‑ (li)+ ‑‑ Simple
list ‑‑>
<!ATTLIST
sl compact (compact) #IMPLIED ‑‑ Spacing between
items ‑‑
level
NUMBER #IMPLIED ‑‑ Nesting level of
list ‑‑>
Example:
(see below)
34. <UL> : Unordered List
This indicates a portion of structured text
known as a list. An unordered list will
have symbols generated at the time of presentation to indicate each item. Lists may be nested. An end tag is required.
Required Attribute(s):
ST= This
attribute is followed by an identifier for the character or the graphic symbol
required to indicate each separate item in the list.
Optional Attribute(s):
COMPACT= Used to
indicate when no blank lines are to be left between items at the time of
presentation.
LEVEL= Used
to indicate the nesting level of a list.
DTD Syntax:
<!ELEMENT ul ‑ ‑ (li)+ ‑‑ Unordered
list ‑‑>
<!ATTLIST
ul st NMTOKEN
#REQUIRED ‑‑
Ulist symbol ‑‑
level NUMBER
#IMPLIED ‑‑
Nesting level of list ‑‑
compact (compact) #IMPLIED ‑‑ Spacing between
items ‑‑>
Example:
(see below)
35. <LI> : List Item
This indicates an item of a list,
<OL>,
<SL> and
<UL>. No end tag is necessary.
Required Attribute(s):
None
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
li ‑ o ((%ptext;)|p)+ ‑‑ List item ‑‑>
Examples:
|
Text
First item in a simple
list.
Second item.
more text.
|
Text<SL><LI>First item in a simple list. <LI>Second item.</SL>more text.
|
|
Text
1. First item in a
compact ordered list.
2. Second item.
more text.
|
Text<OL
COMPACT=COMPACT><LI>First
item in a compact ordered list.<LI>Second item.
</OL>more
text.
|
|
Text
·
First
item in an unordered list with ‘bullets’.
·
Second
item.
more
text.
|
Text
<UL ST=“•”>
<LI>First item in an
unordered list with ‘bullets’.
<LI>Second item.
</UL>
more text
|
Note: here we have a character
entity reference “•” since a ‘bullet’ is not a character in the base
code page ISO 646. It is contained in
the public entity references cited in the DTD at Annex B.
IMAGES
|
TABLE
OF SGML TAGS AND ATTRIBUTES
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<ELE>
|
Embedded image
LEgend
|
Indicates a portion of text directly related to an embedded
image. Attributes required. An end tag is required.
|
|
<EMI>
|
EMbedded Image
|
Indicates non character-coded data. Attributes required. No end tag is required since this is a
reference to an external image file and the tag is empty.
|
|
<EMR>
|
EMbedded image Reference
|
Indicates a reference to a previous EMI. Attributes required. No end tag is necessary since it is
self-contained and the tag is empty.
|
|
<RTI>
|
Replacement of Text by
Image
|
Indicates text that is also captured as an image. The image data may be used in place of the
text in order to guarantee that presentation is identical to the original
document. Attributes required. An end tag is necessary.
|
|
<GAI>
|
GAIji
|
Indicates a reference to a Gaiji (Japanese) dot font file which
is composed of five dot font files.
Attributes required. An end tag
is required.
|
|
ATTRIBUTE
|
NAME
|
DESCRIPTION
|
|
FILE
|
FILE
|
External file name of the image
|
|
HE
|
HEight
|
Height of images in mm
|
|
ID
|
InDentifier
|
Has various parameters depending on tag
|
|
IMF
|
IMage Format
|
Indicates the image format of a stored image.
|
|
LX
|
X coordinate
|
X coordinate of image in 1/10mm
|
|
LY
|
Y coordinate
|
Y coordinate of image in 1/10mm
|
|
TI
|
Type of Image
|
Type of image stored
|
|
WI
|
WIdth
|
Width of images in mm
|
SGML
TAGS: DESCRIPTION AND USAGE
36. <EMI> : EMbedded Image
This indicates any information which is not
character coded, for example, drawings, chemical structures, graphs, etc. It is non‑SGML data. No end tag is necessary since no text is
allowed, it is empty. The information
will normally be stored in a standard graphics file format. WIPO Standard ST.33 (compression according to CCITT Group 4) is
the recommended default.
For external references, that is, to the image
itself, we have a unique identifier to the external name of the image via the
use of a file name which, for patent documents, is usually the publication
number, or application number, of the patent document (acting as the unique
filename) in combination with the internal identification specified below.
Required Attribute(s):
ID=nnnn.nnnn Internal
identifier consisting of a 4-digit sequence number indicating the original page
number on which the image occurred and a 4‑digit sequence number
indicating the sequence of images on that particular page. (This follows the frame and sequence number
indexing methodology used in WIPO Standard ST.33).
Optionally, it may be replaced by a sequential numbering of images
within a document, in which case use ID=nnnnnnnn. Either form is valid.
HE=nnn Height: 3‑digit expression in millimetres.
WI=nnn Width: 3‑digit expression in millimetres.
Optional Attribute(s):
FILE=name Where
‘name’ is the name (with pointer if
required) of the image file, which contains the embedded image.
LX=nnnn 4‑digit
X‑coordinate expressed in 1/10 millimetres of embedded image location
referencing to the top left corner of the page.
LY=nnnn 4‑digit
Y‑coordinate expressed in 1/10 millimetres of embedded image location
referencing to the top left corner of the page.
Note : The above two attributes
should be used only when physical pages are represented. In all cases leading zeros may be dropped.
IMF= Indicates,
generally, the type of IMage Format, or File, of the stored image. Possible formats and files include:
ST33 WIPO ST.33 (default)
CGM Computer
Graphics Metafile
EPS Encapsulated
Postscript
G3 CCITT
Group 3 compression
G4 CCITT
Group 4 compression
TIFF Tag
Image File Format
IGES Initial
Graphics Exchange Format
JPEG Joint
Photographic Experts Group Format
MPEG Motion
Picture Experts Group Format
GEM Digital
Research GEM
AI Adobe
Illustrator
GIF Compuserve
Graphics Image Format
PCT Apple
Picture File Format
BMP Microsoft
Bitmap File Format
PCX Paintbrush
File Format
WMF Windows
Metafile Format
PGL Hewlett-Packard
Graphics Language
WPG WordPerfect
Graphics File format
etc.
The default format used is office-dependent and must be stated
in the DTD. Also note that they are not
mutually exclusive, for example, ST.33 and TIFF files may comprise CCITT Group 4
compression.
TI= Type
of embedded Image. Possible type names
include:
AD Abstract
Drawing
CF Chemical
Formulae
CI Clipped
Image
CP Computer
Programs
DN DNa
sequences
DR DRawings
FF undefined
characters
FG FiGures
GR GRaphs
MF Mathematical
Formulae
PA Full
PAge facsimile image
PH PHotographs
SR Search
Report forms
TB TaBular
data
TX TeXt
character(s)
UI Undefined
Images
DTD Syntax:
<!ELEMENT emi ‑
o EMPTY ‑‑ Embedded
image ‑‑>
<!ATTLIST emi id
NUTOKEN #REQUIRED ‑‑ Image identity ‑‑
he NUMBER
#REQUIRED ‑‑
Height in mm ‑‑
wi NUMBER
#REQUIRED ‑‑
Width in mm ‑‑
file
CDATA #IMPLIED ‑‑ image file name ‑‑
lx NUMBER
#IMPLIED ‑‑
X‑coord 1/10 mm ‑‑
ly NUMBER
#IMPLIED ‑‑
Y‑coord 1/10 mm ‑‑
imf (%imgfmt;)
#IMPLIED ‑‑ Format
stored emi ‑‑
ti
(AD|CF|CI|CP|DN|DR|FF|FG|GR|MF|PA|PH|SR|TB|TX|UI) #IMPLIED
‑‑
Image type ‑‑>
Examples:
<EMI ID=‘2.1’ HE=10 WI=20
TI=CF>
Identifies the first embedded
image on page 2 of the current document which is a chemical representation with
actual sizes of 10mm vertical and 20mm horizontal.
<EMI FILE=“d:\image\fig22.wpg” ID=“12.6” HE=30
WI=100 IMF=WPG TI=MF>
Note: The identity
attribute has been standardised for embedded images, footnotes and their
associated references. The use of page and
frame number generates a unique code within a document that will:
-
identify the related
entities;
-
form a means of
reference to the original document when inspecting the digitised data; and
-
bind the entities
together at the time of presentation, without regard to the fact that the final
page location may differ from that of the original document.
37. <ELE> : Embedded image LEgend
This indicates a portion of text
directly related to an embedded image.
An end tag is required.
Required Attribute(s):
ID=nnnn.nnnn Consisting
of a 4‑digit sequence number indicating the page number on which the
image occurred and a 4‑digit sequence number indicating the sequence of
images on that particular page. This
attribute contains exactly the same
values as the congruent attribute of the related embedded image. Optionally, it may be replaced by a
sequential numbering of images within a document, in which case use
ID=nnnnnnnn. Either form is valid. Leading zeros may be dropped.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT ele ‑ ‑ (%ptext;)+ ‑‑ Figure
caption ‑‑>
<!ATTLIST ele id NUTOKEN
#REQUIRED
>
Examples:
...<ELE ID=“2.1”>This is the legend of the first embedded image on page 2</ELE>...
38. <EMR> : EMbedded image Reference
This indicates a reference to an
embedded image. The tag is self‑contained. This tag should be used for refering to
images which occur more than once in a document, since the full
<EMI> tag need not be repeated
and the image need not be scanned more than once.
Required Attribute(s):
ID=nnnn.nnnn Consisting
of a 4‑digit sequence number indicating the original page number on which
the image occurred and a 4‑digit sequence number indicating the sequence
of images on that particular page. This
attribute contains exactly the same values as the congruent attribute of the
referenced embedded image. Optionally,
it may be replaced by a sequential numbering of images within a document, in
which case use ID=nnnnnnnn. Either form
is valid. Leading zeros may be dropped.
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT emr ‑ o
EMPTY ‑‑
Reference to emi ‑‑>
<!ATTLIST emr id NUTOKEN
#REQUIRED
>
Examples:
...<EMR ID=“2.1”>This is a reference to the first embedded image on page
2...
Note: For further explanation see
<EMI> above.
39. <RTI> : Replacement of Text by Image
Indicates text that is also
captured as an image. The image data may
be used in place of the text in order to guarantee that presentation is
identical to the original document. An
end tag is required. The image should be
stored in a standard format, for example WIPO Standard ST.33.
Required Attribute(s):
ID=nnnn.nnnn Consisting
of a 4‑digit sequence number indicating the page number on which the
image occurred and a 4‑digit sequence number indicating the sequence of
images on that particular page.
Optionally, it may be replaced by a sequential numbering of images
within a document, in which case use ID=nnnnnnnn. Either form is valid. In both cases leading zeros may be deleted.
HE=nnn Height: 3‑digit expression in millimetres.
WI=nnn Width: 3‑digit expression in millimetres.
Optional Attribute(s):
FILE=name Where
‘name’ is the name (with pointer if
required) of the image file, which contains the RTI image.
IMF= Indicates,
generally, the type of IMage Format, or File, of the stored image.
See <EMI> for full list.
ST33 WIPO ST.33 (default)
The
default format used is office-dependent and must be stated in the DTD. Also note that they are not mutually
exclusive, for example, a TIFF file may comprise CCITT Group 4 compression.
LX=nnnn 4‑digit
X‑coordinate expressed in 1/10 millimetres of embedded image location
referencing to the top left corner of the page.
LY=nnnn 4‑digit
Y‑coordinate expressed in 1/10 millimetres of embedded image location
referencing to the top left corner of the page.
Note: The above two
attributes are used only when physical pages are represented.
DTD Syntax:
<!ELEMENT rti ‑ ‑ CDATA ‑‑ Replace text
with image ‑‑>
<!ATTLIST rti id NUTOKEN #REQUIRED ‑‑ rti identity ‑‑
he NUMBER
#REQUIRED ‑‑
Height in mm ‑‑
wi NUMBER
#REQUIRED ‑‑
Width in mm ‑‑
file
CDATA #IMPLIED ‑‑ image file name ‑‑
lx NUMBER
#IMPLIED ‑‑ X‑coord 1/10 mm ‑‑
ly NUMBER
#IMPLIED ‑‑ Y‑coord 1/10 mm ‑‑
imf
(%imgfmt;)#IMPLIED -- image
format -->
Example:
<SDOBI><B100>Minimum B100 tags required
here<B100>
<RTI ID=00000001 HE=150 WI=170 LX=0200 LY=0300>
Japanese
Patent Office title page (bibliographic information)...
</RTI>
</SDOBI>
40. <GAI> : GAIji
This indicates a reference to a
Gaiji dot font file which is composed of five dot font files each of different
sizes. It may be of particular use
within the Japanese Patent Office. An
end tag is required.
Required Attribute(s):
ID=nnnn Consisting
of a 4‑digit number indicating the sequence number of the dot font
character in the Gaiji file.
Optional Attribute(s):
None.
DTD Syntax:
<!ELEMENT gai ‑ ‑ CDATA ‑‑ Gaiji
character ‑‑>
<!ATTLIST gai id NUTOKEN
#REQUIRED
>
Example:
TABLES
|
TABLE OF SGML TAGS AND ATTRIBUTES
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<CEL>
|
table CELl
|
Indicates start of a new cell. No end tag is necessary.
|
|
<ROW>
|
table ROW
|
Indicates start of a new row. No end tag is necessary.
|
|
<TAB>
|
TABle
|
Indicates the beginning of the tabular data. Attribute required. An end tag is required.
|
|
<TCH>
|
Table Column Header
|
For one particular column or multiple columns. No end tag is necessary.
|
|
<TSB>
|
Table StuB lines
|
For single or multiple rows. No end tag is necessary.
|
|
<TSH>
|
Table SubHeading
|
For one or more columns, same as for header. No end tag is necessary.
|
|
<TTI>
|
Table TItle
|
May appear above or below the actual table. No end tag is necessary.
|
|
ATTRIBUTE
|
NAME
|
DESCRIPTION
|
|
AL
|
ALign
|
Used to justify the tabular data
|
|
CB
|
Column Begin
|
Indicates start and end columns
|
|
CE
|
Column End
|
For straddle headers or cells
|
|
CO
|
COlumn
|
Number of columns in the table
|
|
CS
|
Column Separator
|
Column separation attributes
|
|
ID
|
IDentifier
|
Any identifier applied to the original table
|
|
OR
|
ORientation
|
Used to signal table orientation
|
|
RB
|
Row Begin
|
Indicates start and end rows
|
|
RE
|
Row End
|
For straddle stub lines or cells
|
|
ROTATION
|
ROTATION
|
Rotation of data within
a cell
|
|
RS
|
Row Separator
|
Row separation attributes
|
SGML TAGS:
DESCRIPTION AND USAGE
41. <TAB> : TABular material
This indicates the beginning of
tabular data. An end tag is required.
Required Attribute(s):
CO=nn 2‑digit
number giving the total number of columns in a table.
Optional Attribute(s):
ID= Any
identifier applied to the original table, for example, ‘TABLE 1.’
OR= Orientation.
L Landscape
P Portrait
(default)
RS= Row
Separator(s)
CS= Column
Separator(s)
RS and CS
consist of a row or column identifier and separator style.
Row
and Column identifiers are:
P Preceding
first column or row
F Following
last column or row
A All columns
or rows not explicitly identified
n Explicit
number of row or column to follow
Separator
style.
Possible
styles are:
BL blank space
between (default)
S single
D double
. T triple
B bold
DA dashed
DT dotted
DTD Syntax:
<!ELEMENT tab ‑ ‑
(row,(%rowcnt;))p)+ ‑‑
Main structure ‑‑>
<!ATTLIST tab co NUMBER
#REQUIRED ‑‑
Number of columns ‑‑
or (L|P) “P” ‑‑
Orientation ‑‑
id CDATA
#IMPLIED ‑‑
Identifier ‑‑
cs CDATA
#IMPLIED ‑‑
Col separators ‑‑
rs CDATA
#IMPLIED ‑‑ Row
separators ‑‑
Examples:
<TAB CO=5 ID=‘Table 1’>
<ROW><CEL>DATA 1<CEL>DATA 2<CEL>DATA 3<CEL>DATA 4<CEL>DATA 5
</TAB>
tabular
material consisting of five
columns of information identified as Table 1:
Table 1
|
DATA 1
|
DATA 2
|
DATA 3
|
DATA 4
|
DATA 5
|
<TAB CO=6 RS=‘P B F B A S’ CS=‘P B F B A S’>
<ROW><CEL>DATA 1<CEL>DATA 2<CEL>DATA 3<CEL>DATA 4<CEL>DATA 5<CEL>DATA 6
</TAB>
Tabular
material consisting of six columns of information surrounded by a bold box and
the rows and columns separated by single lines:
|
DATA
1
|
DATA
2
|
DATA
3
|
DATA
4
|
DATA
5
|
DATA 6
|
See also below.
42. <TTI> : Table TItle
This indicates the title of the tabular
data. A title would usually appear above
the table but it may also appear below where it would be termed a caption, but
the same tag will suffice. No end tag is
necessary.
Required Attribute(s):
None
Optional Attribute(s):
AL= L Left
R Right
C Centered
(default)
DTD Syntax:
<!ELEMENT tti ‑ o
(%ptext;)* ‑‑
Table title ‑‑>
<!ATTLIST tti al
(L|R|C) “C” ‑‑ Text
alignment ‑‑>
Example:
<TTI>Title of the
Table.
43. <TCH> : Table Column Header
This indicates the header of one
column or multiple columns in the table.
No end tag is necessary.
Required Attribute(s):
None.
Optional Attribute(s):
AL= L Left
R Right
C Centered
(default)
CB=nn 2‑digit
number giving start column in the case of a straddled header.
CE=nn 2‑digit
number giving end column in the case of a straddled header.
DTD Syntax:
<!ELEMENT tch ‑ o
(%ptext;)* ‑‑
Column header ‑‑>
<!ATTLIST tch cb NUMBER #IMPLIED ‑‑ Start column ‑‑
ce NUMBER #IMPLIED ‑‑ End column ‑‑
al (L | R | C) “C” ‑‑ Text alignment ‑‑>
Examples:
<TCH>Header for
single column
<TCH CB=1 CE=2>Header
which straddles both columns one and two.
44. <TSH> : Table Sub‑Header
This indicates the subheader of
one column or multiple columns in the table.
No end tag is necessary.
Required Attribute(s):
None.
Optional Attribute(s):
AL= L Left
R Right
C Centered
(default)
CB=nn 2‑digit
number giving start column in the case of a straddled header.
CE=nn 2‑digit
number giving end column in the case of a straddled header.
DTD Syntax:
<!ELEMENT tsh ‑ o
(%ptext;)* ‑‑
Column subhead ‑‑>
<!ATTLIST tsh cb NUMBER #IMPLIED ‑‑ Start column ‑‑
ce NUMBER #IMPLIED ‑‑ End column ‑‑
al (L | R | C)
“C” ‑‑ Text
alignment ‑‑>
Examples:
<TSH>Subheader for
single column
<TSH CB=1 CE=2>Subheader
which straddles both columns one and two.
45. <TSB> : Table StuB line
This indicates the stub line (text
descriptor) for one or more rows in the table.
No end tag is necessary.
Required Attribute(s):
None.
Optional Attribute(s):
AL= L Left
(default)
R Right
C Centered
D Decimal
E Exponent
RB=nn 2‑digit
number giving start row in the case of a straddled stub line.
RE=nn 2‑digit
number giving end row in the case of a straddled stub line.
Note: Stub lines may
straddle rows. If the leftmost column
contains row-straddling stub lines, then all stub lines must specify the
RB= (row begin) attribute. Straddling stub lines must also specify the
RE= (row end) attribute.
DTD Syntax:
<!ELEMENT tsb ‑ o
(%ptext;)* ‑‑
Stub field ‑‑>
<!ATTLIST tsb rb NUMBER #IMPLIED ‑‑ Start row ‑‑
re NUMBER #IMPLIED ‑‑ End row ‑‑
al
(L | R | C | D | E) “L” ‑‑ Text alignment ‑‑>
Examples:
<TSB RB=1>Stub line
for a single row where a subsequent stub line straddles more than one row.
<TSB RB=7 RE=8>Stub
line which straddles rows seven and eight.
46. <ROW> : ROW
This indicates the start of a new
row in the table. No end tag is
necessary.
Required Attribute(s):
None
Optional Attribute(s):
None
Note: Simple rows
contain only cells. Each cell may
contain more than one line of type.
Other rows may contain stub lines as the left‑most cell. Stub lines may straddle more than one row.
DTD Syntax:
<!ELEMENT row ‑ o
EMPTY ‑‑
Table row ‑‑>
Examples:
<ROW>row five of
table
<ROW>row six of
table.
47. <CEL> : CELl
This indicates the start of a new
data cell in the table. No end tag is
necessary.
Required Attribute(s):
None.
Optional Attribute(s):
AL= R Right
(default)
L Left
C Centered
D Decimal
E Exponent
RB=nn 2‑digit
number giving start row in the case of straddled cells.
RE=nn 2‑digit
number giving end row in the case of straddled cells.
CB=nn 2‑digit
number giving start column in the case of straddled cells.
CE=nn 2‑digit
number giving end column in the case of straddled cells.
ROTATION= Specifies
the rotation of the contents of a cell.
Note: Cells may straddle columns and/or rows. If a row contains column straddling cells,
then all cells must specify the column begin attribute. Likewise, if a row contains row straddling
cells, all cells must specify the row begin attribute. Straddling cells must also specify the row
end and/or column end attributes. Some
rows may contain stub lines as the leftmost cell. Stub lines may also straddle rows but never
columns.
DTD Syntax:
<!ELEMENT
cel ‑ o ((%ptext;)* ‑‑ Table cell ‑‑>
<!ATTLIST cel
rb NUMBER #IMPLIED ‑‑ Start row ‑‑
re NUMBER #IMPLIED ‑‑ End row ‑‑
cb NUMBER #IMPLIED ‑‑ Start column ‑‑
ce NUMBER #IMPLIED ‑‑ End column ‑‑
al (L | R | C | D | E) “R” ‑‑ Text alignment --
rotation NUMBER
#IMPLIED -- Rotation of cell
contents ‑‑>
Examples:
Simple
Table Rows
<ROW><CEL>Data<CEL>Data<CEL>Data
Complex Table Rows
<ROW><CEL CB=1>Data<CEL CB=2 CE=3>Data<CEL CB=4>Data
Table I ‑ Original
|
COOLING
SYSTEM COMPONENTS
|
|
DESCRIPTION
|
RETAIL PRICE
|
QUANTITY
|
|
|
ex VAT
|
inc VAT
|
in stock
|
|
Radiators
|
295.50
|
330.00
|
3,012
|
|
Hose
Clips
|
5.25
|
6.25
|
27,435
|
|
Lower
Pipes
|
23.66
|
26.50
|
12,445
|
|
Upper
Pipes
|
21.35
|
23.00
|
13,752
|
|
Caps
|
15.50
|
17.00
|
4,049
|
|
Pumps
|
341.00
|
375.00
|
3,553
|
Table I ‑ Structure
+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+
!
!
! <TAB CO=4> !
! +‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑-----‑‑‑‑‑‑‑‑‑‑‑+ !
! ! <TTI> ! !
! +‑‑‑‑‑‑‑‑‑‑‑‑‑‑----‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+ !
!
!
! +‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑‑--‑‑‑‑‑‑‑‑‑+ +‑--‑‑‑-+ !
! ! <TCH> ! !
<TCH> ! ! <TCH> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑---‑‑‑‑‑‑‑‑‑‑‑‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSH> ! ! <TSH> ! ! <TSH> ! ! <TSH> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
!
!
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! !
! +‑‑‑‑‑‑‑+ +‑‑‑-‑‑‑+ +‑‑--‑‑‑+ +‑‑‑‑--‑+ !
!
!
! </TAB> !
!
!
+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑---+
Table I ‑ Markup
<TAB CO=4 RS=0’PS FS AS’ CS=‘PS FS AS’>
<ROW><TTI>COOLING SYSTEM COMPONENTS
<ROW><TCH AL=L>DESCRIPTION
<TCH CB=2 CE=3>RETAIL PRICE
<TCH AL=R>QUANTITY
<ROW><TSH>
<TSH AL=R>ex Vat
<TSH AL=R>inc Vat
<TSH AL=R>in stock
<ROW><TSB>Radiators<CEL
AL=D>295.50<CEL AL=D>330.00<CEL>3,012
<ROW><TSB>Hose
Clips<CEL AL=D>5.25<CEL AL=D>6.25<CEL>27,435
<ROW><TSB>Lower
Pipes<CEL AL=D>23.66<CEL AL=D>26.50<CEL>12,445
<ROW><TSB>Upper
Pipes<CEL AL=D>21.35<CEL AL=D>23.00<CEL>13,752
<ROW><TSB>Caps<CEL
AL=D>15.50<CEL AL=D>17.00<CEL>4,049
<ROW><TSB>Pumps<CEL
AL=D>341.00<CEL AL=D>375.00<CEL>3,553
</TAB>
Table II - Original
|
TABLE 1
THE CURING OF COATING COMPOSITIONS UNDER ULTRAVIOLET LIGHT
|
|
COMPOSITION
|
TIME (MIN.)
|
D-IMPACT*
THICKNESS (MIL)
|
R-IMPACT**
ADMISSION
|
HARDNESS
|
(IN-LB)***
|
(IN-LB2)***
|
|
1
|
75
|
O.1-0.2
|
90 percent
|
8H
|
25
|
10
|
|
|
180
|
O.3-0.5
|
100 percent
|
2H
|
50
|
10
|
|
|
180
|
0.5
|
100 percent
|
HB
|
100
|
0
|
|
2
|
130
|
O.1-0.2
|
100 percent
|
8H
|
25
|
0
|
|
|
150
|
O.1-0.2
|
100 percent
|
8H
|
25
|
0
|
|
3
|
60
|
0.2
|
100 percent
|
8H
|
50
|
0
|
|
|
120
|
0.2
|
100 percent
|
8H
|
50
|
0
|
|
4
|
60
|
0.2
|
100 percent
|
8H
|
30
|
10
|
|
|
90
|
1.0
|
60 percent
|
8H
|
40
|
10
|
|
5
|
120
|
O.4-0.5
|
95 percent
|
8H
|
30
|
10
|
|
6
|
120
|
0.2
|
100 percent
|
8H
|
25
|
0
|
|
7
|
60
|
0.4
|
100 percent
|
8H
|
160
|
50
|
|
|
120
|
0.4
|
100 percent
|
8H
|
160
|
50
|
|
8
|
60
|
O.4-0.5
|
100 percent
|
8H
|
75
|
10
|
|
9
|
60
|
O.2-0.4
|
100 percent
|
8H
|
40
|
0
|
|
10
|
60
|
O.2-0.4
|
100 percent
|
8H
|
40
|
0
|
|
11
|
30
|
0.5
|
100 percent
|
8H
|
100
|
100
|
|
12
|
30
|
O.05-0.07
|
100 percent
|
6H
|
40
|
10
|
|
* Direct impact
** Reverse impact
*** Inch-Pounds
|
Table II ‑ Structure
1 2 3 4
5 6 7 Column
+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+
! Row
!
!
! <TAB CO=7 ID=‘TABLE
1’> !
!
!
! +‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+ !
! ! <TTI> ! ! 1
! +‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+ !
!
!
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TCH> ! ! <TCH>
! ! <TCH> ! ! <TCH> ! ! <TCH>
! ! <TCH> ! ! <TCH> ! ! 2
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 3
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! <CEL> ! ! <CEL> ! ! 4
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 5
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 6
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 7
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 8
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 9
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 10
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 11
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 12
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 13
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 14
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 15
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 16
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 17
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! 18
! ‑‑‑‑‑‑‑‑‑‑
‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑‑
‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑‑
‑‑‑‑‑‑‑‑‑‑ ‑‑‑‑‑‑‑‑‑
!
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! 19
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
! ! <TSB> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! <CEL> ! ! <CEL>
! ! <CEL> ! ! 20
! +‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ +‑‑‑‑‑‑‑‑+
+‑‑‑‑‑‑‑‑+ !
!
!
! </TAB>
!
+‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑+
Table II ‑
Mark‑up
<TAB CO=7 ID=‘TABLE 1’ RS=‘PS FS AS’ CS=‘PS FS AS’>
<ROW><TTI>THE
CURING OF COATING COMPOSITIONS UNDER ULTRAVIOLET LIGHT
<ROW><TCH><U>COMPOSITION</U>
<TCH><U>TIME(MIN.)</U>
<TCH>D‑IMPACT<FOR
FNREF=“18.1”>*</FOR><U>THICKNESS (MIL)</U>
<TCH>R‑IMPACT<FOR
FNREF=“18.2”>**</FOR><U>ADHESION</U>
<TCH><U>HARDNESS</U>
<TCH><U>(IN‑LB)<FOR
FNREF=“18.3”>***</FOR></U>
<TCH><U>(IN‑LB2)<FOR
FNREF=“18.3”>***</FOR></U>
<ROW><TSB RB=3 RE=5>1<CEL>75<CEL AL=C>0.1‑0.2<CEL>90 percent<CEL>8H<CEL>25<CEL>10
<ROW><CEL>180<CEL
AL=C>0.3‑0.5<CEL>100 percent<CEL>2H<CEL>50<CEL>10
<ROW><CEL>180<CEL>0.5<CEL>100 percent<CEL>HB<CEL>100<CEL>0
<ROW><TSB RB=6
RE=7>2<CEL>130<CEL AL=C>0.1‑0.2<CEL>100 percent<CEL>8H<CEL>25<CEL>0
<ROW><CEL>150<CEL AL=C>0.1‑0.2<CEL>100 percent<CEL>8H<CEL>25<CEL>0
<ROW><TSB RB=8
RE=9>3<CEL>60<CEL AL=C>0.2<CEL>100 percent<CEL>8H<CEL>50<CEL>0
<ROW><CEL>120<CEL AL=C>0.2<CEL>100 percent<CEL>8H<CEL>50<CEL>0
<ROW><TSB RB=10
RE=11>4<CEL>60<CEL AL=C>0.2<CEL>100 percent<CEL>8H<CEL>30<CEL>10
<ROW><CEL>90<CEL AL=C>1.0<CEL>60 percent<CEL>8H<CEL>40<CEL>10
<ROW><TSB
RB=12>5<CEL>120<CEL AL=C>0.4‑0.5<CEL>95 percent<CEL>8H<CEL>30<CEL>10
<ROW><TSB
RB=13>6<CEL>120<CEL AL=C>0.2<CEL>100 percent<CEL>8H<CEL>25<CEL>0
<ROW><TSB RB=14
RE=15>7<CEL>60<CEL>0.4<CEL>100 percent<CEL>8H<CEL>160<CEL>50
<ROW><CEL>120<CEL AL=C>0.4<CEL>100 percent<CEL>8H<CEL>160<CEL>50
<ROW><TSB
RB=16>8<CEL>60<CEL AL=C>0.4‑0.5<CEL>100 percent<CEL>8H<CEL>75<CEL>10
<ROW><TSB
RB=17>9<CEL>60<CEL AL=C>0.2‑0.4<CEL>100 percent<CEL>8H<CEL>40<CEL>0
<ROW><TSB
RB=18>10<CEL>60<CEL AL=C>0.2‑0.4<CEL>100 percent<CEL>8H<CEL>40<CEL>0
<ROW><TSB
RB=19>11<CEL>30<CEL AL=C>0.5<CEL>100 percent<CEL>8H<CEL>100<CEL>100
<ROW><TSB
RB=20>12<CEL>30<CEL AL=C>0.05‑0.07<CEL>100 percent<CEL>6H<CEL>40<CEL>10
<FOO FN=“18.1”>*
Direct Impact</FOO>
<FOO FN=“18.2”>**
Reverse Impact</FOO>
<FOO FN=“18.3”>***
Inch‑Pounds</FOO>
</TAB>
Note: The footnote text has
been captured within the table tag. This
will indicate to a formatter that this footnote is associated with the table
and should be presented immediately following the table rather than at the foot
of the page.
CHEMICAL
FORMULAE
|
TABLE
OF TAGS AND ATTRIBUTES
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<CHE>
|
CHEmical formula
|
Indicates the beginning of a quasilinear formula. An end tag is required.
|
|
<CHR>
|
CHemical Reaction
|
Indicates the beginning of a chemical reaction formula. An end tag is required.
|
|
<CRF>
|
Chemical ReFerence
|
Indicates the beginning of a reference to a chemical
formula. Attribute required. No end tag is necessary, it is
self-contained.
|
|
ATTRIBUTE
|
NAME
|
DESCRIPTION
|
|
ID
|
IDentifier attribute
|
A unique name.
|
|
NUM
|
NUMber
|
Used to specify an explicit formula number.
|
|
REFID
|
REFerence number
IDentification
|
An id reference value giving a unique name.
|
SGML
TAGS: DESCRIPTION AND USAGE
Note: Tagging is confined to
relatively simple formulae. No attempt
has been made to develop coding for so‑called “ring‑structures” or
Markush structures.
48. <CHE> : CHEmical formula
This indicates the beginning of a quasi‑linear
chemical formula. An end tag is
required.
Required Attribute(s):
None
Optional Attribute(s):
ID= A
unique name, which must start with a letter, eg. idxyz
NUM= Used
to specify an explicit formula number.
DTD Syntax:
<!ELEMENT che - -
(%ptext;)* -- Chemical formula -->
<!ATTLIST che
id ID #IMPLIED --
chem reaction id --
num CDATA #IMPLIED --
specific number -->
Example:
2FeCl2.FeCl3.xH2O <CHE>2FeCl<SB>2</SB>.FeCl<SB>3</SB>.xH<SB>2</SB>O
</CHE>
49. <CHR> : CHemical Reaction
This indicates the beginning of a chemical
reaction formula. An end tag is
required.
When descriptive text must appear above and/or
below an arrow the <CHF>
construct is used.
Required Attribute(s):
None
Optional Attribute(s):
ID= A
unique name, which must start with a letter, eg. idxyz
NUM= Used
to specify an explicit formula number.
DTD Syntax:
<!ELEMENT chr - -
(%ptext;)*
-- Chemical reaction -->
<!ATTLIST chr id
ID #IMPLIED -- chem reaction id --
num CDATA #IMPLIED -- specific number -->
Examples:
<CHR>BrCH=CH<SB>2</SB>+NO<SB>2</SB> Cl→CHBrClCH<SB>2</SB>NO<SB>2</SB> </CHR>
<CHR>ClCH=CH<SB>2</SB>+NOCl<CHF>NOCl
<CHFBR TYPE=VEC>
oxid.</CHF>CHCl<SB>2</SB>CH<SB>2</SB>NO <SB>2</SB></CHR>
50. <CRF> : Chemical ReFerence
This indicates from which point(s) a chemical representation
is referenced. The tag is self-contained
and therefore there is no end tag.
Although a reference might be a text string requiring no markup, markup
is recommended for purposes of searching.
Required Attribute(s):
REFID= A
unique name, which must start with a letter, eg. refid=xyz
Optional Attribute(s):
None
DTD Syntax:
<!ELEMENT
crf ‑ o EMPTY ‑‑ Reference
to che. formula ‑‑>
<!ATTLIST
crf refid IDREF #REQUIRED -- Unique reference -->
MATHEMATICAL
FORMULAE
|
TABLE
OF SGML TAGS AND ATTRIBUTES
|
|
TAG
|
NAME
|
DESCRIPTION
|
|
<ABOVE>
|
ABOVE
|
Indicates a formula value to be displayed above another formula
value. No end tag is necessary.
|
|
<BOX>
|
BOXes
|
Indicates parts of a formula to be placed in a box. An end tag is required.
|
|
<BREAK>
|
BREAK
|
This indicates a line break in the formula. The tag is self contained, ie. it has no
content.
|
|
<COL>
|
COLumn(s)
|
This indicates a column in a matrix. An end tag is required.
|
|
<DF>
|
Display Formula
|
This indicates the beginning of displayed mathematical
formula(e). An end tag is required.
|
|
<DFG>
|
Display Formula Group
|
This indicates a group of display mathematical formula(e) that
are to be processed together. An end tag is required.
|
|
<DFREF>
|
Display Formula REFerence
|
Indicates a reference to a formula. Attribute required. No end tag is necessary.
|
|
<F>
|
inline Formula
|
Indicates an inline formula.
An end tag is required.
|
|
<FENCE>
|
FENCEs
|
Indicates a fence or bracket.
An end tag is required.
|
|
<FRAC>
|
FRACtions
|
This indicates fractions.
An end tag is required.
|
|
<FROM>
|
FROM
|
Identifies the lower limit for the
<INTEGRAL>,
<PLEX>,
<PRODUCT> and
<SUM> tags. No end tag is required.
|
|
<INTEGRAL>
|
INTEGRAL
|
This indicates information to be displayed as an integral, using
the general limits form of
presentation. An end tag is
required.
|
|
<ITALIC>
|
ITALIC
|
This indicates parts of a formula to be set in italic. An end tag is required.
|
|
<MARK>
|
MARK
|
This indicates a mark for vertical alignment within a
formula. Attribute required. It is self-contained and therefore no end
tag is necessary.
|
|
<MARKREF>
|
MARK REFerence
|
This indicates a reference to a defined mark and causing the
system to vertically align the formula on that mark. Attribute required. No end tag is necessary.
|
|
<MATRIX>
|
MATRIX
|
This indicates a matrix formula.
An end tag is required.
|
|
<MIDDLE>
|
MIDDLE (post)
|
|
