TEIWiki - Recent changes [en]

Samples of TEI texts

2012-05-14T06:00:16Z

broken

← Older revision		Revision as of 06:00, 14 May 2012
(3 intermediate revisions not shown)
Line 2:		Line 2:
	[[Category: TEI:P4]]		[[Category: TEI:P4]]
	[[Category: TEI:P5]]		[[Category: TEI:P5]]
-	Please add links below to ~~any~~ TEI ~~sample~~ texts ~~that are freely available for use~~ by developers ~~working on~~ TEI-~~related software. By listing the~~ texts ~~here you are allowing the developers the right~~ to test ~~their software with your texts, but are not necessarily licensing any other use of these texts~~. ~~Developers~~ should ~~ask permission of~~ the text owners should they wish to make any more in-depth use of these materials.	+	__NOTOC__
		+
		+	''Please add links below to TEI texts.''
		+
		+	The avaliability of texts enables others to learn by example; fosters similar approaches to solving the same problems across the entire community of practice; and gives developers of TEI-based tools a broader sample of texts to test against. The fact a text is listed here should not be taken as a licence to redistribute the text, please check with text owners should they wish to make any more in-depth use of these materials.
		+
		+	== Pedagogical Samples ==
		+
		+	* [http://tbe.kantl.be/TBE/ TEI By Example] is a set of examples design to teach the basics of TEI. Includes TEI P3 (SGML) and P5 examples. [http://creativecommons.org/licenses/by-sa/3.0/ CC licensed].

	== Texts ==		== Texts ==
Line 45:		Line 53:
	* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]		* Some work is ongoing about the possibility to use the TEI to edit and archive [http://www.iso.org ISO] documents. Relevant tips and documentation are provided under [[TEI for ISO]]

-	* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?)	+	* TEI in dspace example http://dspace.nitle.org/handle/10090/11695 (P4?) (seems broken May 2012)

	* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.		* The [[http://sarit.indology.info SARIT]] project has recently brought out an electronic TEI-encoded edition of a 2007 print publication. It is a work on Buddhist tantric religion: Christian K. Wedemeyer, ed., ''Āryadeva's Lamp that Integrates the Practices (Caryāmelāpakapradīpa): The Gradual Path of Vajrayāna Buddhism According to the Esoteric Community Noble Tradition - Part Three: Critically Edited Sanskrit Text of Āryadeva's Caryāmelāpakapradīpa,'' (New York: The American Institute of Buddhist Studies at Columbia University in New York with Columbia University's Center for Buddhist Studies and Tibet House US, 2007). E-details and full text can be seen [[http://sarit.indology.info/newphilo/navigate.pl?indologica.6 here]]. Clicking [[http://sarit.indology.info/downloads.shtml Downloads]] on the above screen offers downloadable TEI, PDF and HTML versions of this e-text, and several others. The interesting thing about this e-text from the TEI point of view is the encoding and display of the manuscript variants to the critical edition. It was good of the publishers and editors to give their permission for the e-dissemination of this work just three years after print publication. Best, Dr Dominik Wujastyk.

	* [http://txm.bfm-corpus.org/txm/ '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.		* [http://txm.bfm-corpus.org/txm/ '''La Queste del Saint Graal'''] (The Quest of the Holy Grail) online interactive edition offers a parallel multi-level (normalized, diplomatic and imitative) transcription of the Lyon MN PA 77 manuscript along with manuscript images and a translation in modern French, powered by TXM text search and statistical analysis platform. The complete source XML-TEI P5 encoded with Menota extensions manuscript transcriptions and an ODD customization file, as well as the stylesheets used to produce HTML editions and a PDF printable version are freely available for [http://txm.bfm-corpus.org/txm/images/graal_src.zip download] under a CC BY-NC-SA 3.0 license.
		+
		+	* [http://docsouth.unc.edu/southlit/poe/menu.html "Tales" by Edgar Allan Poe] at University of North Carolina at Chapel Hill. Uses DTD-style entities for non-ASCII characters.

	== Dictionaries ==		== Dictionaries ==

SIG:Correspondence/EncodingComparisons

2012-05-11T08:59:21Z

Postscript:

← Older revision		Revision as of 08:59, 11 May 2012
(One intermediate revision not shown)
Line 12:		Line 12:

	* '''WeGA''': The [http://weber-gesamtausgabe.de edition of the collected works of Carl Maria von Weber] includes (besides diaries and documents) Weber's letters. We are working with a customised TEI schema with additions in the TEI namespace. A stripped down version of that schema (ODD and RelaxNG) can be obtained from [[SIG:Correspondence/ODD_work]].		* '''WeGA''': The [http://weber-gesamtausgabe.de edition of the collected works of Carl Maria von Weber] includes (besides diaries and documents) Weber's letters. We are working with a customised TEI schema with additions in the TEI namespace. A stripped down version of that schema (ODD and RelaxNG) can be obtained from [[SIG:Correspondence/ODD_work]].
		+
		+	* '''FSiB''': In the BBAW project [http://www.bbaw.de/en/research/schleiermacherII Schleiermacher in Berlin, 1808–1834] an edition will be produced of Friedrich Schleiermacher's surviving correspondence (besides lectures and calendar of appointments). A website isn't yet available, but the researchers work already in a new digital work environment with a customised TEI schema. Unlike the WeGA we had made ''no'' additions to the TEI schema, i.e. our schema is only a (still validating) subset of the TEI schema.

	== Header (Meta Data) ==		== Header (Meta Data) ==
Line 20:		Line 22:

	* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>sender</code> which takes one ore more names. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A041004.		* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>sender</code> which takes one ore more names. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A041004.
		+
		+	* FSiB: We used <code>creation</code> (a child of <code>profileDesc</code>) to note the sender, addressee and dates. The sender is marked as <code>persName</code> with a attribute <code>@type</code>, which indicates the role of the person in the corrspondence, i.e. sender. An other attribute <code>@key</code> refers to the central index of names.

	=== Addressee ===		=== Addressee ===
Line 26:		Line 30:

	* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>addressee</code> which takes one ore more names. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A041004.		* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>addressee</code> which takes one ore more names. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A041004.
		+
		+	* FSiB: We used <code>creation</code> (a child of <code>profileDesc</code>). The addressee is marked as <code>persName</code> with a attribute <code>@type</code>, which indicates the role of the person in the corrspondence, i.e. addressee. An other attribute <code>@key</code> refers to the central index of names.

	=== Dates ===		=== Dates ===
Line 32:		Line 38:

	* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>dateSender</code> and <code>dateAddressee</code> which take the appropriate dates. For an example of <code>dateSender</code> see (the XML tab of) http://weber-gesamtausgabe.de/A041004.		* WeGA: We added a dedicated element <code>correspDesc</code> as child of <code>sourceDesc</code>. Inside <code>correspDesc</code> goes <code>dateSender</code> and <code>dateAddressee</code> which take the appropriate dates. For an example of <code>dateSender</code> see (the XML tab of) http://weber-gesamtausgabe.de/A041004.
		+
		+	* FSiB: We used <code>creation</code> (a child of <code>profileDesc</code>) to note the sender, addressee and dates. Inside <code>creation</code> the date is noted in <code>date</code> with the usual attributes <code>@when, @from, @to, @notBefore, @notAfter</code>. The attribute <code>@type</code> indicates the type of dating, i.e. production, reception etc.

	=== Type of correspondence material ===		=== Type of correspondence material ===
Line 40:		Line 48:

	== Body ==		== Body ==
		+
		+	=== Opener ===
		+
		+	* FSiB: the possibility in the TEI to mark <code>salutation</code> is nice, but we have often problems to encode the salutation conform to the TEI guidelines: in a lot of letters the salutation stands among the first paragraph and not detached at the beginning. Because <code>salutation</code> is only allowed in <code>opener</code>, we don't encoding salutation in these cases.

	=== Postscript ===		=== Postscript ===

	* WeGA: Short postscripts are held in <code>postscript</code> while longer ones are encoded as <code>div</code>. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A040309.		* WeGA: Short postscripts are held in <code>postscript</code> while longer ones are encoded as <code>div</code>. For an example see (the XML tab of) http://weber-gesamtausgabe.de/A040309.
		+
		+	* FSiB: Like the WeGA, short postscript are marked with <code>postscript</code>, while longer ones are noted as <code>div</code>.

XPointer

2012-05-11T05:49:24Z

ref

← Older revision		Revision as of 05:49, 11 May 2012
Line 1:		Line 1:
		+	''For use cases where these techniques might be used, see [[Stand-off use cases]].''
		+
	The '''[http://www.w3.org/TR/xptr-framework/ XPointer Framework]''' is a collection of schemes (note: ''schemes'' not ''schemas'') that specify the method for addressing into the XML tree or help in this task. One end of its functionality overlaps with XPath, but the other allows one to address points and ranges inside elements, and this is often precious to us TEI-ers, especially in some [[stand-off markup]] systems or for working with ontologies (RDF may use it). It was initially defined as a companion to [[XLink]] that took care of URI fragment identifiers (the strings placed after the '#' in a URI).		The '''[http://www.w3.org/TR/xptr-framework/ XPointer Framework]''' is a collection of schemes (note: ''schemes'' not ''schemas'') that specify the method for addressing into the XML tree or help in this task. One end of its functionality overlaps with XPath, but the other allows one to address points and ranges inside elements, and this is often precious to us TEI-ers, especially in some [[stand-off markup]] systems or for working with ontologies (RDF may use it). It was initially defined as a companion to [[XLink]] that took care of URI fragment identifiers (the strings placed after the '#' in a URI).

Stand-off use cases

2012-05-11T05:48:43Z

ref

← Older revision		Revision as of 05:48, 11 May 2012
(5 intermediate revisions not shown)
Line 1:		Line 1:
	[[category:markup]]		[[category:markup]]
		+
		+	''For technical methods that might be used to implement these, see [[XPointer]].''

	=== Use cases ===		=== Use cases ===
Line 11:		Line 13:
	# 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)		# 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 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)
-	# ~~Running an automated tool is run against~~ an XML source~~, generating a~~ TEI ~~document which encodes information discovered in that source. For instance, you might run a process against an~~ RSS ~~news feed,~~ and ~~generate a TEI document containing~~ analysis ~~of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it~~ (~~you might do~~ sentiment analysis ~~or something like that~~). ~~Using TEI Pointers~~, ~~you could point at target words or phrases~~ in the ~~RSS feed which form part of~~ the 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)		# 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 ~~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 ===		=== Challenging aspects of TEI texts ===
Line 20:		Line 22:
	There are a number of challenging features sometimes found in TEI-encoding texts. These include:		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).
-		+	# Significantly richer metadata than many linguistic processing communities general use.

Stand-off use cases

2012-05-11T01:19:55Z

Example from Papyri.info of personal name standoff markup:

← Older revision		Revision as of 01:19, 11 May 2012
Line 36:		Line 36:
	See [https://gist.github.com/2653676 O.Leid. 24]		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.		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.

Stand-off use cases

2012-05-10T23:27:58Z

tweaks

← Older revision		Revision as of 23:27, 10 May 2012
(5 intermediate revisions not shown)
Line 1:		Line 1:
	[[category:markup]]		[[category:markup]]
		+
		+	=== Use cases ===
		+
	This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.		This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.

Line 11:		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)		# 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)		# 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)
		+
		+	=== Challenging aspects of TEI texts ===
		+
		+	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)
		+	# 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)
		+	# texts with errors, omissions or additions
		+	# 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");
		+	# existing semantic, linguistic, bibliographic or provenance tagging which needs to be integrated with the new taggings (usually the new taggings are linguistic in nature).
		+
		+


-	== Example from Papyri.info of personal name standoff markup ==	+	=== Example from Papyri.info of personal name standoff markup ===
	(HC)		(HC)

Stand-off use cases

2012-05-10T16:53:37Z

← Older revision		Revision as of 16:53, 10 May 2012
(One intermediate revision not shown)
Line 14:		Line 14:

	== Example from Papyri.info of personal name standoff markup ==		== Example from Papyri.info of personal name standoff markup ==
		+	(HC)
		+
	See [https://gist.github.com/2653676 O.Leid. 24]		See [https://gist.github.com/2653676 O.Leid. 24]

Stand-off use cases

2012-05-10T16:02:29Z

← Older revision		Revision as of 16:02, 10 May 2012
(3 intermediate revisions not shown)
Line 2:		Line 2:
	This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.		This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.

-	# A third party publishes a text in non-TEI XML at a stable URL. You want to perform linguistic annotations on the text without ~~loosing~~ reference to the underlying third party text. A TEI text is built with references back to the original non-TEI XML.	+	# A third party publishes a text in non-TEI XML at a stable URL. You want to perform linguistic annotations on the text without losing reference to the underlying third party text. A TEI text is built with references back to the original non-TEI XML.
-	# A third party publishes a text in TEI at a stable URL. You want to perform linguistic annotations on the text without ~~loosing~~ reference to the underlying third party text. A new TEI text is built with references back to the original TEI.	+	# A third party publishes a text in TEI at a stable URL. You want to perform linguistic annotations on the text without losing reference to the underlying third party text. A new TEI text is built with references back to the original TEI.
-	# A third party publishes a text in TEI XML at a stable URL. You want to perform linguistic annotations on the text without ~~loosing~~ reference to the underlying third party text. A TEI text is built with references back to the original XML. (SY)	+	# A third party publishes a text in TEI XML at a stable URL. You want to perform linguistic annotations on the text without losing reference to the underlying third party text. A TEI text is built with references back to the original XML. (SY)
	# There are multiple competing marking's up of linguistic information in a TEI text. The 'obvious' one is marked up and the others are relegated to stand-off markup. Tools are used to bring each alternative markup to the fore. (SY)		# There are multiple competing marking's up of linguistic information in a TEI text. The 'obvious' one is marked up and the others are relegated to stand-off markup. Tools are used to bring each alternative markup to the fore. (SY)
-	# There are multiple competing marking's up of linguistic information in a TEI text. Rather than ~~priveledge~~ one marking up, all are relegated to stand-off markup. Tools are used to bring each alternative markup to the fore. (SY)	+	# 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 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)
	# Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)		# Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the 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)		# 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)

Stand-off use cases

2012-05-10T15:20:42Z

← Older revision		Revision as of 15:20, 10 May 2012
Line 10:		Line 10:
	# Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)		# Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the 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)		# 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)
		+
		+
		+	== Example from Papyri.info of personal name standoff markup ==
		+	See [https://gist.github.com/2653676 O.Leid. 24]
		+
		+	The standoff annotation section starts at line 87.
		+
		+	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.
		+
		+	Note: I'm doing several things "wrong" here for the sake of argument. For starters, string-range() does not allow you to use a node without text in it as the first argument. I'd like to change that to allow the starting point to be, e.g. an <lb> (note, however, that if this were a sticking point, an XPath like //lb[@n='1']/following-sibling::text()[1] would work, it's just more verbose). Second, my use of string-range() is incorrect because it does not allow an XPath as the first argument. To be correct according to the current spec, I'd have to do something like:
		+
		+	<nowiki>#string-range(xpath1(//lb[@n='1']/following-sibling::text()[1]),3,6)</nowiki> instead of
		+
		+	<nowiki>#string-range(//lb[@n='1'],3,6)</nowiki>
		+
		+	Note too that since I'm keeping a copy of the recognized name, a scheme like match() might be a better fit, though again, I'd propose doing away with the restriction that the node pointed to must contain the text. In that case, I might posit something like:
		+
		+	<nowiki>#match(//lb[@n='1'],'Κράτης')</nowiki>

TEI-Council-FAQ

2012-05-10T00:38:31Z

Stand-off use cases

2012-05-09T20:45:10Z

a new case

← Older revision		Revision as of 20:45, 9 May 2012
(One intermediate revision not shown)
Line 2:		Line 2:
	This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.		This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.

-	* A third party publishes a text in non-TEI XML at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A TEI text is built with references back to the original non-TEI XML.	+	# A third party publishes a text in non-TEI XML at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A TEI text is built with references back to the original non-TEI XML.
-		+	# A third party publishes a text in TEI at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A new TEI text is built with references back to the original TEI.
-	* A third party publishes a text in TEI at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A new TEI text is built with references back to the original TEI.	+	# A third party publishes a text in TEI XML at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A TEI text is built with references back to the original XML. (SY)
-		+	# There are multiple competing marking's up of linguistic information in a TEI text. The 'obvious' one is marked up and the others 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 TEI XML at a stable URL. You want to perform linguistic annotations on the text without loosing reference to the underlying third party text. A TEI text is built with references back to the original XML. (SY)	+	# There are multiple competing marking's up of linguistic information in a TEI text. Rather than priveledge 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)
-	* There are multiple competing marking's up of linguistic information in a TEI text. The 'obvious' one is marked up and the others are relegated to stand-off markup. Tools are used to bring each alternative markup to the fore. (SY)	+	# Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the 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)
-	* There are multiple competing marking's up of linguistic information in a TEI text. Rather than priveledge 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)	+
-		+
-	* Running an automated tool is run against an XML source, generating a TEI document which encodes information discovered in that source. For instance, you might run a process against an RSS news feed, and generate a TEI document containing analysis of it. You might store a copy of the feed with your TEI document, but you're not really interested in editing it; you're interested in what your process discovered about it (you might do sentiment analysis or something like that). Using TEI Pointers, you could point at target words or phrases in the RSS feed which form part of the analysis. [http://listserv.brown.edu/?A2=TEi-SOM;8464a70e.1205 from here] (MH)	+

TEI-Council-FAQ

2012-05-09T16:14:28Z

What was the War on Free-text-bearing Attributes?:

← Older revision		Revision as of 16:14, 9 May 2012
Line 93:		Line 93:
	The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw20.xml		The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw20.xml

-	== What was the War on Free-text-bearing ~~Attributes~~? ==	+	== What was the War on Free-text-bearing Attribute Values? ==

-	Some have felt that if ~~attributes~~ don't have a datatype, they are more prone to abuse than if they did. So there has been an effort to give datatypes to as many attributes as possible.	+	Some have felt that if attribute values don't have a datatype, they are more prone to abuse than if they did. So there has been an effort to give datatypes to as many attributes as possible. Some discussion of this with respect to @rend is available here: http://blogs.oucs.ox.ac.uk/jamesc/2011/12/01/rend-and-the-war-on-text-bearing-attributes/

	== What is the "Birnbaum doctrine"? ==		== What is the "Birnbaum doctrine"? ==

TEI-Council-FAQ

2012-05-09T14:39:45Z

new section: What was the War on Free-text-bearing Attributes?

← Older revision		Revision as of 14:39, 9 May 2012
Line 92:		Line 92:

	The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw20.xml		The process of making a release is documented at http://www.tei-c.org/Activities/Council/Working/tcw20.xml
		+
		+	== What was the War on Free-text-bearing Attributes? ==
		+
		+	Some have felt that if attributes don't have a datatype, they are more prone to abuse than if they did. So there has been an effort to give datatypes to as many attributes as possible.

	== What is the "Birnbaum doctrine"? ==		== What is the "Birnbaum doctrine"? ==

Stand-off use cases

2012-05-09T11:01:49Z

+ category

← Older revision		Revision as of 11:01, 9 May 2012
Line 1:		Line 1:
		+	[[category:markup]]
	This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.		This is a list of [http://en.wikipedia.org/wiki/Use_case use cases] for using stand-off markup in TEI. These examples are an attempt to build a shared common ground on which to move forward and are the (by-)product of a discussion on [http://listserv.brown.edu/?A0=TEi-SOM TEI-SOM]. Initials indicate discussion members who find this use case important or motivating.

← Older revision		Revision as of 00:38, 10 May 2012
Line 107:		Line 107:
	== What is a "magic token"? ==		== What is a "magic token"? ==

-	This is an value, usually an attribute value, such as that of @key or @rend, which does not follow a standard outside vocabulary but instead is understood in some undocumented way and often used for local processing. It should usually be explained in the teiHeader if possible. Having any processing rely on undocumented magic tokens is generally considered a bad idea.	+	This is an value, usually an attribute value, such as that of @key or @rend, which does not follow a standard outside vocabulary but instead is understood in some undocumented way and often used for local processing. It should usually be explained in the teiHeader if possible. Having any processing rely on undocumented magic tokens is generally considered a bad idea. See also [http://en.wikipedia.org/wiki/Magic_cookie Magic Cookie].

	== Why are some people on the Council email list or attending Council meetings even though they are not on the list of elected members? ==		== Why are some people on the Council email list or attending Council meetings even though they are not on the list of elected members? ==