Also I'd like to add: It bothers me a bit that one day before a release we're still discussing the inclusion of an attribute. I'd be inclined to put off the release until everybody is comfortable with what we're doing. Cheers, Martin On 15-10-07 09:17 AM, Lou Burnard wrote:

My vote is 2 3 4 1

So far only a small minority of council members has expressed any opinion. If we can't get a consensus or at least a majority view I think we have a serious problem.

Sent from my Samsung Galaxy Tab®|PRO

-------- Original message -------- From: Hugh Cayless Date:10/07/2015 15:27 (GMT+00:00) To: TEI Council Subject: [tei-council] Decision time for xenodata/@scope

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. -- 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

My personal preferences are 3,2,4,1 but maybe Martin is right, we could delay some days the release and discuss better the @scope issue (even if I'd rather examine it f2f). f 2015-10-07 18:49 GMT+02:00 Martin Holmes :

Also I'd like to add:

It bothers me a bit that one day before a release we're still discussing the inclusion of an attribute. I'd be inclined to put off the release until everybody is comfortable with what we're doing.

Cheers, Martin

On 15-10-07 09:17 AM, Lou Burnard wrote:

...

My vote is 2 3 4 1

So far only a small minority of council members has expressed any opinion. If we can't get a consensus or at least a majority view I think we have a serious problem.

Sent from my Samsung Galaxy Tab®|PRO

-------- Original message -------- From: Hugh Cayless Date:10/07/2015 15:27 (GMT+00:00) To: TEI Council Subject: [tei-council] Decision time for xenodata/@scope

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. -- 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

-- 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

-- Fabio Ciotti Dipartimento di Studi letterari, Filosofici e Storia dell’arte Università di Roma Tor Vergata President "Associazione Informatica Umanistica Cultura Digitale" (AIUCD)

For the record, I'd go for 2. We can add a suggested value list later with values we agree.

From holiday, James

-- Dr James Cummings, Academic IT, University of Oxford -----Original Message----- From: Hugh Cayless [philomousos@gmail.com] Received: Wednesday, 07 Oct 2015, 21:28 To: TEI Council [tei-council@lists.tei-c.org] Subject: 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.

-- 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