![]() ![]() Where it is often highly desirable to enforce a controlled descriptive vocabulary Use in highly structured composite texts such as corpora or language collections, Its subject matter, the situation in which it was produced, the individuals describedīy or participating in producing it, and so forth. An optional work description or list of the works encoded or described in the file, tagged workList, containing classification and contextual information about the work(s), such as.The MEI elements used to encode the encoding description are described in section.Transcription, how the encoder resolved ambiguities in the source, what levels ofĮncoding or analysis were applied, and similar matters. ![]() It allows for detailed description of whether (or how) the text was normalized during An optional encoding description, tagged encodingDesc, which describes the relationship between an electronic text and its source or sources.The MEI elements used to encode the file description are described in section 3.4 Information about an MEI file.May be described within the manifestationList element). Sources that represent or witness the encoded work in a more general sense these The file description also includes information about the source or sources from which the electronic document was derived (not to be confused with The term computer file here is to be understood as referring to the whole intellectual entity or documentĭescribed by the header, even when this is stored in multiple physical operating systemįiles. A titleStmt within fileDesc captures the title of the file, which may be different than the title of the encoded work, or the title given on any of the sources used to generate the file. Information contained here, a user of the encoding should be able to derive a properīibliographic citation, and a librarian or archivist could use it for creating a catalogĮntry recording its presence within a library or archive. A file description, tagged fileDesc, containing a full bibliographic description of the computer file itself.Is just a simple element that helps to preserve other external identifiers for a file, Zero or more alternative identifiers, tagged with altId, each of which provides an identifying name or number associated with the file.These areas are described following their order of appearance within the meiHead element: Some child elements like titleStmt may appear in various places (see 3.3.1 Title Statement), so it is important to understand the roles of the different areas of the MEI header. The metadata encoded inside meiHead covers a number of different use cases. This set is known as the MEI header, tagged Metadata, such as TEI or METS, must carry a set of descriptions, prefixed to it andĮncoded as described in this chapter. ![]() Manuals customarily accompanying electronic data sets.Įvery MEI-conformant text not embedded in another XML carrier that provides for capturing They also constitute an equivalent for the content of the code books or introductory Together these descriptions andĭeclarations provide an electronic analog to the title page attached to a printed Them, and for catalogers in libraries and archives. Such documentation is necessary for scholars using the texts, for software processing Text, as well as its sources, encoding, and revisions are all thoroughly documented. This chapter thus addresses the description of an encoded item so that the musical It attempts to reflect both current library practiceĪnd common scholarly methods, for example in the field of source descriptions (see MEI’s approach to metadata is heavily influenced by other existing standards and Perspective, as described in 3.2 Structure of the MEI Header. Types of metadata, which MEI tries to order according to their respective scope or Metadata means "data about data", i.e., information about various aspects of an encoding at hand. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |