SIG:Overlap - Revision history

Stuartyeates: Undo revision 7927 by Mary (Talk SPAMMER)

2010-07-19T18:20:14Z

Undo revision 7927 by Mary (Talk SPAMMER)

Mary at 08:49, 19 July 2010

2010-07-19T08:49:27Z

Desmond: /* General Bibliography */

2009-04-05T23:28:37Z

‎General Bibliography

Desmond: /* General Bibliography */

2009-04-05T23:28:11Z

‎General Bibliography

Desmond: /* MVD Multi-Version Document Format */

2009-04-05T23:24:25Z

‎MVD Multi-Version Document Format

Desmond: /* MVD Multi-Version Document Format */

2008-12-18T19:01:16Z

‎MVD Multi-Version Document Format

Desmond: /* MVD Multi-Version Document Format */

2008-12-18T18:58:13Z

‎MVD Multi-Version Document Format

Desmond: /* MVD Multi-Version Document Format */

2008-12-18T18:56:17Z

‎MVD Multi-Version Document Format

Desmond: /* MVD Multi-Version Document Format */

2008-12-18T18:52:19Z

‎MVD Multi-Version Document Format

Desmond: /* MVD Multi-Version Document Format */

2008-12-18T18:51:38Z

‎MVD Multi-Version Document Format

@@ Line 15: / Line 15: @@
 The TEI P4 Guidelines provide a chapter that discusses some ways to deal with markup that is not hierarchical (Chapter 31, "Multiple Hierarchies", http://www.tei-c.org/P4X/NH.html). Specific problems mentioned in that chapter include many that should be familiar to even the most basic user of TEI markup:
-* [http://www.jouercasino.eu/ jeux casino]
 * in narrative, a speech by a character may begin in the middle of a paragraph and continue for several more paragraphs
 * in a verse text, the encoder may need to tag both the formal structure of the verse (its stanzas and lines) and its syntactic structures (which sometimes nest within the metrical structure and sometimes cross metrical boundaries)
@@ Line 22: / Line 22: @@
 * in any kind of text, an embedded text (e.g. a play within a play, or a song) may be interrupted by other matter; the encoder may wish to establish explicitly the logical unity of the embedded material (e.g. to identify the song as a single song, and to mark its internal formal structure)
 * in a dictionary, different types of information (e.g. orthography, syllabification, and hyphenation) may be combined within a single notation; the encoder may wish both to preserve the presentation of the material in the source text and to disentangle the logically distinct pieces of information in the interests of more convenient processing of the lexical information
-−
 Below are some approaches for using multiple hierarchies in XML, both for encoding them and for processing them.

@@ Line 15: / Line 15: @@
 The TEI P4 Guidelines provide a chapter that discusses some ways to deal with markup that is not hierarchical (Chapter 31, "Multiple Hierarchies", http://www.tei-c.org/P4X/NH.html). Specific problems mentioned in that chapter include many that should be familiar to even the most basic user of TEI markup:
+* [http://www.jouercasino.eu/ jeux casino]
 * in narrative, a speech by a character may begin in the middle of a paragraph and continue for several more paragraphs
 * in a verse text, the encoder may need to tag both the formal structure of the verse (its stanzas and lines) and its syntactic structures (which sometimes nest within the metrical structure and sometimes cross metrical boundaries)
@@ Line 22: / Line 22: @@
 * in any kind of text, an embedded text (e.g. a play within a play, or a song) may be interrupted by other matter; the encoder may wish to establish explicitly the logical unity of the embedded material (e.g. to identify the song as a single song, and to mark its internal formal structure)
 * in a dictionary, different types of information (e.g. orthography, syllabification, and hyphenation) may be combined within a single notation; the encoder may wish both to preserve the presentation of the material in the source text and to disentangle the logically distinct pieces of information in the interests of more convenient processing of the lexical information
-−
+*
 Below are some approaches for using multiple hierarchies in XML, both for encoding them and for processing them.

@@ Line 167: / Line 167: @@
 '''Abstract''': The way in which text is represented on a computer affects the kinds of uses to which it can be put by its creator and by subsequent users. The electronic document model currently in use is impoverished and restrictive. The authors argue that text is best represented as an ordered hierarchy of content object (OHCO), because that is what text really is. This model conforms with emerging standards such as SGML and contains within it advantages for the writer, publisher, and researcher. The authors then describe how the hierarchical model can allow future use and reuse of the document as a database, hypertext, or network.
 *A. Renear, et al. "Refining our Notion of What Text Really Is: The Problem of Overlapping Hierarchies" (http://www.stg.brown.edu/resources/stg/monographs/ohco.html)
@@ Line 179: / Line 178: @@
 *D. Barnard et al. (1988) 'SGML-Based Markup for Literary Texts: Two Problems and Some Solutions', Computers and the Humanities 22: 265-276.
 * David Barnard, Lou Burnard, Jean-Pierre Gaspart, Lynne A. Price, Michael Sperberg-McQueen, and Giovanni Battista Varile. "Hierarchical Encoding of Text: Technical Problems and SGML Solutions." In The Text Encoding Initiative: Background and Contents. Guest Editors: Nancy Ide and Jean Veronis. Computers and the Humanities 29/3 (1995), pages 211-231. (http://xml.coverpages.org/bib-ab.html#barnardHierarchicalCHUM)
 * D. Schmidt and R. Colomb (2009) 'A data structure for representing multi-version texts online', International Journal of Human-Computer Studies, 67.6, 497-514.

← Older revision		Revision as of 23:28, 5 April 2009
Line 182:		Line 182:

	* David Barnard, Lou Burnard, Jean-Pierre Gaspart, Lynne A. Price, Michael Sperberg-McQueen, and Giovanni Battista Varile. "Hierarchical Encoding of Text: Technical Problems and SGML Solutions." In The Text Encoding Initiative: Background and Contents. Guest Editors: Nancy Ide and Jean Veronis. Computers and the Humanities 29/3 (1995), pages 211-231. (http://xml.coverpages.org/bib-ab.html#barnardHierarchicalCHUM)		* David Barnard, Lou Burnard, Jean-Pierre Gaspart, Lynne A. Price, Michael Sperberg-McQueen, and Giovanni Battista Varile. "Hierarchical Encoding of Text: Technical Problems and SGML Solutions." In The Text Encoding Initiative: Background and Contents. Guest Editors: Nancy Ide and Jean Veronis. Computers and the Humanities 29/3 (1995), pages 211-231. (http://xml.coverpages.org/bib-ab.html#barnardHierarchicalCHUM)
		+
		+	* D. Schmidt and R. Colomb (2009) 'A data structure for representing multi-version texts online', International Journal of Human-Computer Studies, 67.6, 497-514.

@@ Line 140: / Line 140: @@
 ==== MVD Multi-Version Document Format ====
-Multi-version documents can be used to generally model overlapping hierarchies and textual variation without drawbacks. The MVD format encodes all overlapping structures as a directed graph with one start and one end-point. The arcs of the graph contain the content of each version or encoding perspective, which may contain markup. The versions are the different paths that the text takes through the graph from start to finish. The graph can also be written out as a sequence of pairs, each of which contains a set of versions and a piece of text. This list form can also be converted back into the graph form without loss of information. Efficient procedures exist for
+Multi-version documents can be used to generally model overlapping hierarchies and textual variation without drawbacks. The MVD format encodes all overlapping structures as a directed graph with one start and one end-point. The arcs of the graph contain the content of each version or encoding perspective, which may contain markup. The versions are the different paths that the text takes through the graph from start to finish. The graph can also be written out as a sequence of pairs, each of which contains a set of versions and a piece of text. This list form can also be converted back into the graph form without loss of information. Efficient procedures exist for:
 # listing of a given version
 # comparing two versions
-# search all versions for some text
+# searching all versions for some text
 # finding the variants of a piece of text
 # creating and editing an MVD
-An MVD can represent insertions, deletions, substitutions (or variants) and transpositions. [http://www.itee.uq.edu.au/~schmidt/_articles/elsevier.pdf A paper describing the technology] has been accepted by the International Journal of Human-Computer Studies. See http://multiversiondocs.blogspot.com for further information, in particular, the 'What is an Multi-Version Document' link.
+An MVD can represent insertions, deletions, substitutions (or variants) and transpositions. [http://dx.doi.org/10.1016/j.ijhcs.2009.02.001 A paper describing the technology] has been published by the International Journal of Human-Computer Studies. See http://multiversiondocs.blogspot.com for further information, in particular, the 'What is an Multi-Version Document' link.
 ==== Other Non-XML Approaches ====

@@ Line 140: / Line 140: @@
 ==== MVD Multi-Version Document Format ====
-Multi-version documents can be used to generally model overlapping hierarchies and textual variation without drawbacks. The MVD format encodes all overlapping structures as a directed graph with one start and one end-point. The arcs of the graph contain the content of each version or encoding perspective, which may contain markup. The versions are the different paths that the text takes through the graph from start to finish. The graph can also be written out as a sequence of pairs, each of which contains a set of versions and a piece of text. This list form can also be converted back into the graph form without loss of information.
+Multi-version documents can be used to generally model overlapping hierarchies and textual variation without drawbacks. The MVD format encodes all overlapping structures as a directed graph with one start and one end-point. The arcs of the graph contain the content of each version or encoding perspective, which may contain markup. The versions are the different paths that the text takes through the graph from start to finish. The graph can also be written out as a sequence of pairs, each of which contains a set of versions and a piece of text. This list form can also be converted back into the graph form without loss of information. Efficient procedures exist for
-[[Image:Fig5.jpg]]Efficient procedures exist for
 a) listing of a given version
 b) comparing two versions
 c) search all versions for some text
 d) finding the variants of a piece of text
 e) creating and editing an MVD
 [http://www.itee.uq.edu.au/~schmidt/_articles/elsevier.pdf A paper describing the technology] has been accepted by the International Journal of Human-Computer Studies. See http://multiversiondocs.blogspot.com for further information, in particular, the 'What is an Multi-Version Document' link.