0% found this document useful (0 votes)
64 views14 pages

Tei Header

The TEI (Text Encoding Initiative) is an international standard for encoding texts electronically for research. It aims to support all texts in all languages through an encoding scheme that represents textual features and structure. The TEI document standard includes a header section for metadata and a text section divided into front matter, body, and back matter. The header contains elements for bibliographic description, encoding details, and revision history. The encoding details explain how the text was transcribed and analyzed.

Uploaded by

aymynet
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
64 views14 pages

Tei Header

The TEI (Text Encoding Initiative) is an international standard for encoding texts electronically for research. It aims to support all texts in all languages through an encoding scheme that represents textual features and structure. The TEI document standard includes a header section for metadata and a text section divided into front matter, body, and back matter. The header contains elements for bibliographic description, encoding details, and revision history. The encoding details explain how the text was transcribed and analyzed.

Uploaded by

aymynet
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

TEI H EA D ER

Text Encoding Initiative


Initially launched in 1987, is an international and

interdisciplinary standard that helps libraries,


museums, publishers, and individual scholars
represent all kind of literary and linguistic texts
for online research using an encoding scheme.
TEI is an encoding standard for describing the
physical and logical structure of text material for
the purpose of research analysis and data
interchange.
Said to be the most systematic effort so far to
create standards for scholarly memory in an
evolving digital culture.

TEI was created to provide an

environment into which documents


of scholarly interest can be encoded
in such a way that the documents
properties are represented in their
transcribed form and that the
resultant transcription is
independent of any particular
programming environment and
capable of surviving technological
change.

TEIPrim ary G oals


Better interchange and integration of

scholarly data.
Support for all texts, in all languages,
from all periods.
Guidance for the perplexed
[confused]: what to encode.
Assistance for the specialist: how to
encode.

TEI document has 2 main sections


header section containing descriptive

and administrative metadata.


Text section containing the buck of the
text and divided into front matter, body
and back matter.

TEI Header has 4 sections:


File description contains a bibliographic

description of the materials.


Encoding description explain rules or
editorial decisions were used in
transcribing the text.
Profile description emphasize on access
point and classification notation.
Revision description contains a record of
every change that has been made to the
text.

<fileDesc> element.
<titleStmt> groups information about the title of a work and

those responsible for its intellectual content.


<editionStmt> groups information relating to one edition of
a text.
<extent> describes the approximate size of the electronic
text as stored on some carrier medium, specified in any
convenient units.
<publicationStmt> groups information concerning the
publication or distribution of an electronic or other text.
<seriesStmt> groups information about the series, if any, to
which a publication belongs.
<notesStmt> collects together any notes providing
information about a text additional to that recorded in other
parts of the bibliographic description.
<sourceDesc> supplies a bibliographic description of the
copy text(s) from which an electronic text was derived or
generated.

Encoding description, tagged

<encodingDesc>
Describes the relationship between an

electronic text and its source or sources.


It allows for detailed description of
whether (or how) the text was normalized
during transcription, how the encoder
resolved ambiguities in the source, what
levels of encoding or analysis were
applied, and similar matters.

<encodingDesc> element
<projectDesc> describes in detail the aim or purpose for which an electronic file was encoded,
together with any other relevant information concerning the process by which it was assembled
or collected
<samplingDecl> contains a prose description of the rationale and methods used in sampling
texts in the creation of a corpus or collection.
<editorialDecl> provides details of editorial principles and practices applied during the
encoding of a text.
<tagsDecl> provides detailed information about the tagging applied to an SGML or XML
document.
<refsDecl> specifies how canonical references are constructed for this text. doctype identifies
the document type within which this reference declaration is used.
<classDecl> contains one or more taxonomies defining any classificatory codes used elsewhere
in the text.
<fsdDecl> identifies the feature system declaration which contains definitions for a particular
type of feature structure. type identifies the type of feature structure documented in the FSD;
this will be the value of the type attribute on at least one feature structure. fsd (feature-system
declaration) specifies the external entity containing the feature system declaration; an entity
declaration in the document's DTD subset must associate the entity name with a file on the
system.
<metDecl> documents the notation employed to represent a metrical pattern when this is
specified as the value of a met, real, or rhyme attribute on any structural element of a metrical
text (e.g. lg, l, or seg). type indicates whether the notation conveys the abstract metrical form,
its actual prosodic realization, or the rhyme scheme, or some combination thereof. pattern
specifies a regular expression defining any value that is legal for this notation.
<variantEncoding> declares the method used to encode text-critical variants. method
indicates which method is used to encode the apparatus of variants. location indicates whether
the apparatus appears within the running text or external to it.

Text profile, tagged <profileDesc>


Containing classificatory and contextual information

about the text, such as its subject matter, the situation


in which it was produced, the individuals described by
or participating in producing it, and so forth.
Such a text profile is of particular use in highly
structured composite texts such as corpora or
language collections, where it is often highly desirable
to enforce a controlled descriptive vocabulary or to
perform retrievals from a body of text in terms of text
type or origin.
The text profile may however be of use in any form of
automatic text processing.

<profileDesc> element
<creation> contains information about the creation of a text.
<langUsage> describes the languages, sublanguages, registers,

dialects etc. represented within a text.


<textClass> groups information which describes the nature or
topic of a text in terms of a standard classification scheme,
thesaurus, etc.
other elements may also appear:
<textDesc> provides a description of a text in terms of its
situational parameters.
<particDesc> describes the identifiable speakers, voices, or
other participants in a linguistic interaction
<settingDesc> describes the setting or settings within which a
language interaction takes place, either as a prose description or
as a series of setting elements.

Revision history, tagged

<revisionDesc>
Which allows the encoder to provide a

history of changes made during the


development of the electronic text.
The revision history is important for
version control and for resolving
questions about the history of a file.

<revisionDesc> element
<revisionDesc> summarizes the

revision history for a file.


<change> summarizes a particular
change or correction made to a
particular version of an electronic text
which is shared between several
researchers.

You might also like