Hi all,

Interesting suggestion.  What other use cases could you think of if you had a biblFull there?  What else would/could it sensibly document?  Since that gives you a sourceDesc, might it be a place in ODD to document when one has imported into one's ODD, where that originated? (or something like that).  I've just not thought through what other possibilities this might enable, yet.

-James 

In message <B9CEBE85-BA2D-4AEC-B14F-46DCE7DAFE44@loria.fr> Laurent Romary <laurent.romary@loria.fr> writes:
> my Occam's razor kind-of mood would make me think to identify  
> precisely what we need and just implement this. But your strategy  
> makes senses.
> 
> Others: shout if you think we are going astray!
> 
> Le 26 mars 09 à 12:54, Sebastian Rahtz a écrit :
> 
> > Laurent Romary wrote:
> >> OK. Let me try to be creative there.
> >> I would see an elementSpec as containing a revisionDesc-like child  
> >> indicating its history:
> >> - when it was introduced, maybe taken up from previous editions  
> >> (P1...)
> >> - major revision it ecountered to record, for instance, semantic  
> >> shifts , if people start to wonder why there is a descrepancy  
> >> between an existing corpus and the actual documentation
> >> - the current status, e.g. 'deprecated'
> >
> > I think thats an orthoganal, but interesting, proposal. you'd
> > effectively have most of a teiHeader as child of *Spec. it could
> > have all sorts of uses.
> >
> > but why stop there? why not go all the way and add <biblFull>
> > to the gloss/desc/equiv section? then you can deprecate an attribute,
> > or a valItem or whatever.
> >
> > -- 
> > Sebastian Rahtz
> > 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
>