P5: 전자 텍스트 부호화 및 교환에 대한 지침

TEI: The TEI Header and its Components¶2.1.1 The TEI Header and its Components

The teiHeader element should be clearly distinguished from the front matter of the text itself (for which see section 4.5 Front Matter). A composite text, such as a corpus or collection, may contain several headers, as further discussed below. In the general case, however, a TEI-conformant text will contain a single teiHeader element, followed by a single text or facsimile element, or both.

The header element has the following description:

• teiHeader (TEI 헤더) 모든 TEI 구조의 텍스트 서두에 위치하는 전자 제목 페이지를 구성하는 기술적이고 선언적인 정보를 제공한다.

  type	헤더가 부착된 문서의 종류를 명시한다. 예를 들어 코퍼스 또는 개별 텍스트.

As discussed above, the teiHeader element has four principal components:

• fileDesc (파일 기술) 전자 파일에 관한 완전한 서지 정보의 기술을 포함한다.
• encodingDesc (부호화 기술) 전자 텍스트와 그것의 원전 텍스트 혹은 텍스트들 사이의 관련성을 기록한다.
• profileDesc (텍스트-개요 기술) 분명하게 언어와 특수 언어가 사용된 텍스트, 텍스트가 생산된 상황, 참여자, 배경에 관한 비서지적 측면을 상세히 기술한다.
• revisionDesc (수정 기술) 하나의 파일에 대한 수정 이력을 요약한다.

TEI: Types of Content in the TEI Header¶2.1.2 Types of Content in the TEI Header

The elements occurring within the TEI header may contain several types of content; the following list indicates how these types of content are described in the following sections:

free prose

Most elements contain simple running prose at some level. Many elements may contain either prose (possibly organized into paragraphs) or more specific elements, which themselves contain prose. In this chapter's descriptions of element content, the phrase prose description should be understood to imply a series of paragraphs, each marked as a p element. The word phrase, by contrast, should be understood to imply character data, interspersed as need be with phrase-level elements, but not organized into paragraphs. For more information on paragraphs, highlighted phrases, lists, etc., see section 3.1 Paragraphs.

grouping elements

Elements whose names end with the suffix Stmt (e.g. editionStmt, titleStmt) usually enclose a group of specialized elements recording some structured information. In the case of the bibliographic elements, the suffix Stmt is used in names of elements corresponding to the ‘areas’ of the International Standard Bibliographic Description.⁴ In most cases grouping elements may contain prose descriptions as an alternative to the set of specialized elements, thus allowing the encoder to choose whether or not the information concerned should be presented in a structured form or in prose.

declarations

Elements whose names end with the suffix Decl (e.g. tagsDecl, refsDecl) enclose information about specific encoding practices applied in the electronic text; often these practices are described in coded form. Typically, such information takes the form of a series of declarations, identifying a code with some more complex structure or description. A declaration which applies to more than one text or division of a text need not be repeated in the header of each such text or subdivision. Instead, the decls attribute of each text (or subdivision of the text) to which the declaration applies may be used to supply a cross-reference to it, as further described in section 15.3 Associating Contextual Information with a Text.

descriptions

Elements whose names end with the suffix Desc (e.g. settingDesc, projectDesc) contain a prose description, possibly, but not necessarily, organized under some specific headings by suggested sub-elements.

TEI: The Title Statement¶2.2.1 The Title Statement

The titleStmt element is the first component of the fileDesc element, and is mandatory:

• titleStmt (제목 진술) 저작의 제목 그리고 지적 내용에 대한 책임에 관한 정보를 모아 놓는다.

It contains the title given to the electronic work, together with one or more optional statements of responsibility which identify the encoder, editor, author, compiler, or other parties responsible for it:

• title 다양한 종류의 작업에 대한 전체 제목을 제공한다.
• author 참고문헌에 작가, 단독 저자, 공동 저자의 이름을 포함한다; 서지 항목의 책임에 관한 1차적 진술.
• editor 서지 항목의 책임에 관한 2차적 진술, 예를 들어, 편집, 번역 등의 작업을 한 편집, 개인, 기관, 또는 기구의 이름
• sponsor 후원 조직 또는 기관의 이름을 명시한다.
• funder (재정 지원 조직체) 프로젝트 또는 텍스트의 재정 지원 책임을 지는 개인, 기관, 조직의 이름을 명시한다.
• principal (책임 연구자) 전자 텍스트 생성에 대한 책임을 지는 책임 연구자의 이름을 제시한다.
• respStmt (책임성 진술) 텍스트, 편집, 녹음 또는 총서의 지적 내용에 대한 책임성 진술을 제시한다. 여기에서 작가, 편집자 등에 대한 특별한 요소는 충분치 않거나 적용되지 않는다.
• resp (책임성) 개인의 지적 책임성에 관한 특성을 기술하는 구를 포함한다.
• name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.

The title element contains the chief name of the electronic work, including any alternative title or subtitles it may have. It may be repeated, if the work has more than one title (perhaps in different languages) and takes whatever form is considered appropriate by its creator. Where the electronic work is derived from an existing source text, it is strongly recommended that the title for the former should be derived from the latter, but clearly distinguishable from it, for example by the addition of a phrase such as ‘: an electronic transcription’ or ‘a digital edition’. This will distinguish the electronic work from the source text in citations and in catalogues which contain descriptions of both types of material.

The electronic work will also have an external name (its ‘filename’ or ‘data set name’) or reference number on the computer system where it resides at any time. This name is likely to change frequently, as new copies of the file are made on the computer system. Its form is entirely dependent on the particular computer system in use and thus cannot always easily be transferred from one system to another. Moreover, a given work may be composed of many files. For these reasons, these Guidelines strongly recommend that such names should not be used as the title for any electronic work.

Helpful guidance on the formulation of useful descriptive titles in difficult cases may be found in chapter 25 of Anglo-American Cataloguing Rules (2002–2005)) or another national cataloguing code.

The elements author, editor, sponsor, funder, and principal, are specializations of the more general respStmt element. These elements are used to provide the statements of responsibility which identify the person(s) responsible for the intellectual or artistic content of an item and any corporate bodies from which it emanates.

Any number of such statements may occur within the title statement. At a minimum, identify the author of the text and (where appropriate) the creator of the file. If the bibliographic description is for a corpus, identify the creator of the corpus. Optionally include also names of others involved in the transcription or elaboration of the text, sponsors, and funding agencies. The name of the person responsible for physical data input need not normally be recorded, unless that person is also intellectually responsible for some aspect of the creation of the file.

Where the person whose responsibility is to be documented is not an author, sponsor, funding body, or principal researcher, the respStmt element should be used. This has two subcomponents: a name element identifying a responsible individual or organization, and a resp element indicating the nature of the responsibility. No specific recommendations are made at this time as to appropriate content for the resp: it should make clear the nature of the responsibility concerned, as in the examples below.

Names given may be personal names or corporate names. Give all names in the form in which the persons or bodies wish to be publicly cited. This would usually be the fullest form of the name, including first names.⁵

TEI: The Edition Statement¶2.2.2 The Edition Statement

The editionStmt element is the second component of the fileDesc element. It is optional but recommended.

• editionStmt (편집 진술) 텍스트의 한 판에 관련된 정보를 모아 놓는다.

It contains either phrases or more specialized elements identifying the edition and those responsible for it:

• edition (편집, 판) 텍스트의 한 판의 특성을 기술한다.
• respStmt (책임성 진술) 텍스트, 편집, 녹음 또는 총서의 지적 내용에 대한 책임성 진술을 제시한다. 여기에서 작가, 편집자 등에 대한 특별한 요소는 충분치 않거나 적용되지 않는다.
• name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.
• resp (책임성) 개인의 지적 책임성에 관한 특성을 기술하는 구를 포함한다.

For printed texts, the word edition applies to the set of all the identical copies of an item produced from one master copy and issued by a particular publishing agency or a group of such agencies. A change in the identity of the distributing body or bodies does not normally constitute a change of edition, while a change in the master copy does.

For electronic texts, the notion of a ‘master copy’ is not entirely appropriate, since they are far more easily copied and modified than printed ones; nonetheless the term edition may be used for a particular state of a machine-readable text at which substantive changes are made and fixed. Synonymous terms used in these Guidelines are version, level, and release. The words revision and update, by contrast, are used for minor changes to a file which do not amount to a new edition.

No simple rule can specify how ‘substantive’ changes have to be before they are regarded as producing a new edition, rather than a simple update. The general principle proposed here is that the production of a new edition entails a significant change in the intellectual content of the file, rather than its encoding or appearance. The addition of analytic coding to a text would thus constitute a new edition, while automatic conversion from one coded representation to another would not. Changes relating to the character code or physical storage details, corrections of misspellings, simple changes in the arrangement of the contents and changes in the output format do not normally constitute a new edition, whereas the addition of new information (e.g. a linguistic analysis expressed in part-of-speech tagging, sound or graphics, referential links to external data sets) almost always does.

Clearly, there will always be borderline cases and the matter is somewhat arbitrary. The simplest rule is: if you think that your file is a new edition, then call it such. An edition statement is optional for the first release of a computer file; it is mandatory for each later release, though this requirement cannot be enforced by the parser.

Note that all changes in a file considered significant, whether or not they are regarded as constituting a new edition or simply a new revision, should be independently noted in the revision description section of the file header (see section 2.5 The Revision Description).

The edition element should contain phrases describing the edition or version, including the word edition, version, or equivalent, together with a number or date, or terms indicating difference from other editions such as new edition, revised edition etc. Any dates that occur within the edition statement should be marked with the date element. The n attribute of the edition element may be used as elsewhere to supply any formal identification (such as a version number) for the edition.

One or more respStmt elements may also be used to supply statements of responsibility for the edition in question. These may refer to individuals or corporate bodies and can indicate functions such as that of a reviser, or can name the person or body responsible for the provision of supplementary matter, of appendices, etc., in a new edition. For further detail on the respStmt element, see section 3.11 Bibliographic Citations and References.

TEI: Type and Extent of File¶2.2.3 Type and Extent of File

The extent element is the third component of the fileDesc element. It is optional.

• extent 전달 매체, 즉, 디지털 또는 비디지털로 저장된 텍스트의, 다양한 단위로 명시되는, 대략적 규모를 기술한다.

For printed books, information about the carrier, such as the kind of medium used and its size, are of great importance in cataloguing procedures. The print-oriented rules for bibliographic description of an item's medium and extent need some re-interpretation when applied to electronic media. An electronic file exists as a distinct entity quite independently of its carrier and remains the same intellectual object whether it is stored on a magnetic tape, a CD-ROM, a set of floppy disks, or as a file on a mainframe computer. Since, moreover, these Guidelines are specifically aimed at facilitating transparent document storage and interchange, any purely machine-dependent information should be irrelevant as far as the file header is concerned.

This is particularly true of information about file-type although library-oriented rules for cataloguing often distinguish two types of computer file: ‘data’ and ‘programs’. This distinction is quite difficult to draw in some cases, for example, hypermedia or texts with built in search and retrieval software.

Although it is equally system-dependent, some measure of the size of the computer file may be of use for cataloguing and other practical purposes. Because the measurement and expression of file size is fraught with difficulties, only very general recommendations are possible; the element extent is provided for this purpose. It contains a phrase indicating the size or approximate size of the computer file in one of the following ways:

• in bytes of a specified length (e.g. ‘4000 16-bit bytes’)
• as falling within a range of categories, for example:
  • less than 1 Mb
  • between 1 Mb and 5 Mb
  • between 6 Mb and 10 Mb
  • over 10 Mb
• in terms of any convenient logical units (for example, words or sentences, citations, paragraphs)
• in terms of any convenient physical units (for example, blocks, disks, tapes)

The use of standard abbreviations for units of quantity is recommended where applicable, here as elsewhere (see http://physics.nist.gov/cuu/Units/binary.html).

TEI: Publication, Distribution, Licensing, etc.¶2.2.4 Publication, Distribution, Licensing, etc.

The publicationStmt element is the fourth component of the fileDesc element and is mandatory.

• publicationStmt (출판 진술) 전자 또는 기타 텍스트의 출판 또는 배포에 관한 정보를 모아 놓는다.

It may contain either a simple prose description organized as one or more paragraphs, or one or more elements from the model.publicationStmtPart class. This class groups a number of elements which are discussed in order below.

• publisher 서지 항목의 출판이나 배포에 책임이 있는 기구명을 제시한다.
• distributor 텍스트 배포 권한을 갖는 개인 또는 기관의 이름을 제시한다.
• authority (배포권자) 출판사 또는 배포자 외에 전자 파일 사용 허가에 대한 권한을 갖는 개인 또는 기관의 이름을 제시한다.

The publisher is the person or institution by whose authority a given edition of the file is made public. The distributor is the person or institution from whom copies of the text may be obtained. Where a text is not considered formally published, but is nevertheless made available for circulation by some individual or organization, this person or institution is termed the release authority.

At least one of the above three elements must be present, unless the entire publication statement is given as prose. Each may be followed by one or more of the following elements, in the following order:⁶

• pubPlace (출판지) 서지 대상이 출판된 장소명을 포함한다.
• address 예를 들어, 출판사, 기관, 개인의 우편 주소를 포함한다.
• idno (식별 숫자) 서지 정보 항목을 식별하기 위해 사용되는 표준 또는 비표준 숫자를 제시한다.

  type	예를 들어 ISBN 또는 기타 표준 일련번호로, 숫자를 범주화한다.

• availability 텍스트 이용에 관한 정보를 제시한다. 예를 들어 사용 또는 배포의 제한, 저작권 상태 등.

  status

  텍스트의 현재 이용 가능성을 식별하는 부호를 제공한다.

• date 다양한 형식의 날짜를 포함한다.

Note that the dates, places, etc., given in the publication statement relate to the publisher, distributor, or release authority most recently mentioned. If the text was created at some date other than its date of publication, its date of creation should be given within the profileDesc element, not in the publication statement. Give any other useful dates (e.g., dates of collection of data) in a note.

Additional detailed elements may be used for the encoding of names, dates, and addresses, as further described in section 3.5 Names, Numbers, Dates, Abbreviations, and Addresses when the module described in chapter 13 Names, Dates, People, and Places is included in a schema.

Where the work is covered by a formal licence (such as a Creative Commons licence), the licence element may be included in availability, with its target attribute pointing to an instance of the licence document. The content of the licence element may include the full text of the licence, or a brief statement of its applicability.

TEI: The Series Statement¶2.2.5 The Series Statement

The seriesStmt element is the fifth component of the fileDesc element and is optional.

• seriesStmt (연속간행물 진술) 연속 간행물에 대한 정보를 모아 놓는다.

In bibliographic parlance, a series may be defined in one of the following ways:

• A group of separate items related to one another by the fact that each item bears, in addition to its own title proper, a collective title applying to the group as a whole. The individual items may or may not be numbered.
• Each of two or more volumes of essays, lectures, articles, or other items, similar in character and issued in sequence.
• A separately numbered sequence of volumes within a series or serial.

The seriesStmt element may contain a prose description or one or more of the following more specific elements:

• title 다양한 종류의 작업에 대한 전체 제목을 제공한다.
• idno (식별 숫자) 서지 정보 항목을 식별하기 위해 사용되는 표준 또는 비표준 숫자를 제시한다.
• respStmt (책임성 진술) 텍스트, 편집, 녹음 또는 총서의 지적 내용에 대한 책임성 진술을 제시한다. 여기에서 작가, 편집자 등에 대한 특별한 요소는 충분치 않거나 적용되지 않는다.
• resp (책임성) 개인의 지적 책임성에 관한 특성을 기술하는 구를 포함한다.
• name (이름, 고유명사) 고유명사 또는 명사구를 포함한다.

The idno may be used to supply any identifying number associated with the item, including both standard numbers such as an ISSN and particular issue numbers. (Arabic numerals separated by punctuation are recommended for this purpose: 6.19.33, for example, rather than VI/xix:33). Its type attribute is used to categorize the number further, taking the value ISSN for an ISSN for example.

TEI: The Notes Statement¶2.2.6 The Notes Statement

The notesStmt element is the sixth component of the fileDesc element and is optional. If used, it contains one or more note elements, each containing a single piece of descriptive information of the kind treated as ‘general notes’ in traditional bibliographic descriptions.

• notesStmt (주석 진술) 서지 정보 기술의 다른 부분에 기록된 것들 이외에, 텍스트에 관한 정보를 제공하는 주석들을 모아 놓는다.
• note contains a note or annotation.

Some information found in the notes area in conventional bibliography has been assigned specific elements in these Guidelines; in particular the following items should be tagged as indicated, rather than as general notes:

• the nature, scope, artistic form, or purpose of the file; also the genre or other intellectual category to which it may belong: e.g. ‘Text types: newspaper editorials and reportage, science fiction, westerns, and detective stories’. These should be formally described within the profileDesc element (section 2.4 The Profile Description).
• summary description providing a factual, non-evaluative account of the subject content of the file: e.g. ‘Transcribes interviews on general topics with native speakers of English in 17 cities during the spring and summer of 1963.’ These should also be formally described within the profileDesc element (section 2.4 The Profile Description).
• bibliographic details relating to the source or sources of an electronic text: e.g. ‘Transcribed from the Norton facsimile of the 1623 Folio’. These should be formally described in the sourceDesc element (section 2.2.7 The Source Description).
• further information relating to publication, distribution, or release of the text, including sources from which the text may be obtained, any restrictions on its use or formal terms on its availability. These should be placed in the appropriate division of the publicationStmt element (section 2.2.4 Publication, Distribution, Licensing, etc.).
• publicly documented numbers associated with the file: e.g. ‘ICPSR study number 1803’ or ‘Oxford Text Archive text number 1243’. These should be placed in an idno element within the appropriate division of the publicationStmt element. International Standard Serial Numbers (ISSN), International Standard Book Numbers (ISBN), and other internationally agreed upon standard numbers that uniquely identify an item, should be treated in the same way, rather than as specialized bibliographic notes.

Nevertheless, the notesStmt element may be used to record potentially significant details about the file and its features, e.g.:

• dates, when they are relevant to the content or condition of the computer file: e.g. ‘manual dated 1983’, ‘Interview wave I: Apr. 1989; wave II: Jan. 1990’
• names of persons or bodies connected with the technical production, administration, or consulting functions of the effort which produced the file, if these are not named in statements of responsibility in the title or edition statements of the file description: e.g. ‘Historical commentary provided by Mark Cohen’
• availability of the file in an additional medium or information not already recorded about the availability of documentation: e.g. ‘User manual is loose-leaf in eleven paginated sections’
• language of work and abstract, if not encoded in the langUsage element, e.g. ‘Text in English with summaries in French and German’
• The unique name assigned to a serial by the International Serials Data System (ISDS), if not encoded in an idno
• lists of related publications, either describing the source itself, or concerned with the creation or use of the electronic work, e.g. ‘Texts used in Burrows (1987)’

TEI: The Source Description¶2.2.7 The Source Description

The sourceDesc element is the seventh and final component of the fileDesc element. It is a mandatory element and is used to record details of the source or sources from which a computer file is derived. This might be a printed text or manuscript, another computer file, an audio or video recording of some kind, or a combination of these. An electronic file may also have no source, if what is being catalogued is an original text created in electronic form.

• sourceDesc (원전 기술) 전자 파일을 생성하거나 도출한 원전 텍스트에 대한 기술을 제시한다.

Alternatively, it may contain elements drawn from the following three classes:

• model.biblLike 서지 기술을 포함하는 요소를 모아 놓는다.

  bibl	(서지 인용) 하위 성분이 명시적으로 구분된 또는 그렇지 않은 덜 구조화된 서지 인용을 포함한다.
  biblFull	(완전히 구조화된 서지 인용 정보) 완전히 구조화된 서지 정보를 포함하며, 그 안에 TEI 파일 기술의 모든 성분이 제시된다.
  biblStruct	(구조화된 서지 인용) 서지의 하위 요소만이 나타나는, 명시적 순서로 구성되는 구조화된 서지 인용을 포함한다.
  listBibl	(인용 목록) 여러 종류의 서지 인용 목록을 포함한다.
  msDesc	(원고 기술) 하나의 식별가능한 원고에 대한 기술을 포함한다.

• model.sourceDescPart sourceDesc 내부에 사용되어 여러 번 출현할 수 있는 요소들을 모아 놓는다.

  recordingStmt	(녹음 진술) 구어 텍스트 전사의 기반으로 사용된 녹음 집합을 기술한다.
  scriptStmt	(스크립트 진술) 구어 텍스트에 사용되는 스크립트의 상세 항목을 제시하는 인용을 포함한다.

• model.listLike 목록 같은 요소를 모아 놓는다.

  list	(list) 목록의 형태로 정리된 항목을 포함한다.
  listApp	(list of apparatus entries) contains a list of apparatus entries.
  listEvent	(list of events) contains a list of descriptions, each of which provides information about an identifiable event.
  listNym	(표준 이름 목록) 어떤 사물에 대한 표준화된 이름 목록을 포함한다.
  listOrg	(조직 목록) 식별 가능한 조직에 관한 정보를 제공하며, 각각에 대한 기술 목록을 포함한다.
  listPerson	(개인 목록) 기술 목록을 포함하며, 그 개별 기술 각각은, 언어 상호작용 참여자 또는 역사적 원전에서 언급되는 사람과 같이, 식별 가능한 사람 또는 사람군에 관한 정보를 제공한다.
  listPlace	(장소 목록) 장소 목록을 포함하며, 그 뒤에 수의적으로 그들 사이에 정의된 (포함 외의) 관련성 목록을 제시한다.
  listWit	(비교 대상 텍스트 목록) 비평적 참조 도구에 의해 참조된 모든 비교 대상 텍스트에 대한 정의 목록. 그리고 이는 계층적 그룹으로 수의적으로 구성된다.
  table	행과 열의 테이블 형식으로 제시된 텍스트를 포함한다.

When the header describes a text derived from some pre-existing TEI-conformant or other digital document, it may be simpler to use the following element, which is designed specifically for documents derived from texts which were ‘born digital’:

• biblFull (완전히 구조화된 서지 인용 정보) 완전히 구조화된 서지 정보를 포함하며, 그 안에 TEI 파일 기술의 모든 성분이 제시된다.

For further discussion see section 2.2.8 Computer Files Derived from Other Computer Files .

When the module for manuscript description is included in a schema, this class also makes available the following element:

• msDesc (원고 기술) 하나의 식별가능한 원고에 대한 기술을 포함한다.

This element enables the encoder to record very detailed information about one or more manuscript or analogous sources, as further discussed in 10 Manuscript Description.

The model.sourceDescPart class also makes available additional elements when additional modules are included. For example, when the spoken module is included, the sourceDesc element may also include the following special-purpose elements, intended for cases where an electronic text is derived from a spoken text rather than a written one:

• scriptStmt (스크립트 진술) 구어 텍스트에 사용되는 스크립트의 상세 항목을 제시하는 인용을 포함한다.
• recordingStmt (녹음 진술) 구어 텍스트 전사의 기반으로 사용된 녹음 집합을 기술한다.

Full descriptions of these elements and their contents are given in section 8.2 Documenting the Source of Transcribed Speech.

A single electronic text may be derived from multiple source documents, in whole or in part. The sourceDesc may therefore contain a listBibl element grouping together bibl, biblStruct, or msDesc elements for each of the sources concerned. It is also possible to repeat the sourceDesc element in such a case. The decls attribute described in section 15.3 Associating Contextual Information with a Text may be used to associate parts of the encoded text with the bibliographic element from which it derives in either case.

The source description may also include lists of names, persons, places, etc. when these are considered to form part of the source for an encoded document. When such information is recorded using the specialized elements discussed in the namesdates module (13 Names, Dates, People, and Places), the class model.listLike makes available the following elements to hold such information:

• listNym (표준 이름 목록) 어떤 사물에 대한 표준화된 이름 목록을 포함한다.
• listOrg (조직 목록) 식별 가능한 조직에 관한 정보를 제공하며, 각각에 대한 기술 목록을 포함한다.
• listPerson (개인 목록) 기술 목록을 포함하며, 그 개별 기술 각각은, 언어 상호작용 참여자 또는 역사적 원전에서 언급되는 사람과 같이, 식별 가능한 사람 또는 사람군에 관한 정보를 제공한다.
• listPlace (장소 목록) 장소 목록을 포함하며, 그 뒤에 수의적으로 그들 사이에 정의된 (포함 외의) 관련성 목록을 제시한다.

TEI: Computer Files Derived from Other Computer Files ¶2.2.8 Computer Files Derived from Other Computer Files

If a computer file (call it B) is derived not from a printed source but from another computer file (call it A) which includes a TEI file header, then the source text of computer file B is another computer file, A. The four sections of A's file header will need to be incorporated into the new header for B in slightly differing ways, as listed below:

fileDesc

A's file description should be copied into the sourceDesc section of B's file description, enclosed within a biblFull element

profileDesc

A's profileDesc should be copied into B's, in principle unchanged; it may however be expanded by project-specific information relating to B.

encodingDesc

A's encoding practice may or (more likely) may not be the same as B's. Since the object of the encoding description is to define the relationship between the current file and its source, in principle only changes in encoding practice between A and B need be documented in B. The relationship between A and its source(s) is then only recoverable from the original header of A. In practice it may be more convenient to create a new complete encodingDesc for B based on A's.

revisionDesc

B is a new computer file, and should therefore have a new revision description. If, however, it is felt useful to include some information from A's revisionDesc, for example dates of major updates or versions, such information must be clearly marked as relating to A rather than to B.

This concludes the discussion of the fileDesc element and its contents.

TEI: The Project Description¶2.3.1 The Project Description

The projectDesc element may be used to describe, in prose, the purpose for which a digital resource was created, together with any other relevant information concerning the process by which it was assembled or collected. This is of particular importance for corpora or miscellaneous collections, but may be of use for any text, for example to explain why one kind of encoding practice has been followed rather than another.

• projectDesc (프로젝트 기술) 전자 파일이 부호화된 목적을 상세히 기술하며, 아울러 그것이 수집된 절차에 관한 기타 관련 정보를 기술한다, .

TEI: The Sampling Declaration¶2.3.2 The Sampling Declaration

A sampling declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the decls attribute of each text (or subdivision of the text) to which the sampling declaration applies may be used to supply a cross-reference to it, as further described in section 15.3 Associating Contextual Information with a Text.

TEI: The Editorial Practices Declaration¶2.3.3 The Editorial Practices Declaration

The editorialDecl element is used to provide details of the editorial practices applied during the encoding of a text.

• editorialDecl (편집 실행 선언) 텍스트 부호화에서 적용된 편집 원리 및 기준의 상세 항목을 제시한다.

It may contain a prose description only, or one or more of a set of specialized elements, members of the TEI model.editorialDeclPart class. Where an encoder wishes to record an editorial policy not specified above, this may be done by adding a new element to this class, using the mechanisms discussed in chapter 23.3 Personalization and Customization.

Some of these policy elements carry attributes to support automated processing of certain well-defined editorial decisions; all of them contain a prose description of the editorial principles adopted with respect to the particular feature concerned. Examples of the kinds of questions which these descriptions are intended to answer are given in the list below.

correction

• correction (수정 원리) 텍스트의 수정의 상황과 방법에 대해 설명한다.

  status	텍스트에 적용된 수정의 정도를 표시한다.
  method	텍스트의 수정사항을 표시하기 위해 채택한 방법을 나타낸다.

Was the text corrected during or after data capture? If so, were corrections made silently or are they marked using the tags described in section 3.4 Simple Editorial Changes? What principles have been adopted with respect to omissions, truncations, dubious corrections, alternate readings, false starts, repetitions, etc.?

normalization

• normalization 전자 형식으로 변환할 때 수행된 원본 텍스트의 표준화 또는 규칙화의 정도를 표시한다.

  source	수행된 표준화를 행한 기준 을 표시한다.
  method	텍스트의 표준화를 표시하기 위해 채택한 방법론을 제시한다.

Was the text normalized, for example by regularizing any non-standard spellings, dialect forms, etc.? If so, were normalizations performed silently or are they marked using the tags described in section 3.4 Simple Editorial Changes? What authority was used for the regularization? Also, what principles were used when normalizing numbers to provide the standard values for the value attribute described in section 3.5.3 Numbers and Measures and what format used for them?

quotation

• quotation 원본 인용 부호에 관해 채택한 편집 방식을 명시한다.

  marks	(인용 부호) 인용 부호가 텍스트에 유지되었는지 여부를 표시한다.
  form	텍스트 내에 인용 부호가 표시되는 방법을 명시한다.

How were quotation marks processed? Are apostrophes and quotation marks distinguished? How? Are quotation marks retained as content in the text or replaced by markup? Are there any special conventions regarding for example the use of single or double quotation marks when nested? Is the file consistent in its practice or has this not been checked? See section 3.3.3 Quotation for discussion of ways in which quotation marks may be encoded.

hyphenation

• hyphenation 원본 텍스트의 하이픈이 부호화된 버전에서 처리된 방법을 요약한다.

  eol	(행의 끝) 텍스트에서 행의 끝 하이픈이 포함되었는지의 여부를 표시한다.

Does the encoding distinguish ‘soft’ and ‘hard’ hyphens? What principle has been adopted with respect to end-of-line hyphenation where source lineation has not been retained? Have soft hyphens been silently removed, and if so what is the effect on lineation and pagination? See section 3.2.2 Hyphenation for discussion of ways in which hyphenation may be encoded.

segmentation

• segmentation 예를 들어 문장, 음성 단위, 문자적 층위로 텍스트가 분절되는 원리를 기술한다.

How is the text segmented? If s or seg segmentation units have been used to divide up the text for analysis, how are they marked and how was the segmentation arrived at?

stdVals

• stdVals (표준 값) 표준화된 날짜 또는 숫자 값이 제시될 때 사용되는 형식을 명시한다.

In most cases, attributes bearing standardized values (such as the when or when-iso attribute on dates) should conform to a defined W3C or ISO datatype. In cases where this is not appropriate, this element may be used to describe the standardization methods underlying the values supplied.

interpretation

• interpretation 전사본에 덧붙여 텍스트에 부착된 분석적 또는 해석적 정보의 범위를 기술한다.

Has any analytic or ‘interpretive’ information been provided—that is, information which is felt to be non-obvious, or potentially contentious? If so, how was it generated? How was it encoded? If feature-structure analysis has been used, are fsdDecl elements (section 18.11 Feature System Declaration) present?

An editorial practices declaration which applies to more than one text or division of a text need not be repeated in the header of each such text. Instead, the decls attribute of each text (or subdivision of the text) to which it applies may be used to supply a cross-reference to it, as further described in section 15.3 Associating Contextual Information with a Text.

TEI: The Tagging Declaration¶2.3.4 The Tagging Declaration

The tagsDecl element is used to record the following information about the tagging used within a particular text:

• the namespace to which elements appearing within the transcribed text belong.
• how often particular elements appear within the text, so that a recipient can validate the integrity of a text during interchange.
• any comment relating to the usage of particular elements not specified elsewhere in the header.
• a default rendition applicable to all instances of an element.

This information is conveyed by the following elements:

• rendition 원본 텍스트에서 요소의 모양에 대한 정보를 제공한다.
• att.styleDef groups elements which specify the name of a formal definition language used to provide formatting or rendition information.

  scheme	모양을 기술하는 언어를 식별한다.
  schemeVersion	supplies a version number for the style language provided in scheme.

• namespace 그 자식이 기술한 요소가 속하는 네임스페이스의 공식적 이름을 제공한다.
• tagUsage 텍스트에서 특정 요소의 사용에 관한 정보를 제공한다.

The tagsDecl element consists of an optional sequence of rendition elements, each of which must bear a unique identifier, followed by an optional sequence of one or more namespace elements, each of which contains a series of tagUsage elements, one for each distinct element from that namespace occurring within the outermost text element of a TEI document. Note that these tagUsage elements must be nested within a namespace element, and cannot appear directly within the tagsDecl element.

• » 2.3.4.2 Tag usage
• 가정

TEI: Rendition¶2.3.4.1 Rendition

The rendition element allows the encoder to specify how one or more elements are rendered in the original source in any of the following ways:

• using an informal prose description
• using a standard stylesheet language such as CSS or XSL-FO
• using a project-defined formal language

One or more such specifications may be associated with elements of a document in two ways:

• the render attribute of the appropriate tagUsage element may be used to indicate a default rendition for all occurrences of the named element
• the global rendition attribute may be used on any element to indicate its rendition, overriding or complementing any supplied default value

The global rend and style attributes may also be used to describe the rendering of an element. See further 1.3.1.1.3 Rendition Indicators

For example, the following schematic shows how an encoder might specify that all p elements are by default to be rendered using one set of specifications identified as style1, while hi elements are to use a different set, identified as style2:

<tagsDecl>
 <rendition xml:id="style1">
   ... description of one default rendition here ...
 </rendition>
 <rendition xml:id="style2">
   ... description of another default rendition here ...
 </rendition>
 <namespace name="http://www.tei-c.org/ns/1.0">
  <tagUsage gi="p" render="#style1"> ... </tagUsage>
  <tagUsage gi="hi" render="#style2"> ... </tagUsage>
 </namespace>
</tagsDecl>
<!-- elsewhere in the document -->
<p>This paragraph,mostly rendered in style1, contains a few words
<hi>rendered in style2</hi>
</p>
<p rendition="#style2">This paragraph is all rendered in style2</p>
<p>This is back to style1</p>

As noted above, the content of a rendition element may describe the appearance of the source material using prose, a project-defined formal language, or any standard languages such as the Cascading Stylesheet Language (Bos et al. (eds.) (2011)) or the XML vocabulary for specifying formatting semantics which forms a part of the W3C's Extensible Stylesheet Language (Berglund (ed.) (2006)). A styleDefDecl element (2.3.5 The default style definition language declaration) may be supplied within the encodingDesc to specify which of these applies by default; it may be overridden for one or more specific rendition elements using the scheme attribute.

In the following extended example we consider how to capture the appearance of a typical early 20th century titlepage, such as that in the following figure:

bibliography

Elements for the encoding of the information on a titlepage are presented in 4.6 Title Pages; here we consider how we might go about encoding some of the visual information as well, using the rendition element and its corresponding attributes.

First we define a rendition element for each aspect of the source page rendition that we wish to retain. Details of CSS are given in Bos et al. (eds.) (2011); we use it here simply to provide a vocabulary with which to describe such aspects as font size and style, letter and line spacing, colour, etc. Note that the purpose of this encoding is to describe the original, rather than specify how it should be reproduced, although the two are obviously closely linked.

<styleDefDecl scheme="css" schemeVersion="2.1"/>
<!-- ... -->
<tagsDecl>
 <rendition xml:id="center">text-align: center;</rendition>
 <rendition xml:id="small">font-size: small;</rendition>
 <rendition xml:id="large">font-size: large;</rendition>
 <rendition xml:id="x-large">font-size: x-large;</rendition>
 <rendition xml:id="xx-large">font-size: xx-large</rendition>
 <rendition xml:id="expanded">letter-spacing: +3pt;</rendition>
 <rendition xml:id="x-space">line-height: 150%;</rendition>
 <rendition xml:id="xx-space">line-height: 200%;</rendition>
 <rendition xml:id="red">color: red;</rendition>
</tagsDecl>

The global rendition attribute can now be used to specify on any element which of the above rendition features apply to it. For example, a title page might be encoded as follows:

<titlePage>
 <docTitle rendition="#center #x-space">
  <titlePart>
   <lb/>
   <hi rendition="#x-large">THE POEMS</hi>
   <lb/>
   <hi rendition="#small">OF</hi>
   <lb/>
   <hi rendition="#red #xx-large">ALGERNON CHARLES SWINBURNE</hi>
   <lb/>
   <hi rendition="#large #xx-space">IN SIX VOLUMES</hi>
  </titlePart>
  <titlePart rendition="#xx-space">
   <lb/> VOLUME I.
  <lb/>
   <hi rendition="#red #x-large">POEMS AND BALLADS</hi>
   <lb/>
   <hi rendition="#x-space">FIRST SERIES</hi>
  </titlePart>
 </docTitle>
 <docImprint rendition="#center">
  <lb/>
  <pubPlace rendition="#xx-space">LONDON</pubPlace>
  <lb/>
  <publisher rendition="#red #expanded">CHATTO &amp; WINDUS</publisher>
  <lb/>
  <docDate when="1904" rendition="#small">1904</docDate>
 </docImprint>
</titlePage>

bibliography 

When CSS is used as the style definition language, the scope attribute may be used to specify CSS pseudo-elements. These pseudo-elements are used to specify styling applicable to only a portion of the given text. For example, the first-letter pseudo-element defines styling to be applied to the first letter in the targeted element, while the before and after pseudo-elements can be used often in conjunction with the "content" property to add additional characters which need to be added before or after the element content to make it more closely resemble the appearance of the source.

For example, assuming that a text has been encoded using the q element to enclose passages in quotation marks, but the quotation marks themselves have been routinely omitted from the encoding, a set of renditions such as the following:

<rendition xml:id="quoteBefore" scheme="css" scope="before">content:
'“';</rendition>
<rendition xml:id="quoteAfter" scheme="css" scope="after">content:
'”';</rendition>

might be used to predefine pseudo-elements quoteBefore and quoteAfter. Where a q element is actually rendered in the source with initial and final quotation marks, it may then be encoded as follows:

<q rendition="#quoteBefore #quoteAfter">Four score and seven years
ago...</q>

TEI: The Reference System Declaration¶2.3.6 The Reference System Declaration

The refsDecl element is used to document the way in which any standard referencing scheme built into the encoding works.

• refsDecl (참조 선언) 표준 참조가 이러한 텍스트에 대해 어떻게 구성되는가를 명시한다.

It may contain either a series of prose paragraphs or the following specialized elements:

• cRefPattern (표준 참조 유형) 표준 참조를 URI로 변환하기 위한 표현 및 대체 유형을 명시한다.
• refState/ (참조 상태) 이정표 방법으로 정의된 표준 참조의 한 성분을 명시한다.
• att.patternReplacement provides attributes for regular-expression matching and replacement.

  matchPattern	specifies a regular expression against which the values of other attributes can be matched.
  replacementPattern	하위 유형 대치가 실행되면, URI를 제공하는 ‘replacement pattern’를 명시한다.

Note that not all possible referencing schemes are equally easily supported by current software systems. A choice must be made between the convenience of the encoder and the likely efficiency of the particular software applications envisaged, in this context as in many others. For a more detailed discussion of referencing systems supported by these Guidelines, see section 3.10 Reference Systems below.

A referencing scheme may be described in one of three ways using this element:

• as a prose description
• as a series of pairs of regular expressions and XPaths
• as a concatenation of sequentially organized milestones

Each method is described in more detail below. Only one method can be used within a single refsDecl element.

More than one refsDecl element can be included in the header if more than one canonical reference scheme is to be used in the same document, but the current proposals do not check for mutual inconsistency.

TEI: The Classification Declaration¶2.3.7 The Classification Declaration

TEI: The Geographic Coordinates Declaration¶2.3.8 The Geographic Coordinates Declaration

The following element is provided to indicate (within the header of a document, or in an external location) that a particular coordinate notation, or a particular datum, has been employed in a text. The default notation is a string containing two real numbers separated by whitespace, of which the first indicates latitude and the second longitude according to the 1984 World Geodetic System (WGS84).

• geoDecl (지리적 좌표 선언) 문서 내 어디서든지 geo 요소의 내용으로 표현된 지리적 좌표로 사용된 표기법과 자료를 기재한다.

  datum

  사용된 자료의 일반적 부호명을 제시한다.

TEI: The Schema Specification¶2.3.9 The Schema Specification

The schemaSpec element contains a schema specification. When this element appears inside encodingDesc, it allows embedding of a schema inside a TEI header; alternatively, this element may be used in the body of an ODD document. The use of ODD files, and their relationship to schemas, is described in detail in 22 Documentation Elements.

TEI: The Application Information Element¶2.3.10 The Application Information Element

It is sometimes convenient to store information relating to the processing of an encoded resource within its header. Typical uses for such information might be:

• to allow an application to discover that it has previously opened or edited a file, and what version of itself was used to do that;
• to show (through a date) which application last edited the file to allow for diagnosis of any problems that might have been caused by that application;
• to allow users to discover information about an application used to edit the file
• to allow the application to declare an interest in elements of the file which it has edited, so that other applications or human editors may be more wary of making changes to those sections of the file.

The class model.applicationLike provides an element, application, which may be used to record such information within the appInfo element.

• appInfo (애플리케이션 정보) TEI 파일을 편집한 애플리케이션에 관한 정보를 기록한다.
• application 문서에 사용한 애플리케이션에 관한 정보를 제시한다.

  ident	버전 또는 표시명과 상관없이 애플리케이션의 확인소를 제공한다.
  version	확인소 또는 표시명과 상관없이 애플리케이션의 버전을 제공한다.

Each application element identifies the current state of one software application with regard to the current file. This element is a member of the att.datable class, which provides a variety of attributes for associating this state with a date and time, or a temporal range. The ident and version attributes should be used to uniquely identify the application and its major version number (for example, ImageMarkupTool 1.5). It is not intended that an application should add a new application each time it touches the file.

TEI: Creation¶2.4.1 Creation

TEI: Language Usage¶2.4.2 Language Usage

The langUsage element is used within the profileDesc element to describe the languages, sublanguages, registers, dialects, etc. represented within a text. It contains one or more language elements, each of which provides information about a single language, notably the quantity of that language present in the text. Note that this element should not be used to supply information about any non-standard characters or glyphs used by this language; such information should be recorded in the charDecl element in the encoding description (see further 5 Non-standard Characters and Glyphs).

• langUsage (언어 사용) 텍스트 내에 나타나는 언어, 특수 언어, 레지스터, 방언 등을 기술한다.
• language 텍스트 내에서 사용되는 언어 또는 특수 언어의 특징을 기술한다.

  usage	이 언어를 사용하는 텍스트의 대략적 백분율(분량)을 명시한다.
  ident	(확인소) 요소로 기록된 언어를 식별하고기 위해 사용되는, 전체 xml:lang 속성에 의해 참조되는 BCP 47에서 정의된 방식대로 구축된 언어 부호를 제시한다.

A language element may be supplied for each different language used in a document. If used, its ident attribute should specify an appropriate language identifier, as further discussed in section vi.1. Language identification. This is particularly important if extended language identifiers have been used as the value of xml:lang attributes elsewhere in the document.

TEI: The Text Classification¶2.4.3 The Text Classification

The textClass element is used to classify a text in some way.

• textClass (텍스트 분류) 표준 분류 스키마, 시소러스 등을 통해서 텍스트의 특성 또는 주제를 기술하는 정보를 모아 놓는다.

Text classification may be carried out according to one or more of the following methods:

• by reference to a recognized international classification such as the Dewey Decimal Classification, the Universal Decimal Classification, the Colon Classification, the Library of Congress Classification, or any other system widely used in library and documentation work
• by providing a set of keywords, as provided for example by British Library or Library of Congress Cataloguing in Publication data
• by referencing any other taxonomy of text categories recognized in the field concerned, or peculiar to the material in hand; this may include one based on recurring sets of values for the situational parameters defined in section 15.2.1 The Text Description, or the demographic elements described in section 15.2.2 The Participant Description

The last of these may be particularly important for dealing with existing corpora or collections, both as a means of avoiding the expense or inconvenience of reclassification and as a means of documenting the organizing principles of such materials.

The following elements are provided for this purpose:

• keywords 텍스트의 주제 또는 특성을 식별하는 주제어 또는 구의 목록을 포함한다.

  scheme

  관련 키워드 집합이 정의된 통제 어휘를 식별하며, 이 정의는 통제 어휘 내에서 수행된다.

• classCode (분류 부호) 표준 분류 체계에서 이 텍스트에 대하여 사용된 분류 부호를 포함한다.

  scheme

  사용하고 있는 분류 체계 또는 분류법을 표시한다.

• catRef/ (범주 참조) 분류법 또는 텍스트 유형 내에서 하나 이상의 정의된 범주를 명시한다.

The keywords element simply categorizes an individual text by supplying a list of keywords which may describe its topic or subject matter, its form, date, etc. In some schemes, the order of items in the list is significant, for example, from major topic to minor; in others, the list has an organized substructure of its own. No recommendations are made here as to which method is to be preferred. Wherever possible, such keywords should be taken from a recognized source, such as the British Library/Library of Congress Cataloguing in Publication data in the case of printed books, or a published thesaurus appropriate to the field.

If no authority file exists, perhaps because the keywords used were assigned directly by an author, the scheme attribute should be omitted.

Alternatively, if the keyword vocabulary itself is locally defined, the scheme attribute will point to the local definition, which will typically be held in a taxonomy element within the classDecl part of the encoding description (see section 2.3.7 The Classification Declaration).

The catRef element categorizes an individual text by pointing to one or more category elements using the target attribute, which it inherits from the att.pointing class. The category element (which is fully described in section 2.3.7 The Classification Declaration) holds information about a particular classification or category within a given taxonomy. Each such category must have a unique identifier, which may be supplied as the value of the target attribute for catRef elements which are regarded as falling within the category indicated.

In general, it is a matter of style whether to use a single catRef with multiple identifiers in the value of target or multiple catRef elements, each with a single identifier in the value of target. However, note that maintenance of a TEI document with a large number of values within a single target can be cumbersome.

The distinction between the catRef and classCode elements is that the values used as identifying codes are exhaustively enumerated for the former, typically within the TEI header. In the latter case, however, the values use any externally-defined scheme, and therefore may be taken from a more open-ended descriptive classification system.

TEI: Calendar Description¶2.4.4 Calendar Description

The calendarDesc element is used within the profileDesc element to document objects referenced by means of either the calendar attribute on date or the dateScheme attribute on any member of the att.datable class.

• calendarDesc (calendar description) contains a description of the calendar system used in any dating expression found in the text.

This element may contain one or more calendar elements:

• calendar describes a calendar or dating system used in a dating formula in the text.