====================================================
[S4]    ISO STANDARDS PUBLICATIONS GERMANE TO SGML
====================================================

The following ISO (standards) publications are listed in two groups:
(A) the SGML standard and eight other standards/documents considered
to belong to the fuller suite of 'SGML' standards; (B) other standards
which are referenced by SGML or otherwise, for various reasons, are of
interest to SGML users.  In the first list, numerically, are: the ISO
8879 (SGML) standard [63] and its amendment [64]; ISO 9069 SDIF [65],
ISO/IEC Public Text Owner Identifiers [66], ISO/IEC TR 9573 Techniques
for Using SGML [67], ISO/IEC TR 10037 Syntax-Directed Editing Systems
[68], ISO/IEC DIS 10179 DSSSL [69], ISO/IEC DIS 10180 SPDL [70],
ISO/IEC CD 10743 SMDL [71], and ISO/IEC DIS 10744 HyTime [72].

The ISO documents listed below are available from national member
bodies of ISO, but many are also available from the Graphic
Communications Association using phone (credit card) or FAX ordering.
The GCA may be reached for ordering as follows: TEL: (1 703) 519-8157;
FAX (1 703) 548-2867.  GCA's postal address is: Graphic Communications
Association; 100 Daingerfield Road, Alexandria, VA  22314.  A smaller
number of standards documents (e.g., ISO 8879, ISO 8879 Amendment, ISO
9069, ISO 9544, ISO 9573) are available from the secretary of the SGML
Users' Group at member prices: contact Mr. Stephen G. Downie; SGML
Users' Group, Secretary; c/o SoftQuad Inc.; 56 Aberfoyle Crescent,
Suite 810; Toronto, Ontario; Canada M8X 2W4; TEL: +1 416 239 4801;
FAX: +1 416 239 7105.  The address for ISO is: ISO Central
Secretariat; 1, rue de Varemb&eacute;; Case Postale 56; CH-1211 Geneva
20; SWITZERLAND; TEL: (022) 34-12-40; FAX: +41-22-33-34-30; TELEX: 23
887 iso ch.

The bibliographic information below is current through about November
1991, but incomplete citations and inaccuracies are certain to be
found. Corrections/additions/updates in support of currency and
accuracy will be welcomed.

PRIMARY ISO DOCUMENTS RELATING TO SGML:

[63]  ISO 8879:1986.  Information Processing -- Text and Office
      Systems -- Standard Generalized Markup Language (SGML).
      International Organization for Standardization.  Ref. No. ISO
      8879:1986 (E). Geneva/New York, 1986.  A subset of SGML became a
      US FIPS (Federal Information Processing Standard) in 1988.  The
      British Standards Institution adopted SGML as a national
      standard (BS 6868) in 1987, and in 1989 SGML was adopted by the
      CEN/CENELEC Standards Committees as a European standard, #28879.
      Australia has dual numbered versions of ISO 8879 SGML and ISO
      9069 SDIF (AS 3514 - SGML 1987; AS 3649 - 1990 SDIF).

      A one-page NTIS technical note on ISO 8879 as a US FIPS
      document, FIPS-PUB-152, provides the following abstract for ISO
      8879:  Abstract "This citation summarizes a one-page
      announcement of technology available for utilization.  A Federal
      Information Processing Standard (FIPS) recently approved by the
      Secretary of Commerce should help federal agencies improve their
      communications with publishing organizations.  (FIPS are
      developed by NIST for use by the federal government.)  The new
      standard, called Standard Generalized Markup Language (SGML),
      provides a common way for defining markup languages so documents
      can be transferred from author to publisher in a standardized
      format.  By providing a coherent and unambiguous syntax for
      describing the elements within a document, SGML makes it easier
      to move unformatted textual data among different installations
      and processing systems.  Developed by the International
      Organization for Standardization (ISO) and the American National
      Standards Institute (ANSI) with assistance from NIST, the SGML
      standard is already being used by the Computer-Aided Acquisition
      and Logistics Support (CALS) program of the Department of
      Defense to develop a military specification. NIST is providing
      technical support for the CALS program.  In addition, NIST has
      developed the first set of conformance tests for SGML; ISO and
      ANSI are considering using these tests for their own test
      suites."  See "Publishing Standard Allows for the Transfer of
      Documents from Author to Publisher," NTIS Tech Note, 081914000;
      National Bureau of Standards, Gaithersburg, MD; May 1989.

      The SGML standard is now (1991) in the process of its first
      five-year review.  National member bodies of ISO and other
      entities are submitting revision statements to the ISO/IEC
      JTC1/SC18/WG8 for review.  See, for example, statements by ANSI
      X3VI.8 and the SGML Users' Group, printed in the SGML Users'
      Group Newsletter 20 (September 1991) 20.  For other possible
      addenda and changes to 8879, see "Recommendations for a Possible
      Revision of ISO 8879. ISO/IEC JTC1/SC18/WG8 N931 [Part I],"
      [TAG] 12 (December 1989) 6-8 and "Recommendations for a Possible
      Revision of ISO 8879. Part II. ISO/IEC JTC1/SC18/WG8 N931,"
      [TAG] 13 (February 1990) 12-15;  "Additional Recommendations for
      a Possible Revision of ISO 8879 - Information Processing - Text
      and Office Systems (ISO/IEC JTC1/SC18/WG8 N1013," [TAG] 15
      (August, 1990) 12-14.  Balloting of 18 countries' national
      standards bodies (from 25) based upon review of the standard
      between November 15, 1990 and February 28, 1991 resulted in
      general confirmation of ISO 8879, with six requests for
      revision.  WG8 will continue to review ISO 8879 in light of the
      comments and recommendations for revision, but the standard is
      thus confirmed through 1996.  See details in "Replies on Review
      of ISO 8879 (SGML," EPSIG News 4/4 (December 1991) 8.

[64]  ISO 8879:1986 / A1:1988 (E). Information Processing -- Text and
      Office Systems -- Standard Generalized Markup Language (SGML),
      Amendment 1.  Published 1988-07-01.  Geneva: International
      Organization for Standardization, 1988.

[65]  ISO 9069:1988.  Information Processing -- SGML Support
      Facilities -- SGML Document Interchange Format (SDIF).  13
      September 1988.  Geneva/New York: International Organization for
      Standardization, 1988.  Also available as The British Standard
      Guide to SGML Document Interchange Format (SDIF), BS 7138 1989
      (ISO 9069: 1988; see in "Snippets," SGML Users' Group Newsletter
      14 (October 1989) 12.

[66]  ISO/IEC 9070:1991.  Information Processing -- SGML Support
      Facilities -- Registration Procedures for Public Text Owner
      Identifiers.  Second edition.  15 April 1991.   The "public
      text" envisioned in this standard as applied to SGML might be
      DTDs (Document Type Definitions), or declaration subsets of
      DTDs, public entity sets, etc.  Names include an owner name and
      an object identifier.  Equivalent encodings for the names in
      ASN.1 and SGML may be supplied for interchange purposes.  Note:
      "The intention of the amendment that has resulted in a 2nd
      edition is to extend 9070 beyond the simple boundaries of SGML
      only.  It is now used by 9541 (and 10036) for the definition of
      'structured names'.  A New Work Item Proposal is being submitted
      to change the title and scope of 9070 to show its extended
      usefulness." (note from Paul Ellison, December 1991)

[67]  ISO/IEC TR 9573:1988 (E). Information Processing -- SGML Support
      Facilities -- Techniques for Using Standard Generalized Markup
      Language (SGML). December 09, 1988.  Anders Berglund, editor.
      vi + 124 pages.  A major revision of the TR underway (as of May
      1990) will result in a new TR with (16) parts: (1) SGML Tutorial
      (2) Basic Techniques (3) Advanced Techniques (4) Using Short
      References for Identifying Markup (5) Using non-Latin Alphabets
      (6) Referencing and Synchronisation (7) Mathematics and
      Chemistry (8) Tables (9) Using SGML for Computer-to-Computer
      Interchange (10) Designing Applications for Database Interfacing
      (11) Application at ISO CS for International Standards and
      Technical Reports (12) Public Entity Sets for General and
      Publishing Symbols (13) Public Entity Sets for Mathematics and
      Science (14) Public Entity Sets for Latin Based Alphabets (15)
      Public Entity Sets for non-Latin Based Alphabets (16) Public
      Entity Sets for Ideograms (adapted from Ludo Van Vooren, "SGML
      Standards Committee Update: Activities of ISO SC 18 WG8," [TAG]
      14 (May 1990) 11-12.  See also Joan M. Smith in "More Liaison
      Statements to ISO," SGML Users' Group Newsletter 13 (August
      1989) 6-7.  A description of this ISO document is found in
      "Publication of Techniques for Using SGML," SGML Users' Group
      Newsletter 11 (January 1989) 3-4.  Further update of parts 1-5
      of TR 9573 will be delayed until the 5-year revision of SGML
      (ISO 8879) is completed.

[68]  ISO/IEC TR 10037:1991.  Information Processing -- SGML and Text
      Entry Systems -- Guidelines for SGML Syntax-Directed Editing
      Systems. 15 March 1991. Geneva: International Organization for
      Standardization, 1991.  The document supplies technical guidance
      for the development of context- sensitive SGML editors.  See
      "Guidelines for Syntax-Directed Editing Systems," SGML Users'
      Group Newsletter 14 (October 1989) 3.

[69]  ISO/IEC DIS 10179:1990.  Text Composition -- Document Style
      Semantics and Specification Language (DSSSL).  ISO Project
      18.15.6.01. 1988, 1989, 1990.  Edited by Sharon Adler. vi + 132
      pages.  See [1] for early commentary.  Ocasionally SGML is
      criticized for its fundamental principle (sometimes declared
      'misguided philosophy') of radically separating content from
      appearance.  DSSSL addresses this issue, although as a distinct,
      separate processing matter: DSSSL acknowledges the need to
      support the exchange of semantic information about a document's
      layout structures and other presentation or processing features.
      From the Standard's introduction:

      "This International Standard defines the Document Style
      Semantics and Specification Language (DSSSL) for the
      specification of document processing, such as formatting and
      data management functions, with the initial focus on formatting
      to both print and on display media, and data conversion.  The
      International Standard has been structured to permit future
      sections to be added to this International Standard to cover the
      areas of data management.

      The objective of the DSSSL Standard is to provide a formal and
      rigorous means of expressing the range of document production
      specifications, including high-quality typography, required by
      the graphic arts industry.  These specifications will be
      expressed using standardized basic semantics or combinations of
      the basic standard DSSSL semantics.  These semantics will allow
      users to specify fully the characteristics to be be applied
      during document processing, such as composition, pagination, and
      imposition.  The DSSSL typographic semantics may be used to form
      the basis of a standard style sheet language.   In addition,
      DSSSL includes General Language Transformation constructs which
      provide the capability to translate into an existing processing
      language, such as a data base update language (e.g., SQL) or a
      traditional text formatting language.

      A status summary based on note from Paul Ellison, December 5,
      1991: The DIS ballot on DSSSL has closed, and sufficient votes
      have been received to allow DSSSL to proceed to IS once ballot
      comments have been resolved.  Although a negative vote was
      received from three countries (UK, Germany and France), there
      were a considerable number of major and minor comments. In
      addition an extensive liaison statement has been received from
      SC18/WG3.  Resolution of these comments will take many meetings.

[70]  ISO/IEC DIS 10180:1991.  Information Processing -- Text
      Composition -- Standard Page Description Language (SPDL).
      Geneva: International Organization for Standardization, 1991.
      For a summary, see: (1) SGML Users' Group Newsletter 20
      (September 1991) 17-18; Peter J. Robinson, and Stephen M.
      Strasen, "Standard Page Description Language," Computing
      Communications 12/2 (April 1989) 85-92;  (2) "Text Composition
      Standards," SGML Users' Group Newsletter 15 (January 1990) 7-8.
      Note: ISO/IEC 10180 has now passed DIS ballot with no negative
      votes. The joint editors are expected to have the final text
      ready for publication during 1992 (so Paul Ellison, December
      1991).

[71]  ISO/IEC CD 10743:1991.  Information Technology -- Standard Music
      Description Language (SMDL).  April 1, 1991.   SMDL "defines a
      language for the representation of music information, either
      alone, on in conjunction with text, graphics, or other
      information needed for publishing or business purposes."
      Multimedia time sequence information in also supported.  SMDL is
      a HyTime application conforming to ISO/IEC DIS 10744
      Hypermedia/Time- based Structuring Language (HyTime), and an
      SGML application conforming to Standard Generalized Markup
      Language (ISO 8879:1986).  An earlier version was published by
      ANSI (American National Standards Institute), as ANSI X3V1.8M
      Journal of Development. ANSI Project X3.542-D. Standard Music
      Description Language (SMDL). X3V1.8M/SD-8. 60 pages. Sixth
      Draft. April 15, 1990.  See a description of SMDL in: Steven R.
      Newcomb, "Standard Music Description Language Complies with
      Hypermedia Standard," IEEE Computer 24/7 (July 1991) 76-79.

[72]  ISO/IEC DIS 10744:1991.  Information Technology --
      Hypermedia/Time-based Structuring Language (HyTime).  Edited by
      Charles F. Goldfarb (with assistance from Steven R. Newcomb).
      10-October-1991.  Voting on the Draft International Standard
      terminates on April 10, 1992.  Copies are available from the
      SIGhyper group, [109] below, as well as from any national member
      of ISO.  "HyTime is a standard neutral markup language for
      representing hypertext, multimedia, hypermedia, and time- and
      space-based documents in terms of their logical structure.  Its
      purpose is to make hyperdocuments interoperable and maintainable
      over the long term.  HyTime can be used to represent documents
      containing any combination of digital notations.  HyTime is
      parsable as Standard Generalized Markup Language (ISO
      8879:1986).  HyTime provides standardized means of expressing
      (1) intra- and extra-document locations, and arbitrary links
      between them, (2) the scheduling of multimedia objects in
      'finite coordinate spaces,' and (3) rendering instructions for
      arbitrarily projecting such objects onto other finite coordinate
      spaces, and other constructs."  = Abstract from CACM 34/11
      (November 1991) 67-83.  An earlier version was published as an
      ANSI (American National Standards Institute) standard: ANSI
      X3V1.8M Journal of Development. ANSI Project X3.749-D.
      HyperMedia/Time-Based Structuring Language (HyTime). X3V1.8M/SD-
      7. 68 pages. Sixth Draft. April 15, 1990.

OTHER STANDARDS RELATED TO ISO 8879:1986 (SGML):

[73]  ISO 639:1988 (E/F). Code for the Representation of Names of
      Languages.  First edition, 1988-04-01. Reference number is ISO
      639:1988 (E/F). iii + 17 pages.  Geneva: International
      Organization for Standardization, 1988. This document is a
      technical revision of ISO 639:1967, prepared by Technical
      Committee ISO/TC 37. The two-character language codes of ISO 639
      are relevant to SGML encoding in two respects.  First, the SGML
      standard (ISO 8879) itself specifies that declaration of 'public
      text language' should be given using the language code(s) from
      ISO 639; see ISO 8879-1986(E) page 36, section 10.2.2.3.
      Second, the WSD (Writing System Declaration) implemented in the
      Text Encoding Initiative uses the two-character language code of
      ISO 639 (as amended) as a 'language.code' attribute of the
      'nat.language' declaration, specifying the language in which the
      WSD is written.

      ISO 639 contains much other information about the use of
      language symbols, registration of new symbols, etc.  The
      language codes of ISO 639 are said to be "devised primarily for
      use in terminology, lexicography and linguistics, but they may
      be used for any application requiring the expression of
      languages in coded form."  The registration authority for ISO
      639 is given as Infoterm, &Ouml;sterreiches Normungsinstitut
      (ON), Postfach 130, A-1021 Vienna, AUSTRIA.

      The two-character language codes of ISO 639 are recognized as
      being inadequate for use as SGML language attributes when
      tagging text, viz, for use as global 'lang' attributes attached
      to any element to identify the language of the text element or a
      language shift. In principle, there should be nothing wrong with
      tagging language using SGML elements rather than attributes, if
      the encoder has principled reasons for not using attributes
      (e.g., indexing engines which read simple tags but not SGML
      attributes).  But the two-character codes of ISO 639 are neither
      sufficiently mnemonic nor complete for the world's languages:
      whereas ISO 639 supplies codes for only about 136 languages, the
      Ethnologue published by the Summer Institute of Linguistics
      identifies over 6100 languages (see Ethnologue: Languages of the
      World, ed. Barbara Grimes. 11th edition. Dallas, TX: Summer
      Institute of Linguistics, 1988).  A revision of ISO 639
      completed late 1990 is described as supplying 3-character
      language codes (following MARC 3-character language codes in
      part), based upon the code sequence of the American National
      Standard (ANSI Z39.53).  This draft will be circulated for
      worldwide review in 1991/92.  It remains to be seen whether
      these new ISO 639 3-character codes qualify mnemonically for use
      in SGML tagging and if the set is complete.

[74]  ISO 646:1991.  Information Processing -- 7-bit Coded Character
      Set for Information Interchange.  Geneva: International
      Organization for Standardization, 1991.  (646 IRV identical to
      ASCII)

[75]  ISO 2014:1976.  Writing of Calendar Dates in All-Numeric Form.
      Geneva/New York: ISO (International Organization for
      Standardization), 1976.  Now superseded by ISO 4166 (?).

[76]  ISO 2022:1982.  Information Processing -- ISO 7-bit and 8-bit
      Coded Character Sets -- Code Extension Techniques.

[77]  ISO 2375:1985.  Data Processing -- Procedure for Registration of
      Escape Sequences.  Geneva/New York: International Organization
      for Standardization, 1985.

[78]  ISO 4873:1985.  8-bit Code for Information Interchange --
      Structure and Rules for Implementation.  Geneva/New York:
      International Organization for Standardization, 1985.  (In 1990:
      under review as ISO/DIS 4873:1990.)

[79]  ISO 6429:1988.  Additional Control Functions for Character
      Imaging Devices.

[80]  ISO DIS 6937:1990.  Coded Character Sets for Text Communication.
      ISO DIS 6937 is under review as CD 6937:1990.  The titled parts
      are: ISO DIS 6937-1:1983  General Information; ISO DIS 6937-
      2:1983 Latin alphabetic and non-alphabetic graphic characters;
      ISO DIS 6937-2:1989 Addendum 1, Latin alphabetic and non-
      alphabetic graphic characters.  Parts 3 and 4 (DIS 6937-3 and
      DIS 6937-4) are now superseded by DIS 10538.

[81]  ISO DIS 7350-2:1990.  Text Communication -- Registration of
      Graphic Character Subrepertoires of the Graphic Character
      Repertoire of ISO 10367. Geneva/New York: International
      Organization for Standardization, 1990.

[82]  ISO 8613:1988.  Information Processing -- Text and Office
      Systems -- Office Document Architecture (ODA) and Interchange
      Formats.  1988.  For addenda, see also "Other ISO News. Addenda
      to ISO 8613," SGML Users' Group Newsletter 14 (October 1989) 3-
      4.  The ODA/ODIF standard in 8 parts.  It is also available as a
      CCITT document, according to Erik Naggum, for considerably less
      money.  The fascicles are available free from ECMA to qualifying
      parties. "ODA is also available from your favorite CCITT outlet
      as Blue Book Volume VII, fascicle VII.6, Terminal equipment and
      protocols for telematic services, T.400-T.418, and costs a
      nominal CHF 47 (or CHF 57 if you order it from CCITT yourself).
      ISO 8613 and the T.400-series are supposedly identical, as per
      ISO 8613-1, Annex B, Relationships with other standards, B.2
      Other standards, section B.2.1, second paragraph:  'The text of
      ISO 8613-1 to ISO 8613-8 are identical to the texts in the
      correspondingly numbered CCITT Recommendations T.411 to T.418
      except for mandated stylistic differences and provisions of ISO
      8613 that are outside the scope of these Recommendations'."
      (Erik Naggum [enag@ifi.uio.no], Naggum Software, Oslo, Norway,
      News comp.text, July 13, 1990)

      Fuller bibliographic coverage for ODA/ODIF is not practical
      here, given the immediate goals of the document and space
      limitations.  As pointers to the literature on ODA, here are
      five citations: (1) Appelt, Wolfgang. Document Architecture in
      Open Systems: The ODA Standard. Berlin/Heidelberg/New York:
      Springer-Verlag, 1991. ISBN: 3-540-54539-5.  (2) Bormann, U.;
      Bormann, C.; Bathe, C.  "SDE -- A WYSIWYG Editing and Formatting
      System for ODA and SGML."  In Esprit '88: Putting the Technology
      to Use.  Proceedings of the 5th Annual ESPRIT Conference
      (Brussels, November 14-17, 1988).  II:1075-1095.  Amsterdam/New
      York: Elsevier/North-Holland, 1988.  (3) Brown, H. "Standards
      for Structured Documents," The Computer Journal 32/6 (December
      1989) 505-514.  (4) Dawson, Frank; Nielsen, Fran.  "ODA and
      Document Interchange Office Document Architecture Standard."
      UNIX Review 8/3 (March 1990) 50-57.  (5) Rosenberg, Jonathan;
      Sherman, Mark; Marks, Ann; Akkerhuis, Jaap.  Multi-media
      Document Translation: ODA and the EXPRES Project.  New York, NY:
      Springer-Verlag, 1991.  ISBN 0-387-97397-4 [U.S.]; ISBN 3-540-
      97397-4 [Germany].  See also the excellent survey article in
      [24].

[83]  ISO 8632:1987.  Information Processing Systems - Computer
      Graphics - Metafile for the Storage and Transfer of Picture
      Description Information (CGM). Geneva/New York: International.

      Organization for Standardization, 1987. Note: the standard is in
      several parts. Part 2: Character Encoding; Part 3: Binary
      Encoding; Part 4: Clear-Text Encoding.

[84]  ISO 8859:1987-.  Information Processing -- 8-bit Single-Byte
      Coded Graphic Character Sets.  Multiple parts, 1987-1991.
      Titles for parts 1,2 7,8 are given below.

      Character set and character code issues are not the fundamental
      concern of SGML, since any code sets can be declared and managed
      by SGML.  On the other hand, SGML users typically value SGML for
      its intelligent handling of multi-lingual text and document
      production, so it is natural that code sets are of some
      interest.  See also the multi-byte code standards ISO 10646 [93]
      and Unicode [95] below.

      Anyone interested ISO 8859 discussions may subscribe to the
      electronic mailing list: ISO8859@JHUVM.BITNET, ASCII/EBCDIC
      character set related issues. Owner = HART@APLVM (Ed Hart).  A
      variety of ASCII/EBCDIC character set related issues are
      discussed on the ISO8859 list, including (but not limited to)
      the following: (1) Definitions of codes  (2) Translations
      between ASCII and EBCDIC ISO 8859/1 (8-bit ASCII with
      international accented characters for Latin alphabets) and ANSI
      equivalent X3.134.2-198x (3) IBM Country Extended Code Pages
      (CECPs) particularly, U.S./Canada English CECP 37, V1; and Code
      Page 850 (PC, PS/2); (4) Application/Program Product support of
      characters and codes.

[85]  ISO 8859-1: 1987 (E).  Information Processing -- 8-Bit Single-
      Byte Coded Graphic Character Sets -- Part 1: Latin Alphabet No.
      1.  First edition. 15 February 1987.  Geneva/New York:
      International Organization for Standardization, 1987.

[86]  ISO 8859-2: 1987 (E).  Information Processing -- 8-Bit Single-
      Byte Coded Graphic Character Sets -- Part 2: Latin Alphabet No.
      2.  First edition.  15 February 1987. Geneva/New York:
      International Organization for Standardization, 1987.

[87]  ISO 8859-7:1987 (E).  Information Processing -- 8-Bit Single-
      Byte Coded Graphic Character Sets -- Part 7: Latin/Greek
      Alphabet.  First edition.  15 November 1987.  Geneva/New York:
      International Organization for Standardization, 1987.

[88]  ISO 8859-8:1988 (E).  Information Processing -- 8-Bit Single-
      Byte Coded Graphic Character Sets -- Part 8: Latin/Hebrew
      Alphabet.  First edition. 1 June 1988.  Geneva/New York:
      International Organization for Standardization, 1988.

[89]  ISO DIS 9541:1989.  Information Processing -- Font and Character
      Information Interchange.  Its parts are: ISO DIS 9541-1.2  Part
      1: Architecture; ISO DIS 9541-2.2  Part 2: Interchange Format.
      Note from Paul Ellison, December 5, 1991 follows.  "ISO 9541
      Parts 1 & 2 and ISO 10036 are now published ISO standards.  An
      error in Part 2 has been found, and a 'defects procedure' will
      be set up.  DIS 9541 Part 3 is currently (December 1991) out for
      DIS ballot.  User Requirements were developed for Part 4
      (Application Specific Properties). User Requirements (UR) and
      New Work Item Proposals (NP) were developed for two amendments:
      (1) To Part 1 to add additional properties for the improved
      setting of Latin- based and of East Asian languages, and for the
      setting of script-based languages (eg Arabic and Hindi).  This
      NP will include changes to Part 2 to allow the additional
      properties to be interchanged; (2) To Part 2 only, to add
      facilities for the interchange of partial fonts, subsets of
      fonts, and families of fonts."

[90]  ISO TR 9544:1988.  Information Processing -- Computer-Assisted
      Publishing -- Vocabulary. 15 July 1988.  43 pages.  Due for
      three-year review as of late 1991; discussions are being held to
      change the editorship (Paul Ellison is currently nominated.

[91]  ISO/DIS 10036:1989.  Procedure for Registration of Glyph and
      Glyph-Collection Identifiers.  Includes the text of ISO DIS 9541
      on registration.

[92]  ISO DIS 10538: . Control Functions for Text Communication.
      Incorporates ISO 6937, parts 3 and 4, into a separate standard.

[93]  ISO/IEC DIS 10646.  Information technology - Universal Coded
      Character Set (UCS).  The DIS voting ended 1991-06-06.  Note:
      (from Harry Gaylord, December 1991) "SC2 decided on a revised
      DIS to be sent out for a four month voting period at Rennes,
      France in October.  The revised DIS should be sent to national
      bodies in January/February 1992."   As of late 1991, ISO 10646
      DIS and the consortial 'Unicode' standard, an alternative multi-
      byte code standard, were in a period of 'merger.' Both standards
      efforts attempt to define a multi-byte character encoding large
      enough to account for the world's major writing systems; the
      'merger' is a complex story which can only be summarized here.
      The following paragraphs present a characterization of the ISO
      10646 effort from the perspective of the list owner of the
      electronic discussion group.  Entry [95] below, following the
      ISO documents list, supplies information on Unicode.

      ISO10646 List: Multi-byte Code Issues. ISO10646@JHUVM.BITNET
      Owner = HART@APLVM (Ed Hart).  The purpose of the list is to
      serve as a clearing house for information on and discussion of
      multi-byte coded-character-set issues. The ISO 10646 draft and
      Unicode draft standards represent two different approaches to
      encoding the world's characters into a multi-byte code.

      Background to the disucssion: People are looking at multi-byte
      codes as a way to solve many of the problems we are experiencing
      with single-byte, 7-bit and 8-bit codes.  Although most of us do
      not need all 191 of the characters in the ISO 8859-1 character
      set (repertoire), we frequently need characters outside of this
      set; for example, bullets or nice quotation marks for
      professional looking documents, symbols for mathematics and
      science, etc.  The reason for developing multi-byte codes is
      that processing ONE multi-byte code appears easier than several
      single-byte codes.

      As of March, 1990, two coding schemes have emerged.  The
      International Organization for Standardization (ISO)
      Subcommittee 2, Working Group 2 (SC2/WG2) has developed the ISO
      10646 Multi-Octet Code.  It is now a "draft proposed" standard
      (two levels removed from being an international standard).  The
      ISO working group has been working on this project for the last
      6 years and it has been subject to unusually wide review for a
      proposed standard.  The other draft standard is the result of
      the work of a consortium of U.S. companies, mostly from the west
      coast.  It is called Unicode.  Both of these draft standards
      enable the worlds communication (newspapers and magazines) and
      business characters, ideographs, and symbols to be encoded for
      storage and communication between computers.  However, each uses
      a different approach to making the inevitable tradeoffs.

[94]  TR XXXX Operational Model for Text Description and Processing
      Language.

[95]  Unicode: A Standard International Character Code for
      Multilingual Information Processing.  Unicode is noteworthy in
      *not* being an ISO standard, but promising to become a major
      standard, more or less compatible with ISO 10646. Compare [93]
      above.

      The Unicode Consortium. The Unicode Standard: Worldwide
      Character Encoding, Version 1.0.  Volume 1.  Edited by Erica
      Liederman.  Addison-Wesley, 1991. xx + 682 pages. ISBN 0-201-
      56788-1.  An "implementor's version" of the Unicode Book volume
      one (looseleaf in binder, same text as the bound Addison-Wesley
      volume, no ISBN) comes with a diskette containing chapters 4-6.
      It is available from the Unicode Secretariat, c/o Metaphor
      Computer Systems; see the address below.  An earlier draft of
      Unicode was: Unicode 1.0. Draft Standard, Final Review Document.
      The Unicode Consortium, December, 1990.

      "Unicode is a fixed-width 16-bit multilingual character encoding
      scheme that efficiently and unambiguously represents the world's
      normal text characters for electronic information processing.
      Unicode was devised by a group of individuals and companies,
      including Apple, IBM, Metaphor, Microsoft, NeXT, Research
      Libraries Group (RLG), Sun, Xerox and others.

      "Unicode is designed to meet the need for a simple  multilingual
      character standard in electronic information systems.  The model
      for Unicode is the defacto use of ASCII, with its simple,
      unambiguous, fixed-width characters. Fixed-width characters
      simplify information processing in text streams, flat text
      files, strings, character arrays, database fields, procedure
      arguments and returns.  They simplify text operations such as
      insertion and deletion, truncation, indexing the nth character,
      etc. Conversely, variable width, context dependent encodings or
      code-page switching (that are common in other multilingual
      standards) complicate information interchange and programming.
      Since ASCII's eight-bit character size is inadequate to handle
      multilingual text, and proposals for 32-bit standard are
      unnecessarily cumbersome, Unicode adopts a 16- bit architecture
      which extends the benefits of the ASCII to multilingual text and
      adds new strengths.

      "A 16-bit character code can uniquely specify any character in
      any language that is currently used in electronic information
      systems or is likely to be used in the foreseeable future.
      Moreover, since Unicode characters are consistently 16-bits
      wide, regardless of language, no escape sequence or control code
      is required to specify any character in any language. Unicode
      handles alphabetic and ideographic character sets simultaneously
      and with equal facility.

      "Basic (kernel) computer programs that use Unicode to represent
      characters but do not display or print text can often remain
      undisturbed when new languages or characters are introduced.
      Programmers seeking to adapt a Unicode conformant program to a
      new language environment can allocate their full energies to
      specifying the contents of character sorting and string handling
      algorithms, providing proper fonts, and developing appropriate
      character rendering routines (e.g., date, time, and currency
      formats).

      "Unicode is a product of the collaboration of multilingual
      engineers, managers, linguists, and information specialists from
      various corporations world-wide.  A Unicode Consortium was
      formed in 1991 to bring Unicode to the world under the
      sponsorship of a multi-corporate, multi-national, non-profit
      organization. Membership in the consortium is open to all who
      support Unicode principles.  (Adapted from network postings)

      Contacts: (1) Unicode Consortium; c/o Kenneth Whistler; Metaphor
      Computer Systems; 1965 Charleston Road; Mountain View, CA 94043;
      USA; Email (Internet): whistler@zarasun.metaphor.com; TEL: (1
      415) 691-3600  OR  (2)  Richard McGowan; c/o NeXT Computer, Inc;
      900 Chesapeake Drive; Redwood City, CA 94063; Email (Internet):
      McGowan@next.com; TEL: (1 415) 780-4522; FAX: (1 415) 780-3714.


