I'd agree with James that settingDesc isn't the right place. I don't
think appInfo is either (it's specifically for documenting software
that edited the file... I suppose if the file in hand was created by
translating one document into this document using a stylesheet or a
series of stylesheets you could argue appInfo, but not for a
stylesheet for the *display* of this document).
At a workshop I taught recently someone asked me the same question,
and I think I told him to use a processing instruction. However, he
was really interested in keeping the TEI file and they stylesheet
together (that is, guaranteeing that the file will only be processed
using this stylesheet). If your TEI file and stylesheet are separated,
or your stylesheet is completely lost somehow, no matter where you
document it it won't help, practically speaking.
What about documenting the stylesheet itself within the TEI file (I
mean by including the full stylesheet - not a pointer)? Has anyone
tried this? I can't think of how it would work for processing, but
might be nice simply for documentation purposes.
On Tue, Jul 21, 2009 at 10:23 AM, James
Cummings<[log in to unmask]> wrote:
> Torsten Schaßan wrote:
>> how do others declare respectively document how a born digital document
>> should be presented - e.g. which xslt has to be applied to show the content
>> in a certain and defined way?
>> Wouldn't the profileDesc/settingDesc be the perfect place?
>> Right now the settingDesc is said to contain information about language
>> corpora but the info I need to store seems to fit perfectly into this
>> element if I understood or interpreted it in a broader sense?
> I'm not sure settingDesc is the right place. In my mind that means where
> the text was recorded (in the case of a spoken text) or something about its
> setting. The stylesheet to be chosen to render it in one way or another
> seems much more like it should be in something like appInfo or encodingDesc
> somewhere. (Ok, I recognise appInfo is for information about some program
> that has touched the TEI file, rather than a link between the TEI file and
> one or more stylesheets.)
> Since what you want to link the TEI file to a stylesheet for purposes of
> processing, another option, of course, is to use processing instruction.
> This doesn't really document sufficiently, but would provide a link, and has
> no implications for TEI Conformance or validity.
> <?torsten type="stylesheet1" href="file.xsl" ?>
> Not sure what the best answer is, I'm sure someone here will have a better
> answer, but settingDesc does seem wrong to me.
> Dr James Cummings, Research Technologies Service, University of Oxford
> James dot Cummings at oucs dot ox dot ac dot uk
Dot Porter (MA, MSLS) Metadata Manager
Digital Humanities Observatory (RIA), Regus House, 28-32 Upper
Pembroke Street, Dublin 2, Ireland
-- A Project of the Royal Irish Academy --
Phone: +353 1 234 2444 Fax: +353 1 234 2400
http://dho.ie Email: [log in to unmask]