Re: [tei-council] Decision time for xenodata/@scope

Sounds like #2 is the winner. I’m going to change @scope to data.word and add a description for it. I’m also going to insert one of the examples into the Guidelines. If some of you can take a look at it in the morning, we’ll see if it passes muster and decide whether to proceed with the release this week.

On Oct 7, 2015, at 10:26 , Hugh Cayless wrote:

We seem to be at a bit of an impasse, and we're releasing tomorrow. At this point we can:

1) release xenodata as-is, with @scope and the current value list. 2) release xenodata with @scope, but without a list of recommended values 3) release xenodata without @scope 4) back out xenodata and release without it

My own preferences, in order, are 3, 2, 4, 1. I'm not convinced of the need for @scope, but I really think the value names have to be changed (and some removed) if we go with it.

Thoughts? In addition, I do think we need to provide an example or two in the text of the Guidelines. I can come up with a non-XML one pretty easily.