Difference between revisions of "Council agenda 2013-04"
Jump to navigation
Jump to search
(getting things going) |
|||
Line 1: | Line 1: | ||
− | + | === 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. | |
− | * ADD | + | |
+ | === specific issues, Guidelines === | ||
+ | Note that the Chair may wish to discuss some of these via list instead of face-to-face. | ||
+ | * Shouldn't <tt><event></tt> be allowed in <tt><org></tt> and <tt><item></tt>? | ||
+ | * Shouldn't <tt><email></tt> be allowed as a child of <tt><person></tt>? | ||
+ | * Add <tt><affiliation></tt> to <tt>att.typed</tt> | ||
+ | * Issue: structured vs unstructed data — why can't paragraphs and specialized elements co-exist as children of <tt><particDesc></tt>, <tt><settingDesc></tt>, <tt><setting></tt>, <tt><editionStmt></tt>, <tt><sourceDesc></tt>, <tt><msDesc></tt>, <tt><msContents></tt>, <tt><msItem></tt>, <tt><objectDesc></tt>, <tt><supportDesc></tt>, <tt><supportDesc></tt>, <tt><layoutDesc></tt>, <tt><handDesc></tt>, <tt><typeDesc></tt>, <tt><scriptDesc></tt>, <tt><decoDesc></tt>, <tt><bindingDesc></tt>, <tt><binding></tt>, <tt><sealDesc></tt>, <tt><history></tt>, <tt><recordHist></tt>, <tt><custodialHist></tt>, <tt><msPart></tt>, <tt><climate></tt>, <tt><event></tt>, <tt><langKnowledge></tt>, <tt><org></tt>, <tt><listRelation></tt>, <tt><relationGrp></tt>, <tt><person></tt>, <tt><personGrp></tt>, <tt><place></tt>, <tt><population></tt>, <tt><state></tt>, <tt><terrain></tt>, <tt><scriptStmt></tt>, <tt><recordingStmt></tt>, <tt><recording></tt>, <tt><broadcast></tt>, <tt><metDecl></tt>, <tt><publicationStmt></tt>, and <tt><seriesStmt></tt> | ||
+ | * Should <tt><cRefPattern></tt> apply to ''all'' data.pointer attrs (and drop <tt>@cRef</tt>)? | ||
+ | * Why is <tt>model.pLike</tt> allowed as a child of <tt><msItemStruct></tt>? | ||
+ | * The following content models could probably use re-thinking: | ||
+ | ** <tt><broadcast></tt> | ||
+ | |||
+ | === ADD OTHERS HERE === | ||
[[Category:Council]] | [[Category:Council]] |
Revision as of 04:31, 28 March 2013
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>