[tei-council] Criteria for TEI Repository Inclusion
James.Cummings at oucs.ox.ac.uk
Wed Mar 3 06:36:36 EST 2010
Lou Burnard wrote:
> So I suppose what James meant to say was that the TEI wiki has a place
> for putting *information about* customisations (and links to their
> canonical homes if any)?
Well and indeed I said: "When we get the tei-enrich google code
site sorted out, I will be putting a link to that on the TEI
wiki" as an example of this.
But I still disagree with Sebastian's central assumption. While
I'm not suggesting that ODDs should really be managed in a wiki,
or that this is the best technology to use, it is plainly not the
case that ODDs are software. Yes, we can use software-tools to
manage them and there is nothing wrong with that, but ODDs as
meta-schema and documentation especially when being
collaboratively authored might benefit from collaborative
authoring tools, like say wikis. Alternatively, when an ODD
reaches a certain stability I see no problem having it in a wiki
page with accompanying documentation about how to use it and why
it was made. It is just one tool in the toolbox.
>> no. cos wikis are not, by any stretch of the imagination,
>> the right tool for software distribution. IMHO.
More information about the tei-council