Theoretical writings (Mondrian) - Revision history

PBO: /* The notebooks */

2017-06-01T14:09:45Z

‎The notebooks

PBO at 14:06, 1 June 2017

2017-06-01T14:06:26Z

PBO at 13:52, 1 June 2017

2017-06-01T13:52:11Z

PBO: /* Article in installments */

2017-06-01T13:51:32Z

‎Article in installments

PBO at 13:35, 1 June 2017

2017-06-01T13:35:08Z

PBO at 14:51, 2 May 2017

2017-05-02T14:51:45Z

PBO: Created page with "==Theoretical writings== We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. For now, we have decided t..."

2017-04-26T14:24:07Z

Created page with "==Theoretical writings== We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. For now, we have decided t..."

New page

==Theoretical writings==

We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. 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):
<pre><p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3"></pre>

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

Stages of writing: the TEI also uses the term ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. They are identified on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation). listChange-elements can nest, in order to describe groups of related changes.
To be decided: how do the values in the change attribute relate to the values in the seq-attribute on add’s and dels?

Rotation of the writing surface is encoded on the zones within the surfaces:

{| class="wikitable"
|-
|No rotate-attribute or rotate=”0”
|Zone contains normal writing
|-
|rotate=”90”
|Zone contains writing sideways/downward
|-
|rotate=”-90”
|Zone contains writing sideways/upward
|-
|rotate=”180”
|Zone contains top-down writing
|}

@@ Line 4: / Line 4: @@
 ==The notebooks==
 Properties of the notebooks that we have to deal with are:
 * Texts may be written starting from the first page towards the last page or the other way around
 * Texts may have been rotated with respect to the normal writing direction

@@ Line 8: / Line 8: @@
 * Texts may be discontinuous (interrupted by sketch)
 * Sometimes sketches may be overwritten by texts
 * pages may be missing
 * pages may be empty
 To take this into account, we use the following system:
-* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
+* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine. We ignore missing pages, but include pages that are empty.
 * The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
 <pre>
@@ Line 22: / Line 23: @@
 </div>
 </pre>
 * Sketches without commentary are contained (as a figure element) in their own div
 * Divs can (of course) also contain texts and accompanying sketches

@@ Line 8: / Line 8: @@
 * Texts may be discontinuous (interrupted by sketch)
 * Sometimes sketches may be overwritten by texts
 To take this into account, we use the following system:

@@ Line 60: / Line 60: @@
 * the article as a whole will be transcribed in a single XML file
 * the article is a single div with subdivs for the installments
-* the facsimile element will contain surfaces for all of the pages from different installments that contain text of the article; as usual page break elements will refer to the
+* the facsimile element will contain surfaces for all of the pages from the different installments that contain text of the article; as usual page break elements in the transcription will refer to the relevant surfaces. The n attribute on the <pb> elements will give the original page number.
 * the transcription will ignore metatext that is merely there to point readers to the following or previous installments
-* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article. The notes div will contain page break elements
+* notes by Mondrian will be in a separate div (type = notes) at the same hierarchic level of the article (notes encoded as <origNote>s). The notes div will contain page break  elements to faciltate page by page display of the original version. Notes will have their original numbers in their n-attributes.
-−

← Older revision		Revision as of 14:51, 2 May 2017
Line 1:		Line 1:
−	~~==Theoretical writings==~~

−	We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. 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.	+	We have insufficient knowledge of the properties of the theoretical writings to make final decisions about their encoding. Decisions documented here should be regarded as provisional.
		+
		+	==The notebooks==
		+	Properties of the notebooks that we have to deal with are:
		+	* Texts may be written starting from the first page towards the last page or the other way around
		+	* Texts may have been rotated with respect to the normal writing direction
		+	* Texts may be discontinuous (interrupted by sketch)
		+	* Sometimes sketches may be overwritten by texts
		+
		+	To take this into account, we use the following system:
		+	* The sequence of the surface elements in the facsimile element follows the physical sequence of the notebook, as best we can determine.
		+	* The content of the notebook is transcribed in div elements. Page breaks are inserted in the writing order: when Mondrian wrote a tekst that starts at p. 100 and continues on page 99, we encode:
		+	<pre>
		+	<div>
		+	<pb n="100"/>
		+	... content ...
		+	<pb n="99"/>
		+	... content ...
		+	</div>
		+	</pre>
		+	* Sketches without commentary are contained (as a figure element) in their own div
		+	* Divs can (of course) also contain texts and accompanying sketches
		+	* When an earlier sketch is overwritten by a new text, we will have two dives where the same page number occurs. The situation will presumably be clarified in a note.
		+	<pre>
		+	<div>
		+	<pb n="88"/>
		+	<figure> ... </figure>
		+	</div>
		+	<div>
		+	...
		+	<pb n="88"/>
		+	... transcribed text ...
		+	</div>
		+	</pre>
		+	* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the divs in the transcription.
		+
		+
		+
		+	===Article in installments===
		+
		+
		+
		+
		+	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:		These references may look like:

@@ Line 22: / Line 22: @@
 * Sketches without commentary are contained (as a figure element) in their own div
 * Divs can (of course) also contain texts and accompanying sketches
-* When an earlier sketch is overwritten by a new text, we will have two dives where the same page number occurs. The situation will presumably be clarified in a note.
+* When an earlier sketch is overwritten by a new text, we will have two divs where the same page number occurs. The situation will presumably be clarified in a note.
 <pre>
 <div>
@@ Line 34: / Line 34: @@
 </div>
 </pre>
-* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the divs in the transcription.
+* As the physical sequence is determined by the sequence of the surfaces, and the logical sequence by the sequence of the transcription, no particular meaning is to be assigned to the sequence of the main divs in the transcription.
+* Rotation of the writing surface is encoded on the zones within the surfaces:
-−
-−
-===Article in installments===
-−
-−
-−
-−
-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):
-<pre><p xml:id="p2" corresp="BornInHollandTest.xml#p1 BornInHollandTest.xml#p3"></pre>
-−
-At term level:
-<pre>which obscure <term xml:id="t1" corresp="BornInHolland.xml#t3">pure reality</term>.</pre>
-−
-Stages of writing: the TEI also uses the term ‘revision campaigns’, see http://www.tei-c.org/release/doc/tei-p5-doc/en/html/PH.html#PH-changes. They are identified on div’s and other elements using the change-attribute. The change attributes points to change-elements collected in a listChange-element in the header (in profileDesc/creation).  listChange-elements can nest, in order to describe groups of related changes.
-To be decided: how do the values in the change attribute relate to the values in the seq-attribute on add’s and dels?
-−
 Rotation of the writing surface is encoded on the zones within the surfaces:
-−
 {| class="wikitable"
 |-
@@ Line 72: / Line 50: @@
 |Zone contains top-down writing
 |}