BPTL Workgroup Minutes March 7, 2016

Present:
 * Kevin Hawkins (KH)
 * Stefanie Gehrke (SG)
 * Elli Mylonas (EM)
 * James Griffin (JG)
 * Peter Gorman (PG)
 * Martin Mueller (MM)
 * KH: Any questions about previous minutes? - None to speak of.
 * 1) EM makes google doc
 * JG: What is the relationship between this SIG and the ontology SIG? KH points out it’s not really the same, as Ontology are more concerned with formal ontologies such as CIDOC-CRM.
 * 1) Version numbering: EM asked that we are fine with using “3.0.0” instead of “3.0”.  All agreed, so she will make a release with tag v. 3.0.0. [DONE]
 * 2) Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
 * 3) Issue 19: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
 * 4) Issue 20: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, assigned to EM.
 * 5) Issue 22: Text edit. Easy fix, seems like mistake, assigned to JG
 * 6) Issue 29: It would be very useful, especially for libraries, if we could provide information on how to use only the header component of the schema with another schema/application. SG noted that she found a document referring to header elements recommended for use in TEI Simple. MM agreed to investigate use of header in TEI Simple.
 * 7) If we are going to explain how to incorporate ODD of the Libraries header into another ODD, then this may also apply to incorporating other bits.This leads us down the path of creating tutorials on editing the ODD. It is wiser to just deal with the header as that is the most likely part of the ODD to be re-purposed. Furthermore, this is a lot of work for a hypothetical use.
 * 8) KH drafts text that addresses this, and EM works with Syd Bauman to add the ODD specific issue. This would be incorporated into the TEI in Libraries web page.
 * 9) Issue 3: Recommend use of @style instead of @rend . The group approves, assigned to PG.
 * 10) Issue 4:  Clarify representation of milestones. MM: Discussion about our use. JG said that he prefers a solution in which meaningful typography or other symbols are encoded as content, not attribute values or tagging. SG said it would be nice to have sample encodings of “TEI in Libraries” in TEI-C as well.  Possible to use  instead? MM will post to TEI-L. EM suggests some research on the part of all of us on this since it’s been raised on TEI-L before. KH also points out that in General, BPTL tries to give clear direction, not too many choices.