Difference between revisions of "Council agenda 2013-04"

From TEIWiki
Jump to navigation Jump to search
m
m (Thursday 11 April 2013)
Line 10: Line 10:
 
* Bug/FR Processing
 
* Bug/FR Processing
 
'''11:30 - 13:00'''
 
'''11:30 - 13:00'''
* Discussion of General Issues Here
+
* ODD 'Foxglove' Details Proposal (LB)
* Add them here
+
* More general issues here?
 
'''13:00 - 14:00'''
 
'''13:00 - 14:00'''
 
* Lunch
 
* Lunch
Line 21: Line 21:
 
'''18:30 -'''
 
'''18:30 -'''
 
* Supper
 
* Supper
 
  
 
== Friday 12 April 2013 ==
 
== Friday 12 April 2013 ==

Revision as of 13:54, 28 March 2013


(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

  • ODD 'Foxglove' Details Proposal (LB)
  • 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.

  • Shouldn't <event> be allowed in <org> and <item>?
  • Shouldn't <email> be allowed as a child of <person>?
  • Add <affiliation> to att.typed
  • 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>
  • Should <cRefPattern> apply to all data.pointer attrs (and drop @cRef)?
  • Why is model.pLike allowed as a child of <msItemStruct>?
  • The following content models could probably use re-thinking:
    • <broadcast>

ADD OTHERS HERE