BS ISO IEC TR 9573-13-1991 Information processing - SGML support facilities - Techniques for using SGML - Public entity sets for mathematics and science《信息处理 通用标记语言标准(SGML)支持设施 使用S.pdf

《BS ISO IEC TR 9573-13-1991 Information processing - SGML support facilities - Techniques for using SGML - Public entity sets for mathematics and science《信息处理 通用标记语言标准(SGML)支持设施 使用S.pdf》由会员分享，可在线阅读，更多相关《BS ISO IEC TR 9573-13-1991 Information processing - SGML support facilities - Techniques for using SGML - Public entity sets for mathematics and science《信息处理 通用标记语言标准(SGML)支持设施 使用S.pdf（66页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARD BS ISO/IEC TR 9573-13:1991 Implementation of ISO/IEC TR 9573-13:1991 Information technology SGML support facilities Techniques for using SGML Part 13: Public entity sets for mathematics and scienceBSISO/IECTR9573-13:1991 This British Standard, having been prepared under the directio

2、nof the Information Systems Technology Standards Policy Committee, was published under the authority of the Standards Boardand comes into effect on 31October1991 BSI 04-2000 The following BSI references relate to the work on this standard: Committee reference IST/18 Draft for comment90/68077 DC ISBN

3、 0 580 20060 4 Committees responsible for this British Standard The preparation of this British Standard was entrusted by the Information Systems Technology Standards Policy Committee (IST/-) to Technical Committee IST/18, upon which the following bodies were represented: British Computer Society Br

4、itish Facsimile Industry Consultative Committee British Photographic Association British Printing Industries Federation British Telecommunications plc Computing Services Association Department of Trade and Industry (Information Technology Division) EEA (the Association of Electronics, Telecommunicat

5、ions and Business Equipment Industries) HM Treasury (Central Computer and Telecommunications Agency) Her Majestys Stationery Office Institute of Information Scientists Joint Network Team Ministry of Defence National Computer Users Forum National Computing Centre Ltd. National Health Services SGML Us

6、ers Group University of London User Standards Forum for Information Technology (Institute of Data Processing Management) Amendments issued since publication Amd. No. Date CommentsBSISO/IECTR9573-13:1991 BSI 04-2000 i Contents Page Committees responsible Inside front cover National foreword ii Forewo

7、rd iii Text of ISO/IEC TR 9573-13 1BSISO/IECTR9573-13:1991 ii BSI 04-2000 National foreword This British Standard reproduces verbatim ISO/IEC TR9573-13:1991 and implements it as the UK national standard. This British Standard is published under the direction of the Information Systems Technology Sta

8、ndards Policy Committee whose Technical Committee IST/18 has the responsibility to: aid enquirers to understand the text; present to the responsible international committee any enquiries on interpretation, or proposals for change, and keep UK interests informed; monitor related international and Eur

9、opean developments and promulgate them in the UK. NOTEInternational and European Standards, as well as overseas standards, are available from BSI Sales Department, BSI, Linford Wood, Milton Keynes, MK146LE. A British Standard does not purport to include all the necessary provisions of a contract. Us

10、ers of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, theISO/IEC TR title page, pages ii to i

11、v, pages1to 56, an inside back cover and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover.ISO/IECTR9573-13:1991(E) ii BSI 04-2000 Contents Page Foreword iii Introduction

12、 1 1 Scope 1 2 Reference 1 3 Definitions 1 4 General considerations 1 4.1 Format of Declarations 1 4.2 Corresponding Display Entity Sets 2 4.3 Entity Names 2 4.4 Organization of Entity Sets 3 5 Entity names, characteristic glyph, registered glyph identifier, and short description 3 5.1 Basic mathema

13、tical and scientific symbols 4 5.1.1 General 4 5.1.2 Greek Symbols 9 5.1.3 Alternative Greek Symbols 10 5.2 Additional mathematical symbols 11 5.2.1 Ordinary Symbols 11 5.2.2 Binary and Large Operators 13 5.2.3 Relations 16 5.2.4 Negated Relations 21 5.2.5 Arrow Relations 24 5.2.6 Opening and Closin

14、g Delimiters 28 5.3 Symbols based on the Latin alphabet 29 5.3.1 Fraktur 29 5.3.2 Open Face (Blackboard Bold) 31 5.3.3 Script 32 6 Public text 34 6.1 Basic mathematical and scientific symbols 34 6.1.1 General 34 6.1.2 Greek Symbols 37 6.1.3 Alternative Greek Symbols 38 6.2 Additional mathematical sy

15、mbols 39 6.2.1 Ordinary Symbols 39 6.2.2 Binary and Large Operators 41 6.2.3 Relations 43 6.2.4 Negated Relations 47 6.2.5 Arrow Relations 49 6.2.6 Opening and Closing Delimiters 52 6.3 Symbols based on the Latin alphabet 53 6.3.1 Fraktur 53 6.3.2 Open Face (Blackboard Bold) 54 6.3.3 Script 55 Annex

16、 A (informative) Bibliography Inside back coverISO/IECTR9573-13:1991(E) BSI 04-2000 iii Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are member

17、s of ISO or IEC participate in the development of International Standards through technical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organ

18、izations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC1. The main task of technical committees is to prepare International Standards, but in ex

19、ceptional circumstances a technical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under tech

20、nical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when a technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the

21、art”, for example). Technical Reports of types1 and2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type3 do not necessarily have to be reviewed until the data they provide are considered to be no

22、longer valid or useful. ISO/IEC/TR9573-13, which is a Technical Report of type3, was prepared by Joint Technical Committee ISO/IEC JTC1, Information technology. ISO/IEC/TR9573 consists of the following parts, under the general title Information technology SGML support facilities Techniques for using

23、 SGML: Part 1: SGML tutorial; Part 2: Basic techniques; Part 3: Advanced techniques; Part 4: Using short references for identifying markup; Part 5: Using non-Latin alphabets; Part 6: Referencing and synchronisation; Part 7: Mathematics and chemistry; Part 8: Tables; Part 9: Using SGML for computer t

24、o computer interchange; Part 10: Designing application for database interfacing; Part 11: Application at ISO/CS for International Standards and Technical Reports; Part 12: Public entity sets for general and publishing symbols; Part 13: Public entity sets for mathematics and sciences; Part 14: Public

25、 entity sets for Latin based alphabets; Part 15: Public entity sets for non-Latin based alphabets; Part 16: Public entity sets for ideograms. ISO/IEC/TR9573 was first published in1988 as a single volume. The material has undergone revision and expansion and some of the tutorial material of ISO8879:1

26、986 has been incorporated in some parts: a) Part 1 replaces ISO 8879:1986AnnexesB andC (in part); b) Part 2 replaces ISO/IEC/TR9573:1988 clauses4, 5, 6, 7, 10, 13, and14, and ISO8879:1986AnnexE (in part);ISO/IECTR9573-13:1991(E) iv BSI 04-2000 c) Part 3 replaces ISO 8879:1986AnnexesC (in part), andD

27、 (in part); d) Part 5 replaces ISO/IEC/TR9573 clauses11, 12, and15; e) Part 7 replaces ISO/IEC/TR9573 clause8; f) Part 8 replaces ISO/IEC/TR9573 clause9; g) Part 12 replaces ISO 8879:1986 AnnexD (in part); h) Part 13 replaces ISO 8879:1986 AnnexD (in part); i) Part 14 replaces ISO 8879:1986 AnnexD (

28、in part); j) Part 15 replaces ISO 8879:1986 AnnexD (in part); Annex A of this part of ISO/IEC/TR9573 is for information only.ISO/IECTR9573-13:1991(E) BSI 04-2000 1 Introduction ISO 8879, Information processing Text and office systems Standard Generalized Markup Language (SGML), states the rules for

29、the description and markup of documents for publishing and interchange. ISO/IEC TR9573 complements ISO8879 by providing additional tutorial information. It is not intended, and should not be regarded, as an extension, modification, or interpretation of ISO8879. ISO/IEC TR9573 includes a tutorial on

30、the basic components of the SGML language. It includes notes on the analysis of a document prior to the writing of a formal document type definition, and a series of examples illustrating the use of SGML in various situations together with a discussion of the advantages and disadvantages of differen

31、t approaches. One example given is for a general document type, others of a general nature are for letter and memorandum, and the mixing of text and graphics. The special considerations that apply for use of SGML with non-Latin based languages, as well as linguistic applications, are discussed and e

32、xamples shown. Other parts of ISO/IEC TR9573 contain sample applications of a specialized nature, such as for mathematics, chemistry, and tables. Public entity sets covering a wide variety of widely used special graphic characters are defined. The titles of the parts of ISO/IEC TR9573 are listed in

33、the foreword. 1 Scope Tens of thousands of graphic characters are used in the publishing of text, of which relatively few have been incorporated into standard coded character sets. Even where standard coded representations exist, however, there may be situations in which they cannot be keyboarded co

34、nveniently; or in which it is not possible to display the desired visual depiction of the characters. To help overcome these barriers to successful interchange of SGML documents, this part of ISO/IEC TR9573 defines character entity sets for some of the widely used special graphic characters. The ent

35、ity repertoires are based on applicable published and proposed International Standards for coded character sets, and current industry and professional society practice. NOTE 1Entity repertoires are necessarily larger and more repetitious than character sets, as they deal in general with higher-level

36、 constructs. For example, unique entities have been defined for each accented Latin alphabetic character, while a character set might represent such characters as combinations of letters and diacritical mark characters. These public entity sets should therefore not be construed as requirements for n

37、ew standard coded character sets. In many instances upper- and lower-case is used to differentiate the names of different entities. It is thus assumed that a concrete syntax where entity names are case sensitive is used. NOTE 2In the reference concrete syntax, the entity names are case sensitive. 2

38、Reference The following standard contains provisions which, through reference in this text, constitute provisions of this part of ISO/IEC/TR9573. At the time of publication, the edition indicated was valid. All standards are subject to revision, and parties to agreements based on this part of ISO/IE

39、C/TR9573 are encouraged to investigate the possibility of applying the most recent edition of the standard indicated below. Members of IEC and ISO maintain registers of currently valid International Standards. ISO 8879:1986, Information processing Text and office systems Standard Generalized Markup

40、Language (SGML). 3 Definitions For the purposes of this part of ISO/IEC/TR9573, the definitions given in ISO8879 apply. 4 General considerations This clause discusses design criteria applicable to the public entity sets included in this part of ISO/IEC TR9573. 4.1 Format of Declarations The entity s

41、ets published here are definitional; the entity text simply consists of the entity name in square brackets, and there is a comment describing the symbol, rather than (possibly) system-dependent data that would cause a visual depiction of it to be rendered: ISO/IECTR9573-13:1991(E) 2 BSI 04-2000 If,

42、as in the following example, the comment includes a name (of any length) preceded by a solidus, the name is an identifier of a visual depiction of the character in MathSci, an expansion of mathfile, AppendixD,1/90, published by the American Mathematical Society,201 Charles St., Providence, RI02904,

43、U.S.A.NOTE 3In the MathSci document, an identifier is preceded by a reverse solidus, rather than a solidus. A comment can include a single upper-case letter, followed by a colon, as in the previous example. The letter indicates that the character belongs to a class whose glyphs are given special tre

44、atment in conventional mathematical typesetting. These characters are: 4.2 Corresponding Display Entity Sets Each character has a characteristic visual depiction a “glyph”. A system will need to provide corresponding display entity sets for the output devices it supports, in which the entity text is

45、 replaced by system data that will cause the glyph to be rendered. The entity name and descriptive comment would, of course, remain the same. For example, the declarationmight be used in a display character entity set for output devices that did not support ISO6937-2, whilemight be used in an entity

46、 set for8-bit coded devices that did. For a text formatter driving a photocomposer, a declaration like the following might be used:NOTE 4All of the entity declarations use the “SDATA” keyword as a reminder that the entity text could be system-specific character data that might require modification f

47、or different output devices and applications. 4.3 Entity Names The entity names are derived from the English language. They were chosen for maximum mnemonic value, consistent with the logical and systematic use of abbreviations. NOTE 5Translations may be desired for other languages. The entity names

48、 are case-sensitive, so the case of letters within the name can identify the case of the character, indicate the doubling of a line, or be used for some other convention. The entity names employ only letters and numerals, so they can be used with a variety of concrete syntaxes. NOTE 6If shorter name

49、s are desired for frequently used entities, they can be defined in the documents where the frequent use occurs. Some characters have different semantic connotations in different application contexts. Multiple entities were defined for some of them. NOTE 7If a different name would be more expressive in the context of a particular document, the entity can be redefined within the document. As many technical symbols can be used in more than one context, the entity names in this category normally describe the characters