Konstantin Freybe, M.A.
konstantin.freybe@uni-leipzig.de
Duration:
January 1st 2016 - June 30th 2019
Grant:
8.200.000EUR
received through EU research & innovation programme H2020
Partners:
13 partners coordinated by University of Innsbruck
10 institutions (increasing) as associated partners via memorandum of understanding
Transkribus
ScanREAD
e-Learning-App
Transkribus
ScanREAD
e-Learning-App
Transkribus
ScanREAD
e-Learning-App
Transkribus
ScanREAD
e-Learning-App
Transkribus
Transkribus
In case Transkribus_beta is not running let us take a look at the How-to-Guide in order to understand the functions provided:
https://transkribus.eu/wiki/images/7/77/How_to_use_TRANSKRIBUS_-_10_steps.pdf
Musical Instruments Museum Leipzig, Inv.: 926
- Violin Labels are basically little snippets of paper which were/are used to authenticate musical instruments from the Violin family
- they serve as sources of information for the evaluation of Violin instruments
- prints and other facsimile like those published by Paul de Wit gave rise to industrial use of fake labels in order to gain profit
- extensive research on these historical documents promises to help distinguish fake from original (labels - and maybe even instruments)
Musical Instruments Museum Leipzig, Inv.: 793
Musical Instruments Museum Leipzig, Inv.: 926
=> apply READ's tools
-storing Violin Labels digitally requires use of machine-readable formats like XML
-storing Violin Labels digitally requires use of machine-readable formats like XML
-XML stands for Extensible Markup Language
-storing Violin Labels digitally requires use of machine-readable formats like XML
-XML stands for Extensible Markup Language
-XML's greatest benefits compared to other markup languages:
-storing Violin Labels digitally requires use of machine-readable formats like XML
-XML stands for Extensible Markup Language
-XML's greatest benefits compared to other markup languages:
XML-documents themselves only store or interchange information
-storing Violin Labels digitally requires use of machine-readable formats like XML
-XML stands for Extensible Markup Language
-XML's greatest benefits compared to other markup languages:
XML-documents themselves only store or transport information
XML seperates data/information from its representation
-the Text Encoding Initiative (TEI) provides guidelines & semi-standardised modules in order to allow collaborative research & assure high quality
How can TEI-modules help to enrich Violin Labels?
-the Text Encoding Initiative (TEI) provides guidelines & semi-standardised modules in order to allow collaborative research & assure high quality
How can TEI-modules help to enrich Violin Labels?
TEI-modules already contain a lot of elements that can be used to thoroughly describe Violin Labels in high quantities.
-the Text Encoding Initiative (TEI) provides guidelines & semi-standardised modules in order to allow collaborative research & assure high quality
How can TEI-modules help to enrich Violin Labels?
TEI-modules already contain a lot of elements that can be used to thoroughly describe Violin Labels in high quantities.
How could TEI-XML encoding work on Violin Labels?
- XML is relatively easy
- follows the same syntactic rules as HTML (Hypertext Markup Language)
validate the document
elements are put in brackets "<" & ">" and are formed with an opening tag (<tag>) and a closing tag (</tag>)
- XML is relatively easy
- follows the same syntactic rules as HTML (Hypertext Markup Language)
validate the document
elements are put in brackets "<" & ">" and are formed with an opening tag (<tag>) and a closing tag (</tag>)
- there are lots of online resource that provide aid when learning to encode in XML
W3Schools:
Tutorialspoint:
Youtube Tutorials (my favourite: Derek Banas):
hierarchical document structure
- XML is relatively easy
- follows the same syntactic rules as HTML (Hypertext Markup Language)
validate the document
elements are put in brackets "<" & ">" and are formed with an opening tag (<tag>) and a closing tag (</tag>)
- there are lots of online resource that provide aid when learning to encode in XML
W3Schools:
Tutorialspoint:
Youtube Tutorials (my favourite: Derek Banas):
hierarchical document structure
well formed documents
- well formed documents -
<!-- Write comments like this to keep track of your work! -->
<?xml version="1.0" encoding="UTF-8"?>
<body>
<div>
<element>Element names are case sensitive in XML! This Element is not well formed.</Element>
<!-- The tagging above would produce an error because the contents of opening and closing tag differ. -->
</div>
<div>
<table>I mean furniture not tabular data.</table>
<!-- The tagging above might be well formed but its content/intent conflicts with HTML vocabulary and is therefore invalid. -->
</div>
</body>
correct syntax = well formed
- valid documents -
- a XML document validated against either a Document Type Declaration (DTD) or a Schema is both well formed and valid
- valid documents | DTD -
<!-- Write comments like this to keep track of your work! -->
<?xml version="1.0" encoding="UTF-8"?>
<!-- The followong is an example of the content of a fictional external DTD file "violinLabel.dtd":
<!DOCTYPE violinLabel
[
<!ELEMENT violinLabel (name, term, location, year)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT term (#PCDATA)>
<!ELEMENT location (#PCDATA)>
<!ELEMENT year (#PCDATA)>
]>
-->
<!-- The following is a reference to the external DTD file mentioned above -->
<!DOCTYPE violinLabel SYSTEM "violinLabel.dtd">
<!-- We will discuss the flaws of the following XML document. -->
<violinLabel>
<name>Sympertus Niggell</name>
<term>Geigen- und Lauten- Macher in</term>
<location>Füssen</location>
<year>1791</year>
</violinLabel>
Musical Instruments Museum Leipzig, Inv.: 926
- valid documents | DTD -
<!-- Write comments like this to keep track of your work! -->
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE violinLabel SYSTEM "violinLabel.dtd">
<!-- We will discuss the flaws of the following XML document. -->
<violinLabel>
<name>Sympertus Niggell</name>
<term>Geigen- und Lauten- Macher in</term>
<location>Füssen</location>
<year>1791</year>
</violinLabel>
Musical Instruments Museum Leipzig, Inv.: 926
Flaws:
- valid documents | DTD vs Schema -
- major disadvantage of DTD validation:
decreased flexibility of used elements
Schemas provide a powerful and XML-based alternative to DTD!
- advantageous due to allowing XML documents to carry their own format descriptions
- valid documents | Schema -
Schemas provide a powerful and XML-based alternative to DTD!
- advantageous due to allowing XML documents to carry their own format descriptions
<?xml version="1.0" encoding="UTF-8"?>
<!-- Although more flexible, there are still flaws to discuss. -->
<xs:element name="violinLabel">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="term" type="xs:string"/>
<xs:element name="location" type="xs:string"/>
<xs:element name="year" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
Flaws:
- valid documents -
- in scientific contexts TEI-XML modules have proven useful
As outlined on the handout "TEI-XML & Violin Labels" I identified the following modules as useful for the description of Violin Labels:
ID | Name | URL |
---|---|---|
tei | TEI Infrastructure | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ST.html |
core | Common Core | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html |
gaiji | Character and Glyph Documentation | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/WD.html |
transcr | Transcription of Primary Sources | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html |
namesdates | Names, Dates, People, and Places | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ND.html |
msdescription | Manuscript Description | http://www.tei-c.org/release/doc/tei-p5-doc/en/html/MS.html |
contact me:
konstantin.freybe@uni-leipzig.de
find this presentation online:
https://slides.com/kfreybe/violinlabels/