Council agenda 2013-04

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>