TEIWiki - User contributions [en]

User:Stuart

2006-01-19T12:09:41Z

Stuart:

'''Stuart Brown'''

TEI Junkie

stuart at stuartadrianbrown dot net

User:Stuart

2006-01-19T12:09:29Z

Stuart:

'''Stuart Brown'''
TEI Junkie
stuart at stuartadrianbrown dot net

SIG:Overlap

2006-01-19T12:06:25Z

Stuart: Nasty spam links removed

[[Category:SIG]]

== Introduction ==
The goal of the TEI Overlapping Markup SIG is to bring together users of the TEI who are acutely interested in issues of multiple hierarchies and in particular handling those in XML.
It will do this by:
#running a mailing list about overlapping hierarchies and solutions to encoding them
#assess the TEI and suggest improvements and alterations to the TEI-Council
The SIG is convened by Dot Porter ([mailto:dporter@uky.edu dporter@uky.edu]). If you have developed an approach to overlapping markup, you'd like to comment on existing approaches below, or if you would like to add a citation to the bibliographies, please feel free to log into the Wiki and add you contributions.
The SIG runs a mailing list on this topic. To join visit

== Approaches to Handling Overlapping XML Markup ==

=== Multiple Hierarchies ===

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:

* 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)
* in any kind of text, the encoder may wish to record the physical structure of volume, page, column, and line, as well as the formal or logical structure of chapters and paragraphs or acts and scenes, etc.
* in verse drama, the structure of acts, scenes, and speeches often conflicts with the metrical structure
* 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.

==== Kentucky GODDAG ====

Bibliography:

*"The Extended XPath language (EXPath) for querying Concurrent Markup Hierarchies," from the website of Ionut Emil Iacob (Research in Computing for Humanities, University of Kentucky). http://dblab.csr.uky.edu/%7Eeiaco0/docs/expath/index.html

ABSTRACT: This document provides semantics of the Extended XPath language (EXPath) for Concurrent Markup Hierarchies (CMH).

*I. Iacob et al. "XPath Extension for Querying Concurrent XML Markup", (University of Kentucky, Department of Computer Science), Technical Report TR394-04, February 2004. http://dblab.csr.uky.edu/%7Eeiaco0/publications/TR394-04.pdf

ABSTRACT: XPath is a language for addressing parts of an XML document. It is used in many XML query languages and it can be used by itself for querying XML documents. While XPath is, in general, efficient for querying individual XML documents, it lacks the features for querying over collections of documents or joining parts of the same document.

As the amount of complex document-centric XML data is continually increasing, querying such documents has drawn surprisingly little attention. We propose an XPath axes extension to deal with querying collections of document-centric XML documents sharing the same content (called concurrent XML). The algorithms we propose to evaluate the extended axes work in linear time combined complexity (number of documents and total size of documents).

*A. Dekhtyar et al. "A Framework For Management of Concurrent XML Markup," (2005) Data and Knowledge Engineering, Vol. 52, No. 2, pp. 185 - 215. http://dblab.csr.uky.edu/%7Eeiaco0/publications/dke04-concurrent.pdf

ABSTRACT: The problem of concurrent markup hierarchies in XML encodings of documents has attracted attention of a number of humanities researchers in recent years. The key problem with using concurrent hierarchies to encode documents is that markup in one hierarchy is not necessarily well-formed with respect to the markup in another hierarchy. Previously proposed solutions to this problem rely on the XML expertise of the editors and their ability to maintain correct DTDs for complex markup languages. In this paper, we approach the problem of maintenance of concurrent XML markup from the Computer Science perspective. We propose a framework that allows the editors to concentrate on the semantic aspects of the encoding, while leaving the burden of maintaining XML documents to the software. The paper describes the formal notion of the concurrent markup languages and the algorighms for automatic maintenance of XML documents with concurrent markup.

==== HORSE ====

Bibliography:

*S. DeRose, "Markup Overlap: A Review and a Horse", Extreme Markup Languages 2004: Proceedings http://www.mulberrytech.com/Extreme/Proceedings/html/2004/DeRose01/EML2004DeRose01.html

INTRODUCTION: "Overlap" describes cases where some markup structures do not nest neatly into others, such as when a quotation starts in the middle of one paragraph and ends in the middle of the next. OSIS [Duru03], a standard XML schema for Biblical and related materials, has to deal with extreme amounts of overlap. The simplest is book/chapter/verse and book/story/paragraph hierarchies that pervasively diverge; but many types of overlap are more complicated than this.

The basic options for dealing with overlap in the context of SGML [ISO 8879] or XML [Bray98] are described in the TEI Guidelines [TEI]. I summarize these with their strengths and weaknesses. Previous proposals for expressing overlap, or at least kinds of overlap, don't work well enough for the severe and frequent cases found in OSIS. Thus, I present a variation on TEI milestone markup that has several advantages, though it is not a panacea. This is now the normative way of encoding non-hierarchical structures in OSIS documents.

Citations:

[Bray98] Tim Bray, Jean Paoli, C. M. Sperberg-McQueen. Extensible Markup Language (XML) 1.0. W3C Recommendation 10-February-1998.
[Duru03] Patrick Durusau and Steven J. DeRose. "OSIS: A Users' Guide to the Open Scripture Information Standard." Bible Technologies Group, 2003.
[ISO 8879] International Organization for Standardization. 1986. ISO 8879: 1986(E). Information Processing: Text and Office Information Systems: Standard Generalized Markup Language.
[TEI] Michael Sperberg-McQueen and Lou Burnard (eds). Technical Topics: Multiple Hierarchies. Chapter 31 in the TEI Guidelines for Electronic Text Encoding and Interchange. http://xml.coverpages.org/teichap31.html

*S. Bauman, "TEI HORSEing around: Handling overlap using the Trojan Horse method" Presentation at Extreme Markup 2005 (Link to be added following the conference)

ABSTRACT: The Text Encoding Initiative’s typed segment-boundary delimiter method is only one of several proposed mechanisms for handling overlap in TEI documents. HORSE (aka CLIX) defines a method by which an XML element is used normally when possible and as an improved version of the typed segment-boundary delimiter method when an overlap problem is encountered. A significant portion of the rules necessary for validation of HORSE markup can be expressed using Schematron. This, combined with an utter hack that can "HORSEify" the declaration of elements in a TEI Relax NG grammar, can provide a potential significant step forward in handling overlap in TEI documents.

==== Just-In-Time-Trees ====

==== Segment Trees ====

Bibliography:

*J. W. Jaromczyk, et al. "A web interface to image-based concurrent markup using image maps." Proceedings, 6th ACM International Workshop on Web Information and Data Management (WIDM 2004), November 12-13, 2004, Washington, DC.

*J. W. Jaromczyk, et al. "On Visualization of Complex Image-Based Markup," Proceedings, International Conference on Computer Vision and Geometry. Warsaw, Poland, September 2004.

*J. W. Jaromczyk and N. Moore, "Geometric data structures for multihierarchical XML tagging of manuscripts," Proceedings of the 20th European Workshop on Computational Geometry, Seville, Spain, March 2004.

==== Treespaces ====

From Peter van Hardenberg, University of Victoria ([mailto:pvh@uvic.ca pvh@uvic.ca])

In brief, a treespace document is a document which contains multiple XML documents within it. Treespaces are each, when viewed alone, valid XML documents, and include some syntax for assigning tags to a particular tree. Tags from differing trees may nest however is convenient.

The notion of the treespace is akin to that of the namespace. Just as a single DTD cannot encompass the full range of desired documents (particularly documents containing fragments from multiple sources), a single nesting tree cannot encode all documents. In essence, treespaces are a continuation of the OHCO hypotheses of Allen Renear. He proposes (with OHCO-3) that a document can be decomposed into multiple hierarchies, each one describing a "view" of a document. Unfortunately, this does not provide a conceptual mechanism for dealing with documents that may have overlapping trees combined from various structures.

To resolve this problem, trees must be considered to apply to a span of a document. This, in essence, creates a hybrid spanning/nesting model. Each tree is susceptible to the standard queries of any XML document and can have a DTD or Schema applied to it individually.

More work is necessary to determine useful extensions for determining relationships between trees.

Similarly, a suitably elegant syntax has not yet been developed.

Implementation of a "treespace" document structure is relatively easy aside from the above caveats. All parsers maintain a stack of "open" tags which are used for validation purposes. To extend an existing parser to test wellformedness of a treespace document requires maintaining a seperate tag-context for each tree. No support for relating trees has been considered at this time -- each tree stands alone in the current model.

====Other Approaches to Concurrent Hierarchies ====

*P. Durusau and M. O'Donnell, "Concurrent Markup for XML Documents", Presentation at XML Europe 2002 (http://www.idealliance.org/papers/xmle02/dx_xmle02/papers/03-03-07/03-03-07.html)

ABSTRACT: The implementation of concurrent markup by Durusau and O'Donnell (Extreme Markup 2001) relies upon related but separate principles. First, markup, commonly described in tree notation, is actually metadata about PCDATA. Second, the membership of any "atom of PCDATA" in a given hierarchy can be recorded as metadata for that PCDATA. These two principles have allowed the authoring and querying of overlapping hierarchies using standard XML software.

This presentation moves beyond the use of text snippets to illustrate overlapping hierarchies and applies the authors' technique to one of the classics of Western literature, John Milton's Paradise Lost. This research has resulted in the first release of overlapping texts for experimentation on overlapping hierarchies and in a firmer theoretical foundation for current and future research on this topic.

*R. Gartner presented at ACH/ALLC 2005 on integrating METS and TEI to handle concurrent hierarchies. (http://mustard.tapor.uvic.ca/cocoon/ach_abstracts/xq/xhtml.xq?id=125)

*H. V. Jagadish et al. "Colorful XML: One Hierarchy Isn't Enough", SIGMOD 2004 June 13-18, 2004, Paris, France. (http://www.research.att.com/~divesh/papers/jlssw2004-mct.pdf)

ABSTRACT: XML has a tree-structued data model, which is used to uniformly represent structured as well as semi-structured data, and also enable concise query specification in XQuery, via the use of its XPath (twig) patterns. This in turn can leverage the recently developed technology of structural join algorighms to evaluat the query efficiently. In this paper, we identify a fundamental tension in XML data modeling: (1) data represented as deep trees (which can make effective use of twig patterns) are often un-normalized, leading to update anomalies, while (ii) normalized data tends to be shallow, resulting in heavy use of expensive value-based joins in queries.

Our solution to this data modeling problem is a novel multi-colored trees (MCT) logical data model, which is an evolutionary extension of the XML data model, and permits trees with multi-colored nodes to signify their participation in multiple hierarchies. This adds significant semantic structure to individual data nodes. We extend XQuery expressions to navigate between structurally related nodes, taking color into account, and also to create new colored trees as restructurings of an MCT database. While MCT serves as a significant evolutionary extension to XML as a logical data model, one of the key roles of XML is for information exchange. To enable exchange of MCT information, we develop algorighms for optimally serializing an MCT database as XML. We discuss alternative physical representations for MCT databases, using relations and native XML databases, and describe an implementation on top of the Timber native XML database. Experimental evaluation, using our prototype implementation, shows that not only are MCT queries/updates more succinct and easier to express than equivalent shallow tree XML queries, but they can also be significantly more efficient to evaluate than equivalent deep and shallow tree XML queries/updates.

*A. Witt et al. "Unification of XML Documents with Concurrent Markup", Literary and Linguistic Computing Vol. 20, No. 1, 2005, pp. 103-116. (http://llc.oxfordjournals.org/cgi/reprint/20/1/103)

ABSTRACT: An approach to the unification of XML (Extensible Markup Language) documents with identical textual content and concurrent markup in the framework of XML-based multi-layer annotation is introduced. A Prolog program allows the possible relationships between element instances on two annotation layers that share PCDATA to be explored and also the computing of a target node hierarchy for a well-formed, merged XML document. Special attention is paid to identity conflicts between element instances, for which a default solution that takes into account metarelations that hold between element types on the different annotation layers is provided. In addition, rules can be specified by a user to prescribe how identity conflicts should be solved for certain element types.

=== Other Approaches to Overlapping XML Markup (not concurrent hierarchies) ===

=== Non-XML Approaches ===

==== Layered Markup Annotation Language ====
'''LMNL''', pronounced ''liminal'': "an experimental approach to digital text encoding that supports, in SGML/XML terms, overlapping elements (ranges in LMNL) and structured attributes (annotations in LMNL)."<br>
Project website includes a tutorial and much other informative material: http://www.lmnl.net/index.html

==== TexMECS ====

C. Huitfeldt and C. M. Sperberg-McQueen, "TexMECS: An experimental markup meta-language for complex documents", 25 January 2001, rev. 17 February 2001 (http://helmer.aksis.uib.no/claus/mlcd/papers/texmecs.html)

==== Other Non-XML Approaches ====

Bibliography:

*M. Hilbert et al. "Making CONCUR work," Presentation at Extreme Markup 2005 (Link to be added following the conference)

ABSTRACT:

The SGML feature CONCUR allowed for a document to be simultaneously marked up in multiple conflicting hierarchical tagsets but validated and interpreted in one tagset at a time. Alas, CONCUR was rarely implemented, and XML does not address the problem of conflicting hierarchies at all. The MuLaX document syntax is a non-XML syntax that enables multiply-encoded hierarchies by distinguishing different “layers” in the hierarchy by adding a layer ID as a prefix to the element names. The IDs tie all the elements in a single hierarchy together in an “annotation layer”. Extraction of a single annotation layer results in a well-formed XML document, and each annotation layer may be associated with an XML schema. The MuLaX processing model developed works on the nodes of one annotation layer at a time. Furthermore, an alternative processing model is proposed which uses a multi-rooted trees approach. CONCUR lives!

== General Bibliography ==

*S. J. DeRose et al. (1990), 'What is Text, Really?', Journal of Computing in Higher Education, 1.2: 3-26.

Full-text available through ACM Portal (subscription only): http://portal.acm.org/citation.cfm?doid=264842.264843

'''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)

'''Abstract''': We examine the claim that 'text is an ordered hierarchy of content objects'; this thesis was affirmed by the authors, and others, in the late 1980s and has been associated with certain approaches to text processing and the encoding of literary texts. First we discuss the nature of this claim and its connection with the history of text processing and text encoding standardization projects such as SGML and the Text Encoding Initiative. We then describe how the experience of the text encoding community, as represented and codified in the TEI Guidelines, has raised difficulties for this thesis. Next we consider two progressively weaker versions of this thesis formulated in response to these difficulties. Ultimately we find that no version appears to be free from counterexample.

Although none of these formulations proves to be theoretically sound, they are nonetheless methodologically illuminating as each generalizes actual encoding practices, making explicit certain assumptions that, even though they have been fundamental to the working methodologies of most text encoding projects, have never been explicitly articulated, let alone explained or defended. The counterexamples to the different versions of the OHCO thesis also arise in actual encoding projects -- so although our focus is theoretical it is grounded in the methodology and problems of contemporary encoding practices. The problems discussed here have implications not only for text encoding and our understanding of the nature of textual communication, but raise very fundamental issues in the logic and methodology of the humanities.

*D. Durand, et al. "What should markup really be? Applying theories of text to the design of markup systems," talk presented at ACH 1996 (http://cs-people.bu.edu/dgd/ach96_talk/Redefining_long.html)

*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)

SIG:Education

2006-01-19T12:05:59Z

Stuart: Nasty spam links removed

Holding page for TEI Training SIG

[[Category:SIG]]

SIG:MSS

2006-01-19T12:05:36Z

Stuart: Nasty spam links removed

== TEI Special Interest Group on Manuscripts (TEI MS SIG) ==

=== Introduction ===

The goal of the TEI Special Interest Group on Manuscripts is to bring together users of the TEI who whish to improve the encoding strategies for marking up transcriptions and editions of manuscript materials.

This SIG will explore a range of issues common to editing manuscripts, including:
# how to handle time based encoding
# how to record place based encoding
# how to encode fragments
# how to record codicology (the substance of the medium, ink stints, etc); Robinson noted that the TEI already has mechanisms to record this, but it needs to be better documented
# issues of substitutions
# issues of variation
# to clarify the role of using the critical apparatus tagset in manuscript transcription (which is dependent on whether one is encoding an edition or encoding a manuscript transcription)

It will do this by:
* running a mailing list on this topic
* assess the TEI and suggest improvements/alterations to the TEI-Council

The SIG is setup by:
* Elena Pierazzo of the University of Pisa (Italy)
* Susan Schreibman of the Maryland Institute for Technology in the Humanities (US), who is also a member of the TEI Council.
* Edward Vanhoutte of the Centre for [http://www.kantl.be/ctb/ Scholarly Editing and Document Studies] of the Royal Academy of Dutch Language and Literature (Belgium), who is also a member of the TEI Council.

The SIG is convened by Edward Vanhoutte who also manages the TEI-MS-SIG List

The SIG runs a mailing list on this topic. To join visit http://listserv.brown.edu/tei-ms-sig.html

=== Activities ===

The SIG met at the Third Annual TEI Members' Meeting in Nancy, France on 08 November 2003. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr01.html here].

The second meeting of the SIG was held at the Fourth Annual TEI Members' Meeting at Johns Hopkins University, Baltimore, USA, 23 October 2004. The report can be found [http://www.tei-c.org.uk/Activities/SIG/Manuscript/mssigr02.html here].

[[Category:SIG]]

SIG:Tools

2006-01-19T12:05:17Z

Stuart: Nasty spam links removed

=Purpose=

The aim of the TEI Special Interest Group on Presentation Tools is to bring together members who wish to share information about XML presentation and querying tools. This covers:
* querying tools such as native XML databases
* web application servers such as Cocoon, PHP, JSP etc.
* presentation languages such as XSLT
The aim is to generate:
* a web resource where members can learn about different presentation and querying tools
* collaborations between members using the same tools

=To Participate=

To join the discussion list on this topic, send a blank email to join-tei-presentation@forums.nyu.edu

or

Contribute to this WIKI

== Tools ==

This wiki has a [[:Category:Tools]] to allow people to categorise pages they create about tools.

[[Category:SIG]]

Stylesheets

2006-01-19T12:04:53Z

Stuart: Nasty spam links removed

* [[:Call for stylesheets]]
* [[:Category:XSLT|XSLT]]
* [[:Category:CSS|CSS]]

Category:XSLT

2006-01-19T12:04:20Z

Stuart: Nasty spam links removed

This page collects together any pages relating to XSLT (Extensible Stylesheet Language Transformations) for TEI resources. The main TEI website has [http://www.tei-c.org/Stylesheets/ a page about stylesheets] as well. 

All of the stylesheets posted here are freely available for public use. They are offered as is, and we make no guarantees about their usefulness or effectiveness. Please feel free to experiment with them. If you make any useful revisions, please post the modified version here.
The [[call for stylesheets]] includes more details about what we are seeking and how you can help.
----
'''To contribute a stylesheet, please email your stylesheet with accompanying information to [mailto:stylesheets@tei-c.org stylesheets@tei-c.org] or you can create a new page within this category and post your stylesheet.'''
<p>
'''To create a new page and post your stylesheet, you should:'''
* Log in (Create a user account for this WIKI if you have not done so.)
* Add a new page.
** To do this, add the name of the new page to the URL in your browser's address bar after index.php/
** For example, if you wish to create a new page called "MyNewStylesheet.xsl", just edit the URL in your web browser's address bar to look like this: '''<nowiki>http://www.tei-c.org.uk/wiki/index.php/MyNewStylesheet.xsl</nowiki>'''
* Assuming no one else has made a page with the name you chose, you will be brought to a blank page. Click the edit button and do the following:
** Provide some accompanying explanation at the top of the page
** Cut and paste your stylesheet into the window.
** Wrap any stylesheet content in <nowiki><pre> .... </pre></nowiki> tags
** Add the text <nowiki>[[Category:XSLT]]</nowiki> to the bottom of the page. This is important. It ensures that your page will show up on the XSLT page.
** Click "Save Page" when you are finished. Your page should show up on this page in the list of stylesheets. You can go back and edit at any time.
** As a reference [[SampleXSLTPage]] displays the text that was entered to create the [[Remove-Namespaces.xsl]] page.
* '''Note:''' We strongly suggest providing a Summary, and information about Required Input, Expected Output, and Known Restrictions or Problems before the Stylesheet itself, as done in the [[SampleXSLTPage]].
</p>

Call for stylesheets

2006-01-19T12:03:34Z

Stuart: Nasty spam links removed

The TEI is beginning an initiative to collect and disseminate well-documented XSLT and CSS stylesheets for TEI data. This call for submissions is an invitation to anyone who has developed a useful stylesheet and would like to share it with the TEI community. We have several goals in mind for this project:

*to make existing stylesheets available to a wider audience
*to provide good models for people designing their own stylesheets
*to allow existing stylesheets to be improved and the results shared with the community
You may submit stylesheets to the [http://www.tei-c.org.uk/wiki/ TEI wiki]
A few points:
*all stylesheets will be made available at the TEI web site. We will categorize what we receive based on function and level of documentation.
*all submitted stylesheets will be distributed under a GNU Lesser Public License, which allows them to be freely redistributed, modified, and incorporated into other software tools as long as any copy continues to carry the GLPL. Please let us know if you strongly prefer some other license.
*stylesheets submitted may be of any sort, as long as they work on TEI documents: they may produce HTML, XML of any sort, XSL FO, RTF, OpenOffice, etc.
*all submitted stylesheets should be accompanied by some documentation. At the very least, we appreciate a brief statement of what kind of TEI document the stylesheet expects as input, and what kind of output it produces. Best of all are stylesheets that have detailed comments, so that other users can understand how they work and modify them further.
*stylesheets need not be general-purpose. If you have come up with an immensely clever way to display the TEI header, or a highly artistic display for sonnets that places them in a grid of varying colors, please feel free to share these.

Category:CSS

2006-01-19T12:03:04Z

Stuart: Nasty spam links removed

This page collects together any pages relating to CSS (Cascading Style Sheets) for TEI resources. The main TEI website has [http://www.tei-c.org/Stylesheets/ a page about stylesheets] as well. 
All of the stylesheets posted here are freely available for public use. They are offered as is, and we make no guarantees about their usefulness or effectiveness. Please feel free to experiment with them. If you make any useful revisions, please post the modified version here.
The [[call for stylesheets]] includes more details about what we are seeking and how you can help.
----
'''To contribute a stylesheet, please email your stylesheet with accompanying information to foo@foo.org or you can create a new page within this category and post your stylesheet.'''

Category:Interfaces

2006-01-19T12:02:37Z

Stuart: Nasty spam links removed

This page collects the different interfaces for versioning systems

CSV2TEI.xsl

2006-01-19T12:02:04Z

Stuart: Nasty spam links removed

== Summary ==

This stylesheet takes a comma-separated-values file and converts it to a basic TEI table structure.

Add any comments to the 'discussion' tab.

== Required Input ==

Using Saxon 8 or above use it as:

'''saxon -it main styesheet.xsl input-uri=filename.csv'''

So input can be any file resembling:
<pre>
<nowiki>
This,is,a,test,only,a,test!
This, is a, variation, on a, test!
"This","is","another","variation."
</nowiki>
</pre>

== Expected Output ==

The output is a TEI table with table, rows and cells but nothing else which can then be cut-and-pasted into a TEI document.
For example, with the above input, the output should be:
<pre>
<nowiki>
<table>
<row>
<cell>This</cell>
<cell>is</cell>
<cell>a</cell>
<cell>test</cell>
<cell>only</cell>
<cell>a</cell>
</row>
<row>
<cell>This</cell>
<cell>is a</cell>
<cell>variation</cell>
<cell>on a</cell>
</row>
<row>
<cell>This</cell>
<cell>is</cell>
<cell>another</cell>
<cell>variation.</cell>
</row>
</table>
</nowiki>
</pre>

== Known Restrictions or Problems ==

Note:
* It assumes cells are comma separated and rows are on individual lines
* If surrounded in double-quotes, it will remove them.
* It normalize-space()s the individual cell contents so leading/trailing spaces
are removed.
* It assumes things are in UTF-8 but this can be changed with the encoding
parameter output is converted to UTF-8.
* It is an XSLT2 stylesheet and requires an XSLT2 processor such as Saxon8

== Stylesheet ==
<pre>
<nowiki>
<?xml version="1.0"?>


<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
version="2.0" exclude-result-prefixes="#all">
<xsl:param name="input-uri" as="xs:string"/>
<xsl:param name="encoding" select="'UTF-8'" as="xs:string"/>
<xsl:output indent="yes" encoding="UTF-8" />

<xsl:template name="main">
<xsl:variable name="in"
select="unparsed-text($input-uri, $encoding)"/>
<table>
<xsl:analyze-string select="$in" regex="\n">
<xsl:non-matching-substring>
<row>
<xsl:analyze-string select="."
regex='("([^"]*?)")|([^,]+?),'>
<xsl:matching-substring>
<cell>
<xsl:value-of select="normalize-space(regex-group(2))"/>
<xsl:value-of select="normalize-space(regex-group(3))"/>
</cell>
</xsl:matching-substring>
</xsl:analyze-string>
</row>
</xsl:non-matching-substring>
</xsl:analyze-string>
</table>
</xsl:template>

</xsl:stylesheet>
</nowiki>
</pre>

[[Category:XSLT]]
[[Category:XSLT:2.0]]

IRC

2006-01-19T12:01:06Z

Stuart: Nasty spam links removed

== Introduction ==

Although it is completely unofficial, a number of us involved with the [http://www.tei-c.org/ Text Encoding Initiative] have been hanging out in an Internet Relay Chat (IRC) channel. This allows us to communicate on all sorts of topics quickly, and occasionally a bit of social banter. In order to join into the network and the #tei-c channel you will need to use an IRC client which you run on your computer.

The technical information needed is:
* Server: '''irc.freenode.net'''
* Channel: '''#tei-c'''

More information is available about the [http://freenode.net/ freenode network] if you wish.

== IRC Commands ==
IRC is at its heart a text-based discussion network. This network is controlled by text-based commands prefixed with a '/'. Text without this command prefix is sent to the chat channel. In many modern clients there are graphical buttons or other methods instead of typing the following commands. However, for reference, some basic IRC commands are:

* '''/away [message]''' (Set an away message, or use no message to return from being away)
** /away In a meeting, back at 1pm
* '''/invite <nick> [channel]''' (Invite a user to join the current or a specific channel)
** /invite JuliaF #tei-c
* '''/join <channel>''' (Join an existing or new IRC channel)
** /join #tei-c
* '''/list''' (Display a list of channels on a server. '''Warning, this can be quite large!''')
** /list
* '''/me <action to perform>''' (Perform an action in a channel or private chat)
** /me yawns and falls asleep over Chapter 16.
* '''/msg <nick> <message>''' (Send a private message to a user (as opposed to a channel))
** /msg Syd What is your opinion on floating <div> elements?
* '''/names [channel]''' (List the users currently in a channel)
** /names #tei-c
* '''/nick <new nickname>''' (Change your nickname)
** /nick SebastianR
* '''/part [room] [message]''' (Leave the current channel, or a specified channel, with an optional message)
** /part #tei-c I'm off to the pub!
* '''/ping [nick]''' (Asks how much lag a user (or the server if no user specified) has)
** /ping LOU
* '''/quit [message]''' (Disconnect from the server, with an optional message)
** /quit I'm off to the pub!
* '''/whois <nick>''' (Get information on a user)
** e.g. /whois James-C

There are other commands, but those basic ones should allow you to participate fully in discussions. Some clients remove the ability to send these commands in this way and implement other ways to send them on your behalf.

== Freenode 'NickServ' Service ==

Freenode provides a method of your to have control over a static nickname. The 'NickServ' service allows you to register a nickname and prevent others from using it. The following commands allow for registration and maintenance of nicknames; to use them, type '''/msg NickServ <command>'''.
For more information on a specific command, type '''/msg NickServ help <command>''' where <command> is any of:

* '''access''' (Modify the list of authorized addresses)
* '''drop''' (Cancel the registration of a nickname)
* '''ghost''' (Kill a ghosted nickname)
* '''identify''' (Identify yourself with your password)
* '''info''' (Get information for a nickname)
* '''link''' (Link your nickname to another)
* '''list''' (Display list of nicks matching a pattern)
* '''recover''' (Kill another user who has taken your nick)
* '''register''' (Register a nickname)
* '''release''' (Regain custody of your nick after RECOVER)
* '''set''' (Set various options for your nickname)
* '''unlink''' (UnLink your nickname)

== Channel Robot ==

Currently sitting on the #tei-c channel is a fake user. This user is the venerable 'BedeBot', an [http://www.eggheads.org/ Eggdrop] IRC robot. While most of his functions have been turned off, there are a number of commands setup up for the benefit of #tei-c users. He is unofficial and there is no guarantee that he will be inhabiting the channel when you visit. His knowledge of TEI is generated from the TEI P5 CVS files but not done so automatically so he may not always be up to date.

TEI P5:
* '''? tei:elementName''' (Display the description of a particular P5 element)
** ? tei:teiHeader
* '''? @attribute''' (Display the description of the first definition of an attribute in the guidelines) '''N.B.: This should be revised to show all instances of that attribute, when I have time.'''
** ? @desc
* '''? tei.className''' (Display the description of a particular P5 class)
** ? tei.phrase

'''N.B.''': You should provide a space between the question-mark and the tei-style keyword.

Google:
* '''!google <google search term>''' (Search google for the top 4 results of your keywords)
** !google Text Encoding Initiative
** !g TEI XSLT stylesheets (!g is an alternative short form for !google)
** !g site:tei-c.org overlap (various google search options are available)
** !g 23 C in F (conversions are part of google search options)
* '''!image <google image search term>''' (Search google for images)
** !image Lou Burnard
** !gi Julia Flanders (!gi is an alternative short form for !image)
* '''!local <what> near <where>''' (Search google local)
** !local pubs near oxford
** !gl restaurants near 90210 (Google local accepts post/zip codes)

There is also a freenode channel robot present in the channel as well 'ChanServ' whose purpose is to keep the channel open, and lock the topic.

== Setup for Specific Clients ==

If you want to add installation instructions, helpful hints, or suggested customisations and links for specific clients, do it here.

=== Gaim ===

Gaim is a multi-protocol multi-operating system client that allows connection not only to IRC, but AIM/AOL, MSN, Yahoo, Jabber/Gmail, and other chat protocols all from a single client.

* http://gaim.sourceforge.net/

=== XChat ===

XChat is a multi-operating system IRC client

* http://www.xchat.org/

=== Chatzilla ===

Chatzilla is a a firefox extension IRC client. If you have it installed then [irc://irc.freenode.net irc://irc.freenode.net] url should take you straight to the #tei-c channel.

* https://addons.mozilla.org/extensions/moreinfo.php?id=16

== IRC-Related Links ==
* http://freenode.net/ (The irc.freenode.net network website)
* http://www.irc.org/

Apache Cocoon

2006-01-19T11:50:24Z

Stuart: Nasty spam links removed

= Summary =

Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development. The TEI consortium website is dynamically produced from TEI XML using Cocoon.

= Description =

Apache Cocoon is a web development framework built around the concepts of separation of concerns (making sure people can interact and collaborate on a project, without stepping on each other toes) and component-based web development.

Cocoon implements these concepts around the notion of "component pipelines", each component on the pipeline specializing on a particular operation. This makes it possible to use a "building block" approach for web solutions, hooking together components into pipelines without any required programming.

Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of the two sides, improving development pace and reducing the chance of conflicts.

Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure.

Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, SAP® systems and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion.

= Installation Notes =

There are many different ways to install Cocoon, and so it is probably best that you look at the [http://cocoon.apache.org/2.1/installing/index.html Cocoon installation instructions]. However, those of you using debian-compatible systems can install a packaged version of cocoon maintained by Sebastian Rahtz. See: http://tei.oucs.ox.ac.uk/teideb/

= External Links =

* http://cocoon.apache.org/
* http://cocoon.apache.org/2.1/installing/index.html
* http://cocoon.apache.org/2.1/introduction.html
* http://tei.oucs.ox.ac.uk/teideb/

[[Category:Tools]]

Category:Tools

2006-01-19T11:49:59Z

Stuart: Nasty spam links removed

This page collects together any pages relating to Tools for use with TEI resources. Any wiki pages which include '''<nowiki>[[Category:Tools]]</nowiki>''' will appear here.

----
<p>
'''To create a new page and post your description of a tool, you should:'''
* Log in (Create a user account for this WIKI if you have not done so.)
* Add a new page.
** To do this, add the name of the new page to the URL in your browser's address bar after index.php/
** For example, if you wish to create a new page called "ApacheCocoon", just edit the URL in your web browser's address bar to look like this: '''<nowiki>http://www.tei-c.org.uk/wiki/index.php/ApacheCocoon</nowiki>'''
* Assuming no one else has made a page with the name you chose, you will be brought to a blank page. Click the edit button and do the following:
** Provide your description of the tool with as much information as you can, including at least a Summary, Description, Installation Notes, and External Links.
** Wrap any non-wiki content (scripts, code, command-line setup instructions, etc.)in <nowiki><nowiki><pre> .... </pre></nowiki></nowiki> tags
** Add the text <nowiki>[[Category:Tools]]</nowiki> to the bottom of the page. This is important. It ensures that your page will show up on the Tools page.
** Preview and then Save your page and you are finished. You can go back and edit at any time.

Current events

2006-01-19T11:48:07Z

Stuart: Nasty spam links removed; was the page previously empty? Because it is now.

Category:Customization

2006-01-19T11:47:28Z

Stuart: Nasty spam links removed

This page collects together any pages relating to customizations of the TEI schemas. If you have created a customization that you think may be of use to others in the TEI community, then the TEI wiki is one place to put it.
All of the customizations posted here are freely available for public use. They are offered as is, and we make no guarantees about their usefulness or effectiveness. Please feel free to experiment with them. If you make any useful revisions, please post the modified version here. Customizations can be made on the web via [[Roma]], and saved as [[ODD]] files. It is these saved customizations which we are encouraging people to share.
----
'''To create a new page and post your customization, you should:'''
* Log in (Create a user account for this WIKI if you have not done so.)
* Add a new page.
** To do this, add the name of the new page to the URL in your browser's address bar after index.php/
** For example, if you wish to create a new page called "MyNewCustomization.odd", just edit the URL in your web browser's address bar to look like this:
'''<nowiki>http://www.tei-c.org.uk/wiki/index.php/MyNewCustomization.odd</nowiki>'''
* Assuming no one else has made a page with the name you chose, you will be brought to a blank page. Click the edit button and do the following:
** Provide accompanying detailed explanation at the top of the page
** Cut and paste your ODD into the window.
** Wrap any ODD content content in <nowiki></nowiki>

Roma

2006-01-19T11:46:37Z

Stuart: Nasty spam links removed

Roma is the TEI tool for creating schemas an customisations from [http://www.tei-c.org/P5/ P5] [[ODD]] specifications.

See http://www.tei-c.org/Roma/