TEIWiki - User contributions [en]

BP revision ticket triage

2017-04-03T20:12:41Z

Elli Mylonas: /* easy implementation */

== Probably not controversial ==

=== easy implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 issue 6: revisit encoding of ISBNs] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 issue 20: revised "display examples" for levels 3 and 4] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/21 issue 21: reconsider rend="keep-hyphen"] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/43 issue 43: header section: note about complete customizations] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/45 issue 45: controlled vocabulary for @type on divs?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/56 issue 56: consider <p> and <ab> inside of header elements]

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 issue 3: rewrite section on @rend and @rendition to account for @style] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/5 issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 issue 8: consider adding <width> and <height> as children of <extent>] – After reflection, Kevin has withdrawn this.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/51 issue 51: Appendix A: Recommended Attributes] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/53 issue 53: transcriptional omissions] – Syd partially implemented but still needs some work on the prose.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/2 issue 2: update the tie to a specific version of P5] – completed
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/7 issue 7: give guidance on incorporating outside metadata into a header] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/9 issue 9: intertwingled content in <editorialDecl>] – completed
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/13 issue 13: update to take into account RDA] – Kevin has recruited a cataloger colleague to help.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27 issue 27: Coordinated OCR in BPTL] – postponed indefinitely ("dormant")
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/38 issue 38: build process broken] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/47 issue 47: Some comments on the Header (comparison of BPTL against P5)] – Elli will investigate, consulting with Syd as necessary

== Could be controversial ==

=== easy implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/36 issue 36: specify how to encode sigla] – complete

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/31 issue 31: ambiguity over use of <lb/>, <cb/>, and <pb/> in Level 4] – complete

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/10 issue 10: indicating interviewers and interviewees] — assigned to Syd and Andrew, but next step is for Andrew
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/11 issue 11: encoding <pb>s within <note>s] — complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/16 issue 16: give guidance on encoding serials and composite documents]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/26 issue 26: Add (or update) examples to show use of modern authorities]

== Postpone ==

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 issue 19: pb@xml:id and METS]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/23 issue 23: relation of BP to TEI Simple (explaining the difference between the BPTL, TEI Simple, and TEI Lite)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/28 issue 28: update to take into account BIBFRAME]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/46 issue 46: BPTL Level 4 and Simple (attempting to reconcile the two)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/50 issue 50: update BPTL ODDs to use Pure ODD syntax] – complete (but should double-check after other issues are resolved)
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/37 issue 37: ODDs are invalid] – Syd will complete once TEI Technical Council acts.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/52 issue 52: reconsider our use of modal expressions]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/12 issue 12: bibliographies and other lists of works cited] – decided how to proceed but need to assign to someone
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/57 issue 57: update "Acknowledgements"]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/44 issue 44: proofreading auto-generated HTML] – assigned to James for the future

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BP revision ticket triage

2017-01-09T18:39:37Z

Elli Mylonas:

== Probably not controversial ==

=== easy implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 issue 6: revisit encoding of ISBNs] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 issue 20: revised "display examples" for levels 3 and 4] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/21 issue 21: reconsider rend="keep-hyphen"] – complete.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 issue 29: explain how to use just the header recommendations from the Best Practices] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/33 issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/34 issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/43 issue 43: header section: note about complete customizations] – Syd agreed to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/45 issue 45: controlled vocabulary for @type on divs?] – Elli is working on this.

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 issue 3: rewrite section on @rend and @rendition to account for @style] – assigned to Peter to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/5 issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 issue 8: consider adding <width> and <height> as children of <extent>] – After reflection, Kevin has withdrawn this.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] – decided not to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body] – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/42 issue 42: idno as child of biblStruct] – Kevin will implement.

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/2 issue 2: update the tie to a specific version of P5] – Syd will return to this after release of P5 3.0.0 – and [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/37 issue 37: ODDs are invalid] – Syd will complete.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/7 issue 7: give guidance on incorporating outside metadata into a header] – Kevin will propose a solution.
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/9 issue 9: intertwingled content in <editorialDecl>] – Syd will implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/13 issue 13: update to take into account RDA] – Kevin has recruited a cataloger colleague to help
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27 issue 27: Coordinated OCR in BPTL] – postponed indefinitely ("dormant")
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/38 issue 38: build process broken] – complete
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/47 issue 47: Some comments on the Header (comparison of BPTL against P5)] – Elli will investigate, consulting with Syd as necessary

== Could be controversial ==

=== easy implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/36 issue 36: specify how to encode sigla] – Kevin will propose a solution

=== medium implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] – Elli and Syd to check Kevin's draft prose
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] – waiting on December 2016 release of P5 to proceed
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/31 issue 31: ambiguity over use of <lb/>, <cb/>, and <pb/> in Level 4] – Elli will implement

=== hard implementation ===

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/10 issue 10: indicating interviewers and interviewees] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/11 issue 11: encoding <pb>s within <note>s] — agreed to implement, need a volunteer to implement
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/12 issue 12: bibliographies and other lists of works cited]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/16 issue 16: give guidance on encoding serials and composite documents]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/26 issue 26: Add (or update) examples to show use of modern authorities]

== Postpone ==

* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 issue 19: pb@xml:id and METS]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/23 issue 23: relation of BP to TEI Simple (explaining the difference between the BPTL, TEI Simple, and TEI Lite)]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/28 issue 28: update to take into account BIBFRAME]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/44 issue 44: proofreading auto-generated HTML] – assigned to James for the future
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/46 issue 46: BPTL Level 4 and Simple (attempting to reconcile the two)]

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

April 4, 2016

2016-05-02T01:41:50Z

Elli Mylonas: Created page with "'''Present:''' * Kevin Hawkins (KH) * Elli Mylonas (EM) * Peter Gorman (PG) * Martin Mueller (MM) '''Apologies:''' * Stephanie Gehrke '''Discussion''' # Merging pull requests:..."

'''Present:'''
* Kevin Hawkins (KH)
* Elli Mylonas (EM)
* Peter Gorman (PG)
* Martin Mueller (MM)

'''Apologies:'''
* Stephanie Gehrke

'''Discussion'''
# Merging pull requests: PG suggests we limit the number of people.
# Minutes from last meeting: EM asks for clarification on SG’s comment on issue 4. (not answered as she was not present.)
# Start looking at tickets, using Ticket Triage wiki page: [[BP_revision_ticket_triage]]
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 Issue 29]: KH has suggested prose, EM added one sentence explaining the circumstances under which you might want to do this. We all agree that he can make this change without further scrutiny by the workgroup.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 Issue 30]: - <milestone/> at <div> boundaries - PG suggests that Paul’s comments are on a different issue: <pb>s deeper inside nested structures. What about multiple blank pages, multiple blank pages in a row? PG points out that these seem to belong to the previous <div>. KH thinks that we need to phrase the following more properly: <pb> and other milestone elements should be nested inside the deepest possible <div>. MM suggests that we make it explicit that this recommendation is based on processing constraints, so if you don’t care about them, then you can ignore it, but that whatever choice is made should be indicated in the <encodingDecl>. KH read existing language (which addresses needs of indexing software) and proposed new language. Workgroup agreed to it. KH will create a new issue and implement if no objections raised. Workgroup agreed that we should have similar language for milestones (what issue 30 was originally about). KH will note in the issue and implement if no objections are raised.
## Paul’s comment about <pb> in footnotes. Discussion so far: we recommend marking <pb> in notes. We could have further discussions and instructions about edge cases - e.g. notes that start on a page different from the attachment page. ''Action on KH to create a new issue for this.''
## MM raised question of encoding the siglum of a note as content of a <ref> element or as an attribute value on a <ptr/> or empty <ref>. TEI Guidelines seem to recommend replacing the siglum with a note and indicating the siglum in an attribute value @anchored or @n. MM will research and write up a summary to share with the WG. The WG may decide to post a query to the list for comment at that point.
# Read and comment on the minutes by 4/6. ''Action on everyone.'' '' EM to post on wiki''

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T13:21:08Z

Elli Mylonas:

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion) Also the Issue Triage Page [[BP_revision_ticket_triage]]
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?]
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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.'' (clarify this sentence?) Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T13:04:27Z

Elli Mylonas:

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?]
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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.'' (clarify this sentence?) Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T04:06:54Z

Elli Mylonas: moved March 7, 2016 to BPTL Workgroup Minutes March 7, 2016: clarity

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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. Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

March 7, 2016

2016-04-04T04:06:54Z

Elli Mylonas: moved March 7, 2016 to BPTL Workgroup Minutes March 7, 2016: clarity

#REDIRECT [[BPTL Workgroup Minutes March 7, 2016]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T03:58:52Z

Elli Mylonas:

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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. Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T03:57:43Z

Elli Mylonas:

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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. Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T03:57:00Z

Elli Mylonas:

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 Issue 4]: Clarify representation of milestones. 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. Is it possible to use <pc> 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. '''TODO:''' MM post query to TEI-L.
# EM to write up minutes, post on wiki.

[[Category:Workgroup to revise the Best Practices for TEI in Libraries]]
[[Category:SIG:Libraries]]

BPTL Workgroup Minutes March 7, 2016

2016-04-04T03:50:35Z

Elli Mylonas: Created page with "'''Present:''' * Kevin Hawkins (KH) * Stefanie Gehrke (SG) * Elli Mylonas (EM) * James Griffin (JG) * Peter Gorman (PG) * Martin Mueller (MM) # KH: Any questions about previous ..."

'''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.
# 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.
# 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]
# Start to work through issues (discussion is summarized in the minutes, but it's best to see the issue itself for full discussion)
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 Issue 19]: The workgroup waits for feedback from Michelle Dalmau [Who contacts her? - or assume she is watching the issue?
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 Issue 20]: Change level 3 display examples to make them simpler and clearer. All agree with Kevin’s suggestions, ''assigned to EM''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 Issue 22]: Text edit. Easy fix, seems like mistake,'' assigned to JG''
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/29 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.
### 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.
### 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.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 Issue 3]: Recommend use of @style instead of @rend . The group approves, ''assigned to PG''.
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 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 <pc> 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.

Workgroup to revise the Best Practices for TEI in Libraries

2016-04-04T03:26:45Z

Elli Mylonas: /* Meeting minutes */

Workgroup to revise the Best Practices for TEI in Libraries

2016-02-05T18:51:49Z

Elli Mylonas: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman ()
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* February 1, 2016

[[Category:SIG:Libraries]]

'''Present:'''
* Kevin Hawkins (KH)
* Stefanie Gehrke (SG)
* Elli Mylonas (EM)
# KH: Discuss meeting procedure. Others agree that it seems reasonable as laid out in wiki by KH.
# Make Google Docs folder and document for minutes, appoint note taker (EM), but all can chip in.
# Look at tickets:
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 Issue 6]: Since we released BPTL, P5 Guidelines have standardized on sourceDesc/@type=”ISBN”. Kevin suggests not specifying if it’s a 10- or 13-digit ISBN; instead, let the user figure it out, either by the length of the string or using check digit as Stuart Yeates suggests in comment.
## SG: We are looking at details but should keep overall structures and relationship of BPTL and P5. Perhaps a wider view might be a better way to guide decisions. KH: Yes, I was wondering about that. We could allow minutiae to raise the larger issues, but perhaps it’s better to start with overall goals.
# KH reviews goals of and structure of BPTL version 3:
## Intended to provide something that serves needs of libraries (sometimes larger scale encoding, often little domain expertise)
## Intended to provide a framework for determining the level of encoding depending on the features of the document to be encoded and the resource constraints (time and money). One workflow BPTL wanted to allow for was to start with a low level encoding and then revisit and upgrade to a higher level of encoding in the future. While we weren’t aware of this happening in practice, we still wanted to allow for it.
## Allows round tripping of header with MARC. Group spent time mapping to MARC, Michael Sperberg-McQueen created a tool to execute it.
### EM: Perhaps we should not only look at MARC but also alternative metadata standards used by libraries (a nod to the future, so it’s clear that we are aware and ready to move in that direction)
#### RDA (replacement for AACR2)
#### BIBFRAME (replacement for MARC)
### KH: Yes, we should prepare for the future, but we also can’t get ahead of our users ''(TODO: add issue on BIBFRAME, assigned to KH)''
## Editing the BPTL document:
### The [http://purl.oclc.org/NET/teiinlibraries BPTL homepage] is a static file. The first link is to a long file (main-driver.html) that is a snapshot generated from the ODD documents. These were created by Syd Bauman. There’s one file for the header specification and one for each level’s “body.” The build process allows you to put these fragments together to create an ODD for the level.
### As “best practices”, the document doesn’t use the term “must” (except in element specifications inherited from P5, which show up at the end of main-driver.html). BPTL indicates what people should do to be conformant, not what they must. However, in the ODDs, all the “should” statements are enforced. This helps users who would like to make sure they are following the recommendations of the BPTL, but for any given encoding project, they could further customize the ODD to enforce only those recommendations they decided to actually follow.
## EM: Is version 3.0 tagged in the GitHub source? KH: No. ''(TODO: add tag to github to indicate v3.0 release, assigned to EM)''
## SG: We should focus on the relationship of the BPTL with TEI Tite and TEI Simple.
### Discussion: Perhaps the BPTL can provide a header to be used with those customizations, both of which lack header elements [CORRECTION: Tite lacks a header, whereas Simple doesn’t constrain the header in any particular way.]. We could add some documentation of how to do this. ''(TODO: create a new issue on this, assigned to KH)''
### Further discussion: Perhaps we should also map differences in body elements. SG: It could be simple list of elements in the BPTL, with three columns for “used as in customization X”, “not used as in customization X”, and “it’s complicated”. You’d put a checkmark in whichever column applies. [SG has started creating a Google spreadsheet with correspondences: [https://docs.google.com/spreadsheets/d/12cj7e88THNna0euRur4HxPgqK92u-0JuwcYwkjBOWTI/edit#gid=0]
## How to proceed? Before each call, we should all review the next couple of tickets in the [[BP_revision_ticket_triage triage document]] and the corresponding sections of the BPTL (comment odd on github / comment on google docs version as well ?) KH: I can include a reminder about this in my reminder emails for each call (which I pledge to send with more notice than this past time!). ''(TODO: create calendar reminders to send these reminders, assigned to KH)''
## Resumed discussion of issue 6:
### KH: Any objection to updating all instances of “isbn-10” and “isbn-13” to “ISBN” (in prose of BPTL, in elementSpecs, and in encoding examples)? None heard.
### KH: I’ll post this as a comment on the issue as in our meeting procedure.
## How to handle these minutes?
### Discussion: Read and comment by end of business on Wednesday. Then EM will post to the wiki. KH: Please also announce on TEILIB-L so that I’m not the only one pushing this group forward. ''(TODO: clean up these minutes, assigned to EM, SG, and KH; TODO: convert to wiki and announce, assigned to EM)''

Workgroup to revise the Best Practices for TEI in Libraries

2016-02-05T18:49:44Z

Elli Mylonas: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman ()
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* February 1, 2016

[[Category:SIG:Libraries]]

'''Present:'''
Kevin Hawkins (KH)
Stefanie Gehrke (SG)
Elli Mylonas (EM)
# KH: Discuss meeting procedure. Others agree that it seems reasonable as laid out in wiki by KH.
# Make Google Docs folder and document for minutes, appoint note taker (EM), but all can chip in.
# Look at tickets:
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 Issue 6]: Since we released BPTL, P5 Guidelines have standardized on sourceDesc/@type=”ISBN”. Kevin suggests not specifying if it’s a 10- or 13-digit ISBN; instead, let the user figure it out, either by the length of the string or using check digit as Stuart Yeates suggests in comment.
## SG: We are looking at details but should keep overall structures and relationship of BPTL and P5. Perhaps a wider view might be a better way to guide decisions. KH: Yes, I was wondering about that. We could allow minutiae to raise the larger issues, but perhaps it’s better to start with overall goals.
# KH reviews goals of and structure of BPTL version 3:
## Intended to provide something that serves needs of libraries (sometimes larger scale encoding, often little domain expertise)
## Intended to provide a framework for determining the level of encoding depending on the features of the document to be encoded and the resource constraints (time and money). One workflow BPTL wanted to allow for was to start with a low level encoding and then revisit and upgrade to a higher level of encoding in the future. While we weren’t aware of this happening in practice, we still wanted to allow for it.
## Allows round tripping of header with MARC. Group spent time mapping to MARC, Michael Sperberg-McQueen created a tool to execute it.
### EM: Perhaps we should not only look at MARC but also alternative metadata standards used by libraries (a nod to the future, so it’s clear that we are aware and ready to move in that direction)
#### RDA (replacement for AACR2)
#### BIBFRAME (replacement for MARC)
### KH: Yes, we should prepare for the future, but we also can’t get ahead of our users ''(TODO: add issue on BIBFRAME, assigned to KH)''
## Editing the BPTL document:
### The [http://purl.oclc.org/NET/teiinlibraries BPTL homepage] is a static file. The first link is to a long file (main-driver.html) that is a snapshot generated from the ODD documents. These were created by Syd Bauman. There’s one file for the header specification and one for each level’s “body.” The build process allows you to put these fragments together to create an ODD for the level.
### As “best practices”, the document doesn’t use the term “must” (except in element specifications inherited from P5, which show up at the end of main-driver.html). BPTL indicates what people should do to be conformant, not what they must. However, in the ODDs, all the “should” statements are enforced. This helps users who would like to make sure they are following the recommendations of the BPTL, but for any given encoding project, they could further customize the ODD to enforce only those recommendations they decided to actually follow.
## EM: Is version 3.0 tagged in the GitHub source? KH: No. ''(TODO: add tag to github to indicate v3.0 release, assigned to EM)''
## SG: We should focus on the relationship of the BPTL with TEI Tite and TEI Simple.
### Discussion: Perhaps the BPTL can provide a header to be used with those customizations, both of which lack header elements [CORRECTION: Tite lacks a header, whereas Simple doesn’t constrain the header in any particular way.]. We could add some documentation of how to do this. ''(TODO: create a new issue on this, assigned to KH)''
### Further discussion: Perhaps we should also map differences in body elements. SG: It could be simple list of elements in the BPTL, with three columns for “used as in customization X”, “not used as in customization X”, and “it’s complicated”. You’d put a checkmark in whichever column applies. [SG has started creating a Google spreadsheet with correspondences: [https://docs.google.com/spreadsheets/d/12cj7e88THNna0euRur4HxPgqK92u-0JuwcYwkjBOWTI/edit#gid=0]
## How to proceed? Before each call, we should all review the next couple of tickets in the [[BP_revision_ticket_triage triage document]] and the corresponding sections of the BPTL (comment odd on github / comment on google docs version as well ?) KH: I can include a reminder about this in my reminder emails for each call (which I pledge to send with more notice than this past time!). ''(TODO: create calendar reminders to send these reminders, assigned to KH)''
## Resumed discussion of issue 6:
### KH: Any objection to updating all instances of “isbn-10” and “isbn-13” to “ISBN” (in prose of BPTL, in elementSpecs, and in encoding examples)? None heard.
### KH: I’ll post this as a comment on the issue as in our meeting procedure.
## How to handle these minutes?
### Discussion: Read and comment by end of business on Wednesday. Then EM will post to the wiki. KH: Please also announce on TEILIB-L so that I’m not the only one pushing this group forward. ''(TODO: clean up these minutes, assigned to EM, SG, and KH; TODO: convert to wiki and announce, assigned to EM)''

Workgroup to revise the Best Practices for TEI in Libraries

2016-02-05T18:48:14Z

Elli Mylonas: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman ()
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* February 1, 2016

[[Category:SIG:Libraries]]

'''Present:'''
Kevin Hawkins (KH)
Stefanie Gehrke (SG)
Elli Mylonas (EM)
# KH: Discuss meeting procedure. Others agree that it seems reasonable as laid out in wiki by KH.
# Make Google Docs folder and document for minutes, appoint note taker (EM), but all can chip in.
# Look at tickets:
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 Issue 6]: Since we released BPTL, P5 Guidelines have standardized on sourceDesc/@type=”ISBN”. Kevin suggests not specifying if it’s a 10- or 13-digit ISBN; instead, let the user figure it out, either by the length of the string or using check digit as Stuart Yeates suggests in comment.
## SG: We are looking at details but should keep overall structures and relationship of BPTL and P5. Perhaps a wider view might be a better way to guide decisions. KH: Yes, I was wondering about that. We could allow minutiae to raise the larger issues, but perhaps it’s better to start with overall goals.
# KH reviews goals of and structure of BPTL version 3:
## Intended to provide something that serves needs of libraries (sometimes larger scale encoding, often little domain expertise)
## Intended to provide a framework for determining the level of encoding depending on the features of the document to be encoded and the resource constraints (time and money). One workflow BPTL wanted to allow for was to start with a low level encoding and then revisit and upgrade to a higher level of encoding in the future. While we weren’t aware of this happening in practice, we still wanted to allow for it.
## Allows round tripping of header with MARC. Group spent time mapping to MARC, Michael Sperberg-McQueen created a tool to execute it.
### EM: Perhaps we should not only look at MARC but also alternative metadata standards used by libraries (a nod to the future, so it’s clear that we are aware and ready to move in that direction)
*##* RDA (replacement for AACR2)
*##* BIBFRAME (replacement for MARC)
### KH: Yes, we should prepare for the future, but we also can’t get ahead of our users ''(TODO: add issue on BIBFRAME, assigned to KH)''
## Editing the BPTL document:
### The [http://purl.oclc.org/NET/teiinlibraries BPTL homepage] is a static file. The first link is to a long file (main-driver.html) that is a snapshot generated from the ODD documents. These were created by Syd Bauman. There’s one file for the header specification and one for each level’s “body.” The build process allows you to put these fragments together to create an ODD for the level.
### As “best practices”, the document doesn’t use the term “must” (except in element specifications inherited from P5, which show up at the end of main-driver.html). BPTL indicates what people should do to be conformant, not what they must. However, in the ODDs, all the “should” statements are enforced. This helps users who would like to make sure they are following the recommendations of the BPTL, but for any given encoding project, they could further customize the ODD to enforce only those recommendations they decided to actually follow.
## EM: Is version 3.0 tagged in the GitHub source? KH: No. ''(TODO: add tag to github to indicate v3.0 release, assigned to EM)''
## SG: We should focus on the relationship of the BPTL with TEI Tite and TEI Simple.
### Discussion: Perhaps the BPTL can provide a header to be used with those customizations, both of which lack header elements [CORRECTION: Tite lacks a header, whereas Simple doesn’t constrain the header in any particular way.]. We could add some documentation of how to do this. ''(TODO: create a new issue on this, assigned to KH)''
### Further discussion: Perhaps we should also map differences in body elements. SG: It could be simple list of elements in the BPTL, with three columns for “used as in customization X”, “not used as in customization X”, and “it’s complicated”. You’d put a checkmark in whichever column applies. [SG has started creating a Google spreadsheet with correspondences: [https://docs.google.com/spreadsheets/d/12cj7e88THNna0euRur4HxPgqK92u-0JuwcYwkjBOWTI/edit#gid=0]
## How to proceed? Before each call, we should all review the next couple of tickets in the [[BP_revision_ticket_triage triage document]] and the corresponding sections of the BPTL (comment odd on github / comment on google docs version as well ?) KH: I can include a reminder about this in my reminder emails for each call (which I pledge to send with more notice than this past time!). ''(TODO: create calendar reminders to send these reminders, assigned to KH)''
## Resumed discussion of issue 6:
### KH: Any objection to updating all instances of “isbn-10” and “isbn-13” to “ISBN” (in prose of BPTL, in elementSpecs, and in encoding examples)? None heard.
### KH: I’ll post this as a comment on the issue as in our meeting procedure.
## How to handle these minutes?
### Discussion: Read and comment by end of business on Wednesday. Then EM will post to the wiki. KH: Please also announce on TEILIB-L so that I’m not the only one pushing this group forward. ''(TODO: clean up these minutes, assigned to EM, SG, and KH; TODO: convert to wiki and announce, assigned to EM)''

Workgroup to revise the Best Practices for TEI in Libraries

2016-02-05T18:47:14Z

Elli Mylonas: /* Meeting minutes */

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman ()
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* February 1, 2016

[[Category:SIG:Libraries]]

'''Present:'''
Kevin Hawkins (KH)
Stefanie Gehrke (SG)
Elli Mylonas (EM)
# KH: Discuss meeting procedure. Others agree that it seems reasonable as laid out in wiki by KH.
# Make Google Docs folder and document for minutes, appoint note taker (EM), but all can chip in.
# Look at tickets:
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 Issue 6]: Since we released BPTL, P5 Guidelines have standardized on sourceDesc/@type=”ISBN”. Kevin suggests not specifying if it’s a 10- or 13-digit ISBN; instead, let the user figure it out, either by the length of the string or using check digit as Stuart Yeates suggests in comment.
## SG: We are looking at details but should keep overall structures and relationship of BPTL and P5. Perhaps a wider view might be a better way to guide decisions. KH: Yes, I was wondering about that. We could allow minutiae to raise the larger issues, but perhaps it’s better to start with overall goals.
# KH reviews goals of and structure of BPTL version 3:
## Intended to provide something that serves needs of libraries (sometimes larger scale encoding, often little domain expertise)
## Intended to provide a framework for determining the level of encoding depending on the features of the document to be encoded and the resource constraints (time and money). One workflow BPTL wanted to allow for was to start with a low level encoding and then revisit and upgrade to a higher level of encoding in the future. While we weren’t aware of this happening in practice, we still wanted to allow for it.
## Allows round tripping of header with MARC. Group spent time mapping to MARC, Michael Sperberg-McQueen created a tool to execute it.
### EM: Perhaps we should not only look at MARC but also alternative metadata standards used by libraries (a nod to the future, so it’s clear that we are aware and ready to move in that direction)
*### RDA (replacement for AACR2)
*### BIBFRAME (replacement for MARC)
### KH: Yes, we should prepare for the future, but we also can’t get ahead of our users ''(TODO: add issue on BIBFRAME, assigned to KH)''
## Editing the BPTL document:
### The [http://purl.oclc.org/NET/teiinlibraries BPTL homepage] is a static file. The first link is to a long file (main-driver.html) that is a snapshot generated from the ODD documents. These were created by Syd Bauman. There’s one file for the header specification and one for each level’s “body.” The build process allows you to put these fragments together to create an ODD for the level.
### As “best practices”, the document doesn’t use the term “must” (except in element specifications inherited from P5, which show up at the end of main-driver.html). BPTL indicates what people should do to be conformant, not what they must. However, in the ODDs, all the “should” statements are enforced. This helps users who would like to make sure they are following the recommendations of the BPTL, but for any given encoding project, they could further customize the ODD to enforce only those recommendations they decided to actually follow.
## EM: Is version 3.0 tagged in the GitHub source? KH: No. ''(TODO: add tag to github to indicate v3.0 release, assigned to EM)''
## SG: We should focus on the relationship of the BPTL with TEI Tite and TEI Simple.
### Discussion: Perhaps the BPTL can provide a header to be used with those customizations, both of which lack header elements [CORRECTION: Tite lacks a header, whereas Simple doesn’t constrain the header in any particular way.]. We could add some documentation of how to do this. ''(TODO: create a new issue on this, assigned to KH)''
### Further discussion: Perhaps we should also map differences in body elements. SG: It could be simple list of elements in the BPTL, with three columns for “used as in customization X”, “not used as in customization X”, and “it’s complicated”. You’d put a checkmark in whichever column applies. [SG has started creating a Google spreadsheet with correspondences: [https://docs.google.com/spreadsheets/d/12cj7e88THNna0euRur4HxPgqK92u-0JuwcYwkjBOWTI/edit#gid=0]
## How to proceed? Before each call, we should all review the next couple of tickets in the [[BP_revision_ticket_triage triage document]] and the corresponding sections of the BPTL (comment odd on github / comment on google docs version as well ?) KH: I can include a reminder about this in my reminder emails for each call (which I pledge to send with more notice than this past time!). ''(TODO: create calendar reminders to send these reminders, assigned to KH)''
## Resumed discussion of issue 6:
### KH: Any objection to updating all instances of “isbn-10” and “isbn-13” to “ISBN” (in prose of BPTL, in elementSpecs, and in encoding examples)? None heard.
### KH: I’ll post this as a comment on the issue as in our meeting procedure.
## How to handle these minutes?
### Discussion: Read and comment by end of business on Wednesday. Then EM will post to the wiki. KH: Please also announce on TEILIB-L so that I’m not the only one pushing this group forward. ''(TODO: clean up these minutes, assigned to EM, SG, and KH; TODO: convert to wiki and announce, assigned to EM)''

Workgroup to revise the Best Practices for TEI in Libraries

2016-02-05T18:45:19Z

Elli Mylonas: added feb 1 minutes

== Background ==

[https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate] in revision of ''[http://purl.oclc.org/NET/teiinlibraries Best Practices for TEI in Libraries]''

== Logistics ==

First Monday of each month

9–10 a.m. Eastern Time in North America (14:00–15:00 UTC in winter in North America, 13:00–14:00 UTC in summer in North America)

If you can't make it, follow along by reviewing minutes (linked below) and/or watching [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues issues on GitHub] and adding comments there.

[https://drive.google.com/open?id=0B13gonNAATNSSmtJMk14VHpzazQ Our Google Drive folder]

== Members ==
* Kevin Hawkins (kevin.s.hawkins@gmail)
* stuart yeates ()
* stefanie gehrke (stefanie.gehrke9@gmail.com)
* Elli Mylonas (elli_mylonas@brown.edu)
* James Griffin (griffinj@lafayette.edu [or jrgriffiniii@gmail.com])
* Lisa McAulay ()
* Martin Mueller (martinmueller@northwestern.edu)
* Michelle Dalmau ()
* Antonio Rojas ()
* Paul Schaffner (pfspfs@gmail.com [or pfs@umich.edu])
* Peter Gorman ()
* Andrew Rouner (andrew.rouner@gmail.com)

== Suggested meeting procedure ==

# Appoint notetaker, creating a new Google Docs file in our Google Drive folder.
# Resume discussions postponed from last meeting.
# Go through issues not yet discussed in order of [[BP revision ticket triage]]. For each issue, someone volunteers to summarize the issue:
## If the issue is straightforward and there's immediate consensus, ask for volunteer to record consensus as a comment on the issue, wait 7 days for objections, and then implement.
## If issue is complicated, ask for volunteer to examine issue more closely after the meeting to propose a solution (either rejecting suggestion or changing prose and/or schema to implement). Volunteer will post proposed solution as comment on the issue at least 7 days before our next meeting and lead discussion at next meeting.
### If there is consensus, volunteer implements after the meeting.
### If there are any adjustments to proposal at that time, volunteer records in a comment on the issue and waits another 7 days for objections before implementing.
# After meeting, those present review the minutes in the next 48 hours. Notetaker then announces minutes on TEILIB-L.

== Meeting minutes ==

* February 1, 2016

[[Category:SIG:Libraries]]

'''Present:'''
Kevin Hawkins (KH)
Stefanie Gehrke (SG)
Elli Mylonas (EM)
# KH: Discuss meeting procedure. Others agree that it seems reasonable as laid out in wiki by KH.
# Make Google Docs folder and document for minutes, appoint note taker (EM), but all can chip in.
# Look at tickets:
## [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 Issue 6]: Since we released BPTL, P5 Guidelines have standardized on sourceDesc/@type=”ISBN”. Kevin suggests not specifying if it’s a 10- or 13-digit ISBN; instead, let the user figure it out, either by the length of the string or using check digit as Stuart Yeates suggests in comment.
## SG: We are looking at details but should keep overall structures and relationship of BPTL and P5. Perhaps a wider view might be a better way to guide decisions. KH: Yes, I was wondering about that. We could allow minutiae to raise the larger issues, but perhaps it’s better to start with overall goals.
# KH reviews goals of and structure of BPTL version 3:
## Intended to provide something that serves needs of libraries (sometimes larger scale encoding, often little domain expertise)
## Intended to provide a framework for determining the level of encoding depending on the features of the document to be encoded and the resource constraints (time and money). One workflow BPTL wanted to allow for was to start with a low level encoding and then revisit and upgrade to a higher level of encoding in the future. While we weren’t aware of this happening in practice, we still wanted to allow for it.
## Allows round tripping of header with MARC. Group spent time mapping to MARC, Michael Sperberg-McQueen created a tool to execute it.
### EM: Perhaps we should not only look at MARC but also alternative metadata standards used by libraries (a nod to the future, so it’s clear that we are aware and ready to move in that direction)
#### RDA (replacement for AACR2)
#### BIBFRAME (replacement for MARC)
### KH: Yes, we should prepare for the future, but we also can’t get ahead of our users ''(TODO: add issue on BIBFRAME, assigned to KH)''
## Editing the BPTL document:
### The [http://purl.oclc.org/NET/teiinlibraries BPTL homepage] is a static file. The first link is to a long file (main-driver.html) that is a snapshot generated from the ODD documents. These were created by Syd Bauman. There’s one file for the header specification and one for each level’s “body.” The build process allows you to put these fragments together to create an ODD for the level.
### As “best practices”, the document doesn’t use the term “must” (except in element specifications inherited from P5, which show up at the end of main-driver.html). BPTL indicates what people should do to be conformant, not what they must. However, in the ODDs, all the “should” statements are enforced. This helps users who would like to make sure they are following the recommendations of the BPTL, but for any given encoding project, they could further customize the ODD to enforce only those recommendations they decided to actually follow.
## EM: Is version 3.0 tagged in the GitHub source? KH: No. ''(TODO: add tag to github to indicate v3.0 release, assigned to EM)''
## SG: We should focus on the relationship of the BPTL with TEI Tite and TEI Simple.
### Discussion: Perhaps the BPTL can provide a header to be used with those customizations, both of which lack header elements [CORRECTION: Tite lacks a header, whereas Simple doesn’t constrain the header in any particular way.]. We could add some documentation of how to do this. ''(TODO: create a new issue on this, assigned to KH)''
### Further discussion: Perhaps we should also map differences in body elements. SG: It could be simple list of elements in the BPTL, with three columns for “used as in customization X”, “not used as in customization X”, and “it’s complicated”. You’d put a checkmark in whichever column applies. [SG has started creating a Google spreadsheet with correspondences: [https://docs.google.com/spreadsheets/d/12cj7e88THNna0euRur4HxPgqK92u-0JuwcYwkjBOWTI/edit#gid=0]
## How to proceed? Before each call, we should all review the next couple of tickets in the [[BP_revision_ticket_triage triage document]] and the corresponding sections of the BPTL (comment odd on github / comment on google docs version as well ?) KH: I can include a reminder about this in my reminder emails for each call (which I pledge to send with more notice than this past time!). ''(TODO: create calendar reminders to send these reminders, assigned to KH)''
## Resumed discussion of issue 6:
### KH: Any objection to updating all instances of “isbn-10” and “isbn-13” to “ISBN” (in prose of BPTL, in elementSpecs, and in encoding examples)? None heard.
### KH: I’ll post this as a comment on the issue as in our meeting procedure.
## How to handle these minutes?
### Discussion: Read and comment by end of business on Wednesday. Then EM will post to the wiki. KH: Please also announce on TEILIB-L so that I’m not the only one pushing this group forward. ''(TODO: clean up these minutes, assigned to EM, SG, and KH; TODO: convert to wiki and announce, assigned to EM)''

Workgroup to revise the Best Practices for TEI in Libraries

2015-12-08T15:18:06Z

Elli Mylonas:

* [https://list.indiana.edu/sympa/arc/teilib-l/2015-11/msg00006.html Invitation to participate]
* Members
** Kevin Hawkins (kevin.s.hawkins)
** stuart yeates ()
** stefanie gehrke ()
** Elli Mylonas (elli_mylonas@brown.edu)
** James Griffin III ()
** Lisa McAulay ()
** Martin Mueller ()
** Michelle Dalmau ()
** Antonio Rojas ()
** Paul Schaffner ()
** Peter Gorman ()

[[SIG:Libraries]]

DH2014Hackathon-Projects

2014-07-04T09:30:02Z

Elli Mylonas: /* Participants */

= DH2014 Hackathon Project Discussion Page =

== Let's Hack ==

A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!

=== ODD visualizer ===

A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

The group should start by discussing what to visualize, perhaps including some TEI users who has experience in customization.

'''Resources:''' About ODD [http://www.tei-c.org/Support/Learn/odds.xml Getting Started with P5 ODDs], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html Guidelines Chapter 23: Using the TEI] and a look at [http://www.tei-c.org/Roma/ Roma], the tool that is currently in use for generating TEI customizations.

=== Basic framework for rendering a document and creating simple visualizations ===

This project could be quite extensive, so the group should begin by selecting components that they can manage.

The proposed outcome is to be able to display (or at least mine) a document for salient features, and to produce output generic enough that it can be passed to either mapping or to other visualization software. Or perhaps to the NY Times Pourover js library. One possible way to to do this is to decide on a json data structure, as that is a popular format for visualization libraries.

--[[User:Frederike Neuber|Frederike Neuber]] 08:08, 3 July 2014 (CEST) Are you referring to a particular visualization software on which it might be useful to take a quick look before the hackathon?

--[[User:Elli Mylonas|Elli Mylonas]] 11:27, 4 July 2014 (CEST) Frederike has a good comment - are there suggestions? Google Maps is one idea. Leaflet, and D3 (more complex) are others. Thoughts?

=== Develop the MS description framework ===

This was one of the proposed projects that got a lot of comments. It could be developed along the lines of the comments, and generalized a bit.

=== Discussing, working out and documenting best practices for an authoring workflow ===

Projects that last for many years, have many people working on them, and comprise large amounts of material need to ensure that work is being done efficiently, produce accurate output, and move files through transformations and validations. Good workflows can be enhanced by both tools and best practices. The outcome of this project could be a document with explanation and examples of authoring/encoding/proofreading/version control workflows with a focus on software tools.

== Participants ==

* [http://mith.umd.edu/people/person/raffaele-viglianti/ Raffaele Viglianti], University of Maryland
* [http://www.patrikgranholm.com Patrik Granholm], Uppsala University Library: [http://www.manuscripta.se Greek Manuscripts in Sweden. A Digitization and Cataloguing Project]
* Frederike Neuber, DiXiT - research fellow on „Digital Palaeography and scholarly editions“ at Graz University - Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* [https://www.uantwerpen.be/en/staff/elli-bleeker/ Elli Bleeker], PhD student in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* [http://steinheim-institut.de/wiki/index.php/Mitarbeiter:Thomas_Kollatz Thomas Kollatz], Steinheim-Institute for German-Jewish History: [http://steinheim-institut.de/cgi-bin/epidat epidat]
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel, Berlin-Brandenburg Academy of Sciences and Humanities
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?
* [[User:Thomas Kollatz|Thomas Kollatz]] 11:57, 1 July 2014 (CEST) https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 error 404 - not found; maybe visualization: text-information encoded in TEI related to city layout ("plat") in SVG ?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''
A simple demo: https://dl.dropboxusercontent.com/u/2443674/ODDViz/index.html --[[User:Raffaele.viglianti|Raffaele.viglianti]] 03:02, 3 July 2014 (CEST)

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with [http://nginx.org nginx], and [http://exist-db.org eXist-db] following the setup guide and scripts provided by [https://github.com/grantmacken/nginx-eXist-ubuntu Grant Macken]. I have already made some preliminary work on an eXist-db web interface and posted the code in our [https://github.com/manuscripta GitHub repository]. This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

* I believe this would be really useful project, especially if we build it not only having this particular purpose of MS descriptions in mind, but something more general, so other users would potentially swap only source files and stylesheets and would have a basic working website. [[User:Magdalena Turska|Magdalena Turska]] 11:00, 23 June 2014 (CEST)
* me too – more general features almost every project will need after swapping source files and stylesheets: navigation to next page/object ; or: navigation to next entry/object in chronological order, full text search everywhere resp in particular div's (type="edition") etc. [[User:Thomas Kollatz|Thomas Kollatz]] 12:09, 1 July 2014 (CEST)
* I am definitely open to creating a more general display framework in eXist. Perhaps we could make use of Joe Wicentowski’s [http://digital.humanities.ox.ac.uk/dhoxss/2011/presentations/Wicentowski-XMLDatabases-materials.zip Punch eXist tutorial] from DHOxSS 2011. [[User:Patrik Granholm|Patrik Granholm]] 11:16, 2 July 2014 (CEST)

=== Medieval Text Edition ===

<strike>
Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.</strike>

'''Comments:'''
Even now my project is not advanced enough to be used for the hackathon. I will join the discussions on the other projects. --[[User:Frederike Neuber|Frederike Neuber]] 22:05, 24 June 2014 (CEST)

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

--[[User:Frederike Neuber|Frederike Neuber]] 23:02, 24 June 2014 (CEST) Who is responsible for this project and can provide further information?
I would be very interested in joining this project even if I can't offer material and even if I do not understand one step: how can you transform an epidoc document into RDF triples? Do you mean you generate RDF from the annotated entities (extracting them?)? And how do you do it, are there tools or software to support it?

[[User:Thomas Kollatz|Thomas Kollatz]] 12:12, 1 July 2014 (CEST) The [http://www.tei-c.org/oxgarage/ oxgarage] magic box contains already a tool converting TEI2RDF, if so – we should try it out and evaluate it if not - let's develop it …

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''
--[[User:Elli Bleeker|Elli Bleeker]] 15:29, 1 July 2014 (CEST) It seems that working with subversion would improve the workflow a lot and at least illiminate the risk of conflicting issues. Of course users should have the right to work in the (seperate) xml file of the bibliographic masterfile and add/change references. Once completed, the xml file can be exported to Zotero. In short, this would mean a reverse of the current workflow.

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

[[User:Elena Spadini|Elena Spadini]] 00:13, 24 June 2014 (CEST) I'm not well-exeperienced with the author mode in oXygen and its customizations, but I would like to explore it working on this project.

=== Visualization of intertextual TEI content ===
[UPDATED on June 24th]

The focus is on the possibilities offered by TEI XML for encoding intertextuality. The case study concerns the personal library of an author and a digital edition of his work. The objective is to encode the material in such a way that the intertextual relations between the literary work and its external sources is visualized.

These -sometimes subtle- intertextual relationships provide insight into the nature of writing, all the more since the genesis of the literary work itself is already encoded in the edition (i.e. adds, dels, etc.). The envisioned result enables a user to study the writing process in detail as well as on a larger scale.

Material:
* detailed XML TEI transcription of the literary work concerned
* high quality digital facsimiles of the author's personal '''extant''' library
* rough transcriptions of the library books (based on OCR)

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.
*
--[[User:Elli Bleeker|Elli Bleeker]] 15:46, 1 July 2014 (CEST) The idea is to log the complete <nowiki>"path"</nowiki> of a citation: from a phrase underlined in a library book to the incorporation of that phrase in the author's work.
Currently, the intertextual references are encoded with [ref] tag in the XML TEI transcription of the literary work. The [ref]s refer to another xml file containing the transcriptions of the personal library. This file consists of [div]s, that contain anything from a complete library book to a small section (paragraph, phrase) from a library book.

The visualization of the intertextual relations comes in a later stage when transforming the documents. I wonder whether it is possible to change or improve this encoding.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

--[[User:Frederike Neuber|Frederike Neuber]] 22:25, 24 June 2014 (CEST)
Would it be a problem to work on different material? @TEI-experts
I would like to visualize the provenance of medieval manuscripts on a map, so even if I do not work with letters, the task is partly the same (extracting date and time from the <teiHeader> and visualizing it on a map). Then our scopes separate: Magdalena wants to reconstruct the journey, I want to visualize the chronology of different mss on one map.

[[User:Thomas Kollatz|Thomas Kollatz]] 15:56, 1 July 2014 (CEST)
I agree with [[User:Frederike Neuber|Frederike Neuber]]: the task is the same in all projects, where a spatio-temporal visualization makes sense: Extract date and time from header - and visualize the chronology of date/time and place on a map and/or timeline
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.
[[User:Thomas Kollatz|Thomas Kollatz]] 15:57, 1 July 2014 (CEST) If Bengali then Hebrew (Arabic … right-to-left), please

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

--[[User:Elli Bleeker|Elli Bleeker]] 16:19, 1 July 2014 (CEST) What is the status of this project? I am also interested in finding ways to visualize relations between texts, perhaps there are similarities?

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
#A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
## between different locations,
## within different periods (based on one or several locations),
## between inscriptions for men and inscriptions for women,
## between hebrew and non-hebrew inscriptions …
#Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''
[[User:Thomas Kollatz|Thomas Kollatz]] 16:05, 1 July 2014 (CEST) The TEI spam filter seems to dislike the person-attribute s_x (middle-letter e) … rather prudish, isn't it

'''Discussion'''

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Frederike Neuber|Frederike Neuber]] 23:21, 24 June 2014 (CEST)
Two (even if very different) projects, "Jewish Sepulchral Headstones DB" and "Rendering complex mark up", are dealing with visualization of spatial and temporal metadata.

Three (again very different) projects, "Visualization of intertextual TEI content", "Semantic Connections for Epigraphic Documents" and "Jewish Sepulchral Headstones DB", are dealing with semantic connection and modelling of content (even if not all of them say it explicitly in the description).

--[[User:Elli Bleeker|Elli Bleeker]] 16:25, 1 July 2014 (CEST)
Add to that the visualization of textual relations in the early Caribbean texts archive.

=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework. --[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)

--[[User:Elli Bleeker|Elli Bleeker]] 16:23, 1 July 2014 (CEST) From the sound of it, I think I would like to work on this project. Some more detail would be great.

Here's a demo of the current version. It's got a few bugs but should show the basic functionality. Pick a couple of sources, then click on any element with xml:id to create a selection. Click add to save it to the "core". https://dl.dropboxusercontent.com/u/2443674/coreBuilder/index.html --[[User:Raffaele.viglianti|Raffaele.viglianti]] 02:31, 3 July 2014 (CEST)

DH2014Hackathon-Projects

2014-07-04T09:27:10Z

Elli Mylonas: /* Basic framework for rendering a document and creating simple visualizations */

= DH2014 Hackathon Project Discussion Page =

== Let's Hack ==

A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!

=== ODD visualizer ===

A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

The group should start by discussing what to visualize, perhaps including some TEI users who has experience in customization.

'''Resources:''' About ODD [http://www.tei-c.org/Support/Learn/odds.xml Getting Started with P5 ODDs], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html Guidelines Chapter 23: Using the TEI] and a look at [http://www.tei-c.org/Roma/ Roma], the tool that is currently in use for generating TEI customizations.

=== Basic framework for rendering a document and creating simple visualizations ===

This project could be quite extensive, so the group should begin by selecting components that they can manage.

The proposed outcome is to be able to display (or at least mine) a document for salient features, and to produce output generic enough that it can be passed to either mapping or to other visualization software. Or perhaps to the NY Times Pourover js library. One possible way to to do this is to decide on a json data structure, as that is a popular format for visualization libraries.

--[[User:Frederike Neuber|Frederike Neuber]] 08:08, 3 July 2014 (CEST) Are you referring to a particular visualization software on which it might be useful to take a quick look before the hackathon?

--[[User:Elli Mylonas|Elli Mylonas]] 11:27, 4 July 2014 (CEST) Frederike has a good comment - are there suggestions? Google Maps is one idea. Leaflet, and D3 (more complex) are others. Thoughts?

=== Develop the MS description framework ===

This was one of the proposed projects that got a lot of comments. It could be developed along the lines of the comments, and generalized a bit.

=== Discussing, working out and documenting best practices for an authoring workflow ===

Projects that last for many years, have many people working on them, and comprise large amounts of material need to ensure that work is being done efficiently, produce accurate output, and move files through transformations and validations. Good workflows can be enhanced by both tools and best practices. The outcome of this project could be a document with explanation and examples of authoring/encoding/proofreading/version control workflows with a focus on software tools.

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* [http://mith.umd.edu/people/person/raffaele-viglianti/ Raffaele Viglianti], University of Maryland
* [http://www.patrikgranholm.com Patrik Granholm], Uppsala University Library: [http://www.manuscripta.se Greek Manuscripts in Sweden. A Digitization and Cataloguing Project]
* Frederike Neuber, DiXiT - research fellow on „Digital Palaeography and scholarly editions“ at Graz University - Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* [https://www.uantwerpen.be/en/staff/elli-bleeker/ Elli Bleeker], PhD student in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* [http://steinheim-institut.de/wiki/index.php/Mitarbeiter:Thomas_Kollatz Thomas Kollatz], Steinheim-Institute for German-Jewish History: [http://steinheim-institut.de/cgi-bin/epidat epidat]
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel, Berlin-Brandenburg Academy of Sciences and Humanities
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?
* [[User:Thomas Kollatz|Thomas Kollatz]] 11:57, 1 July 2014 (CEST) https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 error 404 - not found; maybe visualization: text-information encoded in TEI related to city layout ("plat") in SVG ?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''
A simple demo: https://dl.dropboxusercontent.com/u/2443674/ODDViz/index.html --[[User:Raffaele.viglianti|Raffaele.viglianti]] 03:02, 3 July 2014 (CEST)

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with [http://nginx.org nginx], and [http://exist-db.org eXist-db] following the setup guide and scripts provided by [https://github.com/grantmacken/nginx-eXist-ubuntu Grant Macken]. I have already made some preliminary work on an eXist-db web interface and posted the code in our [https://github.com/manuscripta GitHub repository]. This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

* I believe this would be really useful project, especially if we build it not only having this particular purpose of MS descriptions in mind, but something more general, so other users would potentially swap only source files and stylesheets and would have a basic working website. [[User:Magdalena Turska|Magdalena Turska]] 11:00, 23 June 2014 (CEST)
* me too – more general features almost every project will need after swapping source files and stylesheets: navigation to next page/object ; or: navigation to next entry/object in chronological order, full text search everywhere resp in particular div's (type="edition") etc. [[User:Thomas Kollatz|Thomas Kollatz]] 12:09, 1 July 2014 (CEST)
* I am definitely open to creating a more general display framework in eXist. Perhaps we could make use of Joe Wicentowski’s [http://digital.humanities.ox.ac.uk/dhoxss/2011/presentations/Wicentowski-XMLDatabases-materials.zip Punch eXist tutorial] from DHOxSS 2011. [[User:Patrik Granholm|Patrik Granholm]] 11:16, 2 July 2014 (CEST)

=== Medieval Text Edition ===

<strike>
Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.</strike>

'''Comments:'''
Even now my project is not advanced enough to be used for the hackathon. I will join the discussions on the other projects. --[[User:Frederike Neuber|Frederike Neuber]] 22:05, 24 June 2014 (CEST)

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

--[[User:Frederike Neuber|Frederike Neuber]] 23:02, 24 June 2014 (CEST) Who is responsible for this project and can provide further information?
I would be very interested in joining this project even if I can't offer material and even if I do not understand one step: how can you transform an epidoc document into RDF triples? Do you mean you generate RDF from the annotated entities (extracting them?)? And how do you do it, are there tools or software to support it?

[[User:Thomas Kollatz|Thomas Kollatz]] 12:12, 1 July 2014 (CEST) The [http://www.tei-c.org/oxgarage/ oxgarage] magic box contains already a tool converting TEI2RDF, if so – we should try it out and evaluate it if not - let's develop it …

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''
--[[User:Elli Bleeker|Elli Bleeker]] 15:29, 1 July 2014 (CEST) It seems that working with subversion would improve the workflow a lot and at least illiminate the risk of conflicting issues. Of course users should have the right to work in the (seperate) xml file of the bibliographic masterfile and add/change references. Once completed, the xml file can be exported to Zotero. In short, this would mean a reverse of the current workflow.

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

[[User:Elena Spadini|Elena Spadini]] 00:13, 24 June 2014 (CEST) I'm not well-exeperienced with the author mode in oXygen and its customizations, but I would like to explore it working on this project.

=== Visualization of intertextual TEI content ===
[UPDATED on June 24th]

The focus is on the possibilities offered by TEI XML for encoding intertextuality. The case study concerns the personal library of an author and a digital edition of his work. The objective is to encode the material in such a way that the intertextual relations between the literary work and its external sources is visualized.

These -sometimes subtle- intertextual relationships provide insight into the nature of writing, all the more since the genesis of the literary work itself is already encoded in the edition (i.e. adds, dels, etc.). The envisioned result enables a user to study the writing process in detail as well as on a larger scale.

Material:
* detailed XML TEI transcription of the literary work concerned
* high quality digital facsimiles of the author's personal '''extant''' library
* rough transcriptions of the library books (based on OCR)

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.
*
--[[User:Elli Bleeker|Elli Bleeker]] 15:46, 1 July 2014 (CEST) The idea is to log the complete <nowiki>"path"</nowiki> of a citation: from a phrase underlined in a library book to the incorporation of that phrase in the author's work.
Currently, the intertextual references are encoded with [ref] tag in the XML TEI transcription of the literary work. The [ref]s refer to another xml file containing the transcriptions of the personal library. This file consists of [div]s, that contain anything from a complete library book to a small section (paragraph, phrase) from a library book.

The visualization of the intertextual relations comes in a later stage when transforming the documents. I wonder whether it is possible to change or improve this encoding.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

--[[User:Frederike Neuber|Frederike Neuber]] 22:25, 24 June 2014 (CEST)
Would it be a problem to work on different material? @TEI-experts
I would like to visualize the provenance of medieval manuscripts on a map, so even if I do not work with letters, the task is partly the same (extracting date and time from the <teiHeader> and visualizing it on a map). Then our scopes separate: Magdalena wants to reconstruct the journey, I want to visualize the chronology of different mss on one map.

[[User:Thomas Kollatz|Thomas Kollatz]] 15:56, 1 July 2014 (CEST)
I agree with [[User:Frederike Neuber|Frederike Neuber]]: the task is the same in all projects, where a spatio-temporal visualization makes sense: Extract date and time from header - and visualize the chronology of date/time and place on a map and/or timeline
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.
[[User:Thomas Kollatz|Thomas Kollatz]] 15:57, 1 July 2014 (CEST) If Bengali then Hebrew (Arabic … right-to-left), please

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

--[[User:Elli Bleeker|Elli Bleeker]] 16:19, 1 July 2014 (CEST) What is the status of this project? I am also interested in finding ways to visualize relations between texts, perhaps there are similarities?

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
#A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
## between different locations,
## within different periods (based on one or several locations),
## between inscriptions for men and inscriptions for women,
## between hebrew and non-hebrew inscriptions …
#Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''
[[User:Thomas Kollatz|Thomas Kollatz]] 16:05, 1 July 2014 (CEST) The TEI spam filter seems to dislike the person-attribute s_x (middle-letter e) … rather prudish, isn't it

'''Discussion'''

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Frederike Neuber|Frederike Neuber]] 23:21, 24 June 2014 (CEST)
Two (even if very different) projects, "Jewish Sepulchral Headstones DB" and "Rendering complex mark up", are dealing with visualization of spatial and temporal metadata.

Three (again very different) projects, "Visualization of intertextual TEI content", "Semantic Connections for Epigraphic Documents" and "Jewish Sepulchral Headstones DB", are dealing with semantic connection and modelling of content (even if not all of them say it explicitly in the description).

--[[User:Elli Bleeker|Elli Bleeker]] 16:25, 1 July 2014 (CEST)
Add to that the visualization of textual relations in the early Caribbean texts archive.

=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework. --[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)

--[[User:Elli Bleeker|Elli Bleeker]] 16:23, 1 July 2014 (CEST) From the sound of it, I think I would like to work on this project. Some more detail would be great.

Here's a demo of the current version. It's got a few bugs but should show the basic functionality. Pick a couple of sources, then click on any element with xml:id to create a selection. Click add to save it to the "core". https://dl.dropboxusercontent.com/u/2443674/coreBuilder/index.html --[[User:Raffaele.viglianti|Raffaele.viglianti]] 02:31, 3 July 2014 (CEST)

DH2014Hackathon-Projects

2014-07-02T23:37:00Z

Elli Mylonas: /* Let's Hack */

= DH2014 Hackathon Project Discussion Page =

== Let's Hack ==

A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!

=== ODD visualizer ===

A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

The group should start by discussing what to visualize, perhaps including some TEI users who has experience in customization.

'''Resources:''' About ODD [http://www.tei-c.org/Support/Learn/odds.xml Getting Started with P5 ODDs], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html Guidelines Chapter 23: Using the TEI] and a look at [http://www.tei-c.org/Roma/ Roma], the tool that is currently in use for generating TEI customizations.

=== Basic framework for rendering a document and creating simple visualizations ===

This project could be quite extensive, so the group should begin by selecting components that they can manage.

The proposed outcome is to be able to display (or at least mine) a document for salient features, and to produce output generic enough that it can be passed to either mapping or to other visualization software. Or perhaps to the NY Times Pourover js library. One possible way to to do this is to decide on a json data structure, as that is a popular format for visualization libraries.

=== Develop the MS description framework ===

This was one of the proposed projects that got a lot of comments. It could be developed along the lines of the comments, and generalized a bit.

=== Discussing, working out and documenting best practices for an authoring workflow ===

Projects that last for many years, have many people working on them, and comprise large amounts of material need to ensure that work is being done efficiently, produce accurate output, and move files through transformations and validations. Good workflows can be enhanced by both tools and best practices. The outcome of this project could be a document with explanation and examples of authoring/encoding/proofreading/version control workflows with a focus on software tools.

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* [http://www.patrikgranholm.com Patrik Granholm], Uppsala University Library: [http://www.manuscripta.se Greek Manuscripts in Sweden. A Digitization and Cataloguing Project]
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* [https://www.uantwerpen.be/en/staff/elli-bleeker/ Elli Bleeker], PhD student in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* [http://steinheim-institut.de/wiki/index.php/Mitarbeiter:Thomas_Kollatz Thomas Kollatz], Steinheim-Institute for German-Jewish History: [http://steinheim-institut.de/cgi-bin/epidat epidat]
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel, Berlin-Brandenburg Academy of Sciences and Humanities
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?
* [[User:Thomas Kollatz|Thomas Kollatz]] 11:57, 1 July 2014 (CEST) https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 error 404 - not found; maybe visualization: text-information encoded in TEI related to city layout ("plat") in SVG ?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with [http://nginx.org nginx], and [http://exist-db.org eXist-db] following the setup guide and scripts provided by [https://github.com/grantmacken/nginx-eXist-ubuntu Grant Macken]. I have already made some preliminary work on an eXist-db web interface and posted the code in our [https://github.com/manuscripta GitHub repository]. This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

* I believe this would be really useful project, especially if we build it not only having this particular purpose of MS descriptions in mind, but something more general, so other users would potentially swap only source files and stylesheets and would have a basic working website. [[User:Magdalena Turska|Magdalena Turska]] 11:00, 23 June 2014 (CEST)
* me too – more general features almost every project will need after swapping source files and stylesheets: navigation to next page/object ; or: navigation to next entry/object in chronological order, full text search everywhere resp in particular div's (type="edition") etc. [[User:Thomas Kollatz|Thomas Kollatz]] 12:09, 1 July 2014 (CEST)
* I am definitely open to creating a more general display framework in eXist. Perhaps we could make use of Joe Wicentowski’s [http://digital.humanities.ox.ac.uk/dhoxss/2011/presentations/Wicentowski-XMLDatabases-materials.zip Punch eXist tutorial] from DHOxSS 2011. [[User:Patrik Granholm|Patrik Granholm]] 11:16, 2 July 2014 (CEST)

=== Medieval Text Edition ===

<strike>
Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.</strike>

'''Comments:'''
Even now my project is not advanced enough to be used for the hackathon. I will join the discussions on the other projects. --[[User:Frederike Neuber|Frederike Neuber]] 22:05, 24 June 2014 (CEST)

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

--[[User:Frederike Neuber|Frederike Neuber]] 23:02, 24 June 2014 (CEST) Who is responsible for this project and can provide further information?
I would be very interested in joining this project even if I can't offer material and even if I do not understand one step: how can you transform an epidoc document into RDF triples? Do you mean you generate RDF from the annotated entities (extracting them?)? And how do you do it, are there tools or software to support it?

[[User:Thomas Kollatz|Thomas Kollatz]] 12:12, 1 July 2014 (CEST) The [http://www.tei-c.org/oxgarage/ oxgarage] magic box contains already a tool converting TEI2RDF, if so – we should try it out and evaluate it if not - let's develop it …

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''
--[[User:Elli Bleeker|Elli Bleeker]] 15:29, 1 July 2014 (CEST) It seems that working with subversion would improve the workflow a lot and at least illiminate the risk of conflicting issues. Of course users should have the right to work in the (seperate) xml file of the bibliographic masterfile and add/change references. Once completed, the xml file can be exported to Zotero. In short, this would mean a reverse of the current workflow.

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

[[User:Elena Spadini|Elena Spadini]] 00:13, 24 June 2014 (CEST) I'm not well-exeperienced with the author mode in oXygen and its customizations, but I would like to explore it working on this project.

=== Visualization of intertextual TEI content ===
[UPDATED on June 24th]

The focus is on the possibilities offered by TEI XML for encoding intertextuality. The case study concerns the personal library of an author and a digital edition of his work. The objective is to encode the material in such a way that the intertextual relations between the literary work and its external sources is visualized.

These -sometimes subtle- intertextual relationships provide insight into the nature of writing, all the more since the genesis of the literary work itself is already encoded in the edition (i.e. adds, dels, etc.). The envisioned result enables a user to study the writing process in detail as well as on a larger scale.

Material:
* detailed XML TEI transcription of the literary work concerned
* high quality digital facsimiles of the author's personal '''extant''' library
* rough transcriptions of the library books (based on OCR)

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.
*
--[[User:Elli Bleeker|Elli Bleeker]] 15:46, 1 July 2014 (CEST) The idea is to log the complete <nowiki>"path"</nowiki> of a citation: from a phrase underlined in a library book to the incorporation of that phrase in the author's work.
Currently, the intertextual references are encoded with [ref] tag in the XML TEI transcription of the literary work. The [ref]s refer to another xml file containing the transcriptions of the personal library. This file consists of [div]s, that contain anything from a complete library book to a small section (paragraph, phrase) from a library book.

The visualization of the intertextual relations comes in a later stage when transforming the documents. I wonder whether it is possible to change or improve this encoding.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

--[[User:Frederike Neuber|Frederike Neuber]] 22:25, 24 June 2014 (CEST)
Would it be a problem to work on different material? @TEI-experts
I would like to visualize the provenance of medieval manuscripts on a map, so even if I do not work with letters, the task is partly the same (extracting date and time from the <teiHeader> and visualizing it on a map). Then our scopes separate: Magdalena wants to reconstruct the journey, I want to visualize the chronology of different mss on one map.

[[User:Thomas Kollatz|Thomas Kollatz]] 15:56, 1 July 2014 (CEST)
I agree with [[User:Frederike Neuber|Frederike Neuber]]: the task is the same in all projects, where a spatio-temporal visualization makes sense: Extract date and time from header - and visualize the chronology of date/time and place on a map and/or timeline
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.
[[User:Thomas Kollatz|Thomas Kollatz]] 15:57, 1 July 2014 (CEST) If Bengali then Hebrew (Arabic … right-to-left), please

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

--[[User:Elli Bleeker|Elli Bleeker]] 16:19, 1 July 2014 (CEST) What is the status of this project? I am also interested in finding ways to visualize relations between texts, perhaps there are similarities?

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
#A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
## between different locations,
## within different periods (based on one or several locations),
## between inscriptions for men and inscriptions for women,
## between hebrew and non-hebrew inscriptions …
#Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''
[[User:Thomas Kollatz|Thomas Kollatz]] 16:05, 1 July 2014 (CEST) The TEI spam filter seems to dislike the person-attribute s_x (middle-letter e) … rather prudish, isn't it

'''Discussion'''

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Frederike Neuber|Frederike Neuber]] 23:21, 24 June 2014 (CEST)
Two (even if very different) projects, "Jewish Sepulchral Headstones DB" and "Rendering complex mark up", are dealing with visualization of spatial and temporal metadata.

Three (again very different) projects, "Visualization of intertextual TEI content", "Semantic Connections for Epigraphic Documents" and "Jewish Sepulchral Headstones DB", are dealing with semantic connection and modelling of content (even if not all of them say it explicitly in the description).

--[[User:Elli Bleeker|Elli Bleeker]] 16:25, 1 July 2014 (CEST)
Add to that the visualization of textual relations in the early Caribbean texts archive.

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

--[[User:Elli Bleeker|Elli Bleeker]] 16:23, 1 July 2014 (CEST) From the sound of it, I think I would like to work on this project. Some more detail would be great.

DH2014Hackathon-Projects

2014-07-02T23:20:39Z

Elli Mylonas: /* Discussion */

= DH2014 Hackathon Project Discussion Page =

== Let's Hack ==

A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!

=== ODD visualizer ===

A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

The group should start by discussing what to visualize, perhaps including some TEI users who has experience in customization.

'''Resources:''' About ODD [http://www.tei-c.org/Support/Learn/odds.xml Getting Started with P5 ODDs], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html Guidelines Chapter 23: Using the TEI] and a look at [http://www.tei-c.org/Roma/ Roma], the tool that is currently in use for generating TEI customizations.

=== Basic framework for rendering a document and creating simple visualizations ===

This project could be quite extensive, so the group should begin by selecting components that they can manage.

The proposed outcome is to be able to display (or at least mine) a document for salient features, and to produce output generic enough that it can be passed to either mapping or to other visualization software. Or perhaps to the NY Times Pourover js library. One possible way to to do this is to decide on a json data structure, as that is a popular format for visualization libraries.

=== Discussing, working out and documenting best practices for an authoring workflow ===

Projects that last for many years, have many people working on them, and comprise large amounts of material need to ensure that work is being done efficiently, produce accurate output, and move files through transformations and validations. Good workflows can be enhanced by both tools and best practices. The outcome of this project could be a document with explanation and examples of authoring/encoding/proofreading/version control workflows with a focus on software tools.

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* [http://www.patrikgranholm.com Patrik Granholm], Uppsala University Library: [http://www.manuscripta.se Greek Manuscripts in Sweden. A Digitization and Cataloguing Project]
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* [https://www.uantwerpen.be/en/staff/elli-bleeker/ Elli Bleeker], PhD student in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* [http://steinheim-institut.de/wiki/index.php/Mitarbeiter:Thomas_Kollatz Thomas Kollatz], Steinheim-Institute for German-Jewish History: [http://steinheim-institut.de/cgi-bin/epidat epidat]
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel, Berlin-Brandenburg Academy of Sciences and Humanities
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?
* [[User:Thomas Kollatz|Thomas Kollatz]] 11:57, 1 July 2014 (CEST) https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 error 404 - not found; maybe visualization: text-information encoded in TEI related to city layout ("plat") in SVG ?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with [http://nginx.org nginx], and [http://exist-db.org eXist-db] following the setup guide and scripts provided by [https://github.com/grantmacken/nginx-eXist-ubuntu Grant Macken]. I have already made some preliminary work on an eXist-db web interface and posted the code in our [https://github.com/manuscripta GitHub repository]. This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

* I believe this would be really useful project, especially if we build it not only having this particular purpose of MS descriptions in mind, but something more general, so other users would potentially swap only source files and stylesheets and would have a basic working website. [[User:Magdalena Turska|Magdalena Turska]] 11:00, 23 June 2014 (CEST)
* me too – more general features almost every project will need after swapping source files and stylesheets: navigation to next page/object ; or: navigation to next entry/object in chronological order, full text search everywhere resp in particular div's (type="edition") etc. [[User:Thomas Kollatz|Thomas Kollatz]] 12:09, 1 July 2014 (CEST)
* I am definitely open to creating a more general display framework in eXist. Perhaps we could make use of Joe Wicentowski’s [http://digital.humanities.ox.ac.uk/dhoxss/2011/presentations/Wicentowski-XMLDatabases-materials.zip Punch eXist tutorial] from DHOxSS 2011. [[User:Patrik Granholm|Patrik Granholm]] 11:16, 2 July 2014 (CEST)

=== Medieval Text Edition ===

<strike>
Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.</strike>

'''Comments:'''
Even now my project is not advanced enough to be used for the hackathon. I will join the discussions on the other projects. --[[User:Frederike Neuber|Frederike Neuber]] 22:05, 24 June 2014 (CEST)

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

--[[User:Frederike Neuber|Frederike Neuber]] 23:02, 24 June 2014 (CEST) Who is responsible for this project and can provide further information?
I would be very interested in joining this project even if I can't offer material and even if I do not understand one step: how can you transform an epidoc document into RDF triples? Do you mean you generate RDF from the annotated entities (extracting them?)? And how do you do it, are there tools or software to support it?

[[User:Thomas Kollatz|Thomas Kollatz]] 12:12, 1 July 2014 (CEST) The [http://www.tei-c.org/oxgarage/ oxgarage] magic box contains already a tool converting TEI2RDF, if so – we should try it out and evaluate it if not - let's develop it …

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''
--[[User:Elli Bleeker|Elli Bleeker]] 15:29, 1 July 2014 (CEST) It seems that working with subversion would improve the workflow a lot and at least illiminate the risk of conflicting issues. Of course users should have the right to work in the (seperate) xml file of the bibliographic masterfile and add/change references. Once completed, the xml file can be exported to Zotero. In short, this would mean a reverse of the current workflow.

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

[[User:Elena Spadini|Elena Spadini]] 00:13, 24 June 2014 (CEST) I'm not well-exeperienced with the author mode in oXygen and its customizations, but I would like to explore it working on this project.

=== Visualization of intertextual TEI content ===
[UPDATED on June 24th]

The focus is on the possibilities offered by TEI XML for encoding intertextuality. The case study concerns the personal library of an author and a digital edition of his work. The objective is to encode the material in such a way that the intertextual relations between the literary work and its external sources is visualized.

These -sometimes subtle- intertextual relationships provide insight into the nature of writing, all the more since the genesis of the literary work itself is already encoded in the edition (i.e. adds, dels, etc.). The envisioned result enables a user to study the writing process in detail as well as on a larger scale.

Material:
* detailed XML TEI transcription of the literary work concerned
* high quality digital facsimiles of the author's personal '''extant''' library
* rough transcriptions of the library books (based on OCR)

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.
*
--[[User:Elli Bleeker|Elli Bleeker]] 15:46, 1 July 2014 (CEST) The idea is to log the complete <nowiki>"path"</nowiki> of a citation: from a phrase underlined in a library book to the incorporation of that phrase in the author's work.
Currently, the intertextual references are encoded with [ref] tag in the XML TEI transcription of the literary work. The [ref]s refer to another xml file containing the transcriptions of the personal library. This file consists of [div]s, that contain anything from a complete library book to a small section (paragraph, phrase) from a library book.

The visualization of the intertextual relations comes in a later stage when transforming the documents. I wonder whether it is possible to change or improve this encoding.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

--[[User:Frederike Neuber|Frederike Neuber]] 22:25, 24 June 2014 (CEST)
Would it be a problem to work on different material? @TEI-experts
I would like to visualize the provenance of medieval manuscripts on a map, so even if I do not work with letters, the task is partly the same (extracting date and time from the <teiHeader> and visualizing it on a map). Then our scopes separate: Magdalena wants to reconstruct the journey, I want to visualize the chronology of different mss on one map.

[[User:Thomas Kollatz|Thomas Kollatz]] 15:56, 1 July 2014 (CEST)
I agree with [[User:Frederike Neuber|Frederike Neuber]]: the task is the same in all projects, where a spatio-temporal visualization makes sense: Extract date and time from header - and visualize the chronology of date/time and place on a map and/or timeline
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.
[[User:Thomas Kollatz|Thomas Kollatz]] 15:57, 1 July 2014 (CEST) If Bengali then Hebrew (Arabic … right-to-left), please

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

--[[User:Elli Bleeker|Elli Bleeker]] 16:19, 1 July 2014 (CEST) What is the status of this project? I am also interested in finding ways to visualize relations between texts, perhaps there are similarities?

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
#A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
## between different locations,
## within different periods (based on one or several locations),
## between inscriptions for men and inscriptions for women,
## between hebrew and non-hebrew inscriptions …
#Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''
[[User:Thomas Kollatz|Thomas Kollatz]] 16:05, 1 July 2014 (CEST) The TEI spam filter seems to dislike the person-attribute s_x (middle-letter e) … rather prudish, isn't it

'''Discussion'''

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Frederike Neuber|Frederike Neuber]] 23:21, 24 June 2014 (CEST)
Two (even if very different) projects, "Jewish Sepulchral Headstones DB" and "Rendering complex mark up", are dealing with visualization of spatial and temporal metadata.

Three (again very different) projects, "Visualization of intertextual TEI content", "Semantic Connections for Epigraphic Documents" and "Jewish Sepulchral Headstones DB", are dealing with semantic connection and modelling of content (even if not all of them say it explicitly in the description).

--[[User:Elli Bleeker|Elli Bleeker]] 16:25, 1 July 2014 (CEST)
Add to that the visualization of textual relations in the early Caribbean texts archive.

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

--[[User:Elli Bleeker|Elli Bleeker]] 16:23, 1 July 2014 (CEST) From the sound of it, I think I would like to work on this project. Some more detail would be great.

DH2014Hackathon-Projects

2014-07-02T23:19:53Z

Elli Mylonas: /* Participants */

= DH2014 Hackathon Project Discussion Page =

== Let's Hack ==

A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!

=== ODD visualizer ===

A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

The group should start by discussing what to visualize, perhaps including some TEI users who has experience in customization.

'''Resources:''' About ODD [http://www.tei-c.org/Support/Learn/odds.xml Getting Started with P5 ODDs], [http://www.tei-c.org/release/doc/tei-p5-doc/en/html/USE.html Guidelines Chapter 23: Using the TEI] and a look at [http://www.tei-c.org/Roma/ Roma], the tool that is currently in use for generating TEI customizations.

=== Basic framework for rendering a document and creating simple visualizations ===

This project could be quite extensive, so the group should begin by selecting components that they can manage.

The proposed outcome is to be able to display (or at least mine) a document for salient features, and to produce output generic enough that it can be passed to either mapping or to other visualization software. Or perhaps to the NY Times Pourover js library. One possible way to to do this is to decide on a json data structure, as that is a popular format for visualization libraries.

=== Discussing, working out and documenting best practices for an authoring workflow ===

Projects that last for many years, have many people working on them, and comprise large amounts of material need to ensure that work is being done efficiently, produce accurate output, and move files through transformations and validations. Good workflows can be enhanced by both tools and best practices. The outcome of this project could be a document with explanation and examples of authoring/encoding/proofreading/version control workflows with a focus on software tools.

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* [http://www.patrikgranholm.com Patrik Granholm], Uppsala University Library: [http://www.manuscripta.se Greek Manuscripts in Sweden. A Digitization and Cataloguing Project]
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* [https://www.uantwerpen.be/en/staff/elli-bleeker/ Elli Bleeker], PhD student in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* [http://steinheim-institut.de/wiki/index.php/Mitarbeiter:Thomas_Kollatz Thomas Kollatz], Steinheim-Institute for German-Jewish History: [http://steinheim-institut.de/cgi-bin/epidat epidat]
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel, Berlin-Brandenburg Academy of Sciences and Humanities
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?
* [[User:Thomas Kollatz|Thomas Kollatz]] 11:57, 1 July 2014 (CEST) https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 error 404 - not found; maybe visualization: text-information encoded in TEI related to city layout ("plat") in SVG ?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with [http://nginx.org nginx], and [http://exist-db.org eXist-db] following the setup guide and scripts provided by [https://github.com/grantmacken/nginx-eXist-ubuntu Grant Macken]. I have already made some preliminary work on an eXist-db web interface and posted the code in our [https://github.com/manuscripta GitHub repository]. This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

* I believe this would be really useful project, especially if we build it not only having this particular purpose of MS descriptions in mind, but something more general, so other users would potentially swap only source files and stylesheets and would have a basic working website. [[User:Magdalena Turska|Magdalena Turska]] 11:00, 23 June 2014 (CEST)
* me too – more general features almost every project will need after swapping source files and stylesheets: navigation to next page/object ; or: navigation to next entry/object in chronological order, full text search everywhere resp in particular div's (type="edition") etc. [[User:Thomas Kollatz|Thomas Kollatz]] 12:09, 1 July 2014 (CEST)
* I am definitely open to creating a more general display framework in eXist. Perhaps we could make use of Joe Wicentowski’s [http://digital.humanities.ox.ac.uk/dhoxss/2011/presentations/Wicentowski-XMLDatabases-materials.zip Punch eXist tutorial] from DHOxSS 2011. [[User:Patrik Granholm|Patrik Granholm]] 11:16, 2 July 2014 (CEST)

=== Medieval Text Edition ===

<strike>
Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.</strike>

'''Comments:'''
Even now my project is not advanced enough to be used for the hackathon. I will join the discussions on the other projects. --[[User:Frederike Neuber|Frederike Neuber]] 22:05, 24 June 2014 (CEST)

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

--[[User:Frederike Neuber|Frederike Neuber]] 23:02, 24 June 2014 (CEST) Who is responsible for this project and can provide further information?
I would be very interested in joining this project even if I can't offer material and even if I do not understand one step: how can you transform an epidoc document into RDF triples? Do you mean you generate RDF from the annotated entities (extracting them?)? And how do you do it, are there tools or software to support it?

[[User:Thomas Kollatz|Thomas Kollatz]] 12:12, 1 July 2014 (CEST) The [http://www.tei-c.org/oxgarage/ oxgarage] magic box contains already a tool converting TEI2RDF, if so – we should try it out and evaluate it if not - let's develop it …

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''
--[[User:Elli Bleeker|Elli Bleeker]] 15:29, 1 July 2014 (CEST) It seems that working with subversion would improve the workflow a lot and at least illiminate the risk of conflicting issues. Of course users should have the right to work in the (seperate) xml file of the bibliographic masterfile and add/change references. Once completed, the xml file can be exported to Zotero. In short, this would mean a reverse of the current workflow.

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

[[User:Elena Spadini|Elena Spadini]] 00:13, 24 June 2014 (CEST) I'm not well-exeperienced with the author mode in oXygen and its customizations, but I would like to explore it working on this project.

=== Visualization of intertextual TEI content ===
[UPDATED on June 24th]

The focus is on the possibilities offered by TEI XML for encoding intertextuality. The case study concerns the personal library of an author and a digital edition of his work. The objective is to encode the material in such a way that the intertextual relations between the literary work and its external sources is visualized.

These -sometimes subtle- intertextual relationships provide insight into the nature of writing, all the more since the genesis of the literary work itself is already encoded in the edition (i.e. adds, dels, etc.). The envisioned result enables a user to study the writing process in detail as well as on a larger scale.

Material:
* detailed XML TEI transcription of the literary work concerned
* high quality digital facsimiles of the author's personal '''extant''' library
* rough transcriptions of the library books (based on OCR)

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.
*
--[[User:Elli Bleeker|Elli Bleeker]] 15:46, 1 July 2014 (CEST) The idea is to log the complete <nowiki>"path"</nowiki> of a citation: from a phrase underlined in a library book to the incorporation of that phrase in the author's work.
Currently, the intertextual references are encoded with [ref] tag in the XML TEI transcription of the literary work. The [ref]s refer to another xml file containing the transcriptions of the personal library. This file consists of [div]s, that contain anything from a complete library book to a small section (paragraph, phrase) from a library book.

The visualization of the intertextual relations comes in a later stage when transforming the documents. I wonder whether it is possible to change or improve this encoding.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

--[[User:Frederike Neuber|Frederike Neuber]] 22:25, 24 June 2014 (CEST)
Would it be a problem to work on different material? @TEI-experts
I would like to visualize the provenance of medieval manuscripts on a map, so even if I do not work with letters, the task is partly the same (extracting date and time from the <teiHeader> and visualizing it on a map). Then our scopes separate: Magdalena wants to reconstruct the journey, I want to visualize the chronology of different mss on one map.

[[User:Thomas Kollatz|Thomas Kollatz]] 15:56, 1 July 2014 (CEST)
I agree with [[User:Frederike Neuber|Frederike Neuber]]: the task is the same in all projects, where a spatio-temporal visualization makes sense: Extract date and time from header - and visualize the chronology of date/time and place on a map and/or timeline
/TEI/teiHeader/fileDesc/sourceDesc/msDesc/history/origin

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.
[[User:Thomas Kollatz|Thomas Kollatz]] 15:57, 1 July 2014 (CEST) If Bengali then Hebrew (Arabic … right-to-left), please

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

--[[User:Elli Bleeker|Elli Bleeker]] 16:19, 1 July 2014 (CEST) What is the status of this project? I am also interested in finding ways to visualize relations between texts, perhaps there are similarities?

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
#A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
## between different locations,
## within different periods (based on one or several locations),
## between inscriptions for men and inscriptions for women,
## between hebrew and non-hebrew inscriptions …
#Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''
[[User:Thomas Kollatz|Thomas Kollatz]] 16:05, 1 July 2014 (CEST) The TEI spam filter seems to dislike the person-attribute s_x (middle-letter e) … rather prudish, isn't it

== Discussion ==

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Frederike Neuber|Frederike Neuber]] 23:21, 24 June 2014 (CEST)
Two (even if very different) projects, "Jewish Sepulchral Headstones DB" and "Rendering complex mark up", are dealing with visualization of spatial and temporal metadata.

Three (again very different) projects, "Visualization of intertextual TEI content", "Semantic Connections for Epigraphic Documents" and "Jewish Sepulchral Headstones DB", are dealing with semantic connection and modelling of content (even if not all of them say it explicitly in the description).

--[[User:Elli Bleeker|Elli Bleeker]] 16:25, 1 July 2014 (CEST)
Add to that the visualization of textual relations in the early Caribbean texts archive.

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

--[[User:Elli Bleeker|Elli Bleeker]] 16:23, 1 July 2014 (CEST) From the sound of it, I think I would like to work on this project. Some more detail would be great.

DH2014Hackathon

2014-06-30T10:24:07Z

Elli Mylonas: /* Project Discussion */

==Project Discussion==
See the [[DH2014Hackathon-Projects|List of proposed projects and discussion]]. Comments and suggestions are welcome. You don't have to be a participant.

== Call for Participation ==

We are inviting applications to participate in the TEI Hackathon Workshop that will be held on July 7, 2014, as a pre-conference session at DH2014 (http://dh2014.org/).

Digital humanists, librarians, publishers, and many others use the Text Encoding Initiative (TEI) Guidelines to mark up electronic texts, and over time have created a critical mass of XML — some conforming to known subsets of the TEI Guidelines, some to individual customizations; in some cases intricate and dense, in others lean and expedient; some enriched with extensive external metadata, others with details marked explicitly in the text. The fruits of this labor are most often destined for display online or on paper (!), indexing, and more rarely, visualisation. Techniques of processing this markup beyond display and indexing are less well-understood and not accessible to the broad community of users, however, and programmers sometimes regard TEI XML as over-complex and hard to process.

== What We’ll Do ==

The goal of the hackathon is to make significant progress on a few projects during one day of work (from 9am to roughly 5.30pm).

Possible projects might include but are not limited to:
* applying visualisation to TEI documents or schemas/ODDs (e.g. visualizing the TEI conceptual model)
* mining a large corpus of texts for some data facet and visualising the results
* rendering complex markup in an innovative and playful way
* writing input or output filters for existing bits of software
* extending existing TEI software to take advantage of external resources such as Zotero
* adding a TEI mode to a web editor
* Programming for multilingual resources

All participants will begin discussing the projects that have been proposed before the hackathon, and select a small number to be worked on. More concrete discussion about tools and specs will take place before the date of the hackathon so participants can hit the ground running during the hackathon. On the day of the hackathon, participants will form groups, and work on their projects. Workshop organizers and invited experts will be on hand to consult on TEI details and strategies of dealing with them.

The organisers will provide refreshments during the day, will make sample texts available if needed, and will help with software setup where possible. Participants will need to bring their own laptop computers

== Participants ==

This workshop is intended for reasonably experienced DH practitioners, who may not hitherto have experimented with TEI XML, as well as those who have already been using TEI and developing TEI tools. If you don’t fall into either of these categories, but you have a project that is appropriate for the hackathon, please apply or contact us directly.

== Application process ==

Applicants will email their application with the following information to [mailto:hackathon@tei-c.org hackathon@tei-c.org].
* Name
* Affiliation
* Contact information (email)
* Skills and experience (to help select projects)
* One or two suggested projects. These don’t have to be described in great detail, as they will be discussed and shaped further in June.
Deadline:''' Midnight (EST) April 17''' (applications received after this date will be considered on a rolling basis only if space remains available)
Notification: by April 30

The selection will be carried out by the programme committee based on variety of expertise, interest in challenges with broad application, geographical and gender balance.

== Organizers and Experts ==

Please don’t hesitate to contact the organizers if you have any questions.

===Programme committee:===
; 'Hugh Cayless (hugh.cayless@duke.edu) : TEI Technical Council - Research programmer for the Duke Collaboratory for Classics Computing
; Arianna Ciula (ariananciula@roehampton.ac.uk) : TEI Board of Directors - Research Facilitator (Humanities) at the University of Roehampton
; James Cummings (james.cummings@it.ox.ac.uk) : TEI Technical Council (chair) - Senior Digital Research Specialist in Academic IT at University of Oxford’s IT Services
; Elli Mylonas (elli.mylonas@brown.edu) : TEI Technical Council - Senior Digital Humanities Librarian at Brown University
;'Sebastian Rahtz (sebastian.rahtz@it.ox.ac.uk) : TEI Technical Council - Director of Academic IT at University of Oxford’s IT Services

===Other TEI and DH experts===

; Syd Bauman : Senior XML programmer analyst at Northeastern University Digital Scholarship Group
; Alexander Czmiel : researcher in Digital Humanities at the Berlin-Brandenburg Academy of Sciences and Humanities

== Follow up ==

Participants will have the option of applying for a grant of up to $1000 from the Text Encoding Initiative Consortium to allow them to finish their work and make it available to others. Details for this competition will be provided after the workshop has taken place.

This workshop is being sponsored by the TEI Consortium (http://www.tei-c.org/) which will provide lunch, coffee and snacks.

DH2014Hackathon

2014-06-30T10:20:48Z

Elli Mylonas: /* Call for Participation */

==Project Discussion==
See the [[list of proposed projects and discussion | DH2014Hackathon-Projects]]. Comments and suggestions are welcome. You don't have to be a participant.

== Call for Participation ==

We are inviting applications to participate in the TEI Hackathon Workshop that will be held on July 7, 2014, as a pre-conference session at DH2014 (http://dh2014.org/).

Digital humanists, librarians, publishers, and many others use the Text Encoding Initiative (TEI) Guidelines to mark up electronic texts, and over time have created a critical mass of XML — some conforming to known subsets of the TEI Guidelines, some to individual customizations; in some cases intricate and dense, in others lean and expedient; some enriched with extensive external metadata, others with details marked explicitly in the text. The fruits of this labor are most often destined for display online or on paper (!), indexing, and more rarely, visualisation. Techniques of processing this markup beyond display and indexing are less well-understood and not accessible to the broad community of users, however, and programmers sometimes regard TEI XML as over-complex and hard to process.

== What We’ll Do ==

The goal of the hackathon is to make significant progress on a few projects during one day of work (from 9am to roughly 5.30pm).

Possible projects might include but are not limited to:
* applying visualisation to TEI documents or schemas/ODDs (e.g. visualizing the TEI conceptual model)
* mining a large corpus of texts for some data facet and visualising the results
* rendering complex markup in an innovative and playful way
* writing input or output filters for existing bits of software
* extending existing TEI software to take advantage of external resources such as Zotero
* adding a TEI mode to a web editor
* Programming for multilingual resources

All participants will begin discussing the projects that have been proposed before the hackathon, and select a small number to be worked on. More concrete discussion about tools and specs will take place before the date of the hackathon so participants can hit the ground running during the hackathon. On the day of the hackathon, participants will form groups, and work on their projects. Workshop organizers and invited experts will be on hand to consult on TEI details and strategies of dealing with them.

The organisers will provide refreshments during the day, will make sample texts available if needed, and will help with software setup where possible. Participants will need to bring their own laptop computers

== Participants ==

This workshop is intended for reasonably experienced DH practitioners, who may not hitherto have experimented with TEI XML, as well as those who have already been using TEI and developing TEI tools. If you don’t fall into either of these categories, but you have a project that is appropriate for the hackathon, please apply or contact us directly.

== Application process ==

Applicants will email their application with the following information to [mailto:hackathon@tei-c.org hackathon@tei-c.org].
* Name
* Affiliation
* Contact information (email)
* Skills and experience (to help select projects)
* One or two suggested projects. These don’t have to be described in great detail, as they will be discussed and shaped further in June.
Deadline:''' Midnight (EST) April 17''' (applications received after this date will be considered on a rolling basis only if space remains available)
Notification: by April 30

The selection will be carried out by the programme committee based on variety of expertise, interest in challenges with broad application, geographical and gender balance.

== Organizers and Experts ==

Please don’t hesitate to contact the organizers if you have any questions.

===Programme committee:===
; 'Hugh Cayless (hugh.cayless@duke.edu) : TEI Technical Council - Research programmer for the Duke Collaboratory for Classics Computing
; Arianna Ciula (ariananciula@roehampton.ac.uk) : TEI Board of Directors - Research Facilitator (Humanities) at the University of Roehampton
; James Cummings (james.cummings@it.ox.ac.uk) : TEI Technical Council (chair) - Senior Digital Research Specialist in Academic IT at University of Oxford’s IT Services
; Elli Mylonas (elli.mylonas@brown.edu) : TEI Technical Council - Senior Digital Humanities Librarian at Brown University
;'Sebastian Rahtz (sebastian.rahtz@it.ox.ac.uk) : TEI Technical Council - Director of Academic IT at University of Oxford’s IT Services

===Other TEI and DH experts===

; Syd Bauman : Senior XML programmer analyst at Northeastern University Digital Scholarship Group
; Alexander Czmiel : researcher in Digital Humanities at the Berlin-Brandenburg Academy of Sciences and Humanities

== Follow up ==

Participants will have the option of applying for a grant of up to $1000 from the Text Encoding Initiative Consortium to allow them to finish their work and make it available to others. Details for this competition will be provided after the workshop has taken place.

This workshop is being sponsored by the TEI Consortium (http://www.tei-c.org/) which will provide lunch, coffee and snacks.

DH2014Hackathon-Projects

2014-06-19T02:50:06Z

Elli Mylonas: /* Participants */

= DH2014 Hackathon Project Discussion Page =

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* Patrik Granholm, Uppsala University Library: Greek Manuscripts in Sweden. A Digitization and Cataloguing Project (http://www.manuscripta.se)
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* Elli Bleeker, PhDstudent in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* Thomas Kollatz, Steinheim-Institute for German-Jewish History
* Elena Spadini, Huygens Ing

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel,
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with nginx (http://nginx.org), and eXist-db (http://exist-db.org) following the setup guide and scripts provided by Grant Macken (https://github.com/grantmacken/nginx-eXist-ubuntu). I have already made some preliminary work on an eXist-db web interface and posted the code in our GitHub repository (https://github.com/manuscripta). This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

=== Medieval Text Edition ===

Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.

'''Comments:'''

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

=== Visualization of intertextual TEI content ===

A digital archive containing a variety of material not necessarily limited to text related to a work, and subsequently encoded in such a way that the inter(textual)relations could be visualized.

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
1 A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
– between different locations,
– within different periods (based on one or several locations),
– between inscriptions for men and inscriptions for women.
2 Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''

== Discussion ==

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

DH2014Hackathon-Projects

2014-06-19T02:42:41Z

Elli Mylonas: /* Visualization */

= DH2014 Hackathon Project Discussion Page =

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* Patrik Granholm, Uppsala University Library: Greek Manuscripts in Sweden. A Digitization and Cataloguing Project (http://www.manuscripta.se)
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* Elli Bleeker, PhDstudent in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* Thomas Kollatz, Steinheim-Institute for German-Jewish History

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel,
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with nginx (http://nginx.org), and eXist-db (http://exist-db.org) following the setup guide and scripts provided by Grant Macken (https://github.com/grantmacken/nginx-eXist-ubuntu). I have already made some preliminary work on an eXist-db web interface and posted the code in our GitHub repository (https://github.com/manuscripta). This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

=== Medieval Text Edition ===

Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.

'''Comments:'''

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

=== Visualization of intertextual TEI content ===

A digital archive containing a variety of material not necessarily limited to text related to a work, and subsequently encoded in such a way that the inter(textual)relations could be visualized.

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

=== Jewish Sepulchral Headstones DB ===

Given that all headstones can be clearly located,
and about 20.000 (of total 26.000) inscriptions are dated,
and to a large extend can be distinguished by gender,
and also by language usage (hebrew, german, german in Hebrew letters, …),
they lend themselves to mining the epidat corpus for specific data facets and try to visualize the results "in an innovative and playful way".
1 A challenging research questions could be the search for and visualization of the differences in word usage and specific idiomatic
– between different locations,
– within different periods (based on one or several locations),
– between inscriptions for men and inscriptions for women.
2 Even more challenging is the search for inscriptions with very similar text coverage. These are quite difficult to discover by a simple full text search. The inscriptions are usually rather short, and the filter to develop has to consider the differentiating elements – usually names and dates – in order to determine, whether two text are identical or not.

All necessary information to answer this questions is contained in the metadata <teiHeader> and data <text> of each single record.
example – spatial and temporal metadata (date, country/region code, geo-coordinates, Thesaurus of Getty Names or OSM ID)
<history>
<origin>
<date notBefore='1621-08-17'>1621-08-17</date>
<country type="ISO_3166" key="XA-DE-HH">
Germany
<region>Hamburg</region>
</country>
<settlement type='city' key='tgn:7012310'>
Hamburg-Altona, Königstraße
<geogName>
Jüdischer Friedhof
<geo decls="#WGS">53.549373 9.950545</geo>
</geogName>
</settlement>
</origin>
</history>
example – gender-specific metadata (given according to ISO 5218:2004)
<particDesc>
<listPerson>
<person xml:id="hha-3361-1" s x='1'>
<persName>Schmuel ben Jehuda</persName>
<event when='1621-08-17' type="dateofdeath">
<desc/>
</event>
</person>
</listPerson>
</particDesc>
example – language Usage metadata:
<langUsage>

<language ident='he' usage='100'>Hebrew</language>
</langUsage>

With respect for the TEI Hackathon I have (just) set up a website with very general information how to harvest epidat records:
http://www.steinheim-institut.de/cgi-bin/epidat?info=howtoharvest (to be continued …)
Over and beyond that it would make no great difficulty to provide a zip file with the data available for the workshop.

'''Comments:'''

== Discussion ==

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

DH2014Hackathon-Projects

2014-06-19T02:37:41Z

Elli Mylonas: /* Participants */

= DH2014 Hackathon Project Discussion Page =

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* Patrik Granholm, Uppsala University Library: Greek Manuscripts in Sweden. A Digitization and Cataloguing Project (http://www.manuscripta.se)
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* Elli Bleeker, PhDstudent in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* Thomas Kollatz, Steinheim-Institute for German-Jewish History

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel,
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with nginx (http://nginx.org), and eXist-db (http://exist-db.org) following the setup guide and scripts provided by Grant Macken (https://github.com/grantmacken/nginx-eXist-ubuntu). I have already made some preliminary work on an eXist-db web interface and posted the code in our GitHub repository (https://github.com/manuscripta). This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

=== Medieval Text Edition ===

Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.

'''Comments:'''

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

=== Visualization of intertextual TEI content ===

A digital archive containing a variety of material not necessarily limited to text related to a work, and subsequently encoded in such a way that the inter(textual)relations could be visualized.

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

== Discussion ==

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

DH2014Hackathon-Projects

2014-06-19T02:36:22Z

Elli Mylonas: /* Participants */

= DH2014 Hackathon Project Discussion Page =

== Participants ==

* Robert C Kahlert, Department of Protestant Theology, University of Vienna
* Raffaele Viglianti, University of Maryland
* Patrik Granholm, Uppsala University Library: Greek Manuscripts in Sweden. A Digitization and Cataloguing Project (http://www.manuscripta.se)
* Frederike Neuber,DiXiT - Ph.D. Fellow on „Digital Palaeography and scholarly editions“ at Graz University / Austrian Centre for Digital Humanities
* Felix Lange, Academy of Sciences and Literatur | Mainz, Project IBR (http://www.spatialhumanities.de)
* Emmanuelle Morlock, CNRS, HISoMA Laboratory (Histoire et Sources des mondes antiques / History and Origins of the Antique World)
* Elli Bleeker, PhDstudent in Digital Humanities at Antwerp University; research fellow at DiXiT
* Magdalena Turska, University of Oxford
* Nick Laiacona, Performant Software Solutions LLC www.performantsoftware.com
* Elizabeth Maddock Dillon, Professor of English and CoDirector of NULab for Texts, Maps, and Networks, Northeastern University, Boston, MA USA
* Thomas Kollatz,

* Sebastian Rahtz, University of Oxford
* James Cummings, University of Oxford
* Alex Czmiel,
* Hugh Cayless, Duke University
* Elli Mylonas, Brown University

== Procedure ==

We will be using the wiki as a place for comments and discussion. The projects each participant proposed are all listed below. Ideally, the hackathon will be focussed around one or two projects that are useful to everyone. The participants are all experienced with TEI in various capacities, but they are not all skilled programmers. The hackathon would be a success if the outcome of the one day event was e a good start on one or two useful pieces of TEI related software. In order to achieve this, we should collectively decide on projects that are interesting, useful, generalizable, and do-able! We should also try to capitalize on everyone's skill set, and try to plan the event in such a way that we can all contribute to something.

You are all welcome to introduce yourselves, by adding a description of a few sentences to the list of participants above. And please, edit, correct and comment on the projects. We are also inviting the TEI Council and Board and other interested parties to look in on the discussions.

== Proposed Projects ==

=== Mormon City Planning: ===
when early Mormonism ventured from Kirtland, Ohio, into Missouri, their prophet Joseph Smith Jr provided a revelation for the plat (city layout) of the new Zion (http://urbanplanning.library.cornell.edu/DOCS/smith.htm; http://zomarah.files.wordpress.com/2010/10/firstplatofzion.png), which was subsequently applied in the settlement of Far West, Missouri, for which two plats exist, one on sheepskin (https://www.lds.org/bc/content/shared/content/images/gospel-library/manual/32502/15-02 b.gif) in private possession and one on paper at BYU University (there is no online copy of this, but I have obtained a digital copy from BYU with their permission); however these plats were not only used to sketch out the city, but also to assign lots to settlers, and thus show secondary markup in pencil to allocate houses, redraw lot boundaries, etc; (http://zomarah.files.wordpress.com/2010/10/platoffarwestbig.png)

'''Comments:'''
* A clarification: What would the project strive to accomplish? Is this a visualization? georeferencing based on markup?

=== ODD Customization visualizer ===
A web-based tool to visualize any ODD customization against TEI-all. This could be useful when working on a customization (with Roma, or manually) to quickly and visually check that the ODD is still TEI-conformant and see how it diverges from the standard.
I started working on a basic D3 visualization a couple of years ago, but haven't really touched the code since:https://github.com/raffazizzi/ODDViz I only restructured the repository a bit before sending this proposal.

'''Comments'''

=== ACE-based Web editor ===

MITH, at the University of Maryland has been working on an ACE-based web editor able to validate tei-all files in the browser and provide ODD-based contextual help (e.g. suggesting valid options when entering a new element).
The grant that funded this work is now over, but there's plenty more to do. This is the GitHub repository: https://github.com/umd-mith/angles

'''Comments:'''

=== MS Description Display Framework ===
To create a simple web interface which would provide basic functionalities like browsing, searching and displaying TEI-files containing manuscript descriptions. The interface could be built using a Ubuntu server with nginx (http://nginx.org), and eXist-db (http://exist-db.org) following the setup guide and scripts provided by Grant Macken (https://github.com/grantmacken/nginx-eXist-ubuntu). I have already made some preliminary work on an eXist-db web interface and posted the code in our GitHub repository (https://github.com/manuscripta). This could be used as a starting point for further development. A possible goal for the hackathon could be to create an advanced search form in XQuery which would display snippets of the descriptions in the search results using the transform function with our XSL stylesheet, with links to the full description. All of the code, with detailed documentation, would be made public on GitHub for others to reuse and modify for their own projects. I think this would be beneficial to the TEI community at large, and especially to other cataloguing projects.

'''Comments:'''

=== Medieval Text Edition ===

Project isn't advanced enough to suggest concrete task, but the topic of interest is focussed around a digital scholarly edition of a medieval text (with corresponding images) encoded in XML/TEI. The edition will be enriched with palaeographical and codicological information (in both <text> and <teiHeader>) and the results can be visualized in a way which hopefully goes beyond the sometimes not very enlightening listing of data.

'''Comments:'''

=== Semantic Connections for Epigraphic Documents ===
I am currently working with epidoc documents in the context of the Project IBR. These documents, epigraphical editions from the catalogue "German Inscriptions Online" (inschriften.net), are (1) to be transformed into RDFtriples for semantic connection and for a finegrained quantificational analysis in a Triple Store, (2) XSLT transformed into HTMLDocuments for further annotation in the semantic annotator "Pundit"(thepund.it). I could surely contribute a programming task based on this points, but would also be happy to participate in another task, preferably based on "adding a TEI mode to a web editor".

'''Comments:'''

=== Zotero ===
Some TEI encoding project may need to use a "master bibliography" to group together all the bibliographic references that are used in a given text or collection of texts. Using the "masterfile" option in Oxygen give the user a convenient way of pointing to a reference without having to encode a ref each time it is used in a text or in a specific bibliographic section.
<pre>
<bibl type="fromStone">
<ptr target="#Breal1878"/>
<citedRange>15</citedRange>
</bibl>
</pre>

The bibliography can be inserted in a <back/> element with xinclude. But the question is how to use Zotero to create this file, update it and synchonize it with the biblographic masterfile.
Though incomplete, the workflow I use works like that :
* the entering of the bibliographic entries is done with zotero, in a group library
* the zotero database is then exported in xml using the "bibliontology_rdf" format (the TEI export format being to restrictive in its formatting choices : e.g. does'nt include "short titles" which are a requisite in epigraphy
* the bibliontology rdf is converted in TEI through XSLT in Oxygen (modifying existing xslt :https://github.com/paregorios/Zotero-RDF-to-TEI-XML)
* If the user wants to add a new reference in the masterbibliography or correct an entry, he or she has to do go to zotero and follow the whole workflow of export - tranform process. But the user might not have the user right to do so. And of course, there are some potential conflicting issues.

How to improve that workflow ? use a version control system like git or subversion ? or adding/modifying an entry in xml / tei and then updating the zotero group library via api ?

'''Comments:'''

=== Migrating value lists form CSS frameworks to ODD ===

The author mode of the Oxygen editor can be customized with custom css functions. A part from the function providing a more user-friendly and tag free visualization of the tei content, one of the fuction allow the user to edit attributes or simple elements values using combo boxes or check boxes. The "form controls" can display values collected from an xml schema. But these values can also be just in the oxygen css. This may be used in a workflow to test some choices before integrating them in a more consistent and persistant way in the ODD (then exported in the schema).

This could be useful in case you have user that may be ok to change the values in the css code but would be relunctant to get involved with the ODD editing / schema generation process.
cf. http://www.oxygenxml.com/doc/ug-editor/concepts/combo-box-editor.html#combo-box-editor

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) This is interesting, would like to work on it. I would suggest to make it less tied to Oxygen and think in terms of CSS to ODD, for example to limit attribute values (e.g. hi[rend=italic])

=== Visualization of intertextual TEI content ===

A digital archive containing a variety of material not necessarily limited to text related to a work, and subsequently encoded in such a way that the inter(textual)relations could be visualized.

'''Comments:'''

* Clarification: is the project about the visualization? the relationships? More detail would be great.

=== Rendering Complex Markup ===
Rendering complex markup in an innovative and playful way: reconstructing & visualizing author’s
geographical position by the dates of sending of his letters (taking uncertainty into account)

'''Comments:'''

[[User:Magdalena Turska|Magdalena Turska]] 12:36, 12 June 2014 (CEST)

Starting with a list of letters that have a place and date of sending the idea would be to present map overview of the author's journeys.
See the simple Google Map at https://mapsengine.google.com/map/edit?mid=z3q4AefiR7Us.kf1fVBHlu8qE

Fist ideas re visualisation:
* places color-coded with color getting darker to represent 'later' places
* similarly shaded lines along the routes between places
* animation with slider to show circle moving along the routes, size of the circle getting bigger with the uncertainty

Input data:
each letter has assigned place name and 1+ time intervals (notBefore to not After)

=== Adding a TEI mode to a web editor ===
Title says it all!

'''Comments:'''

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:20, 16 June 2014 (CEST) How does the [http://wiki.tei-c.org/index.php/DH2014Hackathon-Projects#ACE-based_Web_editor Angles] proposal above sound?

=== Juxta Script support ===
Adding support for Bengali text to Juxta Commons

'''Comments:'''
* This is fairly narrow.

=== Visualization ===
The archive of early Caribbean texts and images is a fairly large project which will be heavily encoded (and a portion of texts will be encoded by July). I'd like to explore ways of using the TEI to visualize relations between and among texts and elements of texts.

'''Comments:'''

== Discussion ==

What commonalities to you see? What seems interesting? Anything to add?

--[[User:Raffaele.viglianti|Raffaele.viglianti]] 19:07, 16 June 2014 (CEST)
=== Core Builder ===
Another possible tool to work on: https://github.com/raffazizzi/coreBuilder
It provides a simple web interface to create stand-off markup. TEI files can be open into multiple ACE editors and the user can click on elements with xml:ids to create references.
The current version creates <app> elements containing <rdg>s with pointers to the selected elements. It should be easy enough to make the elements user configurable so that the Core Builder can be used to put together <linkGrp>s or <timeline>s.
The tool is written in CoffeScript with a [http://backbonejs.org/ Backbone] framework.

DH2014Hackathon-Projects

2014-06-11T03:29:48Z

Elli Mylonas: /* Zotero */

DH2014Hackathon-Projects

2014-06-11T03:11:53Z

Elli Mylonas: Created page with "= DH2014 Hackathon Project Discussion Page = == Participants == * Robert C Kahlert, Department of Protestant Theology, University of Vienna * Raffaele Viglianti, University of ..."

Current events

2014-06-11T01:09:01Z

Elli Mylonas: /* DH2014 TEI Hackathon Workshop July 7 2014) */

(In chronological order, nearest events first.)


== DH2014 TEI Hackathon Workshop July 7 2014) ==
The TEI is hosting a one day workshop at [http://dh2014.org/ DH2014] -- [[DH2014Hackathon|Call for participation]] -- [[DH2014Hackathon-Projects|Projects Discussion]]

== Digital.Humanities @ Oxford Summer School 2013 (8-12 July 2013) ==
Annual DH Summer School in Oxford. Has a five day workshop as a general introduction to TEI, and a one-day course on TEI on another workshop (How to do DH). http://digital.humanities.ox.ac.uk/dhoxss/2013/

==EpiDoc Summer School, Sofia, Sept 2013==

Training in the use of EpiDoc (TEI for ancient documents) will be offered in Sofia, Bulgaria, September 3-6, 2013. Details, including programme, will be added to [http://wiki.digitalclassicist.org/EpiDoc_Summer_School EpiDoc Summer School] wiki.

== Edirom-Summer-School 2013, Sept. 23–27 ==

Annual DH Summer School in Paderborn, Germany. Has an ''Introduction to TEI'' as well as an ''Introduction to ODD''. Workshops are in German.
http://ess.uni-paderborn.de

==TEI Conference and Members' Meeting 2013==

2013 Annual Conference and Members’ Meeting of the TEI Consortium

[http://digilab2.let.uniroma1.it/teiconf2013/ The Linked TEI: Text Encoding in the Web]

2-5 October 2013
Università La Sapienza, Rome, Italy

'''See also:'''
* http://members.tei-c.org/Events
* [[Conferences]]
* [[Past events]]

[[Category:Community]]

Current events

2014-06-11T01:08:10Z

Elli Mylonas: /* DH2014 TEI Hackathon Workshop July 7 2014) */

(In chronological order, nearest events first.)


== DH2014 TEI Hackathon Workshop July 7 2014) ==
The TEI is hosting a one day workshop at [http://dh2014.org/ DH2014] . [[DH2014Hackathon|Call for participation]] [[DH2014Hackathon-Projects|Projects Discussion]]

== Digital.Humanities @ Oxford Summer School 2013 (8-12 July 2013) ==
Annual DH Summer School in Oxford. Has a five day workshop as a general introduction to TEI, and a one-day course on TEI on another workshop (How to do DH). http://digital.humanities.ox.ac.uk/dhoxss/2013/

==EpiDoc Summer School, Sofia, Sept 2013==

Training in the use of EpiDoc (TEI for ancient documents) will be offered in Sofia, Bulgaria, September 3-6, 2013. Details, including programme, will be added to [http://wiki.digitalclassicist.org/EpiDoc_Summer_School EpiDoc Summer School] wiki.

== Edirom-Summer-School 2013, Sept. 23–27 ==

Annual DH Summer School in Paderborn, Germany. Has an ''Introduction to TEI'' as well as an ''Introduction to ODD''. Workshops are in German.
http://ess.uni-paderborn.de

==TEI Conference and Members' Meeting 2013==

2013 Annual Conference and Members’ Meeting of the TEI Consortium

[http://digilab2.let.uniroma1.it/teiconf2013/ The Linked TEI: Text Encoding in the Web]

2-5 October 2013
Università La Sapienza, Rome, Italy

'''See also:'''
* http://members.tei-c.org/Events
* [[Conferences]]
* [[Past events]]

[[Category:Community]]

Current events

2014-03-25T21:48:53Z

Elli Mylonas:

(In chronological order, nearest events first.)


== DH2014 TEI Hackathon Workshop July 7 2014) ==
The TEI is hosting a one day workshop at [http://dh2014.org/ DH2014] . [[DH2014Hackathon|Call for participation]].

== Digital.Humanities @ Oxford Summer School 2013 (8-12 July 2013) ==
Annual DH Summer School in Oxford. Has a five day workshop as a general introduction to TEI, and a one-day course on TEI on another workshop (How to do DH). http://digital.humanities.ox.ac.uk/dhoxss/2013/

==EpiDoc Summer School, Sofia, Sept 2013==

Training in the use of EpiDoc (TEI for ancient documents) will be offered in Sofia, Bulgaria, September 3-6, 2013. Details, including programme, will be added to [http://wiki.digitalclassicist.org/EpiDoc_Summer_School EpiDoc Summer School] wiki.

== Edirom-Summer-School 2013, Sept. 23–27 ==

Annual DH Summer School in Paderborn, Germany. Has an ''Introduction to TEI'' as well as an ''Introduction to ODD''. Workshops are in German.
http://ess.uni-paderborn.de

==TEI Conference and Members' Meeting 2013==

2013 Annual Conference and Members’ Meeting of the TEI Consortium

[http://digilab2.let.uniroma1.it/teiconf2013/ The Linked TEI: Text Encoding in the Web]

2-5 October 2013
Università La Sapienza, Rome, Italy

'''See also:'''
* http://members.tei-c.org/Events
* [[Conferences]]
* [[Past events]]

[[Category:Community]]

DH2014Hackathon

2014-03-25T21:47:47Z

Elli Mylonas:

== Call for Participation ==

We are inviting applications to participate in the TEI Hackathon Workshop that will be held on July 7, 2014, as a pre-conference session at DH2014 (http://dh2014.org/).

Digital humanists, librarians, publishers, and many others use the Text Encoding Initiative (TEI) Guidelines to mark up electronic texts, and over time have created a critical mass of XML — some conforming to known subsets of the TEI Guidelines, some to individual customizations; in some cases intricate and dense, in others lean and expedient; some enriched with extensive external metadata, others with details marked explicitly in the text. The fruits of this labor are most often destined for display online or on paper (!), indexing, and more rarely, visualisation. Techniques of processing this markup beyond display and indexing are less well-understood and not accessible to the broad community of users, however, and programmers sometimes regard TEI XML as over-complex and hard to process.

== What We’ll Do ==

The goal of the hackathon is to make significant progress on a few projects during one day of work (from 9am to roughly 5.30pm).

Possible projects might include but are not limited to:
* applying visualisation to TEI documents or schemas/ODDs (e.g. visualizing the TEI conceptual model)
* mining a large corpus of texts for some data facet and visualising the results
* rendering complex markup in an innovative and playful way
* writing input or output filters for existing bits of software
* extending existing TEI software to take advantage of external resources such as Zotero
* adding a TEI mode to a web editor
* Programming for multilingual resources

All participants will begin discussing the projects that have been proposed before the hackathon, and select a small number to be worked on. More concrete discussion about tools and specs will take place before the date of the hackathon so participants can hit the ground running during the hackathon. On the day of the hackathon, participants will form groups, and work on their projects. Workshop organizers and invited experts will be on hand to consult on TEI details and strategies of dealing with them.

The organisers will provide refreshments during the day, will make sample texts available if needed, and will help with software setup where possible. Participants will need to bring their own laptop computers

== Participants ==

This workshop is intended for reasonably experienced DH practitioners, who may not hitherto have experimented with TEI XML, as well as those who have already been using TEI and developing TEI tools. If you don’t fall into either of these categories, but you have a project that is appropriate for the hackathon, please apply or contact us directly.

== Application process ==

Applicants will email their application with the following information to [mailto:hackathon@tei-c.org hackathon@tei-c.org].
* Name
* Affiliation
* Contact information (email)
* Skills and experience (to help select projects)
* One or two suggested projects. These don’t have to be described in great detail, as they will be discussed and shaped further in June.
Deadline:''' Midnight (EST) April 17''' (applications received after this date will be considered on a rolling basis only if space remains available)
Notification: by April 30

The selection will be carried out by the programme committee based on variety of expertise, interest in challenges with broad application, geographical and gender balance.

== Organizers and Experts ==

Please don’t hesitate to contact the organizers if you have any questions.

===Programme committee:===
; 'Hugh Cayless (hugh.cayless@duke.edu) : TEI Technical Council - Research programmer for the Duke Collaboratory for Classics Computing
; Arianna Ciula (ariananciula@roehampton.ac.uk) : TEI Board of Directors - Research Facilitator (Humanities) at the University of Roehampton
; James Cummings (james.cummings@it.ox.ac.uk) : TEI Technical Council (chair) - Senior Digital Research Specialist in Academic IT at University of Oxford’s IT Services
; Elli Mylonas (elli.mylonas@brown.edu) : TEI Technical Council - Senior Digital Humanities Librarian at Brown University
;'Sebastian Rahtz (sebastian.rahtz@it.ox.ac.uk) : TEI Technical Council - Director of Academic IT at University of Oxford’s IT Services

===Other TEI and DH experts===

; Syd Bauman : Senior XML programmer analyst at Northeastern University Digital Scholarship Group
; Alexander Czmiel : researcher in Digital Humanities at the Berlin-Brandenburg Academy of Sciences and Humanities

== Follow up ==

Participants will have the option of applying for a grant of up to $1000 from the Text Encoding Initiative Consortium to allow them to finish their work and make it available to others. Details for this competition will be provided after the workshop has taken place.

This workshop is being sponsored by the TEI Consortium (http://www.tei-c.org/) which will provide lunch, coffee and snacks.

DH2014Hackathon

2014-03-25T21:44:07Z

Elli Mylonas: Created page with "== Call for Participation == We are inviting applications to participate in the TEI Hackathon Workshop that will be held on July 7, 2014, as a pre-conference session at DH2014 ..."

== Call for Participation ==

We are inviting applications to participate in the TEI Hackathon Workshop that will be held on July 7, 2014, as a pre-conference session at DH2014 (http://dh2014.org/).

Digital humanists, librarians, publishers, and many others use the Text Encoding Initiative (TEI) Guidelines to mark up electronic texts, and over time have created a critical mass of XML — some conforming to known subsets of the TEI Guidelines, some to individual customizations; in some cases intricate and dense, in others lean and expedient; some enriched with extensive external metadata, others with details marked explicitly in the text. The fruits of this labor are most often destined for display online or on paper (!), indexing, and more rarely, visualisation. Techniques of processing this markup beyond display and indexing are less well-understood and not accessible to the broad community of users, however, and programmers sometimes regard TEI XML as over-complex and hard to process.

== What We’ll Do ==

The goal of the hackathon is to make significant progress on a few projects during one day of work (from 9am to roughly 5.30pm).

Possible projects might include but are not limited to:
* applying visualisation to TEI documents or schemas/ODDs (e.g. visualizing the TEI conceptual model)
* mining a large corpus of texts for some data facet and visualising the results
* rendering complex markup in an innovative and playful way
* writing input or output filters for existing bits of software
* extending existing TEI software to take advantage of external resources such as Zotero
* adding a TEI mode to a web editor
* Programming for multilingual resources

All participants will begin discussing the projects that have been proposed before the hackathon, and select a small number to be worked on. More concrete discussion about tools and specs will take place before the date of the hackathon so participants can hit the ground running during the hackathon. On the day of the hackathon, participants will form groups, and work on their projects. Workshop organizers and invited experts will be on hand to consult on TEI details and strategies of dealing with them.

The organisers will provide refreshments during the day, will make sample texts available if needed, and will help with software setup where possible. Participants will need to bring their own laptop computers

== Participants ==

This workshop is intended for reasonably experienced DH practitioners, who may not hitherto have experimented with TEI XML, as well as those who have already been using TEI and developing TEI tools. If you don’t fall into either of these categories, but you have a project that is appropriate for the hackathon, please apply or contact us directly.

== Application process ==

Applicants will email their application with the following information to hackathon@tei-c.org.
* Name
* Affiliation
* Contact information (email)
* Skills and experience (to help select projects)
* One or two suggested projects. These don’t have to be described in great detail, as they will be discussed and shaped further in June.
Deadline:''' Midnight (EST) April 17''' (applications received after this date will be considered on a rolling basis only if space remains available)
Notification: by April 30

The selection will be carried out by the programme committee based on variety of expertise, interest in challenges with broad application, geographical and gender balance.

== Organizers and Experts ==

Please don’t hesitate to contact the organizers if you have any questions.

===Programme committee:===
; 'Hugh Cayless (hugh.cayless@duke.edu) : TEI Technical Council - Research programmer for the Duke Collaboratory for Classics Computing
; Arianna Ciula (ariananciula@roehampton.ac.uk) : TEI Board of Directors - Research Facilitator (Humanities) at the University of Roehampton
; James Cummings (james.cummings@it.ox.ac.uk) : TEI Technical Council (chair) - Senior Digital Research Specialist in Academic IT at University of Oxford’s IT Services
; Elli Mylonas (elli.mylonas@brown.edu) : TEI Technical Council - Senior Digital Humanities Librarian at Brown University
;'Sebastian Rahtz (sebastian.rahtz@it.ox.ac.uk) : TEI Technical Council - Director of Academic IT at University of Oxford’s IT Services

===Other TEI and DH experts===

; Syd Bauman : Senior XML programmer analyst at Northeastern University Digital Scholarship Group
; Alexander Czmiel : researcher in Digital Humanities at the Berlin-Brandenburg Academy of Sciences and Humanities

== Follow up ==

Participants will have the option of applying for a grant of up to $1000 from the Text Encoding Initiative Consortium to allow them to finish their work and make it available to others. Details for this competition will be provided after the workshop has taken place.

This workshop is being sponsored by the TEI Consortium (http://www.tei-c.org/) which will provide lunch, coffee and snacks.

Oxford2013-Actions2

2014-02-25T19:35:40Z

Elli Mylonas: /* Actions for Elli Mylonas */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|has now been implemented (twice, sort of); ticket closed
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|DONE. Tried both with Options > Preferences > XML > XML Parser > RELAX NG > Check ID/IDREF checked and unchecked against tei_allPlus.rng 2.5.0, and did not reproduce error.
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|JC did, hand off to EM Jan 9 '14 DONE
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|Jan 28 '14 Discussions begun, proposal draft begun. Feb 21 proposal submitted to DH2014 DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|Dec 10, 2013 done
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|Dec 10, 2013 Done
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-02-25T19:35:18Z

Elli Mylonas: /* Actions for Elli Mylonas */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|has now been implemented (twice, sort of); ticket closed
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|DONE. Tried both with Options > Preferences > XML > XML Parser > RELAX NG > Check ID/IDREF checked and unchecked against tei_allPlus.rng 2.5.0, and did not reproduce error.
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|JC did, hand off to EM Jan 9 '14
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|Jan 28 '14 Discussions begun, proposal draft begun. Feb 21 proposal submitted to DH2014
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|Dec 10, 2013 done
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|Dec 10, 2013 Done
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]

Oxford2013-Actions2

2014-02-04T16:47:18Z

Elli Mylonas: /* Actions for Elli Mylonas */

==Council Actions from November 2013 Oxford Meeting==

A list of actions, those responsible, and what has been done about them from [http://www.tei-c.org/Activities/Council/Meetings/tcm56.xml Oxford 2013 face to face meeting] of TEI Technical Council

===Actions for Brett Barney===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/610/ BUG 610] "lem" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: BB to remove the last c...
|BB
|BB to remove the last clause of the sentence in question, beginning ", or to make clear".
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/bugs/387/ BUG 387] clarifying heading or title of a graphic (GREEN open). LB recently posted a comment approving of the...
|BB
|BB will implement the ticket.
|Done 2013-11-13
|}

===Actions for Lou Burnard===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26; LB updated ticket and emailed the others 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Added comment on ticket suggesting that the proposal seems doomed to be rejected; action to explain how to handle this situation in the Guidelines remains open.
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|New element <abstract> added; examples added .
|Done 2013-11-12
|-
|Pure ODD

|LB
|LB to add the new elements and the documentation ahead of the next release; documentation need only be at the element level, along with some brief introduction in the Guidelines, to be expanded to a full section later.
|First pass completed 2013-12-01
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/458/ FR 458] Make listBibl and model.biblLike member of model.personPart (AMBER open). Lou has already done items...
|LB
|close the ticket.
|Done
|-
|i18n: take forward updating translations

|LB
|LB to testdrive the spreadsheet.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/480/ FR 480] Adding the @hand attribute to all (or most) text-containing elements (AMBER open). Breakout group wa...
|LB
|LB to respond to the ticket FR 480.
|
|-
|[http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence. He noted that not only th...
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|Commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Emailed syd 2014-01-05
|-
|[https://sourceforge.net/p/tei/feature-requests/469/ FR 469] add extent to att.dimensions (GREEN open). Agreed. Action: LB to provide an example in HD chapter (2...
|LB
|LB to provide an example in HD chapter (2.2.3) and close ticket.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done, I think.
|-
|[https://sourceforge.net/p/tei/bugs/609/ BUG 609] "lemma" used in a confusing way in CriticalApparatus.xml (AMBER open). Action: LB to remove the phra...
|LB
|LB to remove the phrase "on any one lemma" from the @varSeq description.
|Done, 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/461/ FR 461] Two small improvements to `recording` (GREEN open). Action: LB to do this by next teleconference....
|LB
|LB to do this by next teleconference.
|Done 2013-11-13
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|}

===Actions for Syd Bauman===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|SB sent e-mail to RW 2013-12-06, no response yet (2014-01-10); pinged again 2014-02-04.
|-
|[https://sourceforge.net/p/tei/feature-requests/459/ FR 459] : This is just waiting for implementation....
|SB
|SB will implement by end of January 2014.
|SB: if I understand ticket correctly, this was done along w/ 486.
|-
|[https://sourceforge.net/p/tei/feature-requests/481/ FR 481] check that all sibling att.translatable elements have @versionDate (AMBER open). (Agreed that siblin...
|SB
|SB to check whether this is implemented, and if not, get it implemented then close the ticket.
|was not implemented; have written code, but not tested sufficiently or checked-in
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|SB
|
|SB: when I checked this had already been done -- HC in r12606
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|This ticket reassigned to Syd, and new ticket created: https://sourceforge.net/p/tei/feature-requests/486/ .
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|
|-
|[https://sourceforge.net/p/tei/bugs/619/ BUG 619] tei_allPlus.rng: conflicting ID-types for attribute "id" of element "partialdiff" from namespace "ht...
|SB
|SB to double-check whether able to reproduce and report back on ticket if able to.
|
|-
|[https://sourceforge.net/p/tei/bugs/288/ BUG 288] deprecate use of gram except as a child of gramGrp (AMBER open-accepted). [This is pending creation ...
|SB
|SB to create the new ticket and write the Schematron for this particular deprecation.
|Elsewhere we decided that KH would create the new ticket, which he's done at https://sourceforge.net/p/tei/feature-requests/486/ . But SB still needs to solve this ticket.
|-
|[https://sourceforge.net/p/tei/bugs/468/ BUG 468] Order of elements in publicationStmt (AMBER open-accepted). Group discussion: SB: Despite Lou’s comm...
|SB, LB
|SB will do the content model and LB will do the prose. They’ll work out the specifics.
|Content model checked-in w/ typo at r12736, fixed in r12748.
|-
|[https://sourceforge.net/p/tei/bugs/405/ BUG 405] XPointer schemes may not nest, but see ch. 16 (AMBER open). Action: SB to fix documentation....
|SB
|SB to fix documentation.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|-
|Correspondence SIG:

|SB, LB
|SB and LB would like to (re?-)join the task force. Council advises them to keep in mind the work by the Ontology/MS SIGs, in particular Torsten Schassan, on an ‘object’ or ‘objectDesc’ element.
|
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|SB
|SB to complete.
|done, at r12767
|}

===Actions for Hugh Cayless===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Report on specification and estimated cost for XPointer resolver [HC/SB]

|HC
|HC to report on XPointer resolver and whether we should progress it.
|Draft GLs revision posted on [http://hcayless.github.io/TEI-Guidelines/Guidelines-web/en/html/SA.html#SATS GitHub]
|-
|[https://sourceforge.net/p/tei/feature-requests/465/ FR 465] : Gabby and HC seem to agree on it, and the example looks sensible. LB’s comment could be raised as ...
|HC
|HC will implement before end of January 2014.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/462/ FR 462] idno@type='uri' for Linked Data AMBER open (We agreed. @type=”URI” alongside @type=”URL”) EM: The su...
|HC
|HC to implement this and close the ticket FR 462.
|Done.
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|HC
|HC to email TEI-L.
|FR implemented at meeting and email sent. No agitated (or indeed, any) responses.
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Gabby says the element/classSpecs were done, but corresponding prose was never added to the Guidelines. Opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address that.
|-
|[https://sourceforge.net/p/tei/bugs/605/ BUG 605] clarifying add vs. supplied and del vs. surplus (AMBER open). Action: HC to emend the prose of the p...
|HC, LB
|HC to emend the prose of the paragraph beginning "The add element should not be used" to reference the surplus element also; LB points out that the specList can't be modified, because supplied/surplus aren't defined in Core.
|Done.
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|
|}

===Actions for James Cummings===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|KH emailed the others on 2013-12-26.
|-
|[https://sourceforge.net/p/tei/feature-requests/476/ FR 476] use of stage inside poetry, and using placement attribute (AMBER open). (Council agreed to @place; s...
|JC
|JC to close ticket FR 476 noting it has been resolved.
|Done
|-
|[https://docs.google.com/document/d/1766WTJV2xcfANh8HRZW5m520yrC1nCzQJzUgKpwiylI/edit TEI Roma Replacement Specification] JC: The existing Roma is dated and flawed, as we all know. Many tickets have come up which we cannot...
|JC
|ALL Council to go through the proposal again and discuss it, remembering to look at the comments, and further refine it. JC to make sure it’s tidied up. Deadline: next teleconference.
|Not finished.
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/305/ FR 305] Updating info on projects page (AMBER open). Project pages go out of date. There is a way to submit ...
|JC
|JC to ask DS to make that correction info available on each project page, along with its last-updated date if possible (and the latter should also show up on the bullet-point list).
|
|-
|[https://sourceforge.net/p/tei/feature-requests/466/ FR 466] Make it possible to add SIG labels to tickets (AMBER open). Action: JC as SIG Coordinator to tell th...
|JC
|JC as SIG Coordinator to tell the SIGs that if they wish, we can make their SIG convener a developer on SF and make it possible to assign SIG labels to tickets. Deadline: next teleconference.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/366/ FR 366] rationalize content models of org and place (etc) (AMBER open). Group thinks a small group of people...
|JC, LB, SB
|JC to make ticket red, should stay with JC, and he should initiate the process, working with LB and SB.
|
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/264/ FR 264] altIdentifier in msPart (AMBER pending-accepted). Action: JC to change to Green and assign to himsel...
|JC
|JC to change to Green and assign to himself, then nudge Torsten for an example of an altIdentifier within an msPart.
|Done (awaiting example)
|-
|[https://sourceforge.net/p/tei/bugs/276/ BUG 276] internationalisation links (AMBER open). Language links at bottom of a page should take you to same ...
|JC, SB
|JC to make Green and allocate to SB.
|Ticket Implemented by SR; Closed.
|-
|[https://sourceforge.net/p/tei/bugs/515/ BUG 515] Bad example of feature/@fVal (AMBER open). [Change this to RED as it’s not clear what needs changin...
|JC
|JC to check that’s been changed to RED [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|JC
|JC will create a ticket to reconsider the discussion of “conformable” and “conformant” in the Guidelines.
|
|-
|[https://sourceforge.net/p/tei/bugs/601/ BUG 601] att.patternReplacement/@matchPattern should be XPath regex, not XML Schema (AMBER open). Action: JC ...
|JC
|JC to close as a dupe of FR 432.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/460/ FR 460] Use of geogFeat in transcription? (GREEN open). Ok. Action: JC to do it before next teleconference....
|JC
|JC to do it before next teleconference.
|not done
|-
|[https://sourceforge.net/p/tei/feature-requests/474/ FR 474] add an exemplum for @ref (GREEN open). Action: JC to poke JC; deadline by next teleconference....
|JC
|JC to poke JC; deadline by next teleconference.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/475/ FR 475] Stop using attributes to store space-delimited values (GREEN open). Nothing wrong with space-delimit...
|JC
|JC to Close as Closed-rejected.
|Done
|-
|[https://sourceforge.net/p/tei/feature-requests/401/ FR 401] extend and clarify use of particDesc and settingDesc (GREEN open). JC admits sloth and will implemen...
|JC
|JC to implement before next teleconference; Council decides it might be better to add these (model.
|Done
|-
|[http://sourceforge.net/p/tei/feature-requests/378/ FR 378] ; c.f. A Generic Formalism for Encoding Standoff annotations in TEI). Action: JC to ask Peter Stadle...
|JC, HC, SB
|JC to ask Peter Stadler if he’d like to attend as Council rep; otherwise any interested members of Council (HC,SB) are encouraged to attend virtually.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/229/ BUG 229] Check desc of all xs:anyURI atts for in-doc restrictions (GREEN pending). We got rid of data.code al...
|JC
|JC to check prose discussion all xsd:anyURI attributes by next teleconference.
|pending
|-
|[https://sourceforge.net/p/tei/bugs/336/ BUG 336] AdBlock blocks 'msad' ID (GREEN pending-later). Per last comment, time has passed and nothing else h...
|JC
|JC to close ticket.
|Done
|-
|[https://sourceforge.net/p/tei/bugs/587/ BUG 587] Guidelines version info on pages should link better (GREEN open). Action: JC to carry out his last c...
|JC
|JC to carry out his last comment on the ticket.
|not done
|-
|[https://sourceforge.net/p/tei/bugs/519/ BUG 519] Make lb, pb, cb, gb consistent (GREEN open-accepted). Council decided to close. Action: JC to close ...
|JC
|JC to close [DONE].
|Done
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|unsure
|-
|[https://sourceforge.net/p/tei/bugs/418/ BUG 418] Names and Dates chapter does not mention calendar (GREEN open). Action: JC will add the prose before...
|JC
|JC will add the prose before the next teleconference.
|not done
|}

===Actions for Kevin Hawkins===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/457/ FR 457] : KH: In the ticket I want to clarify what you use tagUsage for and what to put in a project-specifi...
|KH, LB, JC
|KH, LB, and JC will review and make a recommendation to Council before the next face-to-face.
|Discussion happening on ticket.
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] that once 384 is implemented, we’ll add a note on att.typed reminding people that this is meant for ...
|HC, KH
|HC will implement [DONE]. KH will add a comment to FR 384 [DONE].
|done during Council meeting
|-
|[https://sourceforge.net/p/tei/feature-requests/468/ FR 468] : HC: precision expresses false precision that’s not real probability. It’s something more like cert...
|KH
|KH to add to the deprecation document the requirement to announce to the community that we plan to deprecate something and to get in touch if you object.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|KH, SB
|KH will create a new ticket pointing to this and the other two tickets with deprecation problems (as listed on the wiki) saying we need a way to deprecate members of content model and reassign to SB to solve the three tickets using a Schematron warning, and to add @validUntil on constraintSpec.
|done 2013-12-08 (new ticket is at https://sourceforge.net/p/tei/feature-requests/486/)
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] The term strikes back - terminology chapter (AMBER open). The ISO is working on a standard for termi...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/feature-requests/294/ FR 294] altIdentifier is deprecated within msPart (AMBER open). Action: KH to change to Green and add to the...
|KH
|KH to change to Green and add to the ticket about deprecation using Schematron along with 383, if not already done.
|done 2013-12-08
|-
|[https://sourceforge.net/p/tei/bugs/528/ BUG 528] consistency in "the Guidelines" vs. "these Guidelines" (AMBER open). This should be green. Action: K...
|KH
|KH to do this.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|LB commented out otiose paragraph.
|-
|[https://sourceforge.net/p/tei/bugs/216/ BUG 216] half title pages in TEI Tite (AMBER open-postponed). KH has to finish comparing TEI-Tite with the Ap...
|KH
|KH to resolve Tite problems and report regularly to Council on progress.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/280/ FR 280] clarification of colloc (GREEN pending-accepted). #1 is already done. #2: Breakout group agreed that...
|KH
|KH to remove @type from both examples, etc.
|done 2013-12-26
|-
|[https://sourceforge.net/p/tei/feature-requests/482/ FR 482] Earlier we decided:Action: LB, KH and SB to articulate a more generic policy for TEI on the integrat...
|LB, KH, SB
|LB, KH and SB to articulate a more generic policy for TEI on the integration of external standards and will generate a one-page proposal for this policy. This should be provided to Council ahead of the next teleconference. In addition, LB, KH, and SB will check with Laurent that he wants TBX incorporated into the Guidelines as is or kept in sync in the future and what he thinks about melding into the rest of the TEI Guidelines (in language, approach, element naming conventions) or keeping it self-contained.
|Kevin drafted a [http://www.tei-c.org/Activities/Council/Working/tcw28.xml generic policy] and circulated to Lou and Syd on 2013-12-26. Discussion of whether to incorporate TBX into the Guidelines is [http://sourceforge.net/p/tei/feature-requests/482/#28f3 happening on ticket].
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|n/a
|}

===Actions for Martin Holmes===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|Examples provided 2013-11-20
|-
|[https://sourceforge.net/p/tei/feature-requests/471/ FR 471] extend the possible usages of argument (AMBER open). (If the intended use case is encoder-supplied a...
|LB, MH
|
|Done. Fourth example added in rev 12666 2013-11-27.
|-
|[https://sourceforge.net/p/tei/feature-requests/472/ FR 472] docDate in dateline ? EM: dateline does not allow docDate, but byline allows docAuthor. This is inco...
|MH
|MH to add docDate to dateline, and clarify with usage notes.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/443/ FR 443] @resp should be a member of att.global AMBER open. JC and SR: Global attributes should really not be...
|MH, LB
|MH and LB to agree on clarification to Guidelines to say that @resp means different things: responsibility for markup and content except when the element in question is a transcriptional element, in which case the content of the element is marked as coming from the source.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/303/ FR 303] check the apache logs for frequent 404s (AMBER open). Action: JC to ask DS to make the TEI-C webserv...
|JC, MH
|JC to ask DS to make the TEI-C webserver logs available somewhere we can see them; then action on MH to write script to generate lists of bad links of various types. JC also to check google analytics/Webmaster tools. Deadline to report back by next conference call.
|I've checked through the logs, which the webmaster provided for me. There seem to be no instances of systematic errors. There seems to be little to gain from this, assuming the sysadmins are already routine monitoring.
|-
|[https://sourceforge.net/p/tei/feature-requests/470/ FR 470] att.measurement and att.dimensions overlap (AMBER open). We are not really sure why all of these att...
|MH
|MH to move @commodity into its own class, and move measure and measureGrp to att.dimensions. Ticket to GREEN, assign to MH. [Subsequent study suggests to MH that this may be more complicated than it seems, and may have to wait on our having the ability to override valLists in attributes from attribute classes at the element level.]
|Set back to Amber pending further discussion. See ticket for details.
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.
|-
|[https://sourceforge.net/p/tei/feature-requests/405/ FR 405] Wrong schema generated (AMBER pending-accepted). This is due to a bug in the current version in Roma...
|MH
|MH to see if it has been fixed, and if so, close the ticket.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/feature-requests/342/ FR 342] [http://wiki.tei-c.org/index.php/Text_Directionality_Draft first draft of new Guidelines sections] and questions [MH] MH summarized the genesis of this text from Providence.
|MH, LB
|Entire Council to (re)read MH’s draft before next face-to-face meeting. Once we’ve done that and agreed, someone will rewrite chapter 5 (WD) to include MH’s draft and the current section 10.6.6. LB volunteered.
|Council and the WG members have been asked to read and comment on the draft (2013-11-28).
|-
|[https://sourceforge.net/p/tei/bugs/578/ BUG 578] partial and recursive segmentation of s-units (AMBER open). [The Guidelines text is clear enough. Th...
|MH
|MH will revise content model to match the prose.
|Done 2013-11-27, although I really don't like the results of this.
|-
|[https://sourceforge.net/p/tei/feature-requests/298/ BUG 298] att.editLike should not bring att.dimensions & att.ranging (AMBER open-accepted). [MH to ask Gabriel...
|MH
|MH to ask Gabby to implement.
|GB has asked to pass the ticket to MH (2013-11-28). MH to create a full proposal and implement if approved.
|-
|[https://sourceforge.net/p/tei/feature-requests/212/ FR 212] Generic dating class (AMBER pending-accepted). Gabby claimed in 2011 that it’s done except needs som...
|HC, MH
|HC to investigate whether it’s actually been done. MH offered examples if needed.
|Hugh has opened a new bug [https://sourceforge.net/p/tei/bugs/635/ #635] to address this.
|-
|[https://sourceforge.net/p/tei/bugs/568/ BUG 568] "How to edit the Guidelines" and chapter organization (AMBER open). SR: What MH found looks distinct...
|MH
|MH to replace references to entity references with explanation of XIncludes in “How to edit the Guidelines”.
|Done 2013-11
|-
|[https://sourceforge.net/p/tei/bugs/506/ BUG 506] Meaning of @corresp rather in dispute (AMBER open). Working group triage: needs to be discussed: Is ...
|MH
|MH to create an example and run it by tei-council before adding to the Guidelines.
|Done 2013-12-23
|-
|[https://sourceforge.net/p/tei/bugs/582/ BUG 582] Need for consistency in terminology relating to TEI conformance (AMBER open). Working group: Agreed ...
|MH
|MH to deal with the ticket narrowly, using a hyphen and lowercase but leaving both “conformant” and “conformable”.
|Done 2013-11-20
|-
|[https://sourceforge.net/p/tei/bugs/460/ BUG 460] list/@type="unordered" is not recommended, but used often (AMBER open). Working group: This bug has...
|MH
|MH to follow the last comment on ticket to figure out our current situation.
|Research done, and a proposal being developed [http://wiki.tei-c.org/index.php/List_types_and_rendering on the wiki].
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|SR recommends holding off on documentation because he may be able to eliminate attRef in favour of classRef.
|-
|[https://sourceforge.net/p/tei/feature-requests/432/ FR 432] Change regex flavor on @matchPattern (GREEN open). Agreed, XPath. Action: MH Write to TEI-L list, if...
|MH
|MH Write to TEI-L list, if no negative feedback, change.
|Done 2013-11-21 rev 12660
|-
|[https://sourceforge.net/p/tei/bugs/312/ BUG 312] i18n revision due (GREEN open). Action: MH, when he completes action on related ticket (perhaps afte...
|MH
|MH, when he completes action on related ticket (perhaps after moving notes from minutes into tickets), to update this ticket.
|Some contacts made with potential translators 2013-12; suggestion for a pilot project with Italian and Chinese posted to Council list.
|-
|[https://sourceforge.net/p/tei/bugs/442/ BUG 442] update ODD documentation on www.tei-c.org and in Guidelines (GREEN open). Action: MH to finish it....
|MH
|MH to finish it.
|
|-
|[https://sourceforge.net/p/tei/bugs/441/ BUG 441] fDecl doesn't allow att.datcat yet (GREEN open-accepted). Action: MH to prod Piotr....
|MH
|MH to prod Piotr.
|Piotr prodded 2013-11-21, and twice more after that.
|-
|[https://sourceforge.net/p/tei/bugs/525/ BUG 525] citedRange and biblScope should share att class (GREEN open). SB admitted to sloth. Action: SB to co...
|MH, JC, KH
|MH to check Allura settings to make sure that the owners of both bugs and feature requests receive email notifications. [JC and KH looked into this during a break and might have fixed it through another mechanism. MH to check with JC].
|According to investigation, we've done what we can with Allura settings here.
|}

===Actions for Elli Mylonas===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|JC did, hand off to EM Jan 9 '14
|-
|Ideas on how to run an experimental TEI Hackathon [SR]

|EM
|EM to make sure this happens.
|Jan 28 '14 Discussions begun, proposal draft begun
|-
|[https://sourceforge.net/p/tei/feature-requests/300/ FR 300] Move witStart et al. to model.milestoneLike (AMBER pending). Action: EM to change to red and assigne...
|EM
|EM to change to red and assigned to EM to chase up or otherwise close ticket.
|
|-
|[https://sourceforge.net/p/tei/bugs/594/ BUG 594] TEI-C website menu points to wrong index page for Guidelines (AMBER open). Fixed, will appear in nex...
|EM
|EM to create a ticket on the Chrome problem.
|Dec 10, 2013 done
|-
|[https://sourceforge.net/p/tei/bugs/589/ BUG 589] add respons and space to att.responsibility (AMBER open). Working group triage: Is it ok to add have...
|EM
|EM will get rid of locally assigned @resp by adding to att.responsibility (thereby getting @cert as well). Will change to GREEN.
|Dec 10, 2013 Done
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/389/ FR 389] clarify definition of @from on locus and biblScope (GREEN open). EM admits to sloth and will do so. ...
|EM
|EM to do before next teleconference.
|
|-
|[http://wiki.tei-c.org/index.php/TEI_Cheatsheets Cheatsheets: Short best/recommended practice documents] EM: Not cheatsheets - negative implication. RW: Quick Start. HC: Quick Reference; SB: “Guidelettes” ...
|EM
|EM to ask MB to clarify what she wants from Council with regard to helping cheatsheets.
|
|}

===Actions for Sebastian Rahtz===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[http://tei.oucs.ox.ac.uk/EEBO/ http://tei.oucs.ox.ac.uk/EEBO/] for summary of problem, and links to tickets) SR: EEBO-TCP is a gigantic resource that claims to be ...
|SR
|SR will implement the schema change of adding @place to stage and will document and provide an example.
|adding @place. example to do
|-
|[https://sourceforge.net/p/tei/feature-requests/479/ FR 479] Adding the @place attribute to head and seg AMBER open JC noted that head is not meta-textual or in ...
|SR
|SR to take the ticket, and get more examples from the submitter
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/445/ FR 445] Conversion of ODD to HTML: Examples should be aware of element renaming closed-fixed, implemented by...
|SR
|SR to add gi and att renaming to complete the ticket.
| COMPLETED FOR gi. Not possible for att.
|-
|[https://sourceforge.net/p/tei/feature-requests/442/ FR 442] Allow foreign to contain q (AMBER open). The group felt this should be rejected. Action:SR to close ...
|SR
|SR to close ticket because it’s rejected
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/433/ FR 433] loosen content model of salute (AMBER open). SR: Underlying this was a desire for symmetry between s...
|SR
|SR will carry this out
|DONE
|-
|[https://sourceforge.net/p/tei/feature-requests/477/ FR 477] lines of poetry inside trailer (AMBER open). The request is for symmetry between head and trailer. T...
|SR
|SR to find a good way to achieve this, since what was done before with head was rather strange.
|DONE. Have copied what was done with head
|-
|[https://sourceforge.net/p/tei/feature-requests/383/ FR 383] where to put idno within biblStruct? (AMBER open) This is one of three tickets where KH could not fi...
|SR
|SR to check how @validUntil makes the build fail when out of date, and if necessary update this mechanism so it can handle @validUntil on constraintSpec. Ticket 383 will wait on all this, along with the two other tickets.
|DONE. It applies to tei:*[@validUntil], so should just work.] .
|-
|[http://wiki.tei-c.org/index.php/Council_agenda_2013-11#More_Details_on_Agenda_topics bottom of wiki agenda page] ) SR: Why are we proposing using alpha and beta? MH: Because we were proposing asking the community ...
|MH, SR
|Assign MH to update the release documentation re alpha and beta, and investigate how we might add the SVN last changed date and the rev number to the bottom of pages.
|Latter bit done by SR 2013-11-14. Documentation in TCW22 updated by MH 2013-11-14.]
|-
|Ideas on how to run an experimental TEI Hackathon [SR]
|JC, HC, SR, EM
|JC to approach the DH 2014 committee and find out how they would prefer us to do it, and whether it’s a good idea; and tell the Board that HC, SR and EM are prepared to be involved in organizing this along with one or more Board members.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/345/ FR 345] members of model.respLike should be members of att.declarable (AMBER open-later). Breakout group ins...
|SR
|SR to make the ticket Green and go ahead and implement it, including some documentation/examples.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/302/ BUG 302] version ignores @source (AMBER open). This is a Roma issue. Recommend marking as closed won’t fix be...
|SR
|SR to try reproducing this and set as closed-won’t fix.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/583/ BUG 583] Adding new attribute fails in Roma schema generation (AMBER open). Same as 302. Action: SR wil set a...
|SR
|SR wil set as closed-won’t fix and check that it has the Roma tag.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/434/ BUG 434] issues with ePub conversion (2/3) (AMBER open). Any issue not dealing with ODD processing should be ...
|SR
|SR will ask poster kindly to post there (explaining why) and close this issue.
|DONE
|-
|[https://sourceforge.net/p/tei/bugs/581/ BUG 581] `attRef` needs better documentation (AMBER open). Action: SR to implement either removal of attRef, ...
|SR, MH
|SR to implement either removal of attRef, MH to adjust documentation.
|FIxed attRef. thinking about classRef
|-
|[https://sourceforge.net/p/tei/feature-requests/467/ FR 467] Make @name optional on tei:relation (GREEN open). Action: SR has already done this....
|SR
|SR to action
|DOne
|-
|[https://sourceforge.net/p/tei/feature-requests/478/ FR 478] loosening content and model of `signed` (GREEN open). Agree that is is green. Though would model.div...
|SR
|SR to implement signed at top as well as bottom
|DONE
|}

===Actions for Paul Schaffner===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/453/ FR 453] a place for metadata that you can't fit into existing header elements AMBER open Discussion talks mo...
|MH, PS, LB
|MH will offer DC examples and PS will offer MARC examples. LB will pull them together into some text to be inserted into the Guidelines. Given this, Council will reconsider the feature request and whether to create the wrapper element.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/360/ FR 360] New attribute @keepHyphen. Ticket open, ticket GREEN, it’s rejected throughout the comments....
|PS
|PS to provide an example of the mechanism recommended to handle the use-case.
|
|-
|[https://sourceforge.net/p/tei/bugs/563/ BUG 563] inconsistent encoding of citations to sources of examples (AMBER open). Working group recommends ass...
|BB, EM, PS
|BB, EM, and PS to work on the ticket by mid-February 2014.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|}

===Actions for Torsten Schassan===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|

|TS
|TS to come up with a more detailed problem description and what the WG should attempt to solve by 2014-01-01.
|
|}

===Actions for Rebecca Welzenbach===
{|class="wikitable sortable"
|Ticket
|Who
|What
|Result
|-
|[https://sourceforge.net/p/tei/feature-requests/384/ FR 384] : In April RW made a spreadsheet showing which elements she recommends moving into att.typed. And in...
|SB, RW
|SB and RW will review the list again.
|
|-
|Attributes without examples

|BB, RW
|BB and RW to turn into bug reports those attributes that are without examples that are high priority or need new/updated definitions.
|
|-
|[https://sourceforge.net/p/tei/feature-requests/377/ FR 377] retaining punctuation marks in the text of a TEI document (AMBER open-accepted). RW says she has add...
|RW
|RW to finish the work and ask for help if necessary.
|
|-
|[https://sourceforge.net/p/tei/bugs/548/ BUG 548] use of modal verbs in Guidelines (AMBER pending-later). Already assigned to KH. RW agreed to help. I...
|KH, RW, LB
|KH and RW to create a new, detailed ticket with all questionable cases. In the meantime, LB will fix the edits that KH made at r12525.
|
|-
|[https://sourceforge.net/p/tei/bugs/558/ BUG 558] name/orgName (AMBER open). Action: RW to ask PS where he is on this; change ticket status to GREEN....
|RW, PS
|RW to ask PS where he is on this; change ticket status to GREEN.
|
|-
|[https://sourceforge.net/p/tei/bugs/401/ BUG 401] Most attributes lack good examples (GREEN open-accepted). This was previously discussed. Action: RW ...
|RW
|RW to follow up.
|
|}

[[Category:Council]]