Council agenda 2013-04

(Note: All agenda times approximate and we will build in some comfort breaks in morning/afternoon.)

Thursday 11 April 2013

09:00 - 09:30

• Opening Discussion

09:30 - 11:30

• Bug/FR Processing

11:30 - 13:00

• Review of any outstanding issues from previous action lists

* http://wiki.tei-c.org/index.php/AnnArbor2012-Actions
* http://wiki.tei-c.org/index.php/Oxford2012-Actions

• Update on "foxglove" proposals to extend ODD : LB/SR have papers in pipeline
• Translation of Guidelines : what practical issues are needed to facilitate it ?
• Change in TEI sourceforge environment : any residual problems? any potential benefits ?
• More general issues here?

13:00 - 14:00

• Lunch

14:00 - 16:30

• Bug/FR Processing

16:30 - 17:30

• Discussion of General Issues Here
• Add them here

18:30 -

• Supper

Friday 12 April 2013

09:00 - 10:00

• Skype call with Elena; Re: Board Proposals
• Another General Issue

10:00 - 12:00

• Bug/FR Processing

12:00 - 13:00

• Discussion of General Issues Here
• Add them here

13:00 - 14:00

• Lunch

14:00 - 16:30

• Bug/FR Processing

16:30 - 17:30

• Discussion of General Issues Here
• Add them here

18:30 -

• Supper

Saturday 13 April 2013

09:00 - 10:00

• Discussion of General Issues Here
• Add them here

10:00 - 12:00

• Bug/FR Processing

12:00 - 13:00

• Discussion of General Issues Here
• Add them here (optional departing for those who need to leave)

13:00 - 14:00

• Lunch (optional)

14:00 - 16:30

• Bug/FR Processing/Discussion/Implementation (optional)

18:30 -

• Supper (for those remaining)

Other notes

Action items from 2012-12-13 conf call

• GB to create a list of possible code-bounty projects
• Continuing discussion on tei-council of separating out community projects from SF repo and using Github for these instead.

specific issues, Guidelines

Note that the Chair may wish to discuss some of these via list instead of face-to-face.

[I think some of these should be submitted as feature requests. They don't make sense as agenda items (but I've added some comments anyway LB)]

• Shouldn't <event> be allowed in <org> and <item>? [Not without justification]
• Shouldn't <email> be allowed as a child of <person>? [Not without justification ]
• Add <affiliation> to att.typed [Why? ]
• Issue: structured vs unstructed data — why can't paragraphs and specialized elements co-exist as children of <particDesc>, <settingDesc>, <setting>, <editionStmt>, <sourceDesc>, <msDesc>, <msContents>, <msItem>, <objectDesc>, <supportDesc>, <supportDesc>, <layoutDesc>, <handDesc>, <typeDesc>, <scriptDesc>, <decoDesc>, <bindingDesc>, <binding>, <sealDesc>, <history>, <recordHist>, <custodialHist>, <msPart>, <climate>, <event>, <langKnowledge>, <org>, <listRelation>, <relationGrp>, <person>, <personGrp>, <place>, <population>, <state>, <terrain>, <scriptStmt>, <recordingStmt>, <recording>, <broadcast>, <metDecl>, <publicationStmt>, and <seriesStmt> [This has been discussed several times before : it was a conscious design decision at the time ]
• Should <cRefPattern> apply to all data.pointer attrs (and drop @cRef)? [no, because data.pointer is mapped to URI; dropping cRef has been proposed, unsuccessfully, before though]
• Why is model.pLike allowed as a child of <msItemStruct>? [possibly a bug?]
• The following content models could probably use re-thinking:
  • <broadcast> [er, quite possibly, care to drop a hint as to how? ]