LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  August 2011

TEI-L August 2011

Subject:

TEI interoperability and interchange

From:

"Birnbaum, David J" <[log in to unmask]>

Reply-To:

Birnbaum, David J

Date:

Mon, 22 Aug 2011 10:59:35 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (173 lines)

Dear TEI-L,

Those who care about interoperability and interchange could read with profit http://conferences.idealliance.org/extreme/html/2002/Usdin01/EML2002Usdin01.html . 

My experience with the TEI Guidelines is very different from John's (although we served together on Council): in my experience the Guidelines often provide alternative ways to represent the same information, that is, alternative encodings that have no clear, stable informational difference. In my experience, the TEI, in an effort to be respectful of its users, has often neglected what I think is a responsibility to guide, that is, to assert that given two ways of encoding the same information, one will be recommended as best practice (and supported in unmodified, off-the-shelf TEI) and the other won't. 

The reduction of alternatives (by recommending one and only one, even if chosen arbitrarily) is beneficial only when there is truly no meaningful informational difference, and making that decision is often difficult. On the other hand, I have heard Council members refuse to make that type of decision not because they perceive an informational difference, but because "we don't want to tell people what to do with their data." Please, tell me what to do with my data that will make it easier to interchange and interoperate! TEI is extensible, so taking seriously what I think is Council's responsibility to dictate best practice doesn't prevent people who really, really want to do something another way from making their own decision and remaining conformant. It does, though, reduce fragmentation in the community because users who don't have a strong preference for one particular solution will most naturally be guided to do things the same way.

Many of my documents are manuscript descriptions and bibliographies, where the ability to query a union catalog formed by merging multiple independent encoding projects is a high priority for users. I'd be very happy to be able to trust that the developers of TEI projects in my field will encode this type of information the same way I will, and that our encodings will differ only when we're encoding different information, and not just because we have different arbitrary preferences. I don't care what that one way of doing a particular something is, but when Council gives me choices that aren't rooted in informational differences, they think they're giving me freedom, but they're also giving me fragmentation and isolation. 

Best,

David



On Aug 22, 2011, at 9:49 AM, "John A. Walsh" <[log in to unmask]> wrote:

> As is so often the case, I am in nearly full agreement with Lou's
> sentiments. Interoperability is not particularly high on my list of
> desiderata for TEI.
> 
> Those of us who have been trying over the  years to justify the
> intellectual and scholarly rigor of text encoding have emphasized that
> an encoding of a text is, among other things, a reading and
> interpretation of that text. When the TEI provides multiple ways to do
> the “same” thing, there are usually subtle or not so subtle rhetorical
> differences that accompany each different way of doing that thing.
> Thus, they are not really the “same” thing at all. By establishing one
> and only one way to do a certain thing, we gut the rhetorical power of
> the TEI. A relentless charge towards interoperability would benefit
> the increasing tendency towards the Googleization of digital
> humanities, in which bigger is generally better, "good enough" OCR is
> good enough, and lip service is paid to beautifully crafted and
> carefully curated smaller projects as they are relegated to a
> necessary but increasingly irrelevant middle ages of digital
> humanities. Rather than have at my disposal millions of homogenous and
> interoperable TEI texts provided by Google or whomever, I would prefer
> to make my way through a smaller number of meticulously encoded texts,
> where the mind of the scholar(s)/editors(s) is present in the
> encoding, along with ingenious and clever encoding strategies that
> suggest important critical insights about the texts. This is the
> nanotechnolgoy of digital humanities.
> 
> The TEI is a monumental intellectual achievement that provides both a
> theory of text and a framework to accommodate many other, often
> competing, theories of text. These theories are not always
> interoperable, and the TEI encodings of different texts are not and
> should not always be interoperable, though as Lou rightly points out,
> they are always or generally interchangeable.
> 
> Having said that, I don't think the TEI as it currently exists is
> necessarily incompatible with greater interoperability, and certainly
> the TEI community has the expertise to provide an interoperable format
> in addition to an interchange format, but it would be something
> different and should supplement rather than replace what we currently
> have.
> 
> I will take issue with Lou's characterization of Mr. Jobs. Flash is
> not absent from certain Apple devices because Apple believes it will
> confuse people. It's absent because it sucks—it degrades performance
> and wreaks havoc on battery life, and Apple has instead thrown their
> considerable weight behind a more open, competing standard: HTML5 and
> related technologies that can provide much or all of the functionality
> of the proprietary Flash. Apple also led the charge to make the 3.5"
> floppy disk obsolete, not because it confused people, but because
> networks and other technologies made them increasingly useless. I
> assume Lou doesn't want a 3.5" floppy drive on his phone, but I may be
> wrong, :-).
> 
> I'm sure we all remember that it was not so long ago that Apple was
> dismissed and ridiculed as a niche player, who, if they wanted to
> succeed, needed to become more interoperable with the dominant
> operating systems and technologies of the day. Mr. Jobs and Apple told
> the pundits to fuck off, and continued their focus on design,
> elegance, aesthetics, and innovation, not interoperability. We all
> know how that worked out for them. I don't think the TEI would do too
> bad moving forward by continuing our own long-standing and successful
> focus on design, elegance, aesthetics, and innovation.
> 
> John
> 
> On Mon, Aug 22, 2011 at 7:19 AM, Lou Burnard
> <[log in to unmask]> wrote:
>> It's interesting how these little words "interoperable" and "interchange"
>> arouse such passion. Let me go on record with the view that the "I" in TEI
>> is for "interchange" not "interoperability".
>> 
>> Total interoperability is I contend an ignis fatuus, a foolish goal. If you
>> want to be able to do on your computer exactly the same with my document as
>> I can do with it with the software running on my computer you're probably
>> going to be disappointed, until such time as we all succumb to the lure of
>> Mr Jobs or whichever avatar of late capitalism replaces him. Or we have to
>> agree to define a fairly low level of common functionality and hobble our
>> systems to provide only that: it's called commodification (no you can't have
>> flash, no you can't have a usb interface... they'd only confuse you, trust
>> me)
>> 
>> Interchange however is another matter. We do it all the time, just as we do
>> with natural language. Actually, natural language is not such a bad analogy.
>> People get by very well at international symposia using a subset of the
>> facilities offered by the whole glorious English language, without losing
>> the ability to be creative in their use of it (This incidentally is why
>> synthetic languages never catch on -- people need to be able to be creative)
>>  All we need is a well defined common set of concepts, and a (preferably
>> fairly small) agreed set of ways of expressing our choice amongst them.
>> Those choices are not all going to be the same because we all want to
>> express our individuality, and a very good thing too, or science would never
>> advance.
>> 
>> I think the TEI is the least worst example of such a set of concepts so far
>> proposed. I think the technical methods it has now in place for
>> customisation and tailoring of that set to the needs of particular research
>> communities are pretty good. They could be improved, and in particular they
>> need to be made much more accessible and more widely understood, but they
>> are functionally up to the task of guaranteeing a degree of
>> interchangeability of digital documents which would otherwise be impossible.
>> 
>> 
>> 
>> On 22/08/11 01:13, Doug Reside wrote:
>>> 
>>> Patrick Durusau wrote:
>>> 
>>>> 1a. Is the TEI about "interchange?"
>>>> Rather than setting users up for the disappointment of expecting to
>>>> easily
>>>> benefit from the texts of others or to create texts that are going to be
>>>> snapped up by other scholars, let's be realistic about the difficulties
>>>> of
>>>> interchange, under the best of circumstances and not make it a selling
>>>> point
>>>> for the TEI.
>>> 
>>> I agree that the TEI is all but useless for interoperable *anything*
>>> at the moment, and I likewise acknowledge that even relatively more
>>> interoperable markup languages such as HTML still suffer greatly from
>>> differing interpretations by software that either ignores the standard
>>> (IE) or interprets it in slightly different ways (Firefox vs Chrome).
>>> Still, if we give up the goal of interoperability as a central, even
>>> primary, goal of the TEI, then I see no reason:
>>> 
>>> * to use it,
>>> * for any institution to support it, or
>>> * for any granting agency to recommend its use.
>>> 
>>> Without a goal of interoperability, I might as well create my own tags
>>> that won't force me to spend a lot of time looking for the appropriate
>>> tag for the textual feature I wish to identify.
>>> 
>>> The current lack of consistency in TEI encoding (admittedly, in part,
>>> the fault of editors like me as much as the standard itself) should be
>>> cause for sorrow leading to repentance rather than an excuse to toss
>>> out the goal itself.  I can't imagine that most of the libraries and
>>> universities that support the TEI do so in the hopes of providing a
>>> medium for literary criticism using exceptionally clunky form of XML.
>>> We already have plenty of better mechanisms for this, and a commented,
>>> public viewable Google Doc would serve the purpose far more
>>> efficiently.
>>> 
>>> 
>>> Doug
>> 
> 
> 
> 
> -- 
> | John A. Walsh
> | Assistant Professor, School of Library and Information Science
> | Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
> | www: <http://www.slis.indiana.edu/faculty/jawalsh/>
> | Voice:812-856-0707 Fax:812-856-2062 <mailto:[log in to unmask]>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994
December 1993
November 1993
October 1993
September 1993
August 1993
July 1993
June 1993
May 1993
April 1993
March 1993
February 1993
January 1993
December 1992
November 1992
October 1992
September 1992
August 1992
July 1992
June 1992
May 1992
April 1992
March 1992
February 1992
January 1992
December 1991
November 1991
October 1991
September 1991
August 1991
July 1991
June 1991
May 1991
April 1991
March 1991
February 1991
January 1991
December 1990
November 1990
October 1990
September 1990
August 1990
July 1990
June 1990
April 1990
March 1990
February 1990
January 1990

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager