[tei-council] confusion about TEI at version and teiCorpus at version

[Kevin Hawkins]

On 11/14/2011 12:40 AM, Laurent Romary wrote:
> I think TEI at version and @source are quite different objects. @source
> is a reference (magic or not) to an ODD spec from which a
> customization is made.

Right.  Forget about @source for now.

 > On the contrary, TEI at version is a vague
> documentary item telling the user against which TEI vocabulary the
> document has been put together. This of course obly applies to the
> TEI elements and if further customization occured (like new
> elements), this will not tell you anything. It is a kind of time
> tracker for TEI document. I would thus not require it to be a URI.
> Laurent

Right, but my point is that I don't see any useful way for someone to 
use this "tracker" with TEI version numbers like "1.9.1".

> Le 13 nov. 2011 à 22:38, Kevin Hawkins a écrit :
>
>> Shouldn't the datatype TEI at version and teiCorpus at version (but not
>> unicodeName at version) be xsd:anyURI so that these two work like
>> @source (in att.readFrom)?  If so, should I submit this as as bug
>> report or a feature request?
>>
>> But more generally, what purpose do TEI at version and
>> teiCorpus at version serve?  We say that people should use a
>> customization of the TEI, so in what way would a given TEI document
>> be valid against a "version number of the TEI Guidelines" (as
>> defined for TEI at version) or "the TEI scheme" (as defined for
>> teiCorpus at version)?
>> _______________________________________________ tei-council mailing
>> list tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
>
> Laurent Romary INRIA&  HUB-IDSL laurent.romary at inria.fr
>
>
>