Council agenda 2013-04
Jump to navigation
Jump to search
'This is obsolete: the agenda has been rearranged as the meeting progressed in the Google Docs file of the minutes.
(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
- Review of any outstanding issues from previous action lists
09:30 - 11:30
- Bug/FR Processing
Amber Feature Requests
- A)[SR MH SB]
- https://sourceforge.net/p/tei/feature-requests/446/ @schemeVersion should be added to specify the version of a style scheme
- https://sourceforge.net/p/tei/feature-requests/447/ model.gLike should be added as member of model.linePart
- https://sourceforge.net/p/tei/feature-requests/402/ A note about white space in <persName> et al.
- B) [JC PS BB]
- https://sourceforge.net/p/tei/feature-requests/449/ am and ex should claim membership of att.typed
- https://sourceforge.net/p/tei/feature-requests/438/ Have fileDesc claim membership of att.docStatus
- https://sourceforge.net/p/tei/feature-requests/421/ Guidelines front pages are confusing
- C) [GB LB RW]
- https://sourceforge.net/p/tei/feature-requests/448/ Improve discussion of <substJoin> element
- https://sourceforge.net/p/tei/feature-requests/443/ @resp should be a member of att.global
- https://sourceforge.net/p/tei/feature-requests/440/ Attribute datatypes should be defined indirectly
- D) [KH EM HC]
- https://sourceforge.net/p/tei/feature-requests/389/ clarify definition of @from on locus and biblScope
- https://sourceforge.net/p/tei/feature-requests/429/ biblScope@unit & citedRange@unit: consistency & sugg. values
- https://sourceforge.net/p/tei/feature-requests/437/ Allow relatedItem in biblFull
11:30 - 13:00
- Deprecation
- TEI SourceForge Environment:
- Change in TEI sourceforge environment: any residual problems? any potential benefits? Discuss remaining questions (under "to decide going forward"). Any suggestions on how to find old-style URLs on the wiki? Can anyone search the wiki db to find pages with links that contain "106328"?
- Splitting out additional resources such as Stylesheets to their own projects/repositories
- Since we have both Specs/ and Specs-Unused/ , what if we create a Guidelines-Unused/ to complement Guidelines/ ? (And then we'd move SH-OtherMetadataStandards.xml to there.) Or we could just rename "Specs-Unused" to "nowDefunct" and keep all the old superseded garbage in there.
13:00 - 14:00
- Lunch
14:00 - 16:30
- Bug/FR Processing -- Continue discussions if necessary, otherwise move on to:
Amber Bugs Part 1
- E)[SR EM RW]
- https://sourceforge.net/p/tei/bugs/501/ att.typed overlapps confusingly with many other definitions
- https://sourceforge.net/p/tei/bugs/516/ Documentation of <equiv> is confusing
- https://sourceforge.net/p/tei/bugs/515/ Bad example of feature/@fVal
- https://sourceforge.net/p/tei/bugs/551/ contained by/contained in
- F) [JC MH HC]
- https://sourceforge.net/p/tei/bugs/504/ An illogicality in styleDefDecl & styleDef
- https://sourceforge.net/p/tei/bugs/539/ @scheme on <styleDefDecl> and <rendition> should be a class
- https://sourceforge.net/p/tei/bugs/544/ Whitespace handling in Guidelines examples
- https://sourceforge.net/p/tei/bugs/552/ races
- G) [GB PS SB]
- https://sourceforge.net/p/tei/bugs/496/ inconsistencies in app@from and app@to
- https://sourceforge.net/p/tei/bugs/528/ consistency in "the Guidelines" vs. "these Guidelines"
- https://sourceforge.net/p/tei/bugs/543/ Use of `<add>` etc for "authorial" interventions
- https://sourceforge.net/p/tei/bugs/553/ relationships between objects
- H) [KH LB BB]
- https://sourceforge.net/p/tei/bugs/288/ deprecate use of gram except as a child of gramGrp
- https://sourceforge.net/p/tei/bugs/493/ value of biblScope@type in example in seriesStmt spec
- https://sourceforge.net/p/tei/bugs/541/ canonical references: imprecise language about software handling and errors
- https://sourceforge.net/p/tei/bugs/555/ counting people
16:30 - 17:30
- Code Bounties
18:30 -
- Supper
Friday 12 April 2013
09:00 - 10:00
- Skype call with Elena; Re: Board Proposals
- Report on TEI SIGs activities (JC)
10:00 - 12:00
- Bug/FR Processing -- Continue discussions if necessary, otherwise move on to:
Amber Bugs Part 2
- I)[JC LB RW]
- https://sourceforge.net/p/tei/bugs/506/ Meaning of @corresp rather in dispute
- https://sourceforge.net/p/tei/bugs/468/ Order of elements in publicationStmt
- https://sourceforge.net/p/tei/bugs/557/ Category mistake
- J) [KH EM SB]
- https://sourceforge.net/p/tei/bugs/448/ Bibliography: use of <idno> needs checking
- https://sourceforge.net/p/tei/bugs/512/ Generate statistics in the Guidelines rather than hard code
- https://sourceforge.net/p/tei/bugs/558/ name/orgName
- K) [SR MH BB]
- https://sourceforge.net/p/tei/bugs/549/ Uses of <person> element
- https://sourceforge.net/p/tei/bugs/550/ prescription/description
- https://sourceforge.net/p/tei/bugs/560/ Arne Magnusson, again
- L) [GB PS HC]
- https://sourceforge.net/p/tei/bugs/405/ XPointer schemes may not nest, but see ch. 16
- https://sourceforge.net/p/tei/bugs/548/ use of modal verbs in Guidelines
- https://sourceforge.net/p/tei/bugs/527/ move citations from <note>s to BIB
12:00 - 13:00
- Translation of Guidelines : what practical issues are needed to facilitate it ?
- Approval of TEI-SIG for "Computer-Mediated Communication" (JC)
13:00 - 14:00
- Lunch
14:00 - 16:30
- Bug/FR Processing -- Continue discussions if necessary, otherwise move on to:
Review of Green FR / Green Bugs/ Red FR / Red Bugs 16:30 - 17:30
- Update on proposals to extend ODD : LB/SR have papers in pipeline
- Attributes without examples: http://sourceforge.net/p/tei/bugs/401/ and http://wiki.tei-c.org/index.php/AttsWithoutEgs
18:30 -
- Supper
Saturday 13 April 2013
09:00 - 10:00
- Update on the work of the Text Directionality Working Group (MH)
- Update on the work of the div.liminal working group (LB/KH/PS)
10:00 - 12:00
- Bug/FR Processing if done start implementation!
12:00 - 13:00
- Any remaining general discussion items (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)]
- I would also like to have these in the SF ticketing system. It allows for involvement of non-Council members in the discussion. (Kshawkin 16:03, 29 March 2013 (EDT))
- 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? ]
