For questions, please contact us at info.salamanca(at)adwmainz.de.
Andreas Wagner, Cindy Rico Carmona, Marie-Astrid Hugel - Last Updated: December 2024
The documents published on this website have been encoded within the scope of the project "The School of Salamanca. A Digital Collection of Sources and a Dictionary of its Juridical-Political Language" of the Akademie der Wissenschaften und der Literatur | Mainz. Besides creating a dictionary, the project aims at a freely available and easily accessible collection of important texts from the discoursive context of the so called "School of Salamanca", which are being digitized for this purpose (usually in the form of their initial edition). A critical revision, or a recourse to manuscript templates, for instance, has been refrained from. The total corpus of works can be found at here.
The digital edition is organized into two main sections based on content. The first section includes fully edited works, selected for their significance as the most important contributions of the School of Salamanca. The second section contains reference works, frequently cited by the authors.
In terms of technical treatment, fully edited works undergo thorough technical revisions and scientific corrections to ensure their suitability for online publication. These works are divided into two groups:
Group Awas selected as a representative corpus with texts of varying scope, text types, and languages. It consists of works that are both manually and technically corrected, serving as models (training corpus) from which linguistic resources are extracted for the development of automated correction tools.Group Bwhich includes the remaining works to be fully edited, in which only automated correction tools are applied.
In contrast, reference works receive basic technical editing and are published primarily as resources to support the research community. They are not subjected to the same level of thorough revision as the fully edited works, but they provide essential references and context for primary research.
The following table illustrates the plan of edition of these groups.
* Tools, constantly being improved and derived from Group A
For validation and well-formedness control, schematrons and a schema (SvSal TEI) are employed, specifically designed to meet the research demands of the project.
At this, the edition of the sources is not to be considered a strictly sequential process of text preparation and enrichment towards a single and "ultimately" published edition text, but rather makes use of the possibilities of the digital medium in that already published works are further enrichable (possibly involving the larger scholarly community). The multidimensionality of the research demands as well as the step-by-step (re-)editability of the texts pose, at the same time, challenges to the digital edition when it comes to editing and publication of the texts, which are to be encountered, for instance, documented in the <teiHeader> under <revisionDesc>.
The edition guidelines at hand (henceforth "the guidelines") are to be understood
as XML encoding guidelines with the purpose of:
The comprehensive SalTEI tagset cannot be covered in its completeness at this point; for this purpose, please refer to the technical reference documents linked below. The guidelines rather aim at describing the applied standards of text encoding, such as the handling of special characters, abbreviations, foot notes or marginal notes, damages in original samples, citations, annotations of person and place names, etc. They explain how special characters are represented, or how references to lemmata, works, or authors are realized by means of TEI XML.
In addition to the examples mentioned in the following, exemplary use cases (in fact, all use cases) can be extracted automatically from our texts on our codesharing page. For that, we have installed the comfortable codesharing service developed by Martin Holmes for the Map of Early Modern London project.
Definitions and documentations for the edition's TEI P5 adaptation are available in the form of the following data:
Furthermore, the following data are available for download:
In the process of editing and annotation, texts generally traverse different statuses of processing,
their ordering not everywhere to be understood as sequential; for instance, a text may traverse several times the
-
a_raw The text, encoded through double keying and/or OCR, has been converted to a simple TEI file conforming to the schema specifications. -
b_cleared Uncertainty marks by the typists have been resolved through comparison with the original reference. -
c_hyph_proposed Propositions for hyphenations, corrections, and/or abbreviation expansions have been created. -
d_hyph_approved Propositions for hyphenations, corrections, and/or abbreviation expansions have been accepted by the project's scholars and have been implemented in the text. -
e_emended_unenriched Enrichment of the text (annotation of special characters, annotation of persons, places, bibliographic references, and linking to datasets of authors and of the dictionary) is in progress. -
f_enriched Enrichment of the text has been done. Four-eye examination and correction of the enrichment annotations is still pending. -
g_enriched_approved The examination and/or correction of the enrichment has been done. The text has been released officially, publicly and in a persistently quotable way and thus stands at the disposal of the scholarly community. -
h_revised Further propositions for correction and enrichment of the text, collected during a qualifying period and potentially originating from third parties within the scholarly community, have been added to the text. A four-eye examination and correction of the further annotations is still pending. -
i_revised_approved Further propositions for correction and enrichment of the text have been accepted by the project's scholars, the text has been released anew (i.e., with new persistent identifiers), although older versions are still available. -
z_final The text has been "frozen" in the form of a version not further modifiable at the end of all editing phases and for the purpose of long-term archival and/or presentation of the project results.
The revision history for a text records all changes of/within
the TEI document and is maintained within the
The parts of text relevant, transcribed and encoded within the scope of the edition comprise, firstly, the "main area" of the original text, that is, the (potentially multi-column) part of text at the center of a page that itself does not encompass other parts of text on that page. Furthermore, from the marginal area of text encompassing the aforementioned main area, marginal and foot notes are encoded, as well as page or folio numbers. However, running heads/titles, signature marks, or catchwords are not encoded. Equally, manually written elements (handwritten notes, additions, symbols, drawings, marks, etc.) occurring on print pages are not encoded or documented.
For the annotation of graphic elements, please refer to the specific section.
- Ligatures (
ß, ſt, st, fi, fl, , ij
, etc.) are silently resolved; however, the digraphsw, œ, æ
are adopted from the original text. The hereby underlying assumption is that these digraphs form an orthographic unit consisting of two letters and, accordingly, one sound, whereas ligatures can be regarded as a merely typographical phenomenon. The systematic differentiation in this case is not simple, but rather controversial; yet, in our case it only applies to these mentioned three digraphs. At any rate, both phenomena (digraphs and ligatures) are, furthermore, possibly subject to normalization or expansion (see below). -
The long, or descending, s (
ſ
) was handled depending on the origin of the double-keyed text transcriptions. How a text handles the spelling of s is documented within theteiHeader 'sencodingDesc . Furthermore, in case of a text not containing resolvedſ
, a formal algorithm for convertingſ
tos
is provided; however, the contrary case of converting froms
toſ
cannot be defined unambiguously in our case. - The utilization of blank space was adjusted, to the greatest extent, according to modern conventions, making clear the correct compounding and hyphenation of words, which is not necessarily visible in the print image of the original sample.
-
Citations/quotations are represented by means of
q orquote elements, respectively (cf. the TEI Guidelines), potentially existing quotation signs from the original text are thereby omitted. - Identified transcription errors (introduced during the double keying phase of text encoding and not existent in the original source) are silently corrected in Group A.
Non-Standard characters are encoded as Unicode characters as far as possible.
Characters of the so called "Codepage Latin-1", meaning the first two Unicode blocks
[Basic Latin] and
[Latin-1 Supplement] – hence, characters with a codepoint below
ä
or é
).
Further Unicode characters are encoded either as precomposed characters as well, or as
numeric character references (NCR) (for instance: ẽ stands for ẽ
). In both
cases, potentially, character combinations using combining characters such as accents, tildes, or apostrophes, may be
utilized (see, for instance, ẽ as ẽ). Generally, the edition's XML data are declared as
<?xml encoding="UTF-8"?> (see
TEI P5 Guidelines, vi.2).
If non-standard characters are not unambiguously definable as Unicode characters and
are also not expressible as a combination of such characters, the recommendations
of the Medieval Unicode Font Initiative (in version 4.0) apply, if possible:
MUFI character recommendation v. 4.0
.
At least all non-standard characters not available in the Codepage Latin-1
(see above)
are declared, with recourse to the
TEI gaiji
module,
within the Codepage Latin-1
are declared
if they are to be normalized for the reading view, such as ã
). The MUFI
recommendations, etc.) are
obtained, primarily, from the ENRICH gBank;
then, the "prerendered" Unicode characters (if available) or NCR entities stated in the gBank
(or in the respective MUFI specification) are added to the declaration as
Expansions of words that are abbreviated by means of non-standard characters
are not resolved via the
Examples of non-standard character declarations:
An overview of the complete set of non-standard characters encountered thus far within the scope of the digital edition, and of their respective encodings, is available in the Encoding Table of (Non-Standard) Characters.
The XML declarations of all these characters and their encodings are to
be found in the following TEI file:
specialchars.xml
(The
With regards to the encoding of non-standard characters, abbreviations, and ligatures please also refer to the section above, and for the ("historic") practices of text encodings within the scope of this project during the transcription phase, see also the general transcription guidelines and the specific transcription guidelines (available in German only).
Page or folio numbers are encoded through the [...]
" within the value of
In case a work (or part of it) is paginated folio-wise, with only the front side ("recto") of a sheet being numbered, the (existing) folio number of the front side is complemented through an "r" suffix, whereas the (non-existing) back page ("verso") number is added by adopting the front page number and adding a "v" suffix:
With sections before the main part of the text (see also
General Structure of a Work/Volume) that do not have any
numeration, regularly incrementing pagination (regardless of the
type of numeration of the main part) by means of Roman numerals is added; with
unnumbered parts after the main part, the (type of) numeration
of the main part is carried on in the way explained above (for example,
marked through square brackets).
If existent in the original source, column numbers
are encoded – in a way analogous to
page numbers
– through the
Argumentative shifts in (the content of) the text, usually signified on a
typographic level by means of
marginal numbers, or *
or †
symbols, are encoded by means of
Abbreviations and printing errors are encoded and resolved within
In case of a page, column, or line break (see also
Page, Column, and Line Breaks)
occuring within a token to be expanded (encoded
by means of element
Abbreviations are marked through
The set of abbreviations also contains the "&
"
and "⁊
" breviographs, either of them being resolved by means of the "et
" expansion.
When tokens abbreviated through non-standard characters (see also
Non-Standard Characters) are
resolved, the respective non-standard character only is stated within the non-expanded element (
Identified printing errors are encoded by means of
By contrast, identified transcription errors – resulting,
for example, from the double keying of the text – are resolved silently.
Page, column, and line breaks are marked by means of empty elements
at the beginning
of a page, column, or line, respectively. With page or column beginnings, original
page numbers or (if existent)
column numbers are recorded within the type="start" in type="end" (these
elements imply, at the same time, the beginning of the new/first column,
or of the non-column layout, respectively).
With regards to the positioning of the previously mentioned break elements – of which
there currently appears to be no clear consent in the TEI community – the following rule applies
within the scope of this edition: In case a page, column, or line beginning occurs in conjunction with
a respectively encoded "conceptual" text element (e.g., child of the first
mixed-content element occurring in the structure of this conjunction. In the event of more than
one break element (also including "anchor" elements such as
Consider the following, comprehensive example:
Caput VIII
... first line of first column ...
... second line of first column ... ...
... first line of second column ... ...
...
Blank pages (i.e., pages without any content) after the title page and before the last
page are represented by means of <pb type="blank"/>; blank pages before the title page or
after the last page of a work may be omitted altogether.
Hyphens occurring at the end of lines are not retained in
the text, but encoded by means of an attribute rendition="#hyphen" within
the respective
uino prohibita, & an ali
qua sit solùm iure positiuo. 12. 172 ]]>
-
Hyphenation Variants
- Separations of syllables marked in the original source text by means of hyphens
are encoded through a respective break element obtaining an attribute
rendition with value#hyphen . - Separations of syllables
notmarked in the source text by means of hyphens are encoded through therendition attribute with value#noHyphen within the respective break element. - Furthermore, separations – regardless of their
markedness in the source text – are annotated
through an attribute
break="no"within any intervening break elements. At this,break="no"signifies the coherence of a word divided by means of the respective break element(s). It is important that in such cases no whitespace (i.e., no blank, tab, or newline character) occurs outside of these elements; newlines are encoded in the XML documentwithinpb ,cb , andlb elements, by preference immediately after the element name and before thebreak attribute. - By contrast, a "normal" line break not dividing a word is encoded
by means of a simple
lb element (see Page, Column, and Line Breaks).
In case of text loss due to censorship on the scale of single characters,
words, or a sentence, the respective range of text is marked through a
Text passages barely legible or utterly illegible due to reasons other than censorship
are marked by means of
If the text within a passage of these types is still readable, it is annotated by means
of an #xx abbreviation of the name initials as value)
and his/her certainty with regards to the resolved text within
Should the text not be readable anymore, but the editing person
has a readable substitution page of the same edition of the work at her disposal, the text is plainly encoded, without a specific
annotation. Instead, the usage of pages from an other original sample of the same edition
is stated within the
If the text is not readable anymore, but the editing person has
a legible substitution page of an other, differing edition of the work at her disposal,
the utilized source
is stated in the
In this case (readable substitution page of a different edition is on hand), or in the
case of the editing person having an assumption about the supplementation of the missing text,
the supplementation is added by means of the
...
Should the text not be readable and there is also no assumption
to be made about its supplementation, the existing gap is signified by means of
a
Typographic chacteristics in the text are encoded by means
of the
- Characters meaningful with regards textual or argumentative
structures, such as hyphens, asterisks or daggers, are captured in different types of
elements (e.g.,
milestone ) by means of therendition attribute. (With regards to non-standard characters without specific meaning, please refer to Non-Standard Characters.) The encoding of typographic features within the respective (type of) element appears reasonable due to the immediate correlation of the character and the text phenomenon expressed by means of the respective element. - Specific formattings of the font (such as initials, italics, recte, bold,
small caps, superscript, subscript, or spaced) are usually encoded through
hi elements withrendition attributes. This is supposed to serve, firstly, as a simple rule for consistency, and is also meant, secondly, to express a logical separation between text phenomena (and the respective elements) of a rather "conceptual", structural nature (such asp orhead ) on the one side, and text phenomena and elements of a typographic nature on the other side. - Text alignment: Centered or right-aligned formatting of a text block is usually
encoded through the
hi element with arendition attribute if the text block is a "simple" block (e.g., captured by means of ap element) without special formatting within the scope of this edition, and not a "conceptual" block (such as ahead heading) with inherent formatting.
The following formattings by means of
Larger images, illustrations or graphics
are not recorded as such but marked in the text by means of
Smaller graphic elements such as (ornamental) asterisks, solid or curly lines, smaller illustrations, etc.,
that perform a structural function – for instance, as separators between headings and/or sections – are
captured as:
Multi-volume works are encoded as one XML dataset
that contains groups (
On the highest structural level of a text (i.e., directly below
the
Title pages are each (there may be several) encoded by means of the
respective elements (described, for instance, in the
TEI P5 guidelines).
At this, the title page is altogether captured in a
Further elements of the title page, if existing, are annotated through the following types of tags (the descriptions are taken from the respective part of the guidelines linked above):
byline : "... the primary statement of responsibility given for a work".docAuthor : "contains the name of the author of the [work/volume]"; in itskey , the normalized form of the author's name is stated (see also the respective section).imprimatur : "contains a formal statement authorizing the publiction of a work".docEdition : "contains an edition statement" (including, for instance, statements about the current edition in comparison with previous ones – although the "School of Salamanca" project usually collects a text's first edition).docImprint : "contains the imprint statement (place and date of publication, publisher name)";docImprint may includedocDate , see below.docDate : "contains the date of a [work/volume]" (potentially occurs withindocImprint ); thewhen attribute contains the year of publication as a four-digit number.
The thus encoded metadata of a text as given on its title page may also serve for
cross-checking with the Bibliographic Description of the work.
All text blocks on a title page not mentioned here are annotated as
typographic paragraphs (
The structural units of the text (e.g., lectures, books, chapters,
questions) that are marked in the original text by means of headings or numerations, for
instance, are annotated as far as possible
as
In order to allow for a differentiated searchability of the texts,
the following values of
Each child axis.
This means, by implication, that the headings of sections marked as not be encoded as within
other child elements of
The typographic paragraph divisions, marked in the source
by means of vertical margins, first-line indentation, shorter line endings (not reaching
the end of the justification), or others,
are annotated as
Shifts from one argumentative paragraph
to the next, usually marked through marginal numbers, "*" or "†" symbols, or others,
are annotated by means of child
elements of
Tables of contents, indices, dictionaries, and other types of list structures
are annotated as
Text blocks consisting exclusively of verses
– usually identifiable by deeper indentation than the surrounding text and, potentially,
italicization – are annotated by means of the
EIVSDEM AD LIBRVM.
I liber in lucem tineis blattísque sepultus:
Iam ter quinque annos delituisse sat est.
Iam p
Zoilus haud, qui te mordeat, ullus erit.
Comments, bottom notes, or marginal notes are annotated through
the
If the exact position of the note can be clearly
identified, the note (including all its text and markup content) is encoded
at this very position. Otherwise, the note is encoded (completely) at the end of the line
occurring on the same height on the page as the note, and it obtains an attribute
anchored="false".
In the event of a page or column break occurring within the note,
the respective element (
A symbol that references a note in
the main area of the text is annotated by means of a
A symbol identifying/labeling the note at the
beginning of a note is solely encoded as value of the
d
Generally,
At this, the concrete values of
The
The
The values of all elements within (or
below, so to speak) of the
xml:id="[work ID]-[volume number]-[facsimile number]-[element code]-[alphan. code]"
Description:
Work ID
: project-specific 5-place ID of the work (not the volume) that the element is to be found in, such as "W0002" or "W0013".Volume number
: 2-digit number of the volume within the work, in which the element identified through thexml:id attribute is to be found; is "00" in case of a single-volume work, "01" with the first volume, "02" with the second volume, and so on.Facsimile number
: 4-digit value stating the number of the facsimile that corresponds to the element identified by thexml:id ; the value follows the value of thefacs attribute of the nearest previous page break (pb ).Element code
: a 2-letter abbreviation for the type of element that is to be identified, such as "pa" forp elements. For a complete list of all possible element codes, please see further below in this section.Alphanumeric code
: a 4-place alphanumeric value which primarily serves for the uniqueness of thexml:id value, and which only in the case oflb elements contains relevant information (in the form of line numeration, please see Page, Column, and Line Breaks).
The following elements obtain an
front : "fm" (front matter)body : "tb" (text body)back : "bm" (back matter)titlePage : "tp"docTitle : "dt"titlePart : "tt"div : "dX" (division, with "X" as a numeric value stating thediv 's position in the overalldiv hierarchy: e.g., "d1" is a "top-level"div )head : "he" (heading)item : "it"list : "li"p : "pa" (paragraph)pb : "pb"lb : "lb"note : with attribute@type="margin": "nm" (Marginalnote)milestone : "mi"lg : "lg"unclear : "un"persName : "pe"placeName : "pl"term : "te"title : "ti"supplied : "su"
Priuilegio del Rey de Portugal.
EV El Rey...
...
]]>
The consistent syntax of
If annotated, cross-references are annotated generally by means of
the
...
Ni es
...
n
Maior. in 4...
The edition of the "School of Salamanca" project links different internal
datasets: works, dictionary articles, and authors. Furthermore, there are references to
external data from authority files, leading out of the web application. For the latter purpose, the
CERL-Thesaurus (Consortium of European Research Libraries),
the
Gemeinsame Normdatei der Deutschen Nationalbibliothek (GND)
and, with place names, the
Getty Thesaurus of Geographic Names ® Online
are referenced. All these (internal and external) references make use of the
Please note that the reference by means of the
element, while the
former can only be identified,
to a large extent, through scholarly studying of the text (ultimately, then, being encoded
within the attribute).
Depending on the type of reference to be made, there are three different scenarios for
using the
- 1. A place/element within the same dataset is referenced.
context ... ]]> -
2. A different, project-specific dataset (or a place/entity therein) is referenced.
FRANCISCI ... ]]> - 3. A dataset/entity external to the project's digital edition is referenced. Please see External Linked Data.
If there are established and well-known forms of work titles or proper names,
they may be recorded in their normalized/modernized variant
(in addition to the annotated, original variant of the text)
by means of the
(With regards to proper names and work titles, please see also
the sections on Persons,
Places, and Bibliographic
References. For the
The
With numerated or named elements, the name or number
of the element (i.e., the text passage) can be stated within the value of
Internal references designate links between datasets within the digital edition (see also Variants of @ref) and can be applied, for instance, in the following scenarios:
- References from a work to passages in other works, to authors of works of the digital edition, or to lemmata of the dictionary;
- Reference from a dictionary article (i.e., from a lemma dataset) to passages of other dictionary articles and/or to specific authors, or to passages in specific works of the source collection.
Lemmata – i.e., references to terms covered in the project's dictionary –
are annotated in the work corpus specifically by means of the
An example (for illustrative purposes):
ne cognita ad Deum et divina quaedam pertinent:
tiae Theologiae
The "authors" designate those persons authoring one or several works of the
corpus. In the event of an author being mentioned (e.g., in the form of a clearly assignable
citation or paraphrase), the mentioned proper name, or reference to the author is annotated
by means of the
The annotation of authors is to be differentiated from the annotation of
"external" person names in that, with authors, the author's key (e.g., ref="author:A0001") must be stated.
(with regards to external person names, see also Persons in the "External
Linked Data" section).
The "works" are those works that are encoded within the scope of the digital edition of
this project. Citations and other bibliographic references to these works, occurring in a text (of an other work),
are annotated by means of the
The annotation of citations of, or bibliographic references to "external" authors (authoring works that are not included in the corpus at hand) are described in Bibliographic References.
"External linked data" refer to persons, places, or cited literature not
encoded or described within the scope of this digital edition. In the process of contentual
analysis and enrichment of the texts, these persons, places, or literary references are
successively – and, potentially, constrained to certain parts of the texts – annotated.
Consequently, the annotation may not be conducted to the full extent, but rather in the
process of studying the source material. With specific works or sequences in single works, in which
persons, places, or bibliographic references are annotated rather exhaustively,
informations about these annotations need to be stated in the
For the demands of these guidelines, references to persons – different from
Authors
– are external references. With persons (i.e.,
With places (
Citations and other references to external literature (not
included in the corpus described here) occurring in the text are annotated by means of the
In the Reference works contain automatic hyphenation of marked and un-marked words in the pb, cb and lb elements. Abbreviations are coded as they appear in the origi-nal. Only automatically edited work: it contains automatic hypenation of marked and unmarked words in the pb, cb and lb elements. Abbreviations are partially re-solved.
In the documentation file for TEI metadata of the project, the
non-standard characters declared in the
In opposition to these generically (i.e., corpus-wide) applying information, the following data is
to be annotated in a work-specific way:
Bibliographic information about the original source used for encoding are recorded in the
The bibliographic description follows, with regards to the full title (type="main"), the guidelines
"Alte Drucke"
(German) of the
Head Office of Gemeinsamer Bibliotheksverbund (p. 6-7),
as well as, analogously, the guidelines of the
Mindestanforderungen für die autoptische Katalogisierung Alter Drucke (AAD)
(German). As the example shows, an established, citable short title and a "Ansetzungssachtitel" (according to the guidelines) are
stated along with the full title. Authors and places are annotated corresponding to the edition guidelines at hand.
The information about the original source may contain the following exception: If the digitized and encoded edition
is not the first edition of the text, a
A similar exception applies with regards to the datasets of multi-volume works:
Should the digitized series not be the one containing the first editions of the volumes,
the
In conjunction with the information about imprints (Printers/publishers, publication place and year),
the institution in possession of the digital scans of the original and a link to the corresponding catalogue entry
are recorded. Should pages be missing in this original source, they are substituted through those of other versions/editions as
far as possible. Die Addition of "external" pages and their origin are documented within the