Serveur d'exploration sur la TEI

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Library as virtual abbey

Identifieur interne : 000169 ( Istex/Corpus ); précédent : 000168; suivant : 000170

Library as virtual abbey

Auteurs : Robert Fox

Source :

RBID : ISTEX:C2DB569658374CB92253686134291328DF266272

Abstract

Purpose The purpose of this paper is to explore the current state of the text encoding initiative TEI community and suggests directions in which that community should strive based on recommendations from experts in the field. Designmethodologyapproach Looks at the history of, the present state of and future of TEI. Findings This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium. Practical implications TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least. Originalityvalue This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by nonexperts, can be expanded in order to enrich scholarship.

Url:
DOI: 10.1108/10650750810875421

Links to Exploration step

ISTEX:C2DB569658374CB92253686134291328DF266272

Le document en format XML

<record>
<TEI wicri:istexFullTextTei="biblStruct">
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">Library as virtual abbey</title>
<author wicri:is="90%">
<name sortKey="Fox, Robert" sort="Fox, Robert" uniqKey="Fox R" first="Robert" last="Fox">Robert Fox</name>
<affiliation>
<mods:affiliation>Notre Dame University Libraries, Notre Dame, Indiana, USA</mods:affiliation>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">ISTEX</idno>
<idno type="RBID">ISTEX:C2DB569658374CB92253686134291328DF266272</idno>
<date when="2008" year="2008">2008</date>
<idno type="doi">10.1108/10650750810875421</idno>
<idno type="url">https://api.istex.fr/document/C2DB569658374CB92253686134291328DF266272/fulltext/pdf</idno>
<idno type="wicri:Area/Istex/Corpus">000169</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title level="a" type="main" xml:lang="en">Library as virtual abbey</title>
<author wicri:is="90%">
<name sortKey="Fox, Robert" sort="Fox, Robert" uniqKey="Fox R" first="Robert" last="Fox">Robert Fox</name>
<affiliation>
<mods:affiliation>Notre Dame University Libraries, Notre Dame, Indiana, USA</mods:affiliation>
</affiliation>
</author>
</analytic>
<monogr></monogr>
<series>
<title level="j">OCLC Systems & Services: International digital library perspectives</title>
<idno type="ISSN">1065-075X</idno>
<imprint>
<publisher>Emerald Group Publishing Limited</publisher>
<date type="published" when="2008-05-30">2008-05-30</date>
<biblScope unit="volume">24</biblScope>
<biblScope unit="issue">2</biblScope>
<biblScope unit="page" from="80">80</biblScope>
<biblScope unit="page" to="86">86</biblScope>
</imprint>
<idno type="ISSN">1065-075X</idno>
</series>
<idno type="istex">C2DB569658374CB92253686134291328DF266272</idno>
<idno type="DOI">10.1108/10650750810875421</idno>
<idno type="filenameID">1640240202</idno>
<idno type="original-pdf">1640240202.pdf</idno>
<idno type="href">10650750810875421.pdf</idno>
</biblStruct>
</sourceDesc>
<seriesStmt>
<idno type="ISSN">1065-075X</idno>
</seriesStmt>
</fileDesc>
<profileDesc>
<textClass></textClass>
<langUsage>
<language ident="en">en</language>
</langUsage>
</profileDesc>
</teiHeader>
<front>
<div type="abstract">Purpose The purpose of this paper is to explore the current state of the text encoding initiative TEI community and suggests directions in which that community should strive based on recommendations from experts in the field. Designmethodologyapproach Looks at the history of, the present state of and future of TEI. Findings This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium. Practical implications TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least. Originalityvalue This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by nonexperts, can be expanded in order to enrich scholarship.</div>
</front>
</TEI>
<istex>
<corpusName>emerald</corpusName>
<author>
<json:item>
<name>Robert Fox</name>
<affiliations>
<json:string>Notre Dame University Libraries, Notre Dame, Indiana, USA</json:string>
</affiliations>
</json:item>
</author>
<subject>
<json:item>
<lang>
<json:string>eng</json:string>
</lang>
<value>Markup languages</value>
</json:item>
<json:item>
<lang>
<json:string>eng</json:string>
</lang>
<value>Digital libraries</value>
</json:item>
</subject>
<language>
<json:string>eng</json:string>
</language>
<originalGenre>
<json:string>e-conceptual-paper</json:string>
</originalGenre>
<abstract>Purpose The purpose of this paper is to explore the current state of the text encoding initiative TEI community and suggests directions in which that community should strive based on recommendations from experts in the field. Designmethodologyapproach Looks at the history of, the present state of and future of TEI. Findings This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium. Practical implications TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least. Originalityvalue This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by nonexperts, can be expanded in order to enrich scholarship.</abstract>
<qualityIndicators>
<score>5.258</score>
<pdfVersion>1.3</pdfVersion>
<pdfPageSize>519 x 680 pts</pdfPageSize>
<refBibsNative>true</refBibsNative>
<keywordCount>2</keywordCount>
<abstractCharCount>905</abstractCharCount>
<pdfWordCount>3518</pdfWordCount>
<pdfCharCount>19315</pdfCharCount>
<pdfPageCount>7</pdfPageCount>
<abstractWordCount>145</abstractWordCount>
</qualityIndicators>
<title>Library as virtual abbey</title>
<genre>
<json:string>other</json:string>
</genre>
<host>
<volume>24</volume>
<publisherId>
<json:string>oclc</json:string>
</publisherId>
<pages>
<last>86</last>
<first>80</first>
</pages>
<issn>
<json:string>1065-075X</json:string>
</issn>
<issue>2</issue>
<subject>
<json:item>
<value>Library & information science</value>
</json:item>
<json:item>
<value>Librarianship/library management</value>
</json:item>
<json:item>
<value>Records management & preservation</value>
</json:item>
<json:item>
<value>Library technology</value>
</json:item>
<json:item>
<value>Information repositories</value>
</json:item>
</subject>
<genre>
<json:string>journal</json:string>
</genre>
<language>
<json:string>unknown</json:string>
</language>
<title>OCLC Systems & Services: International digital library perspectives</title>
<doi>
<json:string>10.1108/oclc</json:string>
</doi>
</host>
<publicationDate>2008</publicationDate>
<copyrightDate>2008</copyrightDate>
<doi>
<json:string>10.1108/10650750810875421</json:string>
</doi>
<id>C2DB569658374CB92253686134291328DF266272</id>
<score>0.2448495</score>
<fulltext>
<json:item>
<original>true</original>
<mimetype>application/pdf</mimetype>
<extension>pdf</extension>
<uri>https://api.istex.fr/document/C2DB569658374CB92253686134291328DF266272/fulltext/pdf</uri>
</json:item>
<json:item>
<original>false</original>
<mimetype>application/zip</mimetype>
<extension>zip</extension>
<uri>https://api.istex.fr/document/C2DB569658374CB92253686134291328DF266272/fulltext/zip</uri>
</json:item>
<istex:fulltextTEI uri="https://api.istex.fr/document/C2DB569658374CB92253686134291328DF266272/fulltext/tei">
<teiHeader>
<fileDesc>
<titleStmt>
<title level="a" type="main" xml:lang="en">Library as virtual abbey</title>
</titleStmt>
<publicationStmt>
<authority>ISTEX</authority>
<publisher>Emerald Group Publishing Limited</publisher>
<availability>
<p>EMERALD</p>
</availability>
<date>2008</date>
</publicationStmt>
<sourceDesc>
<biblStruct type="inbook">
<analytic>
<title level="a" type="main" xml:lang="en">Library as virtual abbey</title>
<author>
<persName>
<forename type="first">Robert</forename>
<surname>Fox</surname>
</persName>
<affiliation>Notre Dame University Libraries, Notre Dame, Indiana, USA</affiliation>
</author>
</analytic>
<monogr>
<title level="j">OCLC Systems & Services: International digital library perspectives</title>
<idno type="pISSN">1065-075X</idno>
<idno type="DOI">10.1108/oclc</idno>
<imprint>
<publisher>Emerald Group Publishing Limited</publisher>
<date type="published" when="2008-05-30"></date>
<biblScope unit="volume">24</biblScope>
<biblScope unit="issue">2</biblScope>
<biblScope unit="page" from="80">80</biblScope>
<biblScope unit="page" to="86">86</biblScope>
</imprint>
</monogr>
<idno type="istex">C2DB569658374CB92253686134291328DF266272</idno>
<idno type="DOI">10.1108/10650750810875421</idno>
<idno type="filenameID">1640240202</idno>
<idno type="original-pdf">1640240202.pdf</idno>
<idno type="href">10650750810875421.pdf</idno>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<creation>
<date>2008</date>
</creation>
<langUsage>
<language ident="en">en</language>
</langUsage>
<abstract>
<p>Purpose The purpose of this paper is to explore the current state of the text encoding initiative TEI community and suggests directions in which that community should strive based on recommendations from experts in the field. Designmethodologyapproach Looks at the history of, the present state of and future of TEI. Findings This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium. Practical implications TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least. Originalityvalue This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by nonexperts, can be expanded in order to enrich scholarship.</p>
</abstract>
<textClass>
<keywords scheme="keyword">
<list>
<head>Keywords</head>
<item>
<term>Markup languages</term>
</item>
<item>
<term>Digital libraries</term>
</item>
</list>
</keywords>
</textClass>
<textClass>
<keywords scheme="Emerald Subject Group">
<list>
<label>cat-LISC</label>
<item>
<term>Library & information science</term>
</item>
<label>cat-LLM</label>
<item>
<term>Librarianship/library management</term>
</item>
<label>cat-RMP</label>
<item>
<term>Records management & preservation</term>
</item>
<label>cat-LTC</label>
<item>
<term>Library technology</term>
</item>
<label>cat-IREP</label>
<item>
<term>Information repositories</term>
</item>
</list>
</keywords>
</textClass>
</profileDesc>
<revisionDesc>
<change when="2008-05-30">Published</change>
</revisionDesc>
</teiHeader>
</istex:fulltextTEI>
<json:item>
<original>false</original>
<mimetype>text/plain</mimetype>
<extension>txt</extension>
<uri>https://api.istex.fr/document/C2DB569658374CB92253686134291328DF266272/fulltext/txt</uri>
</json:item>
</fulltext>
<metadata>
<istex:metadataXml wicri:clean="corpus emerald not found" wicri:toSee="no header">
<istex:xmlDeclaration>version="1.0" encoding="UTF-8"</istex:xmlDeclaration>
<istex:document><!-- Auto generated NISO JATS XML created by Atypon out of MCB DTD source files. Do Not Edit! -->
<article dtd-version="1.0" xml:lang="en" article-type="e-conceptual-paper">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">oclc</journal-id>
<journal-id journal-id-type="doi">10.1108/oclc</journal-id>
<journal-title-group>
<journal-title>OCLC Systems & Services: International digital library perspectives</journal-title>
</journal-title-group>
<issn pub-type="ppub">1065-075X</issn>
<publisher>
<publisher-name>Emerald Group Publishing Limited</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="doi">10.1108/10650750810875421</article-id>
<article-id pub-id-type="original-pdf">1640240202.pdf</article-id>
<article-id pub-id-type="filename">1640240202</article-id>
<article-categories>
<subj-group subj-group-type="type-of-publication">
<compound-subject>
<compound-subject-part content-type="code">e-conceptual-paper</compound-subject-part>
<compound-subject-part content-type="label">Conceptual paper</compound-subject-part>
</compound-subject>
</subj-group>
<subj-group subj-group-type="subject">
<compound-subject>
<compound-subject-part content-type="code">cat-LISC</compound-subject-part>
<compound-subject-part content-type="label">Library & information science</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-LLM</compound-subject-part>
<compound-subject-part content-type="label">Librarianship/library management</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-LTC</compound-subject-part>
<compound-subject-part content-type="label">Library technology</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-RMP</compound-subject-part>
<compound-subject-part content-type="label">Records management & preservation</compound-subject-part>
</compound-subject>
<subj-group>
<compound-subject>
<compound-subject-part content-type="code">cat-IREP</compound-subject-part>
<compound-subject-part content-type="label">Information repositories</compound-subject-part>
</compound-subject>
</subj-group>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Library as virtual abbey</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<string-name>
<given-names>Robert</given-names>
<surname>Fox</surname>
</string-name>
<aff>Notre Dame University Libraries, Notre Dame, Indiana, USA</aff>
</contrib>
</contrib-group>
<pub-date pub-type="ppub">
<day>30</day>
<month>05</month>
<year>2008</year>
</pub-date>
<volume>24</volume>
<issue>2</issue>
<fpage>80</fpage>
<lpage>86</lpage>
<permissions>
<copyright-statement>© Emerald Group Publishing Limited</copyright-statement>
<copyright-year>2008</copyright-year>
<license license-type="publisher">
<license-p></license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="10650750810875421.pdf"></self-uri>
<abstract>
<sec>
<title content-type="abstract-heading">Purpose</title>
<x></x>
<p>The purpose of this paper is to explore the current state of the text encoding initiative (TEI) community and suggests directions in which that community should strive based on recommendations from experts in the field.</p>
</sec>
<sec>
<title content-type="abstract-heading">Design/methodology/approach</title>
<x></x>
<p>Looks at the history of, the present state of and future of TEI.</p>
</sec>
<sec>
<title content-type="abstract-heading">Findings</title>
<x></x>
<p>This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium.</p>
</sec>
<sec>
<title content-type="abstract-heading">Practical implications</title>
<x></x>
<p>TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least.</p>
</sec>
<sec>
<title content-type="abstract-heading">Originality/value</title>
<x></x>
<p>This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by non‐experts, can be expanded in order to enrich scholarship.</p>
</sec>
</abstract>
<kwd-group>
<kwd>Markup languages</kwd>
<x>, </x>
<kwd>Digital libraries</kwd>
</kwd-group>
<custom-meta-group>
<custom-meta>
<meta-name>peer-reviewed</meta-name>
<meta-value>no</meta-value>
</custom-meta>
<custom-meta>
<meta-name>academic-content</meta-name>
<meta-value>yes</meta-value>
</custom-meta>
<custom-meta>
<meta-name>rightslink</meta-name>
<meta-value>included</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<p>Beginning around the ninth century in Europe, and for the following 400 or so odd years, a renaissance occurred that would have an unprecedented impact on western civilization, the influence of which has been felt in the literary world ever since. It was during this period, the early portion of which is known as the Carolingian Renaissance that dramatic changes occurred in the way in which important texts were copied and composed. Prior to this era, there were no standards for manuscript copying and editing which made future transcription very difficult both for scholars and copyists. Following the Carolingian reforms (instituted under the emperor Charlemagne, d. 814), new standards were put into place which dictated a new kind of writing style known as Carolingian miniscule. This style established a new method of writing letters such that each letter was made uniform, with rounded portions, capital letters at appropriate points, and a standardized way of writing words and sentences which increased the legibility of texts exponentially. There may have been political motives behind this reform (after all, it's important for the emperor's subjects to be able to read imperial decrees), but the overall effect had an incredible impact in the realm of scholarship both then and now. For the first time, texts could fairly easily be compared for veracity against an autograph (the original text), writing styles could be analyzed, and thoughts could be better organized. Today, the bulk of our knowledge of classical texts is derived from texts written using this miniscule script, and more refined styles that appeared later in history. Modern typefaces have their roots in Carolingian miniscule.</p>
<p>A similar but hardly known or marketed enterprise is taking place in the digital world. The text encoding initiative (TEI) is in many ways the modern equivalent to the standardization of manuscript copying and editing, and in the library and scholarly world, it seems to have even broader implications. Whether the TEI will have as great an impact on the literary and scholarly world is improbable at this stage, but it is none the less one of the many uncelebrated enterprises in the digital library field, due not only to it's value as a comprehensive tool for textual analysis but also to the amazing amount of work that has been done with the TEI and digital texts but is largely unrecognized. This is very akin to the work done throughout Europe in the middle ages to preserve and illuminate (both artistically and in a scholarly fashion) important texts in the western canon, in abbeys and monestaries where monks quietly labored at an extremely vital task.</p>
<p>I had the pleasure recently of attending the 20th anniversary Conference of the TEI Consortium at the University of Maryland, and it was very impressive to see so many people from such a wide range of backgrounds and scholarly interests coming together to celebrate and promote the TEI standard. It was a very humbling experience in many ways because of the incredible amount of work that has been done in analyzing texts and applying scholarly principles in a technological field using XML and a very complex, well thought out schema for analyzing digital texts of all variety. As has been spoken about in this journal and elsewhere, the TEI standard is an amazingly expressive tool which is used for the analysis of texts of literally every kind whether those texts include irregular type setting, illustrations, illuminations, tables, photographs, etc. The standard has the ability to analyze poetic style, text organization, editions of works, linguistic styles and more. While a great quantity of work has been done using this tool, there is so much more that could be done, and the work is obviously labor intensive and requires expertise in both history and literary analysis which is why this is both a product of experts in the markup language field as well as top notch scholars. It was interesting to note, though, that there was also at this conference an air of uncertainty about the future of the TEI. While it's clear that the TEI has a great deal of potential and demonstrated value, what remains uncertain is the level at which it will be adopted by future scholars, librarians and archivists and this was a common theme at the TEI@20 conference. Part of the uncertainty, for better or worse, seems to stem from the history of the TEI and how it was developed as well as how it has been maintained over the last 20 years.</p>
<sec>
<title>History of a standard</title>
<p>The inception of the TEI began as a response to the lack of standards when digital documents began to proliferate over twenty years ago. This was new technology which brought along with it it's share of apprehension on the part of librarians and archivists. Given the lack of standards, it was doubtful that any serious fruit could be harvested from the enormous diversity of tools and software being used to create and maintain digital texts. It was in 1987 that an NEH sponsored event was held at Vassar College
<xref ref-type="fn" rid="fn1">[1]</xref>
that eventually culminated in 1990 with the first TEI standard (the “P1” standard). Almost every year following that initial standard a new standard was released such that in 1994 the TEI was up to version P3. It's important to realize that at this stage, the TEI was not an XML standard. That did not arrive until June 2002 with the P4 version. In the intervening years, a new TEI Consortium had been formed which had been incorporated in the year 2000. This consortium has been guiding the development of the standard since then up to the present version, P5. With P5, a host of new features has been added to the standard allowing for the analysis of almost any textual format. It is now at such a level of complexity that it requires training to use the markup in an appropriate manner, or at the very least, to take advantage of the standards expressive character.</p>
<p>The great weight of scholarly effort has gone into the P5 standard, and it is now more useful than ever for analyzing historical and highly complex literary texts as well as editions of the same work. While the benefit of TEI has grown as a valuable asset to the humanities research community, the complexity of the markup has risen to a level where it has become opaque to the new user. It is very rare to find a comprehensive introduction to the use of the TEI in any format, even as strides are being taken to remedy the situation. The keynote speaker on the first day of the TEI@20 Conference, B. Tommie Usdin, delivered a very incisive message to the TEI consortium: become relevant or fade away. Tommie Usdin (as she prefers to be addressed) has a very long and respected history in the markup language world. She was involved in the development of some of the initial tools used to edit and maintain SGML (the precursor to HTML) and has watched closely as the standards for HTML and XML have developed over the last 20‐30 years. Her experience far precedes the commercial utility of the web when HTML/SGML took on a character vastly different from when Timothy Berners‐Lee had originally intended (
<xref ref-type="bibr" rid="b1">Berners‐Lee and Fischetti, 1999</xref>
). In a sense, the TEI has taken an opposite sort of trajectory, and instead of being exploited by the commercial enterprise, the TEI consortium has become very insular, according to Ms Usdin. If TEI is to remain relevant Tommie Usdin suggests, the community must become amenable to the needs of newcomers and must consider the issue of marketing and instruction.</p>
</sec>
<sec>
<title>Digital scribes in action</title>
<p>It is beyond a doubt that TEI has demonstrated its usefulness within the scope of it's original conception. The examples are far too numerous to expound upon but a few examples here should be sufficient to demonstrate the point. It is truly amazing the depth of analysis and the enhancement to scholarship that can be accomplished when TEI is used to it's greatest potential. In the humanities field, TEI is analogous to the use of data mining techniques for a data warehouse depending upon the granularity to which a text has been marked up. In fact, fascinating and intricate relations between ideas within a text and between texts can emerge with the analytical detail that TEI offers.</p>
<p>A project that grew out of two sister projects, the Nora project (
<ext-link ext-link-type="uri" xlink:href="http://www.noraproject.org/">www.noraproject.org/</ext-link>
) and the Wordhoard project at Northwestern University (
<ext-link ext-link-type="uri" xlink:href="http://wordhoard.northwestern.edu/userman/index.html">http://wordhoard.northwestern.edu/userman/index.html</ext-link>
), the MONK (Metadata Offer New Knowledge) project (
<ext-link ext-link-type="uri" xlink:href="http://monkproject.org">http://monkproject.org</ext-link>
) aims to merge these two fascinating initiatives into a combined effort with a goal to increase the possibility of text mining and analysis to humanities scholars. They give an analogy in their documentation describing the MONK project as an effort to potentially analyze in a comprehensive manner, texts in the same way that medieval monks created concordances for
<italic>the Bible</italic>
. In this way, patterns, themes and relations between words and phrases can be discerned using the power of a computer application with the expertise of a humanities scholar. This is only possible because enormous amounts of effort have gone into parsing out these documents with TEI. While it's possible that other standards or independent analytic techniques could be utilized, they cannot possibly approach the same level of detail that TEI offers.</p>
<p>One of the goals of the MONK project is to potentially provide for scholars a visual representation of the relations between ideas in texts, which will be more intuitively discernable. This provides the scholar with a “bird's eye view” of a set of texts which could lead to further analysis and exploration. The MONK project provides, on their wiki, some examples of how this technique could be used. For example, the goal could be an examination of texts to determine how readers identify genre or themes based on the overall syntactical methods employed in a given set of literature. This could involve a multi‐layered study with Bayesian statistical analysis, a detailed examination of lexical features, or straight forward numerical studies. Or, a college seminar class may be interested in exploring the rhetorical usage of explicitly political and/or theological themes in a particular set of genres during the sixteenth century. Once a list of keywords or phrases has been assembled, they can use MONK to apply that criteria to a sample of texts in order to analyze patterns of usage. The true intelligence behind such an application, though, is the previous work that had been done in TEI parsing out documents using scholarly expertise and it is highly doubtful that an algorithm could be developed which could independently perform as accurate an assessment of a text due to the complex nature of linguistics and contextual usage. This goes far beyond simple keyword searches within a compiled index. In that sense, the effort of the scholars employing TEI is truly analogous to the work of the monks from eleventh to thirteenth centuries.</p>
<p>In a similar fashion, the Perseus Digital Library has made great strides with classical texts (
<ext-link ext-link-type="uri" xlink:href="http://www.perseus.tufts.edu">www.perseus.tufts.edu</ext-link>
). They have even gone a step further by wedding the textual analytics with GIS in order to reveal relations between texts over “time, space, and language”. The project has also made an effort to be as cross disciplinary as possible, in order for scholars to communicate and share knowledge at a level previous prohibitive. In the area of linguistic study, they have linked all of the versions of a text that is available with tools such as lexicons, concordances, word frequency charts, and geographic locations. One of the primary mechanisms behind this functionality is TEI markup. The latest version of the Perseus tool set (Perseus 4.0) includes the ability to extract well formed XML fragments of primary sources in TEI‐conformant markup, if desired.</p>
<p>The Perseus Library demonstrates just how broad and deep the applicability of TEI actually is. The project is now immense regarding it's work to combine and interlock various kinds of data, which is a demonstrated success from, for example, one “humble” testbed of TEI encoded documents of over five million words, 10,000 scans of illustrations and 2,400 pictures of London (within the London Bolles collection) (
<xref ref-type="bibr" rid="b2">Crane, 2000</xref>
).
<xref ref-type="bibr" rid="b2">Crane (2000)</xref>
states:
<disp-quote>
<p>The techniques that we had developed in our work on Greco‐Roman Perseus did, as we had hoped, constitute a solid foundation for this project, while the richness of the data allowed us to experiment with new ways of representing and visualizing people, things, space and time.</p>
</disp-quote>
</p>
<p>In many ways, this project and others like are just scratching the surface of what could be done in the world of TEI if more institutions could embrace the technology and use it to it's complete potential.</p>
</sec>
<sec>
<title>Barriers to adoption</title>
<p>The TEI@20 Conference carried with it a leitmotif with a look at another of the TEI communities' weaknesses: the distinct lack of TEI examples for educational purposes. Melissa Terras, an instructor from University College, London, gave a very engaging talk on this subject, presenting a plea as someone who is in the front lines of education within the TEI community. Her students are primarily professionals who work in the humanities, librarians or other information specialists who do day to day work with increasing amounts of digital material and need tools such as TEI to help them accomplish their work. Her plea is very similar to Tommie Usdin's: the TEI community needs to become more open to those new to the TEI and markup in general.</p>
<p>A new generation of information workers is entering the field who do not have the extensive background that the existing TEI users have grown accustomed to over the course of the last 20 years, and yet there is a dire need for training and education both in the theory behind the TEI and by example. Melissa made a very convincing case that there needs to be more tutorials at all levels of usage from beginner to advance. And, not only is this information required, but also it should be provided by the TEI community itself. Not wasting any time, Melissa has been very active in this regard. She has created a site called “TEI by example” (
<ext-link ext-link-type="uri" xlink:href="http://www.kantl.be/ctb/project/2006/tei-ex.htm">www.kantl.be/ctb/project/2006/tei‐ex.htm</ext-link>
) and it includes a software toolkit as well as documentation of the methodology and workflow of the project. The site also provides PDF versions of the tutorials along with the software toolkit as well as a downloadable CD ROM image for course participants. This is a great beginning as a remedy to the problem of education and TEI adoption.</p>
<p>Tommie Usdin as well as Melissa Terras also chastised the TEI community for not creating a web site that is user friendly. A redesign just before the conference was an attempt to correct this issue, but there is still a distinct lack of officially supported examples and education materials that are accessible from the primary TEI site. The only page on the site, which is not immediately obvious, to provide such material is a “support” page with links to introductions to XML and one link to tutorials. However, the tutorials page doesn't include a link to Melissa Terras' “TEI by example” site. While there is a small amount of information, much of it assumes some prior knowledge, and none of it appears to be a sufficient introduction, for example, to the latest P5 standard. Ms Terras' point, though, is that without a sufficient quantity of material giving an overview (by example) of how to use TEI, the complexity of the standard will remain a significant barrier to adoption.</p>
</sec>
<sec>
<title>The future of TEI</title>
<p>What will the next 20 years hold for TEI? The TEI (as an initiative) fills a gap within the scholarly community that cannot be filled in like manner using another markup standard. The enhancements for scholarly research are a celebrated fact among specialists who know and use the standard. And, even for those who are unaware of the standard, TEI undergirds many projects that have become a gift to the academic community. No one wants to see happen to the TEI what happened to z39.50 and other standards that expired under their own weight. Given that there is very little, if any, competition in this arena it is highly unlikely that a replacement for TEI will come into being, but there is a danger that it's usage will become marginalized. As Tommie Usdin and Melissa Terras have suggested by word and deed, there are several potential remedies for the situation.</p>
<p>Among the potential solutions is the effort to educate along a broad front. Melissa does this primarily among non‐specialits in the field, and it seems necessary that this be expanded. While TEI was developed among humanities experts and developed for those experts, more than just technologists and scholars need to understand how to use TEI. In order for the richness of the markup to be fully exploited, education on how to apply TEI to texts needs to occur with many individuals who are not experts, and who can apply that knowledge to a vast quantity of texts. It may be possible then to create collaborative efforts within and between projects such as MONK and Perseus. There will always be a need for the humanities scholar to create a framework in which the markup of texts can occur, and there will also be a need for editing work. But given the vastness of the texts that could be analyzed, both at a work level and at an edition level, more folks need to be educated in the complexity of the various sub‐areas (such as manuscript analysis) in TEI.</p>
<p>The second area which has already been pointed out by Melissa Terras is in the provision of examples. There is a need both for examples in the various genres of literature that can be marked up such as medieval manuscripts, poetry, prose from various historical periods, literature with illustrations, irregular text blocks, etc. It is not as though there are no examples available, and work that has been accomplished could certainly be used as prototypes, but usually work that has been completed is at such a level of complexity that it is inaccessible to beginners. Therefore, examples which demonstrate technique at a very simple level are needed in order to get people started. As folks progress, then it would be possible for them to consult mentors in the field as the work becomes more complicated.</p>
<p>Tommie Usdin also suggests that TEI be “marketed” to a certain extent in order to make scholars and technologists more aware of it's potential. For years, collaboration and communication on TEI and the resulting consortium occurred mainly between specialists at participating institutions, and very little communication took place outside of that context. One primary means of communication is, of course, the TEI web site. While this has been recently revised and ongoing work is being done, there are still areas where usability is an issue. Several presenters at the TEI@20 commented on this issue, and the maintainers of the site are aware of the issues. Scholars also have a responsibility to share the details of their work with colleagues and encourage participation in projects that involve TEI. In that way, familiarity with TEI will dispel potential “technophobia” and also demonstrate what can be done with the standard.</p>
<p>Finally, just as easy to use tools have developed to help in the creation and editing of HTML and other XML documents, new tools which incorporate a bit of intelligence regarding the standard syntax also need to come on the scene. This will make adoption by inexperienced users easier, and lower the threshold of complexity. A few presentations were given at the TEI@20 Conference, among my own, regarding the various tools that are currently in existence for working with TEI both on the formulation end and on the presentation end. And, while there are tools available that do basic validation and other related tasks, there are none catered exclusively for TEI, which incorporate the many versions which may be present in existing TEI documents. It would be very helpful to have tools that could create a dynamic document map, along with error correction and syntax auto‐completion. Such tools exist for many programming languages and they certainly exist for HTML, but again, given the nature of the TEI community they have not yet attracted individuals with the comprehension of TEI and the requisite programming skills to create such a tool (or set of tools).</p>
<p>It is definitely worth the time and effort, on the part of the TEI user community and the TEI consortium to invest effort in these areas. While a great deal of passion has gone into the development of the standard, it is now time to branch outward and embrace a larger audience. This will help to ensure that TEI does not ultimately become a niche standard, and expand it's utility to many more areas of academics and research. If those steps are taken, then there is definitely much to look forward to in the next 20 years of TEI encoding.</p>
</sec>
</body>
<back>
<fn-group>
<title>Notes</title>
<fn id="fn1">
<p>Please see
<ext-link ext-link-type="uri" xlink:href="http://www.tei-c.org/About/history.xml">www.tei‐c.org/About/history.xml</ext-link>
for a more complete history of the TEI.</p>
</fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="b1">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Berners‐Lee</surname>
,
<given-names>T.</given-names>
</string-name>
</person-group>
and
<person-group person-group-type="author">
<string-name>
<surname>Fischetti</surname>
,
<given-names>M.</given-names>
</string-name>
</person-group>
(
<year>1999</year>
),
<source>
<italic>Weaving the Web: The Original Design and Ultimate Destiny of the World Wide Web by its Inventor</italic>
</source>
,
<publisher-name>Harper</publisher-name>
,
<publisher-loc>San Francisco, CA</publisher-loc>
.</mixed-citation>
</ref>
<ref id="b2">
<mixed-citation>
<person-group person-group-type="author">
<string-name>
<surname>Crane</surname>
,
<given-names>G.</given-names>
</string-name>
</person-group>
(
<year>2000</year>
), “
<article-title>
<italic>Designing documents to enhance the performance of digital libraries: time, space, people and a digital library on London</italic>
</article-title>
”,
<source>
<italic>D‐Lib Magazine</italic>
</source>
, Vol.
<volume>6</volume>
Nos
<issue>7/8</issue>
, available at:
<ext-link ext-link-type="uri" xlink:href="http://www.dlib.org/dlib/july00/crane/07crane.html">www.dlib.org/dlib/july00/crane/07crane.html</ext-link>
.</mixed-citation>
</ref>
</ref-list>
</back>
</article>
</istex:document>
</istex:metadataXml>
<mods version="3.6">
<titleInfo lang="en">
<title>Library as virtual abbey</title>
</titleInfo>
<titleInfo type="alternative" lang="en" contentType="CDATA">
<title>Library as virtual abbey</title>
</titleInfo>
<name type="personal">
<namePart type="given">Robert</namePart>
<namePart type="family">Fox</namePart>
<affiliation>Notre Dame University Libraries, Notre Dame, Indiana, USA</affiliation>
</name>
<typeOfResource>text</typeOfResource>
<genre type="other" displayLabel="e-conceptual-paper"></genre>
<originInfo>
<publisher>Emerald Group Publishing Limited</publisher>
<dateIssued encoding="w3cdtf">2008-05-30</dateIssued>
<copyrightDate encoding="w3cdtf">2008</copyrightDate>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
<languageTerm type="code" authority="rfc3066">en</languageTerm>
</language>
<physicalDescription>
<internetMediaType>text/html</internetMediaType>
</physicalDescription>
<abstract>Purpose The purpose of this paper is to explore the current state of the text encoding initiative TEI community and suggests directions in which that community should strive based on recommendations from experts in the field. Designmethodologyapproach Looks at the history of, the present state of and future of TEI. Findings This column is simply exploratory, and examines issues regarding the TEI and the TEI consortium. Practical implications TEI is a very robust and expressive markup language used in the analysis of literature in the humanities fields. The community is encouraged to take proactive steps to ensure TEI as a viable markup language for the next 20 years, at least. Originalityvalue This column examines the enormous contribution that TEI has made to the humanities fields and explores ways in which the usage of TEI, even by nonexperts, can be expanded in order to enrich scholarship.</abstract>
<subject>
<genre>keywords</genre>
<topic>Markup languages</topic>
<topic>Digital libraries</topic>
</subject>
<relatedItem type="host">
<titleInfo>
<title>OCLC Systems & Services: International digital library perspectives</title>
</titleInfo>
<genre type="journal">journal</genre>
<subject>
<genre>Emerald Subject Group</genre>
<topic authority="SubjectCodesPrimary" authorityURI="cat-LISC">Library & information science</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LLM">Librarianship/library management</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-RMP">Records management & preservation</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-LTC">Library technology</topic>
<topic authority="SubjectCodesSecondary" authorityURI="cat-IREP">Information repositories</topic>
</subject>
<identifier type="ISSN">1065-075X</identifier>
<identifier type="PublisherID">oclc</identifier>
<identifier type="DOI">10.1108/oclc</identifier>
<part>
<date>2008</date>
<detail type="volume">
<caption>vol.</caption>
<number>24</number>
</detail>
<detail type="issue">
<caption>no.</caption>
<number>2</number>
</detail>
<extent unit="pages">
<start>80</start>
<end>86</end>
</extent>
</part>
</relatedItem>
<identifier type="istex">C2DB569658374CB92253686134291328DF266272</identifier>
<identifier type="DOI">10.1108/10650750810875421</identifier>
<identifier type="filenameID">1640240202</identifier>
<identifier type="original-pdf">1640240202.pdf</identifier>
<identifier type="href">10650750810875421.pdf</identifier>
<accessCondition type="use and reproduction" contentType="copyright">© Emerald Group Publishing Limited</accessCondition>
<recordInfo>
<recordContentSource>EMERALD</recordContentSource>
</recordInfo>
</mods>
</metadata>
<serie></serie>
</istex>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Wicri/Ticri/explor/TeiVM2/Data/Istex/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000169 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Istex/Corpus/biblio.hfd -nk 000169 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Wicri/Ticri
   |area=    TeiVM2
   |flux=    Istex
   |étape=   Corpus
   |type=    RBID
   |clé=     ISTEX:C2DB569658374CB92253686134291328DF266272
   |texte=   Library as virtual abbey
}}

Wicri

This area was generated with Dilib version V0.6.31.
Data generation: Mon Oct 30 21:59:18 2017. Site generation: Sun Feb 11 23:16:06 2024