[tei-council] Supplying default namespace with TEI Tite
daniel.odonnell at uleth.ca
Thu Jul 9 10:53:14 EDT 2009
I think we agree on the issues: but you raise an interesting question about council's role--especially if as looks very likely now we do end up with a very useful keyboarding members' benefit based on Tite. We were asked to support rather than direct it, but now it and a number of other 'community' initiatives are playing a bigger and bigger role in the activities of the 'official' TEI.
This is an interesting problem caused in my view by a number of changes over the years--from going to source forge, introducing such cool modification mechanisms, starting the SIGs, turning the meeting into a conference.
Initially council (and the editors') job was conceptually straightforward: build and maintain the guidelines. And the function of the Consortium was to enable that effort.
Now this is changing and council, and the rest of the consortium, is acquiring new functions as well in community development and support. It's exciting times and a direct result of some of the things that make P5 and the process behind its development and maintenance so neat.
University of Lethbridge
(From my mobile telephone)
--- original message ---
From: "Sebastian Rahtz" <sebastian.rahtz at oucs.ox.ac.uk>
Subject: Re: [tei-council] Supplying default namespace with TEI Tite
Date: July 9, 2009
O'Donnell, Dan wrote:
> as a product of a small group of community members for a
> fairly specific purpose with occassional council assistance but not
> really council or editorial direction.
the flaw was that the TEI Council was asked to
_support_ and adopt the thing.
> * really addressing this question of conformance
you mean reopen the debate on what conformance means? <shudder/>
> * addressing the question of keystrokes more directly: can we reduce them further?
as Lou said, dont use XML :-}
I do find this hard to take seriously, that vendors and clients really
collaborate on such a crude level. Why don't they contract
on the basis of the number of _content_ characters (and the proportion
of markup to content)? we know that keyboarders don't
actually type the tags anyway!
> * Situating tite more securely and explicitly in the library SIGs encoding level practices document
yes, thats interesting. making the SIG doc into an ODD, you mean?
mind you, I think this would mostly be a waste of the Council's
time. We are here to create the infrastructure for this work,
aren't we, not actually do it?
Information Manager, Oxford University Computing Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Sólo le pido a Dios
que el futuro no me sea indiferente
More information about the tei-council