From 50c2c29e7c6107d37ae8c555b196e43a498df359 Mon Sep 17 00:00:00 2001 From: holfordm Date: Mon, 18 Feb 2019 16:15:18 +0000 Subject: [PATCH 01/10] improve decoration guidance --- msdesc.odd | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index be23978..fd82b00 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -2230,17 +2230,21 @@ carpetPage - Historiated initials + Historiated initials(i.e., containing an identifiable narrative scene) (Brown: historiated initial) histInit - decorated initials + decorated initials (Brown: decorated initial, anthropomorphic initial, zoomorphoric initial, gymnastic initial, inhabited initial). decInit coloured initials colInit + + initials with penwork flourishing (Reallexikon zur Deutschen Kunstgeschichte: fleuronné) (Brown: pen-flourished initial, littera florissa). Also use for so-called arabesque initials. + flourInit + plain initials plainInit @@ -2339,7 +2343,7 @@ (fol. 49r) Hours of the Virgin, Lauds. Visitation.

-

Aspects of the manuscript relating to the presentation of the text - notably rubrication - should also be included in the decoDesc element (rather than in the layout element.

+

Aspects of the manuscript relating to the presentation of the text - notably rubrication - should also be included in the decoDesc element (rather than in the layout element, using decoNote with attribute type of value rubrication.

From e85ffaf61b7d2473b22ab6ff8402462dde93e278 Mon Sep 17 00:00:00 2001 From: holfordm Date: Fri, 1 Mar 2019 16:33:54 +0000 Subject: [PATCH 02/10] update values for `supportDesc/@material` -a fairly urgent change, as currently the suggested values for the attribute in Oxygen are the default TEI values (paper, parch, mixed) rather than chart, perg and mixed --- msdesc.odd | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index fd82b00..8c53f27 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -3785,8 +3785,29 @@ - - + + + + + + The object is composed of parchment + + + The object is composed of paper + + + The object is composed of a combination of paper and parchment. The nature of the combination should be specified in the support element. + + + The object is composed of another material (e.g. wood). + + + The material of which is object is composed is not known. + + + + + From a10f9bcc913879ad40c180df9cf449c8a5cba0a9 Mon Sep 17 00:00:00 2001 From: holfordm Date: Fri, 1 Mar 2019 16:40:58 +0000 Subject: [PATCH 03/10] new schematron rule: dimensions must have unit attribute --- msdesc.odd | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/msdesc.odd b/msdesc.odd index 8c53f27..d0ff83b 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -3785,6 +3785,7 @@ + @@ -4022,6 +4023,22 @@ + + + + + + + + The unit of measurement must be specified in the unit attribute on the dimensions element + + + + + From 65d44a2978ed27c7db0f50e0338328fffccff09a Mon Sep 17 00:00:00 2001 From: holfordm Date: Wed, 13 Mar 2019 15:48:30 +0000 Subject: [PATCH 04/10] various updates and corrections (see below) -ensure role attributes are consistent -add more examples -remove specList -more guidance on gap element -more guidance on msItem -guidance on pseudonymous and attributed authorship -more guidance on incipits -more guidance on parchment disposition -more guidance on paper description -more detail on script attributes -add value 'mixed' to attribute rulingMedium -rules for form attribute on objectDesc --- msdesc.odd | 2034 ++++++++++++++++++++++++++++++++++------------------ 1 file changed, 1355 insertions(+), 679 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index d0ff83b..9306fe9 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -6,7 +6,8 @@ - TEI P5 Customization and Encoding Guidelines - Bodleian Library UNFINISHED DRAFT - IN PROGRESS + TEI P5 Customization and Encoding Guidelines - Bodleian Library UNFINISHED + DRAFT - IN PROGRESS Bodleian Library, Oxford @@ -46,10 +47,18 @@
Introduction -

These draft guidelines are currently based on two main sources - the encoding guidelines for the Fihrist project [pdf], and encoding guidelines for medieval manuscripts jointly created by Cambridge University Library (James Freeman, with Suzanne Paul) and the Bodleian Library (Matthew Holford) with contributions by Andrew Dunning (formerly British Library). The medieval guidelines in turn draw in places on the guidelines created by Patrick Granholm and Eva Nyström for manuscripta.se.

+

These draft guidelines are currently based on two main sources - the encoding + guidelines for the Fihrist project [pdf], and encoding guidelines for medieval manuscripts jointly + created by Cambridge University Library (James Freeman, with Suzanne Paul) + and the Bodleian Library (Matthew Holford) with contributions by Andrew + Dunning (formerly British Library). The medieval guidelines in turn draw in + places on the guidelines created by Patrick Granholm and Eva Nyström for + manuscripta.se.

- +
General principles
@@ -57,10 +66,9 @@

Phrases or words in other languages than English may be tagged by adding the xml:lang attribute to the element enclosing the text, or where no other element is available with a foreign element and - a xml:lang attribute. By default this text displays in italic when rendered in the online catalogue. - - - + a xml:lang attribute. By default this text displays in italic + when rendered in the online catalogue. +

@@ -68,7 +76,8 @@

References to a specific location or range within a manuscripts should be given in a locus element. The from and to attributes are optional but recommended, as they enable links to images - to be generated and allow calculation of the length of manuscript items.

+ to be generated and allow calculation of the length of manuscript + items.

If from and to attributes are used to refer to a specific folio or page they should be used with identical values. The foliation scheme should be specified in the scheme attribute @@ -90,14 +99,20 @@ (fols. 1r-10r, margins)

+

For texts scattered over more than one location in the manuscript the + locusGrp element should be used. + + Fols 356rb-vb, + 374rab + + +

-

- - - -

@@ -109,31 +124,44 @@ the role attribute. Values should correspond to the Library of Congress relator term list (http://www.loc.gov/marc//relators/relaterm.html). The most commonly occurring roles are: - "aut" (author), "scr" (scribe), "art" (artist; NB this is preferred to illustrator), "fmo" (former owner),"sgn" (signer), "pat" (patron). If - necessary, multiple roles can be separated with whitespace. http://www.loc.gov/marc//relators/relaterm.html). The most + commonly occurring roles are: "aut" (author), "scr" (scribe), "art" + (artist; NB this is preferred to illustrator), "fmo" (former + owner),"sgn" (signer), "pat" (patron). If necessary, multiple roles can + be separated with whitespace. Common-place book of - John + John Curteys of Winchester College and New College, Oxford

-

Use "fmo" where there is evidence that a person owned an item. Use "sgn" where the person is only associated with the item by a signature or an inscription which does not necessarily imply ownership.

+

Use "fmo" where there is evidence that a person owned an item. Use "sgn" + where the person is only associated with the item by a signature or an + inscription which does not necessarily imply ownership. "dnr" (donor) + may be used where the person gave the manuscript to an institution but + evidence of ownership before the gift is lacking; i.e. to describe + manuscripts apparently bought or made with the intention of being + directly presented, or manuscripts may have been purchased with money + given by a donor rather than directly presented.

- Corporate / organization names + Corporate / Organization Names

Corporate entities should be tagged using the orgName element. For indexing to function correctly this MUST be linked to the persons authority file using the key attribute. The role of the organization referred to should be indicated using the role attribute. Values should correspond to the Library of Congress relator term list (http://www.loc.gov/marc//relators/relaterm.html). Separate multiple roles with whitespace. - + >http://www.loc.gov/marc//relators/relaterm.html). Separate + multiple roles with whitespace. Würzburg, Domstift St Kilian, + 12th-century ex libris, fol. 1r, and 15th-century shelfmark, fol. + 2r.

- Place names + Placenames

In sections relating to manuscript contents, physical description and provenance, placenames should be tagged using the placeName. For indexing to function correctly this MUST be linked to the places @@ -148,18 +176,21 @@

In the origPlace element, placenames should be tagged using (as appropriate) country, region and settlement. Again, for indexing to function correctly these MUST be linked to the - places authority file using the key attribute.

- -

To accommodate geodata in legacy data, or for use by other systems, geo - elements are permitted. But they are not displayed in catalogue web sites. For - example, from the International Dunhuang Project:

- - DHMG.(Dunhuang Mogao) DHMG.17. - 94.80388888888889198 40.03638888888888658 + places authority file using the key attribute. See under origPlace.

+

To accommodate geodata in legacy data, or for use by other systems, + geo elements are permitted. But they are not displayed in + catalogue web sites. For example, from the International Dunhuang + Project:

+ + DHMG.(Dunhuang Mogao) DHMG.17. 94.80388888888889198 40.03638888888888658 95.9375 40.04833333333333201 +

In other cataloguing projects geodata should be given in the places + authority file.

+
Hyperlinks @@ -199,12 +230,14 @@ Transcription

Transcriptions from the manuscript in the rubric, incipit, explicit, etc. elements, or in the - provenance section, should be made diplomatically. Expand standard - abbreviations silently. If the abbreviation can be expanded with some - but not complete confidence, enclose the expansion in the ex - element. Denote uncertain or ambiguous abbreviations with the character ’ [U0146], e.g. Westm’

+ provenance section, should be made diplomatically. + Expand standard abbreviations silently. + If the abbreviation can be expanded with some but not complete + confidence, enclose the expansion in the ex element. Denote + uncertain or ambiguous abbreviations with the character ’ [U0146], e.g. + Westm’

Use capital letters only when they appear in the manuscript.

- +

Transcription of special characters: e-caudata should be transcribed using U+0119: Latin Small Letter E With Ogonek

The relevant elements from the TEI transcription module should be used @@ -219,20 +252,21 @@ with the relevant elements from the TEI transcription module.

-

Manuscript punctuation may be simplified by replacing the punctus versus and punctus elevatus with a point (.).

+

Manuscript punctuation may be simplified by replacing the punctus versus + and punctus elevatus with a point (.).

Indicate damage using the damage element.

Errors in the manuscript may be indicated using the sic and - corr and choice elements. sic by itself simply signals the - presence of an error, corr provides the correction. + corr and choice elements. sic by itself + simply signals the presence of an error, corr provides the + correction. Explicit loica magistri pauli de Venetijs Explicit - loicalogica + loicalogica magistri pauli de Venetijs

@@ -245,75 +279,126 @@

- -

Deletions by the scribe or later annotators should be recorded using the del element. The rend attribute may be used to indicate the manner of erasure: suggested values include strikethrough (the text has a line through it), erasure (the text has been scraped off), expunction. + +

Deletions by the scribe or later annotators should be recorded using the + del element. The rend attribute may be used to + indicate the manner of erasure: suggested values include + strikethrough (the text has a line through it), + erasure (the text has been scraped off), + expunction.

- - -

Additions by the scribe or later annotators should be recorded using the add element, with the - place attribute. The values of the place attribute should be one of the values specified in the EpiDoc guidelines, e.g: - + + +

Additions by the scribe or later annotators should be recorded using the + add element, with the place attribute. The + values of the place attribute should be one of the values specified in + the EpiDoc guidelines, e.g: above: written above the line below: written below the line top: written in the top margin bottom: written in the top margin margin: written in an unspecified margin - unspecified: written in an unspecified location + unspecified: written in an unspecified + location -

- -

Corrections by the scribe or later annotators should be recorded using a combination of the add and del elements with the subst or mod element. - - - Theodocius dicit De coniugationibus apud grecos iii sunt coniugationes uerborum quaorum prima positione - -

- - - -

Gaps due to damage, and illegible characters, should be marked with - gap with reason of damage and - illegible respectively. The extent of a gap should be - indicated in characters if possible. Corrections by the scribe or later annotators should be recorded using a + combination of the add and del elements with the + subst or mod element. + Theodocius dicit De coniugationibus apud grecos iii sunt + coniugationes uerborum + quaorum prima + positione + +

+ + + +

Gaps should be marked with gap element, using the + reason attribute to described the nature of the gap, and + the unit attribute, in combination with quantity, + atMost, atLeast, and if necessary + precision, to specify its extent. This extent should be + indicated in characters if possible. + Suggested values for reason + damage: text has been omitted due to damage to the + manuscript + illegible: text has been omitted because it is + illegible (but the manuscript is not otherwise damaged) + ellipsis: text (e.g. the formulaic ending of an + explicit) has been omitted for brevity + space: the gap in the transcription represents + space that has been left in the manuscript itself, usually with + the intention of text being supplied at a later stage. (Note: do + not use this to transcribe initial letters which have been + omitted: these should be transcribed using the supplied + element. + lacuna: there is no gap in the text being + transcribed, but the text is not complete (e.g. words or lines + have been omitted from an exemplar). + + + - + + + +

Questionable or partly legible readings should be marked with unclear (generates a ‘(?)’ after the text in html)

-

Line breaks should be indicated with empty lb elements.

+

Line beginnings should be indicated with empty lb elements, + column beginnings with empty cb elements

Quotations from the manuscript -

Quotations from the manuscript, outside of elements such as incipit, explicit and so on, should be enclosed in the q element. This may have attribute type with sample values: - - pressmark: the quotation is a pressmark, shelfmark or similar - exLibris: the quotation is an ex libris inscription - inscription: the quotation is the inscription of a signer or reader - +

Quotations from the manuscript, outside of elements such as + incipit, explicit and so on, should be enclosed in + the q element. This may have attribute type with + sample values: + pressmark: the quotation is a pressmark, shelfmark + or similar + exLibris: the quotation is an ex libris + inscription + inscription: the quotation is the inscription of a + signer or reader +

- References to manuscripts -

References in the description to other manuscripts should be enclosed in bibl tags with type of value MS. The subtype may be used to indicate if the manuscript is held by the same institution that holds the manuscript being catalogued (value interal) or by another institution (value external). In the former case, the shelfmark should not include the location or institution name; in the latter case, location and institution should be included.

-

- The ref element may be used to provide a link to an online catalogue or digital fascimile. - - Eberbach, Cistercian abbey (?): ‘modern’ chapter numbers added in boxes in the margin, as in MS. Laud Lat. 107. - - - This scribe was also responsible for most of the Simeon manuscript (London, British Library, Add. MS. 22283) but has not yet been identified in any other manuscripts or documents. + References to other manuscripts +

References in the description to other manuscripts should be enclosed in + bibl tags with type of value MS. The + subtype may be used to indicate if the manuscript is held + by the same institution that holds the manuscript being catalogued + (value interal) or by another institution (value + external). In the former case, the shelfmark should not + include the location or institution name; in the latter case, location + and institution should be included.

+

The ref element may be used to provide a link to an online + catalogue or digital fascimile. Eberbach, Cistercian abbey + (?): ‘modern’ chapter numbers added in boxes in the margin, as in + MS. Laud Lat. 107. + This scribe was also + responsible for most of the Simeon manuscript (London, British Library, Add. MS. 22283) but + has not yet been identified in any other manuscripts or documents.

@@ -359,20 +444,21 @@ - +

File Description

The fileDesc element contains a titleStmt, - publicationStmt, and sourceDesc element. + publicationStmt, and sourceDesc + element.

Title Statement @@ -383,18 +469,18 @@ the TEI file, and the cataloguing project of which it is a part, rather than for the manuscript itself (which is described in the sourceDesc). It must contain (1) a title - element containing the manuscript shelfmark, (2) a title - element with type attribute of value - collection describing the collection of which the - manuscript is a part, and (3) one or more respStmt elements - listing the person(s) responsible for the cataloguing and encoding. - The respStmt element must have a xml:id - attribute containing an identifier for the person(s) responsible for - the cataloguing and/or encoding. The name should be recorded in a - persName element (see ) and the role - of the person responsible in resp elements. If known, the - date should be given in the when attribute of - resp + element containing the manuscript shelfmark, (2) [for the medieval + catalogue] a title element with type attribute + of value collection describing the collection of which + the manuscript is a part, and (3) one or more respStmt + elements listing the person(s) responsible for the cataloguing and + encoding. The respStmt element must have a + xml:id attribute containing an identifier for the + person(s) responsible for the cataloguing and/or encoding. The name + should be recorded in a persName element (see ) and the role of the person + responsible in resp elements. If known, the date should be + given in the when attribute of resp @@ -409,14 +495,14 @@ - +

@@ -451,13 +537,13 @@ - William Wilson, F.S.A., of - the Minories, his sale, Christie's, 31 Jan.-1 Feb. 1833, lot - 56 on 1 Feb.; bought by Thorpe for £53. 11s. + William Wilson, F.S.A., of the Minories, his + sale, Christie's, 31 Jan.-1 Feb. 1833, lot 56 on 1 Feb.; + bought by Thorpe for £53. 11s. Purchased from Thorpe by Douce, Feb. 1833. + key="person_69848690" role="fmo">Douce, Feb. + 1833.

@@ -495,13 +581,13 @@ - +

@@ -529,10 +615,10 @@ First online publication. - +

@@ -591,8 +677,8 @@ as a physical object, its constituent parts, and intellectual works represented within.

All manuscript descriptions must be informed by attention to codicological - units. In other words, whether the manuscript was created in one place, - over one period of time, or is a composite of parts from multiple sources, + units. In other words, whether the manuscript was created in one place, over + one period of time, or is a composite of parts from multiple sources, assembled at a later date.

If the manuscript forms a single codicological unit, its intellectual content, physical description, and history should be described directly @@ -611,14 +697,14 @@ for the whole volume was added by a later owner, or if the manuscript has replacement leaves). Conversely information relevant to each unit should be described in separate msPart elements.

-

In each case the following elements are used: +

In each case the following elements are used: @@ -644,7 +730,8 @@ (type attribute with value former). If the manuscript has a reference number in another catalogue or reference work, this should be given inside an altIdentifier element in - an idno element. The following values are currently used in the medieval catalogue: + an idno element. The following values are currently used in the + medieval catalogue: SCN - Summary catalogue number TM - identifier in Trismegistos PR - papyrological reference @@ -676,7 +763,7 @@ - +

@@ -697,19 +784,20 @@ instead. Ovid; England, 12th century - +

Intellectual Content

The intellectual content of the manuscript or codicological unit should - be listed in the msContents element. + be listed in the msContents element. +

Summary (optional) @@ -747,21 +835,27 @@

If the unit contains multiple works, in different languages or scripts, the textLang element should be used in the msItem instead, q.v.

-

According to the conventions of the catalogue, languages may be encoded at a high or low level of granularity - for example, Middle English may be encoded as "enm" or as "en", Anglo-Norman French may be encoded as "fr" or "xno"..

+

According to the conventions of the catalogue, languages may be + encoded at a high or low level of granularity - for example, Middle + English may be encoded as "enm" or as "en", Anglo-Norman French may + be encoded as "fr" or "xno".

Manuscript Item -

The msItem element may be used: - - To describe an item of intellectual content (including blank leaves if necessary) - To provide various note about the manuscript's contents (e.g. to compare items and their order with the contents of other manuscripts), or to provide a note of content now missing that was formerly present.) - +

The msItem element may be used: + To describe an item of intellectual content (including + blank leaves if necessary) + To provide various notes about the manuscript's contents + (e.g. to compare items and their order with the contents of + other manuscripts, or to provide a note of content now + missing that was formerly present.) +

- + -

As a general rule, each distinct item in the manuscript should be descibed in a distinct - msItem tag

+

As a general rule, each distinct item in the manuscript should be + descibed in a distinct msItem tag.

The items should be numbered with the n attribute. (This is particularly useful when the msItem element is nested, @@ -797,7 +891,8 @@

More extensive streches of blank pages can be placed in a separate msItem. - Fols. 187v-189v blank. + (fols. 187v-189v) + Blank.

Pages containing short notes or scribbles by later hands should be @@ -805,8 +900,41 @@ target="#additions"/>.

What is a manuscript item? -

The identification of manuscript items can pose difficulties both - for the cataloguer and the encoder. Special cases include: +

The Guidelines offer the following definitions: ‘each discrete + item in a manuscript’; ‘an individual work or item within the + intellectual content of a manuscript’. Often the identification + of these works or items does not pose difficulties, but many + more complex cases do occur.

+

A more helpful definition of a manuscript item may be ‘a complete + work or item, or a self-contained part of a larger work with + (potentially) independent circulation’. A ‘self-contained part + of a larger work’ could be a letter in a letter-collection, or a + sermon in a homiliary; it could also represent the biblical text + or the commentary in a glossed biblical manuscript.

+

As a guiding principle, where possible and practicable the + msItem element should be used to markup up the work + as a whole, and its self-contained parts, and the nesting of the + different msItem elements should express the + relationship between part and whole.

+

However, it is recognised that it may not be practical (for + example) to markup every letter in a letter-collection as an + msItem, and that the contents and order of a + collection may simply be recorded in a note element. + + Jerome + 112 letters + + Epist. 57 (38), 73 (44), 129 (57), 35 + (1), 36 (2; as 3 items, dividing in sects. 10-15), 62 + (3), 19 (4), 20 (5), 15 (6), 16 (7), 18B (8), 18A (9), + 21 (10), 14 (37), 52 (33), 58 (34), 55 (?), 83-4 + (39-40), + +

+ + + +

Difficulties are posed by: texts which circulate with shorter related texts, for example Augustine’s De Trinitate, preceded in Merton College MS. 32 by the relevant extract from @@ -870,24 +998,9 @@

-
- Nesting of msItem -

If necessary, a text may be further subdivided into numbered - constituent parts. This may be necessary/useful in the case of, - for example: - Bibles - liturgical books - legal collections - sermon collections - texts containing several sections, e.g. preface, - prologue, dedicatory letter, multiple books. - poetry collections - -

-

The level of detail and elements required in sub-items will vary - according to the text involved. For examples, see the Appendix. - -

+
+

For sample encodings of liturgical books (a Book of Hours) and a + Bible, see the Appendix.

Texts with gloss and commentary @@ -900,22 +1013,23 @@

- - - Psalter with Old English gloss - - Psalms (Roman version), beginning imperfectly at - 2.4 and ending at 144.6 - Qui habitat in - caelis - terribiliorum tuorum - dicent - - Continuous interlinear gloss in Old - English - se eardað in heofonum - þinra eyes fulnessa cweoðað + Psalter with Old English gloss + + Psalms (Roman version) + Beginning imperfectly at 2.4 and ending at + 144.6 + Qui habitat in + caelis + terribiliorum tuorum + dicent + + + Continuous interlinear gloss in + Old English + se eardað in heofonum + þinra eyes fulnessa cweoðað + @@ -925,17 +1039,23 @@ Pauline Epistles, with gloss - Pavlvs seruus ihesu cristi uocatus - apostolus segregatus - Saluatoris Regis - sacerdotis cui merito omnes serui - predicandum - Pro altercatione scribit - apostolus Romanis confutans modo gentiles + + Pavlvs seruus ihesu cristi + uocatus apostolus segregatus + + Interlinear gloss: + Saluatoris Regis sacerdotis cui merito + omnes serui predicandum + + + Marginal gloss: + Pro altercatione scribit apostolus Romanis + confutans modo gentiles + - +

@@ -961,18 +1081,22 @@

- +
Added texts +

Significant added texts should be described in msContents, NOT in additions. Decision as - to what is ‘significant’ will be a matter of judgement, but if - it is important for the text to be identified or described, or - to have its rubrics / incipits recorded, etc., this is much - better done using msItem inside msContents. - This may involve some reorganization of the description during - retroconversion.

-

There are two approaches: + to what is ‘significant’ will be a matter of judgement, but in + general if the text is to be discoverable - if it is important + for the text to be identified or described, or to have its + rubrics / incipits recorded, etc. - it should be encoded using + msItem. This may involve some reorganization of the + description during retroconversion.

+

Two possible approaches are described here. Each may be + appropriate in different circumstances, dependent for example on + the nature of the manuscript and/or the nature of the + description being converted: describe every msItem in sequence, using note to indicate if it is a later addition @@ -989,7 +1113,8 @@

- Added texts: + + Added texts: Fol. 164v Calendar @@ -1086,15 +1211,20 @@

Author -

The author name should be recorded inside the author - element. This MUST have a reference, using the key - attribute, to the persons authority file, see . The author element - should be omitted for anonymous works. The author of a manuscript item, if known, should be recorded + inside the author element. This MUST have a reference, + using the key attribute, to the persons authority + file, see . The author + element should be omitted for anonymous works. Augustine

+

The author name should be given in a standardized form. For + retroconversion, use the form of the name given in the source + text; for new cataloguing, use a standard form from the usual + reference works.

If you are not responsible for maintaining the authority files, go to the web site, click the People button, and search to see if the same person already exists in another manuscript in the @@ -1130,9 +1260,80 @@

-

For retroconversion, use the form of the name given in the source - text; for new cataloguing, use a standard form from the usual - reference works.

+
+ Pseudonymous, multiple, uncertain, disputed and attributed + authorship +

Texts which circulated consistently but incorrectly under the + name of an author, but whose true author is not known, are + by convention attributed to Pseudo-Augustine, + Pseudo-Ambrose, etc., and these conventional attributions + should be followed. + Ps.-Augustine + De Vera et Falsa + Poenitentia +

+

Texts which circulated consistently but incorrectly under the + name of an author, but whose true author IS now known or + suspected, should be catalogued under the author which + modern scholarship prefers. In some cases, where the + association with other authors is strong, it will be useful + to give these in addition. + Haimo of Auxerre + (Ps.-Haimo of Halberstadt, Ps.-Cassiodorus) + Commentary on the Song of + Songs + Note that the pseudonymous authors do not have + their own author element (these may be given in the + authority file: q.v.).

+

Where the attribution of a text in the manuscript differs + from the attribution of modern scholarship, this can be + recorded either in a note element or by relevant + markup in the rubric element. Use the + persName element with attribute role + of value att (= ‘attributed name’) + Ivo of Chartres + Epistola ad Seuerinum + Incipit liber Anselmi de caritate + + + Ps.-Bede + <supplied>Commentary on + John</supplied> + Cap. 3. Here ascribed to Augustine. + +

+

Multiple authors can be indicated using repeated + author elements. + + Guillaume de + Lorris + Jean de + Meung + Le Roman de la Rose + French + +

+

Uncertainly regarding authorship can be indicated using the + cert attribute. Following the usage of + Richard Sharpe, ‘attrib.’ can be used for modern scholarly + attributions of authorship; ‘ascr.’ denotes ascriptions in + manuscripts; and ‘(?)’ denotes broader uncertainty. + Roger of Caen + (attrib.) (Ps.-Alexander Nequam) + De professione monachorum + +

+ +
+
Editor / translator / etc. @@ -1158,18 +1359,21 @@ authority file, so that they are indexed on the web site.) Further details about their role in the creation of the work can be explained in a separate note.

-

Alternatively (this is current practice in the medieval catalogue) information about translators, etc., may be provided in the note element as follows: - - - Origen - - Homilies on Joshua - (Latin tr. by Rufinus) - +

Alternatively (this is current practice in the medieval + catalogue) information about translators, etc., may be provided + in the note element as follows: + Origen + Homilies on Joshua + (Latin tr. by Rufinus) +

Title +

The title element provides a standarized uniform title or a + descriptive title for a manuscript item.

For retroconversion, use the form of the title given in the source catalogue (if one is given); for new cataloguing (or if the converted catalogue does not supply a title), use a standard @@ -1206,6 +1410,17 @@ the part of the URL after the last slash, starting with "work_". Otherwise, leave the key attribute blank and an identifier will be assigned to it at a later date.

+

(optional) to indicate the title is not given in the manuscript, + use the supplied element. + Bonaventure + <supplied>Legenda + maior</supplied> + +

+ +
@@ -1224,22 +1439,49 @@ to use xml:lang to specify the language of the incipit (etc.), unless multiple languages are involved (e.g. msItem with rubric in French but - incipit in Latin).

+ incipit in Latin). + + (fols.18r-21v) + Oraison tres deuote de nostre + dame + Obsecro te + [masculine forms] (cf. MS. Buchanan e. 2) + + +

For mutilated items the attribute defective should be - used with value true. -

-

Multiple incipits, rubrics, etc., e.g. for prologues, prefaces, - text, may be distinguished using type, or by location - by including a child locus element at the start of each - one; this will not always be possible in retroversion if the - catalogue does not provide the information. In this case a - series of the relevant elements without type should - be used.

+ used with value true.

The formatting of the rubric can be recorded in the rend attribute (see ). Comments on the rubric (e.g. if it is a later addition) can be recorded using a note tag inside the rubric - tag. + tag. + + (fols. 64r-70v) + Divinacio + ciceronalis(incomplete) + See A. A. Guardo, 'La Divinacio Ciceronalis: un libro de + suertes medieval. Estudio introductorio', in + De lo humano y lo divino en la literatura + medieval: santos, ángeles y demonios, ed. + Juan Paredes Núñez (2012), 17-34. + The surviving section in this MS. comprises the + responses, fourteen (of originally 20) sections of + 21 lines, the first line of each in red, each + section attributed to sun, moon, a planet or a sign + of the zodiac (Guardo's section 4). The text in MS. + Digby 46 has in addition a miniature of Cicero, + twenty prognostical questions, and directions for + use (see Guardo). + Sol iudex primus + (first line in + red) Mittam te ad amicum meum et dicet tibi + uerum Certe tibi dico prope est ut gaudeas et mutes + fortunam + +

Note that TEI distinguishes between the finalRubric, which contains a statement relating to the end of a particular @@ -1247,20 +1489,39 @@ contains a statement about the scribe and/or date and/or place of writing (‘scriptum apud Oxon.’). If the final rubric and colophon form a single sentence, put both inside - finalRubric.

-

These elements should not have final punctuation, unless they - contain more than one sentence, in which case there should be a - closing period.

-

Where (as for example in sermons or commentaries) the incipit - begins with a quotation, this should be placed in hi - tags with rend of value italic [There is - an active ticket with the TEI about improving this markup: - https://github.com/TEIC/TEI/issues/1755] - + finalRubric with type attribute of value + colophon. (The colophon element cannot + have the type attribute.) + Expliciunt omelie Iohannis + Crisostomi patriarche Constantinopolitanis super Matheum + operis imperfecti scripte anno Domini 1382 +

- -

+

Multiple incipits, rubrics, etc., e.g. for prologues, + dedications, text, should be distinguished using type + (and if necessary by location, by including a child + locus element at the start of each one). Suggested + values of the type attribute are prologue + (use for preface, prohemium, etc), dedication, + text + + (fol. 12v) + Garland + Compotus + Sepe uolumina domni + Bede + Superioris igitur pagine + + +

+ +

Use of the type attribute will not always be possible + in retroversion if the catalogue does not provide the + information. In this case a series of the relevant elements + without type should be used. (fols. 1-14v) @@ -1281,8 +1542,63 @@ SAO 1. 13-87.

- - + +

The rubric, incipit, etc. elements should not + have final punctuation, unless they contain more than one + sentence, in which case there should be a closing period.

+
+ Complex incipits +

The incipit elements in a catalogue may be processed + to generate an alphabetical list of incipits similar to + those in a print catalogue.

+

For long and complex incipits, care should be taken to mark + up the content in a way that enables multiple index entries + to be generated to aid discovery.

+

Incipits containing an initial address should be divided into + two incipit elements, the first containing the + address and the second the incipit itself. + PETER OF WALTHAM + Remediarium Conuersorum + Reuerendo patri Ricardo ecclesie Londoniensi + episcopo tercio suus Petrus Blesensis archidiaconus + eiusdem ecclesie sic currere per temporalia ut + brauium apprehendat eternum + De beata mentis solitudine necnon et euangelice + paupertatis beatitudine + +

+

Incipits of sermons often begin with a biblical lemma, and in + a printed catalogue would be indexed both under the lemma + and under the incipit. These should be marked up using the + cit, quote, and bibl elements + as follows. + Qui mihi ministrat me + sequitur. + Io. 15. In his uerbis notantur + duo; primum est Christo debita + administracio + If the source is not given, the quote + element only may be used. + Verbo + Domini celi firmati sunt &c. Tria in + hiis uerbis sunt notari primum omnium sacre + scripture dignitas + +

+

Where a brief lemma would not typically be indexed separately + (e.g. in a glossary or commentary), but would be considered + an integral part of the incipit, the lemma may only be + distinguished typographically. + Abba secundum Papiam + Syrum nomen est + +

+
+ +
@@ -1301,7 +1617,7 @@ Ps. Athanasios Disputatio contra Arium - CPG 2250, PG 28, 440-501. + CPG 2250, PG 28.440-501. @@ -1404,24 +1720,31 @@

The physical form of the carrier should be set in the form attribute of the objectDesc element. This should refer to the form of the object in its original state, before any mutilation, - rebinding etc. The following values are recommended: - - codex: multiple gatherings of leaves, held within a binding of some kind, and used by turning the leaves. - roll: a parchment membrane, or two or more such membranes, either sewn together edge-to-edge to form a continuous surface for writing, or laid together in a pile and sewn together at the head, and used by unrolling the membranes. - sheet: a single sheet of parchment or paper, not intended to form part of a codex, either kept flat or folded (rather than rolled) for storage. + rebinding etc. The following values are recommended: + codex: multiple gatherings of leaves, held + within a binding of some kind, and used by turning the + leaves. + roll: a parchment membrane, or two or more such + membranes, either sewn together edge-to-edge to form a + continuous surface for writing, or laid together in a pile + and sewn together at the head, and used by unrolling the + membranes. + sheet: a single sheet of parchment or paper, + not intended to form part of a codex, either kept flat or + folded (rather than rolled) for storage. faltbuch - + other unknown - - The following may also be used: - + The following may also be used: roll-codex - booklet: a gathering of two or more bifolia, with a binding/covering, that appears to be complete in terms of its original textual content - quire: a complete gathering of two or more bifolia, without a binding/covering. + booklet: a gathering of two or more bifolia, + with a binding/covering, that appears to be complete in + terms of its original textual content + quire: a complete gathering of two or more + bifolia, without a binding/covering. - + @@ -1429,15 +1752,6 @@

-

- - - - - - - -

Support Description

The supportDesc element may contain the following @@ -1459,62 +1773,115 @@ Support

Provides a prose description of the material. For parchment, this may include comment on the quality of the parchment and - its disposition. For mixed material, - the nature of the combination should be described. Paper, with parchment bifolia for the outer and inner leaves of the quire.

-

If the disposition of hair and flesh sides of parchment is recorded, this should be done consistently using the letters H (for hair) and F (for flesh) inside a term element with attribute type of value disposition. For example HFFH indicates that hair and flesh sides face one another, with the hair side on the outside ofthe quire. Formulae such as 'HSOS' (hair side outside) should be altered in retroconversion. If the disposition of parchment varies between quires or otherwise between sections of the manuscript, it should be described in the layout element, rather than in support. + + +

If the disposition of hair and flesh sides of parchment is + recorded, this should be done consistently using the letters + H (for hair) and F (for flesh) inside a term + element with attribute type of value + disposition. If the disposition is consistent + throughout the manuscript, the formula need only refer to + each side of the first two leaves in a quire. For example, + HFFH indicates that the hair side is on the outside of the + quire, with flesh sides facing flesh sides and hair sides + facing hair sides in the rest of the quire (and vice versa). + By contrast, FHFH indicates that the flesh side is on the + outside of the quire, with hair sides facing flesh sides and + flesh sides facing hair sides in the rest of the quire (and + vice versa). For irregularly arranged quires, we recommend + the provision of a full formula. If the disposition varies + between portions of a composite manuscript, use + msPart to provide separate formulae. Formulae + such as 'HSOS' (hair side outside) should be altered in + retroconversion. If the disposition of parchment varies + between quires or otherwise between sections of the + manuscript, it should be described in the layout + element, rather than in support. - Parchment (FHHF) - Parchment (HFHF) + Parchment (FHHF) + Parchment (HFHF) -

-

If different materials are used (paper and parchment, different kinds of parchment, or different paper stocks, for example), - these may be described in separate material elements.

+

Note that this convention regarding H and F differs from the + usage attributed to Julian Brown, in which our HFFH would be + rendered HHHH, the H in the latter case describing the recto + of each leaf in the first half of the quire. If + retroconverting, ensure that you have understood the + original intention of the cataloguer.

+

If different materials are used (paper and parchment, + different kinds of parchment, or different paper stocks, for + example), these may be described in separate + material elements.

+ -
Description of paper

The level of detail in which paper is described will vary: in retroconversion, according to the detail of existing descriptions; in cataloguing afresh, according to the resources available

-

The paper should be described inside the support element. - If there are multiple paper stocks, each should be described in its own material element.

+

The paper should be described inside the support + element. If there are multiple paper stocks, each should + be described in its own material element.

The folding of the paper should be recorded using a measure element with the type - attribute (value: folding)

- -

The distance between chainlines should be recorded using + attribute (value: folding) whose values will + be folio, quarto, etc.

+

The original size of the sheet may be given using + dimensions with attribute type + of value paperSheet

+

The number of chainlines per leaf should be recorded + using a num element with type of + value chainlinesLeaf.

+

The distance between chainlines may be recorded using dimensions with type of chainLines, containing a width element with quantity.

-

The number of laidlines per 20mm. should be recorded + +

Watermarks

Describe each watermark in the watermark element.

-

The motif should be encoded using the term - element with attribute type of value - watermarkMotif and attribute - key with the relevant value from the - IPH standard.

-

Use locusGrp and locus to indicate - the bifolia on which the watermark is found.

-

The dimensions of the watermark should be given in a +

The key term for the motif should be encoded using + the term element with attribute + type of value watermarkMotif + and attribute key with the relevant value + from the IPH standard. Additional descriptive terms + may be placed inside a note element with + type of + watermarkVariation

+

The position of the watermark should be recorded in a + note element with type of + watermarkPosition

+ + +

The dimensions of the watermark may be given in a dimensions element with type of watermark.

-

References to printed repertories should be given in - the format specified above at Repertories.

-

Countermarks should be described using the countermark element. Note that this customization is not currently part of the TEI P5 standard.

+

References to printed repertories may be given in the + format specified above at Repertories. References to + online repertories may be given using the + ref element.

+

Countermarks should be described using the + countermark element. Note that this + customization is not currently part of the TEI P5 + standard.

+
@@ -1525,6 +1892,68 @@ Monts/Dreiberg + + + + Fols. 1-48, + paper, folded in quarto; 8 chainlines per leaf. + Watermark: Hand, surmounted by + a fleuron, on a + chainline. + + + + + + + 1-48, paper, + folded in quarto, chancery; original size of + the sheet + 315 + 425 + Chainlines: 8 chainlines per leaf, + 23 chainlines + per sheet. 19 mm. between + chainlines. Watermark: Hand, surmounted by a + fleuron, on + a chainline (Briquet 10713) + + 49-72, paper, + folded in folio, chancery; original size of + the sheet + 290 + 420 + . Chainlines: 6 chainlines per leaf, + 12 chainlines + per sheet. 33 mm. between + chainlines. Watermark: Bird, with a cross surmounted + with trefoils, between chainlines + (Briquet 12170) + 41 + 19 + + + + +

@@ -1541,14 +1970,15 @@ the number of leaves, using num measurements of the leaves, using dimensions - Use seg and type to separate + + seg and type may be used to separate these sections within extent, as shown below.

If the present state of the item is different from its original state, record this information within objectType, using the following terms: roll-codex = a codex in which formerly joined - membranes have been separated and rebound to resemble a - codex, perhaps in concertina form + membranes have been separated and rebound to + resemble a codex, perhaps in concertina form fragment = one or more remnants from a manuscript, whose survival in a form different to their original state has been accidental or an unintended @@ -1624,20 +2054,25 @@ as type=endleaf Arabic numerals to refer to leaves that are the ‘core’ of the volume, encoded as: - type=leaf + type=leaf. (If the volume is + paginated, use + type=page.) for rolls: Arabic numerals to refer to the number of membranes, encoded as: type=membrane

-

The terms ‘medieval’ and ‘post-medieval’ have been avoided in order that it might be possible to apply the same vocabulary and encoding practice to the task of cataloguing early modern manuscripts.

+

The terms ‘medieval’ and ‘post-medieval’ have been + avoided in order that it might be possible to apply the + same vocabulary and encoding practice to the task of + cataloguing early modern manuscripts.

[...] - ii + - 1 + 320 + ii + ii + 1 + 320 + ii @@ -1650,8 +2085,8 @@ distinguished), but any rear endleaves are included in with the main block. In such cases mark up as follows: - ii + 73 + ii + 73

@@ -1695,11 +2130,10 @@ 10mm between the leaves), use min and max: - - - 176 - 125 - + + 176 + 125 + 290-315 160-180 @@ -1822,9 +2256,9 @@ xmlns="http://www.tei-c.org/ns/Examples"> - iv + - 288 + ii + iv + + 288 + ii @@ -1862,42 +2296,51 @@
Foliation -

The foliation element is used to provide information about the systems used to - number the folios or pages in the manuscript. It should record where and in what medium the - numbers are written, and when this was done, and the sequence of those numbers. Where - multiple systems have been used these can be referred to elsewhere if xml:id - attributes are used. For example:

+

The foliation element is used to provide information + about the systems used to number the folios or pages in the + manuscript. It should record where and in what medium the + numbers are written, and when this was done, and the sequence of + those numbers. Where multiple systems have been used these can + be referred to elsewhere if xml:id attributes are + used. For example:

-

Original foliation in red Arab numerals in the outer margin of each recto

+

Original foliation in red Arab numerals in the outer + margin of each recto

 -

Additional pagination in pencil in ff. 1b-67a

+

Additional pagination in pencil in ff. 1b-67a

 -

The dating attributes notBefore, notAfter and (less probably) - when may be used if desired to (note: this is a customization and not - currently part of the TEI P5 standard). - Fifteenth-century foliation in roman +

The dating attributes notBefore, notAfter + and (less probably) when may be used if desired to + (note: this is a customization and not currently part of the TEI + P5 standard). + Fifteenth-century foliation in roman numerals.

-

The fw element can be used to describe running heads. For example:

+

The fw element can be used to describe running heads. + For example:

- Has pagination in Tibetan + Has pagination + in Tibetan ཁི

+
Collation

The collation formula should be given inside the formula element.

-

The mainStructures attribute (a customization not currently part of the TEI P5 standard) - may be used to record the +

The mainStructures attribute (a customization not + currently part of the TEI P5 standard) may be used to record the most frequently occuring quire structure(s). The value of the attribute should be the number of leaves in the most frequently-occuring structure(s). A single value indicates that @@ -1914,33 +2357,50 @@ XVII(13)

-

The formula element should be used for brief collation formulae. For more detailed formulae, use the list element with attribute type of value collationFormula. - - - +

The formula element should be used for brief collation + formulae. For more detailed formulae, use the list + element with attribute type of value + collationFormula. + 2 modern paper endleaves 1 medieval endleaf - Quire 16 (fols 1-6) - Quire 28 (fols 7-14) - Quire 310 (fols 15-24) - Quire 412 (fols 25-36) - 2 modern paper endleaves + Quire 16 (fols + 1-6) + Quire 28 (fols + 7-14) + Quire 310 (fols + 15-24) + Quire 412 (fols + 25-36) + 2 modern paper endleaves - - - - - + + +

Record quire or leaf signatures in the signatures - element. Use the attribute type to distinguish leaf and quire signatures. (NB this is a customization and not currently part of the TEI standard.) - - leaf: the description refers to leaf or bifolium signatures (usually located in the lower right-hand corner of the recto side of the leaves in the first half of a quire, usually in alphanumerical sequence). - quire: the descripion refers to quire signatures or numbers, usually on the verso of the last leaf of the quire, or sometimes the recto of the first leaf, which assign a sequence of numbers, letters or a combination thereof to the sequence of quires. - + element. Use the attribute type to distinguish leaf + and quire signatures. (NB this is a customization and not + currently part of the TEI standard.) + leaf: the description refers to leaf or + bifolium signatures (usually located in the lower + right-hand corner of the recto side of the leaves in the + first half of a quire, usually in alphanumerical + sequence). + quire: the descripion refers to quire + signatures or numbers, usually on the verso of the last + leaf of the quire, or sometimes the recto of the first + leaf, which assign a sequence of numbers, letters or a + combination thereof to the sequence of quires. + - Bifolium signatures, a-k, accompanied by Roman numerals, on Quires 1-10; none thereafter. Quires numbered 1-12 in a sixteenth-century hand. + Bifolium signatures, a-k, + accompanied by Roman numerals, on Quires 1-10; none + thereafter. + Quires numbered 1-12 in a + sixteenth-century hand.

Record the catchwords in the catchwords element.

@@ -1992,16 +2452,28 @@ ruled space (but see also under Extent); number of columns and number of written and/or ruled lines; how and according to what pattern ruling was executed; whether the writing is ‘above’ or - ‘below’ top line; and evidence for pricking of the page. This section comprises one or more layout elements inside the layoutDesc element.

-

If desired, the seg element may be used to divide the content of a layout element, using attribute type to label the sections, suggested values ruling, pricking.

+ ‘below’ top line; and evidence for pricking of the page. This + section comprises one or more layout elements inside the + layoutDesc element.

+

If desired, the seg element may be used to divide the + content of a layout element, using attribute + type to label the sections, suggested values + ruling, pricking.

Give the number of columns and ruled lines in the layout element using the columns and ruledLines or - writtenLines attribute. If the number of written or - ruled lines varies give the minimum and maximum values with - whitespace in-between. Give the height and width of the writing area - in mm (with 5 mm precision) in the dimensions element - (type attribute with value written, - preceding this with the explanatory text 'written space'). writtenLines attribute. If the number of columns + and/or written or ruled lines varies give the minimum and maximum + values with whitespace in-between.

+

In retroconversion: if a varying number of lines and/or columns is + given, but a typical number is specified, encode the typical number + in the attributes. + 1-10 cols. (typically 2) + +

+

Give the height and width of the writing area in mm (with 5 mm + precision) in the dimensions element (type + attribute with value written, preceding this with the + explanatory text 'written space'). 30 long lines; written space @@ -2010,11 +2482,15 @@ - 28 lines ruled in pale brown ink, - with single vertical bounding lines, extending the full height of the page, - ruled on the flesh side of the leaves with an instrument which produced a - scored line, but also often left a brown 'crayon' trace. PRICKINGS are often visible in the - upper and lower margins, and in the outer margin c.7 mm. below the bottom ruled + 28 lines ruled in pale + brown ink, with single vertical bounding lines, + extending the full height of the page, ruled on the + flesh side of the leaves with an instrument which + produced a scored line, but also often left a brown + 'crayon' trace. PRICKINGS are often visible + in the upper and lower margins, and in the outer + margin c.7 mm. below the bottom ruled line.

@@ -2037,7 +2513,8 @@ target="http://www.palaeographia.org/muzerelle/index.htm" >http://www.palaeographia.org/muzerelle/index.htm]. In the latter case the formula should be enclosed in a formula - element with attribute notation of value Muzerelle

+ element with attribute notation of value + Muzerelle

@@ -2053,12 +2530,21 @@ twice as many lines per page. - - 25 long lines. Pricked in the outer margins. Ruled in leadpoint; ruling often very faint, with double vertical bounding lines extending the full height of the page, and the first, third, twenty-third and twenty-fifth horizontal lines extending the full width of the page (Muzerelle, Mastara, formula 2-2/0/101-101/J). Written above top line. Written space - c. 115-125 - 75-85 - - + 25 long lines. Pricked in the outer margins. Ruled in leadpoint; + ruling often very faint, with double vertical bounding lines + extending the full height of the page, and the first, third, + twenty-third and twenty-fifth horizontal lines extending the + full width of the page (Muzerelle, Mastara, formula 2-2/0/101-101/J). Written above top line. + Written space + c. 115-125 + 75-85 + +

If the layout varies between different sections of the manuscript, @@ -2070,15 +2556,17 @@

Description of Hands -

Each distinct hand in the codicological unit should be described in a - separate handNote element in the handDesc element. - The handDesc element itself has an attribute - hands which can be used to record the number of hands - identified. This is optional but recommended. The value of the attribute should be the number - of hands involved in the original production of the manuscripts and should not include later additions or annotations.

- +

Each distinct hand and/or script in the codicological unit should be + described in a separate handNote element in the + handDesc element. The handDesc element itself + has an attribute hands which can be used to record the + number of hands identified. This is optional but recommended. The + value of the attribute should be the number of hands involved in the + original production of the manuscripts and should not include later + additions or annotations.

+ - +

The handNote element may have an xml:id attribute with the values hand-1, hand-2 etc, numbered in the order of appearance in the manuscript. If the same @@ -2116,14 +2604,18 @@ continental variants of the script) minuscule (other forms of minuscule: Beneventan, Luxeuil, etc.) - protogothic + protogothic (‘praegothica’) textualisNorthern textualisSouthern semitextualis - cursivaAntiquior - cursiva - hybrida - gothicoAntiqua + cursivaAntiquior (‘anglicana’, ‘anglicana formata‘, + etc.) + cursiva (‘cancelleresca’, ‘bastarda’, ‘lettre + batarde’, ‘secretary’) + hybrida (‘semihybrida’, ‘loopless bastarda’, + ‘fractura’, ‘mercantesca’) + gothicoAntiqua (‘fere-humanistica’, + ‘gothico-humanistica’) humanisticaTextualis humanisticaSemitextualis humanisticaCursiva @@ -2159,18 +2651,24 @@ scribe. - +

-

Punctuation should be described in the handNote element. Use the term element with attribute type of value punctuation to mark up particular types of punctuation, if desired. - - Written in gothic textura quadrata. Punctuation by point and double point. - +

Punctuation should be described in the handNote element. Use + the term element with attribute type of value + punctuation to mark up particular types of + punctuation, if desired. + Written in gothic textura + quadrata. Punctuation by point and double + point. +

@@ -2190,7 +2688,11 @@
Description of the Decoration -

The decoDesc element contains a description of the decoration in the manuscript or codicological unit, together with other ‘decorative’ aspects of the presentation of the text such as rubrication, It can only contain the elements p, summary, and decoNote.

+

The decoDesc element contains a description of the + decoration in the manuscript or codicological unit, together with + other ‘decorative’ aspects of the presentation of the text such as + rubrication, It can only contain the elements p, + summary, and decoNote.

Within the tag decoDesc, use decoNote to provide a hierarchical breakdown of the decoration in the manuscript, in the order given in the following table, with the appropriate values of @@ -2230,11 +2732,14 @@ carpetPage - Historiated initials(i.e., containing an identifiable narrative scene) (Brown: historiated initial) + Historiated initials (i.e., containing an identifiable + narrative scene) (Brown: historiated initial) histInit - decorated initials (Brown: decorated initial, anthropomorphic initial, zoomorphoric initial, gymnastic initial, inhabited initial). + decorated initials (Brown: decorated initial, + anthropomorphic initial, zoomorphoric initial, gymnastic + initial, inhabited initial). decInit @@ -2242,9 +2747,18 @@ colInit - initials with penwork flourishing (Reallexikon zur Deutschen Kunstgeschichte: fleuronné) (Brown: pen-flourished initial, littera florissa). Also use for so-called arabesque initials. + initials with penwork flourishing (Reallexikon zur + Deutschen Kunstgeschichte: fleuronné) (Brown: pen-flourished initial, + littera florissa). Also use for so-called arabesque + initials. flourInit + + chrysography (i.e. writing in gold) + chrysography + plain initials plainInit @@ -2270,6 +2784,10 @@ specifies this) none + + rubrication + rubrication +

In Fihrist, the following values for the type attribute @@ -2296,8 +2814,8 @@ vignette

Artists should be identified using the persName element with - role = art and key referring - to the persons authority file.

+ role = art and key referring to + the persons authority file.

@@ -2308,55 +2826,77 @@ terminating in gold disks and ivy leaves.

The second miniature is signed ‘Willelmus de monte acuto me fecit’ by the artist William Montague - (fl. 1390s?) (William Montague (fl. + 1390s?) (37r).

-

To provide a more structured entry in the case of detailed descriptions of decoration, use the list, head, and item elements.

+

To provide a more structured entry in the case of detailed + descriptions of decoration, use the list, head, + and item elements.

- - - - - Two five-line historiated initials: - (fol. 19v) Obsecro te. Virgin and Child enthroned; the - Virgin holding a red fruit(?). - (fol. 23r) O intemerata. Pietà. - - - Four- or three-line initials in blue and red, enclosing foliage, - on a gold ground, at the start of each text with a large miniature; two-line - initals in gold, on a blue and red ground with white tracery, to psalms, - capitula, lessons, etc. and the KL monograms in the calendar; similar one-line - initials to verses and other minor divisions; similar line-fillers - throughout. - + + + + + Two five-line historiated initials: + (fol. 19v) + Obsecro te. Virgin and Child enthroned; the Virgin + holding a red fruit(?). + + (fol. 23r) O + intemerata. Pietà. + + + Four- or three-line initials in blue + and red, enclosing foliage, on a gold ground, at the start + of each text with a large miniature; two-line initals in + gold, on a blue and red ground with white tracery, to + psalms, capitula, lessons, etc. and the KL monograms in the + calendar; similar one-line initials to verses and other + minor divisions; similar line-fillers throughout. +

-

The subjects of miniatures can be classified using the term element with attribute type of value iconography. The ref attribute can be used to point to a thesaurus, such as Iconclass. - - - One six-line historiated initial: - (fol. 49r) Hours of the Virgin, Lauds. Visitation. - -

-

Aspects of the manuscript relating to the presentation of the text - notably rubrication - should also be included in the decoDesc element (rather than in the layout element, using decoNote with attribute type of value rubrication.

+

The subjects of miniatures can be classified using the term + element with attribute type of value + iconography. The ref attribute can be used + to point to a thesaurus, such as Iconclass. + + + One six-line historiated initial: + (fol. 49r) + Hours of the Virgin, Lauds. Visitation. + +

+

Aspects of the manuscript relating to the presentation of the text - + notably rubrication - should also be included in the + decoDesc element (rather than in the layout + element, using decoNote with attribute type of + value rubrication.

Additions -

Marginalia, notes, and other additions of interest should usually be recorded - in the additions element, inside one or more p - elements. Use locus to specify the location of these - features.

-

If the language of the marginalia is significant (e.g., Latin marginalia in a Greek manuscript), - the marginalia will need to be recorded as an additional text using msItem in msContents.

+

Marginalia, notes, and other additions of interest should usually be + recorded in the additions element, inside one or more + p or note elements. The note element + can have the type and subtype attributes. Use + locus to specify the location of these features.

+

If the language of the marginalia is significant (e.g., Latin + marginalia in a Greek manuscript), the marginalia will need to be + recorded as an additional text using msItem in + msContents.

- Marginal and interlinear Latin glosses. + Marginal and interlinear + Latin glosses. Latin @@ -2370,36 +2910,44 @@ bindingDesc element. The standard dating attributes should be used on the binding element if information about the date of the binding is available.

-

The following order may be followed in the description: covering material and coverage (full, half, quarter; textile; limp vellum; treasure) - chemise (alum-tawed, textile) - board material (wooden boards, pasteboard) - tooling patterns (blind, gold) - spine covering and tooling, incl. labels - metalwork fittings (plates, plaques, enamels, bosses, cornerpieces, strap and pin, clasps, chain staples). - inlaid/inset plaques - labels (esp. horn-plaques) +

The following order may be followed in the description: + covering material and coverage (full, half, quarter; + textile; limp vellum; treasure) + chemise (alum-tawed, textile) + board material (wooden boards, pasteboard) + tooling patterns (blind, gold) + spine covering and tooling, + incl. labels + metalwork fittings (plates, plaques, enamels, bosses, + cornerpieces, strap and pin, clasps, chain staples). + inlaid/inset plaques + labels (esp. horn-plaques) +

Key elements of the description may be marked with the term with relevant type attribute and with attribute ref referring to the appropriate URI in the Ligatus thesaurus.

-

Give the height, width and - depth of the binding may be given in mm (with 5 mm precision) in the - dimensions element (type attribute with - value binding).

A description of decorative features on - the binding can be recorded in one or more decoNote - elements (note that this needs to be outside the p element - as a child of binding)

Use the condition element to record repairs to the binding, such as rebacking.

-

Fore-edge painting or decoration should be described inside a decoDesc element, in a decoNote element with attribute type of value foreedge.

+

Give the height, width and depth of the binding may be given in mm + (with 5 mm precision) in the dimensions element + (type attribute with value binding).

+

A description of decorative features on the binding can be recorded + in one or more decoNote elements (note that this needs to + be outside the p element as a child of + binding)

+

Use the condition element to record repairs to the binding, + such as rebacking.

+

Fore-edge painting or decoration should be described inside a + decoDesc element, in a decoNote element with + attribute type of value foreedge.

Bookmarks and other page markers should be described in a separate paragraph in the binding section, using where possible the vocabulary of the Ligatus thesaurus, and linking to that vocabulary - using the term element with attribute type of value - bookmark and relevant ref attribute. -

+ using the term element with attribute type of + value bookmark and relevant ref attribute.

- +

Light brown

-

Evidence of former bindings, or the reuse of earlier binding material in a modern binding, should be recorded in a separate binding element.

-

Note that all the above may require restructuring of an original description during retroconversion.

+

Evidence of former bindings, or the reuse of earlier binding material + in a modern binding, should be recorded in a separate + binding element.

+

Note that all the above may require restructuring of an original + description during retroconversion.

-

Sewing not visible; - tightly rebound between 19th-century pasteboards, reusing earlier panels (see below); the centre of each cover inlaid with a - 17th-century oval medallion of red leather tooled in gilt (perhaps replacing - the identifying mark of a previous owner); the spine similarly tooled, without - raised bands or title-piece (similar in design to ibid. pl. XIXa); coloured endbands; the edges of the - leaves and boards gilt. Boxed.

+

Sewing not visible; tightly rebound between + 19th-century pasteboards, reusing earlier panels + (see below); the centre of each cover inlaid with a + 17th-century oval medallion of red leather tooled in + gilt (perhaps replacing the identifying mark of a + previous owner); the spine similarly tooled, without + raised bands or title-piece (similar in design to + ibid. pl. XIXa); coloured + endbands; the edges of the leaves and boards gilt. + Boxed.

-

The binding re-uses panels of - 16th-century brown leather with gilt tooling à la - fanfare, Paris c. 1580-90, in the style associated with Clovis Eve (of - the bindings ill. in Hobson, - Les reliures à la fanfare, the boards are - closest in general design to pl. XXI b).

+

The binding re-uses panels of 16th-century brown + leather with gilt tooling à + la fanfare, Paris c. 1580-90, in the + style associated with Clovis Eve (of the bindings + ill. in Hobson, Les reliures à la + fanfare, the boards are closest in general + design to pl. XXI b).

 @@ -2545,18 +3101,40 @@ the attribute cert with value high, and the nature of the evidence may be specified with the evidence attribute.

-

In retroconversion, authoritative sources may differ regarding the date (or origin) of a manuscript. - This can also be recorded using multiple origDate elements. - (The resp attribute may be used on the element to indicate responsibility in a machine-readable way). - - 13th century, end (Hutter) or - 14th century, first quarter (Palau) - + +

In retroconversion, authoritative sources may differ regarding + the date (or origin) of a manuscript. This can also be recorded + using multiple origDate elements. (The resp + attribute may be used on the element to indicate responsibility + in a machine-readable way). + 13th century, end (Hutter) + or 14th century, first quarter + (Palau) +

For manuscripts with significant later additions, textual or decorative, use additional origDate elements with type of additions

+

+ + 13th century, first quarter; + additions, 15th + century + + + 1488 + (fols. 126-208); 1464 × 1488 (fols. 1-125v) + +

+
origPlace

The content of origPlace should where possible be @@ -2578,18 +3156,33 @@ Austria, Switzerland, but Bohemia, Dalmatia, Serbia, Flanders.

For manuscripts with significant later additions, textual or - decorative, use additional origDate elements with - type of additions

-

For manuscripts produced in more than one place, use multiple - origDate elements; for manuscripts with significant - later additions, textual or decorative, use additional - origPlace elements with type of - additions.

-

- -

+ decorative, use additional origPlace elements with + type of additions + + + French, Brittany + additions, England + + + +

+

For manuscripts produced in more than one place (or, where there + is more than one potential place of origin), use multiple + origPlace elements, with the cert + attribute if necessary. + + Italian (?) + or + French, + South (?) + +

+ +
-
Provenance @@ -2601,39 +3194,67 @@ retroconversion) is that where possible each provenance event should occur in its own provenance element, which should have relevant dating attributes (when, notBefore, - etc.) or contain date elements. People involved in the - transfer of ownership should be marked up with persName - tags, with a role attribute (a date elements with + those attributes.) As elsewhere, + from and to denote a known period, + presumed to be more or less continuous, beginning at one date and + ending at another. notBefore and notAfter + denote the terminus a quo and terminus ad quem within which the + writing is believed to have occured. when denotes a + single event (such as a dated signature or the donation of an item + to a library). People involved in the transfer of ownership should + be marked up with persName tags, with a role + attribute (a Library of Congress relator code, usually "fmo" for former owner).

-

Pressmarks and shelfmarks should be recorded in a q element with attribute type, value pressmark; see .

+

Pressmarks and shelfmarks should be recorded in a q element + with attribute type, value pressmark; see . It is not necesary to mark up + pressmarks and shelfmarks which are already recorded as manuscript + identifiers. + At the head of f. iiiv is ‘Liber domus scolarium de + Merton ex dono magistro Hamondi Haydok + incathenandus in libraria anno Domini mmoccccolxviiio’, in the same + hand as Wyght’s ex dono in MS 38. For + Hammond Haydok, see MS 16. On the front pastedown is a brief + table of contents, s. xvii, and N. 3. + 13. Art:, canc. and replaced with ‘A. 1. 10 (XXXIX)’ + in red. The College bookplate. At the head of f. i is M. + A. 2. 5, s. xvii. ‘13’ is inked on the + foredge. + +

-

- - -

+
Acquisition

The acquisition element should describe the last stage of the manuscript's history, i.e. how it was acquired by its present - owners. It SHOULD have relevant dating attributes.

- - William Wilson, F.S.A. - (-1832?), of the Minories, his sale, Christie's, 31 Jan.-1 Feb. - 1833, lot 56 on 1 Feb.; bought by Thorpe for £53. - 11s. - Purchased from Thorpe - by Douce, Feb. 1833. - Bequeathed by Douce to the Bodleian in - 1834. -

- -

- + owners. It SHOULD have relevant dating attributes. Because the + present owner, locaton etc. of the manuscript are recorded elsewhere + in the manuscript description, it is NOT necessary to encode them + using orgName or persName elements.

+ +

Note the usage of the different dating attributes in the following + example. + William Wilson, F.S.A. + (-1832?), of the Minories, his sale, Christie's, 31 Jan.-1 + Feb. 1833, lot 56 on 1 Feb.; bought by Thorpe for £53. + 11s. + Purchased from Thorpe by + Douce, Feb. 1833. + Bequeathed by Douce to the Bodleian in + 1834. +

+
@@ -2684,17 +3305,19 @@ Availability

The availability element can be used to supply information about the availability of a manuscript, using the status - attribute. Valid values for status are free, unknown, restricted, offsite, exhibition. It may also - contain information about the images or text, such as any - restrictions on their use or distribution, their copyright status, - etc.

+ attribute. Valid values for status are free, + unknown, restricted, offsite, + exhibition. It may also contain information about the + images or text, such as any restrictions on their use or + distribution, their copyright status, etc.

Custodial History

The custodialHist element can be used to describe a - manuscript's custodial history (e.g. conservation, exhibitions) either as prose tagged with p elements, or as - a series of custodial events, using the custEvent - element with attributes type, when, etc.

+ manuscript's custodial history (e.g. conservation, exhibitions) + either as prose tagged with p elements, or as a series of + custodial events, using the custEvent element with + attributes type, when, etc.

. - + the unit should be given. + @@ -2865,6 +3491,43 @@

+

The data structure of the msPart element assumes that + codicological units follow one another sequentially in the manuscript, + which (in the case of Western manuscripts) is often but not universally + true. In cases where one unit is inserted in the middle of another, the + description should be organized to deal with each part in sequential + order. + + + + Merton College MS. 13 - Part I (fols. 3-13, + 198-243) + + + + Latin + + (fols. 3-13v) + Draft sermons + + + + For items 2, 51-4 see Part II. + For items 3-50 see Part III. + + + (fols. 198-208v) + Eight sermons on Ioh. 17: 1-26, + extracted from <persName role="aut" + key="person_66806872">Augustine</persName>, <title + key="work_822">Tractatus in Iohannis + Euang., 104. 2 – 111. 6 + + + + +

+
Endleaf

Example: MS. Auct. D. 2. 14 (abbreviated)

@@ -2872,104 +3535,59 @@ - + Gospels; Italy, 7th century + - - Gospels - - 9-12th cent. marginal additions for liturgical pericopes (fols. 6v, 7, 8-30, etc.). - - - (fol. 149va) - Liturgical addition in honour of St. Chad (Lichfield ?) - - - (fol. 173v) - 11th cent. addition: [ps] Fundamenta eius in montibus [v] Diliget - dominus. Dominus vobiscum. [oratio] Domine Ihesu Christe qui introitum portarum - … said after the lustration of holy water. - - Latin - + - - - - parchment - iii + 173 + iii fols. (fol. 173 is an endleaf originally from another manuscript: see below) - - 248 - 190 - - - 210 - 157 - - - - - 2 col. of 29 lines. - - - - Uncial script. - - -

Neums (11th cent.) added to the Genealogy of Christ by - St. Luke (fol. 79)

- - - Initial. (P&A ii. 1a) - + + - - Italy - - 7th century - - - Textual relation with Cambridge, Corpus Christi College MS. 286 (Italy, 6th century, 'St Augustine's Gospels'). - In England by late 8th century (fol. 149va). - Owned by Sir Robert Cotton in 1602. - Given by him to the Library in 1603. - + - - - + - MS. Auct. D. 2. 14 - endleaf, fol. 173 + MS. Auct. D. 2. 14 - endleaf, + fol. 173 - (fol. 173r) - Booklist and list of names - N. R. Ker, Catalogue of Manuscripts Containing Anglo-Saxon (1957), p. 350 (no. 290). - Old English + (fol. 173r) + Booklist and list of + names + N. R. Ker, Catalogue of Manuscripts + Containing Anglo-Saxon (1957), p. 350 (no. + 290). + Old English - (fol. 173v) - Ad introitum porte - Latin + (fol. 173v) + Ad introitum porte + Latin - England, Bury St Edmunds (?)11th century, second half + England, Bury St Edmunds + (?)11th century, + second half - 'Bealdewuine abb.', fol. 173r, probably Baldwin, abbot of Bury St Edmunds (d. 1098). + 'Bealdewuine abb.', fol. 173r, probably + Baldwin, abbot of Bury St Edmunds (d. + 1098). - -

@@ -3022,12 +3640,11 @@

Holkham binding of black leather, with Coke family ostrich crest in gilt in the centre of the upper cover; Date: early nineteenth century. - Rebound by John Jones of - Liverpool (worked for Holkham - 1816-1823). SPINE: lettered in gilt: SYMEONIS| - METAPHRASTAE|VITAE| S.S. MARTYRUM| G.R.| M.S.| - SAEC. XII|–| SEP.|

+ Rebound by John Jones of Liverpool (worked for + Holkham 1816-1823). SPINE: lettered in gilt: + SYMEONIS| METAPHRASTAE|VITAE| S.S. MARTYRUM| G.R.| + M.S.| SAEC. XII|–| SEP.|

@@ -3661,15 +4278,20 @@ Specifies the typical quire structure(s) of the book, according to English notation (i.e. the number of folios in the - original quire), e.g. 8, 6 8. - Note: This is a customization which is not currently part of the TEI P5 standard. + original quire), e.g. 8, 6 8. Note: This + is a customization which is not currently part of the TEI P5 + standard. - + + + + + @@ -3677,8 +4299,8 @@ - - + + @@ -3691,7 +4313,8 @@ Specifies the whether the writing is above top line, below top - line, or mixed. Note: This is a customization which is not currently part of the TEI P5 standard. + line, or mixed. Note: This is a customization which is not + currently part of the TEI P5 standard. The writing is above top line. @@ -3708,7 +4331,8 @@ Specifies the medium used to carry out the - ruling. Note: This is a customization which is not currently part of the TEI P5 standard. + ruling. Note: This is a customization which is not currently + part of the TEI P5 standard. @@ -3727,6 +4351,10 @@ The ruling is carried out using ‘crayon’. + + The ruling is carried out using several + methods. + The ruling is carried out using a board. @@ -3735,12 +4363,15 @@ - + - Specifies the availability of a manuscript. This attribute should not be used to specify the availability of manuscript metadata: use the licence element for that purpose. + Specifies the availability of a manuscript. This attribute + should not be used to specify the availability of manuscript + metadata: use the licence element for that + purpose. @@ -3750,13 +4381,17 @@ - Access to the item is restricted for conservation or other reasons. + Access to the item is restricted for conservation or + other reasons. - The item is on exhibition at the owning library or another institution, and is likely to be temporarily unavailable. + The item is on exhibition at the owning library or + another institution, and is likely to be temporarily + unavailable. - The item is stored offsite, and will take at least twenty-four hours to produce. + The item is stored offsite, and will take at least + twenty-four hours to produce. Availability of the item is unknown. @@ -3765,10 +4400,12 @@ - + - - Contains a description of a countermark. Note: This is a customization which is not currently part of the TEI P5 standard. + + Contains a description of a countermark. Note: This is a customization + which is not currently part of the TEI P5 standard. @@ -3783,12 +4420,12 @@ - - - + + + - + The object is composed of parchment @@ -3797,19 +4434,59 @@ The object is composed of paper - The object is composed of a combination of paper and parchment. The nature of the combination should be specified in the support element. + The object is composed of a combination of paper and + parchment. The nature of the combination should be + specified in the support element. - The object is composed of another material (e.g. wood). + The object is composed of another material (e.g. + wood). - The material of which is object is composed is not known. + The material of which is object is composed is not + known. - + + + + + + + + Multiple gatherings of leaves, held within a binding + of some kind, and used by turning the leaves + + + a parchment membrane, or two or more such membranes, + either sewn together edge-to-edge to form a continuous + surface for writing, or laid together in a pile and sewn + together at the head, and used by unrolling the + membranes + + + a single sheet of parchment or paper, not intended to + form part of a codex, either kept flat or folded (rather + than rolled) for storage + + + a codex whose leaves are opened by unfolding rather + than turning; an ‘almanac’ + + + Some other unspecified format + + + The format of the object is not known + + + + + + @@ -3822,21 +4499,16 @@ - - The root TEI element must have an @xml:id beginning with - "manuscript_" then a number (which must be unique across the - entire collection). - + The root TEI element must have an @xml:id + beginning with "manuscript_" then a number (which must be + unique across the entire collection). - - - The root TEI element must have an @xml:id beginning with "volume_" - then a number (which must be unique across the entire collection). - + + The root TEI element must have an @xml:id beginning with + "volume_" then a number (which must be unique across the + entire collection). @@ -3938,34 +4610,30 @@ - - - A manuscript should have one or more languages recorded in a textLang element. - For manuscripts with no linguistic content use code 'zxx'. If the language is - undetermined use the code 'und'. - + + A + manuscript should have one or more languages recorded in a + textLang element. For manuscripts with no linguistic content + use code 'zxx'. If the language is undetermined use the code + 'und'. - - - The predominant language must be recorded in using a code in a mainLang attribute - (and an otherLang attribute if there are other languages) and described as text - within the textLang element. - + + The predominant language must be recorded in + using a code in a mainLang attribute (and an otherLang + attribute if there are other languages) and described as + text within the textLang element. - - Codes in attributes must conform to BCP 47 - (https://tools.ietf.org/html/bcp47), starting with an ISO 639 code for the language, - then optionally further codes for the script (ISO 15924), region, transliteration, etc. + Codes in + attributes must conform to BCP 47 + (https://tools.ietf.org/html/bcp47), starting with an ISO + 639 code for the language, then optionally further codes for + the script (ISO 15924), region, transliteration, etc. @@ -3976,14 +4644,10 @@ - - - The writing support of a manuscript should be specified in the - material attribute on the element supportDesc. - + + The writing support of + a manuscript should be specified in the material attribute + on the element supportDesc. @@ -3994,14 +4658,12 @@ - - - The binding element should have dating attributes (when or notBefore/notAfter) - or a contemporary attribute (with the value 'true'). - + + The binding element should have dating + attributes (when or notBefore/notAfter) or a contemporary + attribute (with the value 'true'). @@ -4011,30 +4673,44 @@ - - - The origDate element must have two or more attributes - calendar and at least one of - when, notBefore, notAfter, from and/or to - and must contain some text describing the date. - + + The origDate element must have two or more + attributes - calendar and at least one of when, notBefore, + notAfter, from and/or to - and must contain some text + describing the date. - + - - - The unit of measurement must be specified in the unit attribute on the dimensions element - + + The unit of measurement + must be specified in the unit attribute on the dimensions + element + + + + + + + + + + + + + + + + The TEI element must have an xml:id matching + the pattern 'manuscript_\d+'. From 54d7ef6269517ada576897d43cf6ca6cf1e3a48a Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Thu, 14 Mar 2019 15:38:59 +0000 Subject: [PATCH 05/10] Documentation: Fix multiple introductions and missing section IDs --- msdesc.odd | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index 9306fe9..45d75c4 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -45,8 +45,8 @@

-
- Introduction +
+ Acknowledgements

These draft guidelines are currently based on two main sources - the encoding guidelines for the Fihrist project [origDate tags.

-
+
origDate

Dating attributes from the set notBefore, notAfter, from, to and From 9744d451009295b12fabcbc10f42cf9cab6193c0 Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Thu, 14 Mar 2019 18:27:30 +0000 Subject: [PATCH 06/10] Material attribute in supportDesc Changes to make it require the value to be a single one of the defined list. Updating docs to match. Also deleting old schematron rule that is no longer needed. --- msdesc.odd | 44 +++++++++++++++++++++----------------------- 1 file changed, 21 insertions(+), 23 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index 45d75c4..a41bd57 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -1764,11 +1764,12 @@

The support material for the codicological unit(s) should be - recorded in the material attribute of - supportDesc (values: chart, - perg, mixed, papyrus, or - other). Further description of the support should - be added in the support element.

+ recorded in the material attribute of supportDesc. + Allowed values are: chart (for all kinds of paper), + perg (for parchment and vellum), papyrus, + palm (palm leaf), mixed, unknown, + or other. Further description of the support should be added + in the support element.

Support

Provides a prose description of the material. For parchment, @@ -4425,13 +4426,24 @@ - - + + The material composing the majority of the support + + + + - The object is composed of parchment + The object is composed of parchment or vellum - The object is composed of paper + The object is composed of any kind of paper. Give more details, + if any, in a child support element. + + + The object is composed of papyrus. + + + The object is composed of palm leaves. The object is composed of a combination of paper and @@ -4640,20 +4652,6 @@ - - - - - - The writing support of - a manuscript should be specified in the material attribute - on the element supportDesc. - - - - - - From 04dd1330df838726b59e792601680e7f089a51de Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Fri, 15 Mar 2019 08:33:38 +0000 Subject: [PATCH 07/10] Deleting duplicate Schematron rule Also was testing the wrong attribute --- msdesc.odd | 36 ++++++++++++++---------------------- 1 file changed, 14 insertions(+), 22 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index a41bd57..6da1ba7 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -1768,8 +1768,19 @@ Allowed values are: chart (for all kinds of paper), perg (for parchment and vellum), papyrus, palm (palm leaf), mixed, unknown, - or other. Further description of the support should be added - in the support element.

+ or other. The name of the material for display purposes, + and further description of the support, should be added + in the support element. For example:

+ + + Paper + + + + + Exceptionally thick, stiff parchment + +
Support

Provides a prose description of the material. For parchment, @@ -4505,7 +4516,7 @@ - + @@ -4701,27 +4712,8 @@ - - - - - - The TEI element must have an xml:id matching - the pattern 'manuscript_\d+'. - - - - - - - - - -

- From 0102c8ef1ea29e67a461eef347255f7cad56b45c Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Fri, 12 Apr 2019 16:51:45 +0100 Subject: [PATCH 08/10] Resolve conflicts between updates and master branch --- msdesc.odd | 62 ++++++++++++++++++++++++++++++++++++++++++------------ 1 file changed, 49 insertions(+), 13 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index 6da1ba7..8b2b2ad 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -4173,6 +4173,7 @@ collection --> + @@ -4667,12 +4668,14 @@ - - The binding element should have dating - attributes (when or notBefore/notAfter) or a contemporary - attribute (with the value 'true'). + + + The binding element should have dating attributes (when or notBefore/notAfter) + or a contemporary attribute (with the value 'true'). + @@ -4682,18 +4685,51 @@ - - The origDate element must have two or more - attributes - calendar and at least one of when, notBefore, - notAfter, from and/or to - and must contain some text - describing the date. + + + The origDate element must have two or more attributes - calendar and at least one of + when, notBefore, notAfter, from and/or to - and must contain some text describing the date. + + + + + + + + Any values can be used in rend attributes, but the web site currently only supports combinations of: + bold, italic, roman, smallcaps, superscript, subscript, underline, overline, and strikethrough. + + + The web site currently only supports rend attributes for hi elements. Using it on + elements is valid but will be ignored. + + + + + The web site currently ignores rendition and style attributes. + + + + + + From 7f29f9845428c3b2b9abb37ff22ca657e24a749b Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Fri, 12 Apr 2019 17:37:53 +0100 Subject: [PATCH 09/10] Move and reformat rule about manuscript IDs Moving so it will appear under the relevant element in the documentation, restructuring for more clarity, but the only change people will see when validating is a slight rewording of the message. --- msdesc.odd | 32 ++++++++++++++++++-------------- 1 file changed, 18 insertions(+), 14 deletions(-) diff --git a/msdesc.odd b/msdesc.odd index 8b2b2ad..f254180 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -4517,22 +4517,26 @@ - - - + + + - The root TEI element must have an @xml:id - beginning with "manuscript_" then a number (which must be - unique across the entire collection). - - - The root TEI element must have an @xml:id beginning with - "volume_" then a number (which must be unique across the - entire collection). + context="tei:TEI"> + + The root TEI element must have an @xml:id beginning with + "manuscript_" then a number (which must also be unique + across the entire catalogue). + + + The root TEI element must have an @xml:id beginning with + "volume_" then a number (which must also be unique + across the entire catalogue). + From dddf8c2977985edd0c3d18a88661aa70147d487f Mon Sep 17 00:00:00 2001 From: Andrew Morrison Date: Fri, 12 Apr 2019 17:52:17 +0100 Subject: [PATCH 10/10] List of values for material attribute are recommendation, not mandatory --- msdesc.odd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/msdesc.odd b/msdesc.odd index f254180..86abcc0 100644 --- a/msdesc.odd +++ b/msdesc.odd @@ -4443,7 +4443,7 @@ - + The object is composed of parchment or vellum