Annotation and indexing (Mondrian) - Revision history

PBO at 14:57, 22 January 2020

2020-01-22T14:57:29Z

PBO: note reference system changed

2020-01-22T14:39:13Z

note reference system changed

PBO: PBO moved page Annotation (Mondrian) to Annotation and indexing (Mondrian) without leaving a redirect

2017-04-26T14:26:05Z

PBO moved page Annotation (Mondrian) to Annotation and indexing (Mondrian) without leaving a redirect

PBO at 14:25, 26 April 2017

2017-04-26T14:25:50Z

PBO: Created page with " ==Explantory notes== To create a note * Put into the transcription or translation an , with @n (short keyword) and @type=“note”. * Create a into the
2017-04-26T12:20:51Z

Created page with " ==Explantory notes== To create a note * Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”. * Create a <note> into the <div..."

New page

==Explantory notes==
To create a note
* Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”.
* Create a <note> into the <div type=“notes”> with the text of the note. It must have the same @n.
* Put all notes in a single language in the same div element.
* Order the notes by their referred location (technically irrelevant, but helpful to the human eye)

For example:
<pre>
<p>This is an exemple<anchor n=“nootje” type= “note”/> of how to create a note</p>

<div type=“notes” xml:lang=“en”>
<note n=“nootje”>This is the note</note>
… other notes in English…
</div>

<div type=“notes” xml:lang=“nl”>
<note n=“nootje”>Dit is de noot</note>
… other notes in Dutch …
</div>
</pre>

==Recurring annotation==

See [[Secondary files (Mondrian)#Recurring notes to persons and other subjects|Recurring notes to persons and other subjects]].

==<rs>==

Referencing string. Into <rs> are encoded names, with attributes, so they can be easily identified (i.e. You have different spellings of the same person's name and you want that they point to the same person), retrieved, indexed.
* '''@type''' kind of entity encoded (i.e. Person, exhibition, museum, journals, location, etc). The available types have been defined in the schema
* '''@ref''' to indicate an external url (RDKarchive url)
* '''@key''' a coded value that identifies the entity encoded (i.e. a number, a normalised spelling, etc.) We prefer to use @key rather than @ref.

It is possible to use multiple values in the key or ref attributes.

In the postal data (transcription of envelope) we don’t use <rs> to index the addressee, as his role is known from the letter metadata. Similarly, we don’t index persons saluted at the beginning or end of a letter, if these are addressees. (But we do tag ‘Jan’ in ‘Give my love to Jan’ if Jan is not an addressee).

When encoding a referring phrase as <rs>, we only tag the noun. This avoids potential problems with other words that need their own encoding.

Not:
<pre>
<rs>the woman who lives next door</rs>
</pre>
but
<pre>
the <rs>woman</rs> who lives next door
</pre>

In the case of multiple references to a person within a single paragraph, we encode each of them.

==References==

The element <ref> points to another resource and it is used for instance when a letter, a painting or another resource is mentioned in the text. @target provides the resource location (local or not).

<ref> is also used for pointing to the [[Secondary files (Mondrian)|bibliography]]. For example:
<pre>
... as mentioned in <ref target="biblio.xml#Andersen1861">Andersen 1861</ref>, we ...
</pre>
Here, 'Andersen1861' should be an entry in the bibliography.

==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
|}

==See also==
* [[Transcription: structure (Mondrian)]]
* [[Transcription: representation of the source (Mondrian)]]
* [[Transcription (Mondrian)]]

[[Category:XML Mondrian]]

← Older revision		Revision as of 14:57, 22 January 2020
Line 1:		Line 1:
		+
		+	==Annotation at the level of the letter==
		+	Annotation for which the [[TEI_Header_(Mondrian)\|teiHeader]] provides a natural place is stored there. Besides that,
		+	each letter or manuscript contains a <div> containing annotation, structured as follows:
		+	* a number of typed notes with fixed subjects (now: source of transcription, dating and remarks)
		+	* zero or more of ongoing topic notes
		+	* zero or more notes to specific locations in the text
		+
		+
		+	An example:
		+	<pre>
		+	<div type="annotation">
		+	<div type="typednotes" xml:lang="nl">
		+	<note type="transcrSource">Manuscript.</note>
		+	<note type="dating">Poststempel.</note>
		+	<note type="remarks">Beeldzijde: watermolen bij Delden, nabij Hengelo; cf. ongoing topic.</note>
		+	</div>
		+	<div type="ogtnotes">
		+	<note target="MEP_0011.xml#verblijfplaats">Mondriaans verblijf in Hengelo bij Hulshoff Pol.</note>
		+	</div>
		+	<div type="notes" xml:lang="nl">
		+	<note xml:id="openingTeekening">De tentoonstelling <ref target="exhibitions.xml"><hi rend="italics">Aquarellen, Teekeningen en ... </note>
		+	</div>
		+	</div>
		+	</pre>

	==Explanatory notes==		==Explanatory notes==

@@ Line 1: / Line 1: @@
-==Explantory notes==
+==Explanatory notes==
 To create a note
-* Put into the transcription or translation an <anchor/>, with @n (short keyword) and @type=“note”.
+* Put into the transcription or translation a pointer (<ptr/>), with @target consisting of '#' and a short keyword (start with letter, no spaces) and @type=“note”.
-* Create a <note> into the <div type=“notes”> with the text of the note. It must have the same @n.
+* Create a <note> into the &lt;div type=“notes”> with the text of the note. Its @xml:id must must be the keyword used in the pointer's @target.
 * Put all notes in a single language in the same div element.
 * Order the notes by their referred location (technically irrelevant, but helpful to the human eye)
@@ Line 9: / Line 9: @@
 For example:
 <pre>
-<p>This is an exemple<anchor n=“nootje”  type= “note”/> of how to create a note</p>
+<p>This is an example<anchor target="#nootje"  type= "note"/> of how to create a note</p>
-<div  type=“notes”  xml:lang=“en”>
+<div  type="notes"  xml:lang="en">
-<note n=“nootje”>This is the note</note>
+<note xml:id="nootje">This is the note</note>
 … other notes in English…
 </div>
-<div  type=“notes”  xml:lang=“nl”>
+<div  type="notes"  xml:lang="nl">
-<note n=“nootje”>Dit is de noot</note>
+<note n="nootje">Dit is de noot</note>
 … other notes in Dutch …
 </div>

← Older revision	Revision as of 14:26, 26 April 2017
(No difference)

@@ Line 59: / Line 59: @@
 </pre>
 Here, 'Andersen1861' should be an entry in the bibliography.
 ==See also==