Presumably there are changes in some content models as well, at the very least to make macro.anyxml use the new anyElement element? As per my doc? Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC: #1373 is implemented in the Stylesheets. I need to update the documentation to reflect the decisions made in the course of implementing it. I hope I've done it right :-). On Fri, Nov 4, 2016 at 9:41 PM, Syd Bauman wrote:

I just skimmed the 15 open tickets flagged as "Guidelines 3.1.0"[1]. IMHO, none are outright release blocking, but #1501 "Cannot generate valid DTD within oXygen" is seriously high priority, and we should be working on it ASAP.

I've CCed Martin on this, as he knows a lot about the oXygen framework.

I note that there has been a lot of activity on #1373 "Need for some way to represent macro.anyXML in Pure ODD", which I have yet to have the chance to read. I hope to dive into this issue tomorrow. But in any case, I do not think it a release blocker to leave PureODD without a macro.anyXML replacement for a release or two -- better to do it right than to do it rushed, IMHO.

Notes ----- [1] From the link in the minutes: https://github.com/TEIC/TEI/milestone/2 -- 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

This suggests you haven't tested your changes yet... Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC: Yeah, I think that's an open question: whether we want to make that change now or not, and how it looks when we make it. We could go halfway, for example, and only change macro.anyXML. On Sat, Nov 5, 2016 at 9:21 AM, Lou Burnard wrote:

Presumably there are changes in some content models as well, at the very least to make macro.anyxml use the new anyElement element? As per my doc?

Sent from my Honor Mobile

-------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC:

#1373 is implemented in the Stylesheets. I need to update the documentation to reflect the decisions made in the course of implementing it. I hope I've done it right :-).

On Fri, Nov 4, 2016 at 9:41 PM, Syd Bauman wrote:

...

I just skimmed the 15 open tickets flagged as "Guidelines 3.1.0"[1]. IMHO, none are outright release blocking, but #1501 "Cannot generate valid DTD within oXygen" is seriously high priority, and we should be working on it ASAP.

I've CCed Martin on this, as he knows a lot about the oXygen framework.

I note that there has been a lot of activity on #1373 "Need for some way to represent macro.anyXML in Pure ODD", which I have yet to have the chance to read. I hope to dive into this issue tomorrow. But in any case, I do not think it a release blocker to leave PureODD without a macro.anyXML replacement for a release or two -- better to do it right than to do it rushed, IMHO.

Notes ----- [1] From the link in the minutes: https://github.com/TEIC/TEI/milestone/2 -- 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 -- 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

My working hypothesis is that we should make the changes I specified in that doc, tweak till they work, and then commit the changes! Am starting to do this in my local copy anyway. Sent from my Honor Mobile -------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC: I've tested them, but I haven't pushed changes to the TEI repo yet. On Sat, Nov 5, 2016 at 9:33 AM, Lou Burnard wrote:

This suggests you haven't tested your changes yet...

Sent from my Honor Mobile

-------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC:

Yeah, I think that's an open question: whether we want to make that change now or not, and how it looks when we make it. We could go halfway, for example, and only change macro.anyXML.

On Sat, Nov 5, 2016 at 9:21 AM, Lou Burnard wrote:

...

Presumably there are changes in some content models as well, at the very least to make macro.anyxml use the new anyElement element? As per my doc?

Sent from my Honor Mobile

-------- Original Message -------- Subject: Re: [tei-council] release blockers for 3.1.0 From: Hugh Cayless To: TEI Council CC:

#1373 is implemented in the Stylesheets. I need to update the documentation to reflect the decisions made in the course of implementing it. I hope I've done it right :-).

On Fri, Nov 4, 2016 at 9:41 PM, Syd Bauman wrote:

...

I just skimmed the 15 open tickets flagged as "Guidelines 3.1.0"[1]. IMHO, none are outright release blocking, but #1501 "Cannot generate valid DTD within oXygen" is seriously high priority, and we should be working on it ASAP.

I've CCed Martin on this, as he knows a lot about the oXygen framework.

I note that there has been a lot of activity on #1373 "Need for some way to represent macro.anyXML in Pure ODD", which I have yet to have the chance to read. I hope to dive into this issue tomorrow. But in any case, I do not think it a release blocker to leave PureODD without a macro.anyXML replacement for a release or two -- better to do it right than to do it rushed, IMHO.

Notes ----- [1] From the link in the minutes: https://github.com/TEIC/TEI/milestone/2 -- 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 -- 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 -- 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