[tei-council] Proposal for TEI website stable URIs and archiving

[Elena Pierazzo]

I was not in Lyon so possibly you already discussed a couple of the 
things I am commenting on now, so please forgive me if it is the case.

1. Have we considered to use PURL or DOI as a tool to enhance the 
persistence? In this case we might be able to change all links (for 
instance go to extension-less) without fear of breaking them.
2. I cannot understand the difference between point releases (par. 1.2.) 
and the one in the Vault (par. 3): when a point release become part of 
the Vault?
3. Simplify the access to Guidelines: David was mentioning Melissa's 
presentation: I remember she also said the codes as P5 should be avoided 
until someone has understood what P5 is, so what about calling the link 
"TEI Guidelines (current)" or similar? (by the way, I prefer the link 
from the home page, so option 1).

Thank you for your work!
Elena


Sebastian Rahtz wrote:
> * as regards the web site making P5 more visible and prominent,
>    I think tha arguments are good, any I don't have any
>    great wisdom to add. rewriting the "P5 index page"
>    will need someone to hack the hard-wired XSL, by the way.
>
> * the versioning of releases - I have two concerns
>
>     1. that it be 100% automated. ie write a script which
>        does all the moving and making of symlinks/rewrites.
>        make it _really_ easy, else we'll forget to do it
>     2. what about all the rest of the release? you only
>        mention the HTML. the whole tree just moves around,
>        no changes which might affect relative links?
>
> * as regardless extensionless URLs, I'd like some
>    confirmation that no browers would misbehave with this.
>    are our files being delivered with the right mimetypes or whatever?
>
>    I do worry that this is a step too far. without rewrites,
>    all the existing URLs would break, and I think the rewrites
>    may be complex.
>
>
> I'd vote for doing the web site changes and the versioning,
> (as separate exercises) and holding off on the extensionless
> stuff for a bit.
>
> Finally, if we do it, lets make this a clear project with
> allowed person time, deadlines
> and deliverables. Be specific about what can be achieved
> by the next MM. I personally am sort of thinking
> I will very little time to assist on it before October.
>
>   

-- 

Dr Elena Pierazzo

Research Associate

Centre for Computing in the Humanities

King's College London

26-29 Drury Lane

London WC2B 5RL


Phone: 0207-848-1949

Fax: 0207-848-2980

elena.pierazzo[at]kcl.ac.uk

www.kcl.ac.uk/cch