Re: [tei-council] Pull Reqs on Stylesheets : Release 3.1.0 where are we?

Sorry--I'm not awake yet...Of course, now that I reread all the posts, I guess we're not ready to commit these branches to Stylesheets dev. (Of course we haven't resolved the minOccurs/maxOccurs discussion and DTD processing doesn't work yet, though I think if we have to ignore DTDs the latest solution ought to be fine generally). But hope we're testing stuff against the branches. Elisa Typeset by hand on my iPad -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text Associate Professor of English University of Pittsburgh at Greensburg 150 Finoli Drive, Greensburg, PA 15601 USA E-mail: ebb8@pitt.edu | Development site: http://newtfire.org Typeset by hand on my iPad

On Dec 3, 2016, at 8:48 AM, Elisa wrote:

I don't know if this is significant or if someone's on top of this, but I see 5 pull requests waiting to be merged into the Stylesheets repo, including the one from Syd's sydboccurs2 branch with corrections on @minOccurs and @maxOccurs.

I'm not sure of protocol on merging pull requests, but don't we need to pull in Syd's branch, or are we testing the Stylesheets using that branch to make sure the updates work properly prior to release?

Elisa

Typeset by hand on my iPad

...

On Dec 2, 2016, at 2:06 PM, Syd Bauman wrote:

The updates for *validation* of @minOccurs and @maxOccurs have been pushed into the TEI repo, and seem to be working fine. (HTML tagdoc page correct, but a bit ugly IIRC.) I had hoped to get wide agreement (preferable) or serious dissension from my "do what W3C does" solution, but haven't really.

As for *processing* of @minOccurs and @maxOccurs, I am pretty sure that the code in the sydb-occurs2/ branch works for RNG (and thus XSD), although Lou would prefer some different choices for some invalid combinations. (In particular, LB wants the invalid combination @minOccurs="3" with no @maxOccurs to behave as though @maxOccurs were unbounded.) I have no objection to changing it to what LB wants, but see no need to do so in a rush.

HOWEVER, I am having a bit of a hard time getting DTDs to work, in large part because they are always invalid because there are content models that are not surrounded by parens. I do not know if this is an error in something I did or that "dtdMagic" absorption into odd2dtd was incomplete. I tried calling Hugh a few minutes ago to see if we could hammer that out, but he wasn't around.

SO, my point is that release is not ready because DTDs are not ready, but otherwise things should be ready very soon, IMHO. -- 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