Stand-off use cases - Revision history

Stuartyeates: ref

2012-05-11T05:48:43Z

ref

Stuartyeates: regularise

2012-05-11T03:09:54Z

regularise

Stuartyeates: links, links, links!

2012-05-11T02:55:58Z

links, links, links!

Stuartyeates: richer metadata

2012-05-11T02:51:51Z

richer metadata

Stuartyeates: tweak

2012-05-11T02:49:12Z

tweak

Stuartyeates: attempt to regularise

2012-05-11T02:48:11Z

attempt to regularise

Hcayless: /* Example from Papyri.info of personal name standoff markup */

2012-05-11T01:19:55Z

‎Example from Papyri.info of personal name standoff markup

Stuartyeates: tweaks

2012-05-10T23:27:58Z

tweaks

Stuartyeates: tweaks

2012-05-10T23:22:55Z

tweaks

Stuartyeates: add detail

2012-05-10T23:15:24Z

add detail

@@ Line 1: / Line 1: @@
 [[category:markup]]
 === Use cases ===
@@ Line 28: / Line 30: @@
 # Existing semantic, linguistic, bibliographic or provenance tagging which needs to be integrated with the new taggings (usually the new taggings are linguistic in nature).
 # Significantly richer metadata than many linguistic processing communities general use.

@@ Line 13: / Line 13: @@
 # A third party publishes an RSS-XML source which is converted to TEI with links back to the original RSS for processing and analysis (sentiment analysis, named entity extraction, etc). The interest is not in the source text per se, but in the resulting analysis and the textual fragments in the source supporting that analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)
 # A text is being being published by the first the first time; TEI with stand-off markup is being used for the linguistic information. (SY)
-# For the purpose of a training course, you want a group of students to do preliminary analysis of the same text (identifying salient features they would choose to mark up, delimiting structural blocks, etc.). An interface allows students to select points and ranges in the text, and attach annotations to them; these are stored in TEI as stand-off markup, and a rendering engine allows the group to view and discuss the annotations. Actual inline TEI can be generated from them when students are ready to begin their markup projects. (MH)
+# Multiple independent markings-up of a TEI-encoded text are done in parallel, for example when there is contention as the the underlying meaning or when the text is set as a pedagogical mark-up exercise. (MH)
 # Textual fragments from within a TEI text are extracted and used in an index into the text as part of the end-matter, in a manner akin to a back-of-the-book index. (see [http://papyri.info/ papyri.info] example below) (HC)

@@ Line 14: / Line 14: @@
 # A text is being being published by the first the first time; TEI with stand-off markup is being used for the linguistic information. (SY)
 # For the purpose of a training course, you want a group of students to do preliminary analysis of the same text (identifying salient features they would choose to mark up, delimiting structural blocks, etc.). An interface allows students to select points and ranges in the text, and attach annotations to them; these are stored in TEI as stand-off markup, and a rendering engine allows the group to view and discuss the annotations. Actual inline TEI can be generated from them when students are ready to begin their markup projects. (MH)
-# Textual fragments from within a TEI text are extracted and used in an index into the text as part of the end-matter, in a manner akin to a back-of-the-book index. (see Papyri.info example below) (HC)
+# Textual fragments from within a TEI text are extracted and used in an index into the text as part of the end-matter, in a manner akin to a back-of-the-book index. (see [http://papyri.info/ papyri.info] example below) (HC)
 === Challenging aspects of TEI texts ===

@@ Line 20: / Line 20: @@
 There are a number of challenging features sometimes found in TEI-encoding texts. These include:
-# non-ASCII character sets (accents, macrons, Arabic, Far Eastern languages, etc)
+# Non-ASCII character sets (accents, macrons, Arabic, Far Eastern languages, etc)
-# characters that do not qualify for inclusion in Unicode (see [http://www.nzetc.org/tm/scholarly/tei-Auc1911NgaM-t1-body-d4.html wh ligature], for exmaple)
+# Characters that do not qualify for inclusion in Unicode (see [http://www.nzetc.org/tm/scholarly/tei-Auc1911NgaM-t1-body-d4.html wh ligature], for exmaple)
-# multicultural naming patterns (proper nouns in different language(s) or scripts to the underlying text, etc)
+# Multicultural naming patterns (proper nouns in different language(s) or scripts to the underlying text, etc)
-# texts with errors, omissions or additions
+# Texts with errors, omissions or additions
-# texts which are compiled with other texts not of interest
+# Texts which are compiled with other texts not of interest
-# linguistically and etymologically complex features of interest: dates based on names ("In the eighth year of the reign of John"); places named after people ("Washington");
+# Linguistically and etymologically complex features of interest: dates based on names ("In the eighth year of the reign of John"); places named after people ("Washington");
-# existing semantic, linguistic, bibliographic or provenance tagging which needs to be integrated with the new taggings (usually the new taggings are linguistic in nature).
+# Existing semantic, linguistic, bibliographic or provenance tagging which needs to be integrated with the new taggings (usually the new taggings are linguistic in nature).

@@ Line 11: / Line 11: @@
 # There are multiple competing marking's up of linguistic information in a TEI text. Rather than privilege one marking up, all are relegated to stand-off markup. Tools are used to bring each alternative markup to the fore.  (SY)
 # A third party publishes a text in non-TEI XML at a stable URL. You wish to use TEI-based tools to find and correct errors in original XML and feed those corrections back to the publisher in a format native to them. (SY)
-# A third party publishes an RSS-XML source which is converted to TEI with links back to the original RSS for processing and analysis (sentiment analysis, named entity extraction, etc). The interest is not in the source text per se, but in the resulting analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)
+# A third party publishes an RSS-XML source which is converted to TEI with links back to the original RSS for processing and analysis (sentiment analysis, named entity extraction, etc). The interest is not in the source text per se, but in the resulting analysis and the textual fragments in the source supporting that analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)
 # A text is being being published by the first the first time; TEI with stand-off markup is being used for the linguistic information. (SY)
 # For the purpose of a training course, you want a group of students to do preliminary analysis of the same text (identifying salient features they would choose to mark up, delimiting structural blocks, etc.). An interface allows students to select points and ranges in the text, and attach annotations to them; these are stored in TEI as stand-off markup, and a rendering engine allows the group to view and discuss the annotations. Actual inline TEI can be generated from them when students are ready to begin their markup projects. (MH)

@@ Line 36: / Line 36: @@
 See [https://gist.github.com/2653676 O.Leid. 24]
-The standoff annotation section starts at line 87.
+The standoff annotation section starts at line 87. I'm doing the annotation in the same document for the sake of argument—it might not be the ultimate solution.
 The use case is that I want to have an automated process attempt to recognize personal names in the text, and then provide an interface for users to correct the automated annotations. Because the text will be edited using a non-TEI interface that does not understand <persName> and the like, I cannot do this with inline markup. Inserting the name markup inline might be tough on the existing element hierarchy anyway. The data from the annotations will be submitted to a partner site, and we will keep the annotations as a record.

@@ Line 22: / Line 22: @@
 # non-ASCII character sets
 # non-Unicode character sets (see [http://www.nzetc.org/tm/scholarly/tei-Auc1911NgaM-t1-body-d4.html wh ligature])
-# multicultural naming patterns (Proper nouns is different language(s) or scripts to the underlying text)
+# multicultural naming patterns (proper nouns in different language(s) or scripts to the underlying text, etc)
 # texts with errors, omissions or additions
 # compound texts which are compiled with other texts not of interest

← Older revision		Revision as of 23:15, 10 May 2012
Line 26:		Line 26:
	# compound texts which are compiled with other texts not of interest		# compound texts which are compiled with other texts not of interest
	# linguistically and etymologically complex features of interest: dates based on names ("In the eighth year of the reign of John"); places named after people ("Washington");		# linguistically and etymologically complex features of interest: dates based on names ("In the eighth year of the reign of John"); places named after people ("Washington");
		+	# existing semantic, linguistic, bibliographic or provenance tagging which needs to be integrated with the new taggings (usually the new taggings are linguistic in nature).