[tei-council] att.sourced (<lb ed="1674">) contradiction

[Lou Burnard]

On 06/01/13 21:37, Sebastian Rahtz wrote:
>
> On 6 Jan 2013, at 19:08, Lou Burnard <lou.burnard at retired.ox.ac.uk> wrote:
>
>> data.enumerated, for example says "the value should (actually or
>> potentially) come from a fixed list of possible values". It also says
>> "the value looks like an XML name". If we found a way of implementing
>> enumerations which didn't need the additional constraint of being a
>> name, then we'd change the mapping of data.enumerated
>
> why do we still have that restriction, I wonder? it used to be, I think,
> 'cos we had that restriction on valItem/@ident, but that is no longer the case.


yes, I'd forgotten that in a weak moment we allowed valItem/ident to 
become just text!


> what would go wrong if we said data.enumerated used data.word instead
> of data.name?

all those people who insisted on using spaces within @ident values would 
get v. cross ?


>
> apologies if we've had this discussion in the past and I have forgot.

good thing we have this tracker system eh


>>