The cover page, and perhaps each subordinate page, in
the html transform of the guidelines should prominently
express the associated release rubric and date, so as
to facilitate citation and update.
This is a good idea, but requires work on xslt and also on the xml because we don't have version/date info easily available. The date that appears now is the date of transform and upload.
SVN used to have the variables for this. XML should have commit info, and web page should have the release info.
I'll track down the @version attribute used in the TEI Guidelines for this purpose, and add that to driver.xml. It's then a relatively simple XSLT question to add this to the web pages, so I'll suggest doing that too. (Open question about what "dev" pages should say?)
@version on <TEI> should read "P5", rather than the EpiDoc version.
Perhaps the @source on <schemaSpec> in the EpiDoc ODD should have a value such as "epidoc:8.18" (by analogy with "tei:1.5.1" recommended at http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-att.readFrom.html). Not sure what the implementation/validation implacations of that are. I suspect the xslt expects something other that what will actually be here.
So maybe then, the answer is something bespoke like @n on the <TEI> of the Guidelines (i.e. in driver.xml)? What do others think? (Perhaps to be discussed on Markup.)
What I'd like to see is the ability to:
GB will implement a bespoke solution in the driver and epidoc gl XSLT, and run past group for approval.
Implemented at [r2213].
I have added a <seg type="version"> in the title of driver.xml, and written an override to the template named "stdfooter" in the TEI stylesheets to display this in the footer. There may be some discussion needed on exactly how we should (a) encode, and (b) display this information, but for now it works so I'm closing the ticket.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.