You will find the discussion of "our" topic (the generalised object element) at:
(Wednesday morning at 09:00).
The relevant action point is:
"Torsten Schassan to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01."
Begin forwarded message:
> From: James Cummings <James.Cummings@...>
> Subject: Minutes of TEI Technical Council Meeting 11-13 November
> Date: 25. november 2013 14:44:15 GMT+01:00
> To: TEI-L@...
> Reply-To: James.Cummings@...
> Dear TEI-L,
> On Monday 11 November to Wednesday 13 November 2013 the TEI Technical Council met at Rewley House at the University of Oxford. This face-to-face meeting alternated between general issue discussion sessions and processing the feature request and bug tickets submitted by the TEI-C community. There was a concerted effort in this meeting to clean up old tickets and resolve them wherever possible. Full detailed minutes are at http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml and a full list of actions and their current status is available from: http://wiki.tei-c.org/index.php/Oxford2013-Actions2
> The general discussion sessions included such issues as:
> - reports on a variety of initiatives the Technical Council is investigating;
> - resolving EEBO-TCP to TEI P5 migration issues;
> - the migration of the underlying TEI ODD language to so-called 'Pure ODD';
> - changes to the release process (to formalise 'alpha' and 'beta' releases);
> - plans for a TEI hackathon;
> - further work on TEI Internationalization;
> - investigations into our examples of attribute usage;
> - work on new Guidelines material such as Text Directionality;
> - reports from SIGs including work cutting across the Ontologies and Manuscripts SIGs concerning Object Description; and the Linguistics SIG and the Correspondence SIG;
> - Cheatsheets and How-tos;
> - processes for election of the new TEI Technical Council chair;
> - planning for face-to-face and teleconference meetings in the new year;
> - the continuation of a Board representative at Technical Council Meetings.
> Feature requests and bugs were all discussed in groups and by the whole Technical Council, they were assigned, if possible agreed, and recategorised for implementation or further work. Many tickets were resolved by the Technical Council during breaks in the meeting, most were given due dates at which to have implemented or report back concerning the ticket. Some random highlights include agreement that: <stage> will have @place; the creation of <abstract> ; better version information on Guidelines HTML footers; <docDate> allowed inside <dateline> ; content model of <salute> loosened to macro.paraContent; regex pattern of @matchPattern better specified; better symmetry between head and trailer; members of model.respLike also become members of att.canonical (and so get @ref); @name on <relation> no longer required; clarification on headings and commentary as part of a figure; decisions on TEI Website bugs; and many more.
> Many thanks to the TEI Technical Council and those submitting the feature requests and bugs,
> James Cummings
> TEI Technical Council Chair
> Dr James Cummings, James.Cummings@...
> Academic IT Services, University of Oxford