Re: [tei-council] Release?

As we seem to be some way from a consensus on the right way forward, may I propose a further vote? Option 1. Remove the attribute @scope for now. Option 2. Remove the xenoData element for now. We can then thrash out what is clearly a somewhat divisive issue at the ftf, targetting the next release for its resolution. My vote is (now) for option 1, but I can live with option 2. On 08/10/15 16:14, Hugh Cayless wrote:

Syd, your input is *always* welcome, and it is possible that we're all wrong and you're right. If so, you get to sing "Nyaa, nyaa, told you so!" at us.

It's not self-evident to me. I'm always learning new stuff about TEI. What's the advantage of data.enumerated in the absence of a valList?

On Thu, Oct 8, 2015 at 11:08 AM, Syd Bauman wrote:

...

I do not know if my comments are welcome on this matter any more, since I am being completely over-ruled on this. So feel free to continue to ignore me. But that said, could we at least make the datatype of @scope data.enumerated, not data.word? I'll argue why if needed, but I'm hoping this is self-evident. (Of course, I think the whole idea of having such an attribute *without* a suggested values list is self-evidently stupid, so apparently my barometer on self-evidentness is mis-calibrated.)

-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived