From MASTER to TEI P5

3. Elements added

A number of new elements were added as a consequence of the restructuring of the MASTER <physDesc> element: specifically <objectDesc>, <supportDesc>, <sealDesc>, and <layoutDesc>. The existing <support>, <extent>, <foliation>, <collation> and <condition> elements, formerly direct children of <physDesc>, are now grouped within the new element <supportDesc>. The existing <layout> element is now wrapped within the new grouping element <layoutDesc>. These two elements now constitute the new <objectDesc> element, which is a child of <physDesc>, along with <accMat>, <additions>, <bindingDesc>, <decoDesc> (formerly <decoration>), <handDesc>, <musicNotation>, and the new <sealDesc> element.

A new <altIdentifier> element replaces <idno> when this appears at the start of a <msPart> element.

A new <msItemStruct> element is available as an alternative to <msitem>: it contains the same child elements, but constrains their order and cardinality.

Question: should we constrain the order in which child elements of <msItem> are presented? should we use <msItemStruct> to enforce this?

Resolution: The ENRICH project decided that it was better to use <msItem> element and remove <msItemStruct> entirely from the ENRICH schema. It also felt that it should not constrain the order of child elements.

TEI P5 provides a small number of new elements which have no counterpart in MASTER:
  • A new <stamp> element is available to record information transcribed from a stamp or similar device.
  • A new <watermark> element is available to record information transcribed from (or descriptive of) a watermark or similar device.
  • A new <filiation> element is available to discuss the manuscript's relationship with other manuscripts.

Question: if these new elements are included in the ENRICH DTD, how should we identify their content in existing elements?

Resolution: These elements should be included in the ENRICH schema for those creating new records, but the ENRICH project reached no consensus on how one should identify such information in existing content as no standard method to delineate it was followed in MASTER.

Up: Contents Previous: 2. Elements renamed Next: 4. Elements removed