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  January 2007

TEI-L January 2007

Subject:

Re: how to remove numbered divs properly?

From:

Wendell Piez <[log in to unmask]>

Reply-To:

Wendell Piez <[log in to unmask]>

Date:

Tue, 2 Jan 2007 17:31:25 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (120 lines)

Dear Sebastian,

At 02:08 PM 1/2/2007, Sebastian Rahtz wrote:
>>As I've said before, I thought the P3/P4 definition had the balance 
>>just about right. It pointed to validation against a DTD and 
>>defined ways in which a custom DTD could vary while remaining in 
>>conformance, while not relying on exclusively automated mechanisms. 
>>It was not a cookie-cutter approach, but instead held projects to a 
>>high standard. Conformance meant not simply formal validation as 
>>such, but intellectual rigor, demonstrated through documentation 
>>and explicit rationales that showed how and why modeling decisions 
>>were made and applied.
>That's a consistent standpoint. I disagree fairly strongly, though. I think
>that P3/P4 provided a test for conformance which made the user feel good,
>but did little to make their documents useable by others.

I think it did far more than "make users feel good". It assured that 
their intellectual decisions and justifications would be made in full 
view of knowledgeable practitioners, and thus legitimated their work, 
while allowing them the scope they needed both to realize their 
technical and intellectual aims and to distinguish themselves by how 
they did so. This was and is very important to audiences, which 
include (now) grant funding agencies and (some day) tenure committees.

As for not delivering on the promise of "making their documents 
usable by others", I submit that it has not been demonstrated that 
ODD will ensure this any more than the older, less formal methods 
did. As far as I can see, ODD does nothing at all for this except 
perhaps make the documentation a bit more accessible -- assuming the 
spirit as well as the letter of ODD is followed (and if it's not, all 
bets are off).

So, I think you're attacking a straw man with a broom. To my mind, 
the TEI is wonderful for achieving a very important kind of 
interchange that machines just aren't very good at ... and the 
history of HTML shows us what the other kind of interchange is good 
for (not very much beyond display).

>>Ah, so you agree with me then. So, if a project has no ODD but can 
>>justify their means and methods, they can yet be blessed? Will the 
>>peer group be willing to acknowledge that ODD implementations are 
>>no better as final arbiters than the schemas they define, and that 
>>indeed there might be a category (albeit narrow) of TEI that may 
>>(now or in future) have good reasons to use other mechanisms?
>Of course. But this isn't self-blessing. As the TEI project stands at present,
>we have a formally elected peer group (viz the Technical Council of TEIC)
>which makes judgements. It's a plausible compromise way of deciding
>what "peer acceptance" is, I suppose. If they say _at present_ "thou 
>shalt use ODD, Wendell", then I'd argue you cannot strike out on 
>your own and say "this is what
>I do and it is  TEI cos I say so" - you have to use your 
>considerable influence
>to persuade that group of peer judges to go other ways as well. As indeed you
>are quite rightly doing in the forum of TEI-L.

Indeed. But I've been arguing preemptively and hypothetically, since 
I think it would be a mistake for the Technical Council to rule, 
without offering any alternatives, "it's ODD or bust" -- which, I 
imagine, would probably lead to more occasions of "bust" than they'd 
like to see -- or perhaps more to the point, of potential TEI users 
and allies just deciding to jump on other bandwagons.

(It would be a different thing altogether for them to rule "we much 
prefer and recommend ODD, but if there are reasons you can't use it, 
technically or practically, we need to learn from these too".)

That is, I am trying to defend the good work of TEI past, present and 
future by warning against letting one particularly fine engine (ODD) 
drive the whole circus -- since in my experience, the finer the 
engine is, the more likely it is that its drivers will try to let it 
steer itself.

But the real test will be in the kinds of work that are enabled and 
frustrated. The pity is that in the nature of things, we learn about 
the successes but rarely get to ponder the failures. Many projects 
have picked up TEI only to let it drop again -- or have twisted it to 
the point where they don't want to show their work in what they think 
of as polite (or over-polite) society. TEI could learn a great deal 
if it could see into this blind spot. Indeed, TEI is good work 
precisely to the extent that its developers and proselytes have said 
"it's not finished yet; we have more to learn".

>>This is highly relevant. Ron demonstrated that he could make a 
>>legal modification that would not pass conformant XML DTD parsers 
>>due to ambiguous content models. Lou argued that this problem comes 
>>with the territory, implying that there is really no good fix.
>What Ron did was a legal modification, and a proper implementation
>of ODD would have generated a legal DTD from it, as it generated
>a legal RELAXNG schema.

Yet as you know, RNG schemas can and do express models impossible to 
express in DTDs. While Ron doesn't have one of those, he has 
something even worse: one impossible to express in the TEI DTD 
architecture as it stands due to the expansion of its parameter 
entities. This implies that in order to support conformant ODD fully, 
an ODD implementation would have to work around the XML modeling 
architecture it is based on. Quite a feat, I submit (particularly the 
part about knowing when to do this), and exactly the kind of "bug" 
(or more precisely, systemic weakness) I'm concerned about.

>[1] oh, you want the precise spec of processing model? er um well,
>just read the code, Luke....

Yes, well.... :-)

Cheers,
Wendell



======================================================================
Wendell Piez                            mailto:[log in to unmask]
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================

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

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