Difference between revisions of "Notes"

Revision as of 10:49, 23 January 2018

Principles

(To be realized step by step)

• All XML documentation on this wiki
• Describe general decisions only once, project-specific changes on project-level pages
• Each project has its own schema, but new elements (not in the general TEI schema) will use a single (Huygens) namespace
• ...

Restjes

For the transcription of the manuscripts, the aim is to stay as close to the original text as possible. We focus on the production of diplomatic editions. This means that the edition is based on only one source and that the text and all graphic information will be displayed in accordance with this source. We don’t aspire a typographic imitation of the source, but aim for a functional reproduction of the text. As already stated, staying true to the text is key for the transcriptions. This means that deviations from the standard spelling and grammar are copied, changes made during writing - immediately or later - are documented, and if relevant, the physical structure of the source is reproduced.

For now, we have decided to relate source and destination texts to each other by pointing from the destination to the source at the paragraph and at the term level.

These references may look like:

At paragraph level (in this example there are two source paragraphs):

<p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3">

At term level:

which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.

Discussion

• How to encode blockquote?
  • q[rend="block"] (http://www.open.ac.uk/blogs/styleproject/?p=52 and https://www.ct-lc.org/sites/ct-lc.org/files/tei-workshop-2015-01-holton_exercise.pdf)
  • q[rend="display"] (http://www.tei-c.org/Vault/ED/edw35.txt)
  • q with child p or lg (http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#COHQQ)

• Use <rs [type="person"]>, <persName> or both?

• Define when to use <ref>, <ptr>, <anchor>?

• Can we make <label> inside <item> the standard? The <label> preceding the <item> generates invalid HTML in the Pergamon implementation of rendering

• Could we remove impliciet whitespace like \n\t\t? In other words: the TEI should be collapsable and no data (whitespace) would be lost.