Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
executable file 22 lines (13 sloc) 3.25 KB
sectionid title version
corpusModuleOverview
Corpus Module Overview
v4

The meiCorpus module defines a single element:

{% include desc elem="meiCorpus" %}

The {% include link elem="meiCorpus" %} element is intended for the encoding of corpora, though it may also be useful in encoding any collection of disparate materials. The individual samples in the corpus are encoded as separate {% include link elem="mei" %} elements, and the entire corpus is enclosed in an {% include link elem="meiCorpus" %} element. Each sample has the usual structure for a {% include link elem="mei" %} document, comprising an {% include link elem="meiHead" %} followed by a {% include link elem="music" %} element. The corpus, too, has a corpus-level {% include link elem="meiHead" %} element, in which the corpus as a whole, and encoding practices common to multiple samples may be described. The overall structure of an MEI-conformant corpus is thus:

{% include mei example="corpus/corpus-sample210.xml" valid="" %}

This two-level structure allows for metadata to be specified at the corpus level, at the individual text level, or at both. However, metadata which relates to the whole corpus rather than to its individual components should be removed from the individual component metadata and included only in the {% include link elem="meiHead" %} element prefixed to the whole.

In some cases, the design of a corpus is reflected in its internal structure. For example, a corpus of musical incipits might be arranged to combine all compositions of one type (symphonies, songs, chamber music, etc.) into some higher-level grouping, possibly with sub-groups for date of publication, instrumentation, key, etc. The {% include link elem="meiCorpus" %} element provides no support for reflecting such internal structure in the markup: it treats the corpus as an undifferentiated series of components, each tagged with an {% include link elem="mei" %} element.

If it is essential to reflect the organization of a corpus into sub-components, then the members of the corpus should be encoded as composite texts instead, using the {% include link elem="group" %} element described section {% include link id="sharedMusicElement" %}. The mechanisms for corpus characterization described in this chapter, however, are designed to reduce the need to do this. Useful groupings of components may easily be expressed using the classification and identification elements described in section {% include link id="headerWorkClass" %}, and those for associating declarations with corpus components described in section {% include link id="headerAssociatingMetadataAndData" %}. These mechanisms also allow several different methods of text grouping to co-exist, each to be used as needed at different times. This helps minimize the danger of cross-classification and mis-classification of samples, and helps improve the flexibility with which parts of a corpus may be characterized for different applications.

All composite texts share the characteristic that their different component texts may be of structurally similar or dissimilar types. If all component texts may all be encoded using the same module, then no problem arises. If however they require different modules, then the various modules must all be included in the schema.

You can’t perform that action at this time.