[tei-council] datatype issues (part 1) continued,,,

[Sebastian Rahtz]

Lou Burnard wrote:

>
> I propose to change this to tei.data.formula which maps to xsd:token

not sure I like the word "formula". that seems too precise to me.
tei.data. notation?

>
> Not bad, but we do use "term" rather a lot in slightly different ways 
> elsewhere in the Guidelines, and, crucially, in my book a "term" is 
> taken from a human language not an artificial one. So my proposal is now
>
> 1. rename tei.data.token as tei.data.ident, mapping it to NMTOKEN.
> 2. tei.data.tokens is a list of tei.data.ident
> 3. tei.data.enumerated is a ref to a tei.data.ident
> 4. tei.data.key is mapped to NCName

"ident" or "name"? and tei.data.enumerated is probably a ref to xsd:token

>
> tei.data.enumerated : the value is defined by a valList (type=closed)

only sometimes. this is still messy

> tei.data.code : the value is defined by a pointer to something which 
> must exist

ok

> tei.data.key : the value is defined by an enumeration elsewhere e.g. a 
> database key

ok

> tei.data.ident : the value is a name or identifier of some kind but 
> not necessarily enumerated or enumeratable


ok

but tei.data.key is not an NMtoken but a simple string

sebastian