Annotation and indexing - Revision history

194.171.144.181 at 14:01, 31 October 2018

2018-10-31T14:01:45Z

PBO at 15:04, 26 April 2017

2017-04-26T15:04:06Z

PBO at 15:03, 26 April 2017

2017-04-26T15:03:02Z

PBO at 15:00, 26 April 2017

2017-04-26T15:00:18Z

PBO at 14:59, 26 April 2017

2017-04-26T14:59:28Z

PBO at 14:58, 26 April 2017

2017-04-26T14:58:19Z

PBO at 14:56, 26 April 2017

2017-04-26T14:56:54Z

PBO at 14:40, 26 April 2017

2017-04-26T14:40:30Z

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

2017-04-26T14:24:58Z

PBO moved page Annotation to Annotation and indexing without leaving a redirect

ASC at 11:27, 15 February 2017

2017-02-15T11:27:51Z

@@ Line 40: / Line 40: @@
 </div>
 </pre>
 ==See also==

@@ Line 23: / Line 23: @@
 should be inserted in the &lt;div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
 The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
-Within each subdivision, the notes should be arranged based on their location in the text.  For example:
+Within each subdivision, the notes should be arranged based on their location in the text. For example:
 <pre>
-<p>This is an example<anchor n="nootje" type= "note"/> of how to create a note</p>
+<p>This is an example<anchor n="mynote" type= "note"/> of how to create a note</p>
 <div type="notes">

@@ Line 28: / Line 28: @@
 <p>This is an example<anchor n="nootje" type= "note"/> of how to create a note</p>
-<div  type=“notes”  xml:lang=“en”>
+<div type="notes">
-<note n=“nootje”>This is the note</note>
+  <div xml:lang="en">
-… other notes in English…
+  <note n="mynote">This is the note</note>
-</div>
+  … other notes in English…
-<div  type=“notes”  xml:lang=“nl”>
+ <div xml:lang="nl">
-<note n=“nootje”>Dit is de noot</note>
+  <note n="mynote">Dit is de noot</note>
-… other notes in Dutch …
+  … other notes in Dutch …
 </div>
 </pre>

@@ Line 17: / Line 17: @@
 at the place where it applies. The disadvantage of this approach is that is diminishes the legibility of the text for the encoder.
 Therefore, at Huygens ING the preffered method for local annotation is to create an anchor in the text that identifies
-the place where a note should be inserted. The actual notes are stored in a separate <div> in the same file.
+the place where a note should be inserted. The actual notes are stored in a separate &lt;div> in the same file.
 In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
 a @n attribute with a short keyword and a @type="note". A corresponding <note> element
-should be inserted inthe <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
+should be inserted in the &lt;div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
 The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
 Within each subdivision, the notes should be arranged based on their location in the text.  For example:

@@ Line 20: / Line 20: @@
 In order to create an annotation, we place an empty <anchor/> element within the transcription. The anchor should contain
-a @n attribute with a short keyword and a @type="note". A corresponding <note> element should be inserted in
+a @n attribute with a short keyword and a @type="note". A corresponding <note> element
-the <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
+should be inserted inthe <div type="notes"> element elsewhere in the document. The @n must have the same value in both elements.
 The notes div can contain subdivisions by language and further subdivisions based on the type attribute of the note.
 Within each subdivision, the notes should be arranged based on their location in the text.  For example:

← Older revision		Revision as of 14:40, 26 April 2017
Line 1:		Line 1:
		+	In a digital edition, annotation can be provided in several ways and at several levels. The most simple form of annotation are
		+	notes anchored to a location in the text. It is also possible to hyperlink certain stretches of text (e.g. those that refer to
		+	persons or other named entitites to external information, created by the project or elsewhere. Annotation can also be provided
		+	at a higher level, for instance about a chapter or a letter in a collection. Most projects will also have some level of annotation
		+	at the level of the entire work or collection being edited, for instance about its publication history or its literary context.
		+
		+	Often, it will be desirable to create annotations of multiple types, e.g. in order to filter the display of annotations by type.
		+	This can occur at the levels of annotation.
		+
		+	Indexing is related to annotation in that it can be used to link stretches of text to an index term, often provided with explanations.
		+
		+	==Local annotations==
		+	Local annotations are annotations anchored to a location in the test. We assume here that a point in the text is sufficient and that
		+	there is no need to mark a stretch of text as the target of annotation (but see Indexing, below).
		+
		+
		+
		+
		+
	A digital edition in TEI provides the ability to encode each peculiarity within the text (source) in detail in the TEI file. It is, however, possible to – for example to achieve a faster result – deal with phenomena the traditional way by discussing them in an annotation, using the <note> element.		A digital edition in TEI provides the ability to encode each peculiarity within the text (source) in detail in the TEI file. It is, however, possible to – for example to achieve a faster result – deal with phenomena the traditional way by discussing them in an annotation, using the <note> element.

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

@@ Line 1: / Line 1: @@
 A digital edition in TEI provides the ability to encode each peculiarity within the text (source) in detail in the TEI file. It is, however, possible to – for example to achieve a faster result – deal with phenomena the traditional way by discussing them in an annotation, using the <note> element.
-An empty &lt;anchor/> element must be placed within the transcription, the element containing a @n attribute with a short keyword and a @type=”note”. Nest another <note> element with @n attribute in the &lt;div type=”notes” n=”sleutelwoord” xml:lang=”taal”> element containing the text of the annotation. The @n must have the same value in both elements. All annotations within the same language must be incorporated within the same &lt;div> element, and the notes should be arranged based on their location in the text.  For example:
+An empty &lt;anchor/> element must be placed within the transcription, the element containing a @n attribute with a short keyword and a @type=”note”. Nest another <note> element with @n attribute in the &lt;div type="notes" n="keyword" xml:lang="language"> element containing the text of the annotation. The @n must have the same value in both elements. All annotations within the same language must be incorporated within the same &lt;div> element, and the notes should be arranged based on their location in the text.  For example:
 <pre>