Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
(→medium implementation: issue 5 needs to be reconsidered) |
m (→easy implementation: issues 30 and 33 done) |
||
Line 8: | Line 8: | ||
* [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/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/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] – | + | * [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] – | + | * [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] – James will implement | * [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] – James will implement | ||
Revision as of 03:26, 3 June 2016
Contents
Probably not controversial
easy implementation
- issue 6: revisit encoding of ISBNs – complete
- issue 19: pb@xml:id and METS – postponed
- issue 20: revised "display examples" for levels 3 and 4 – pending implementation by Elli
- issue 22: a corrigible error to fix (accidentally referring to Tite!) – complete
- issue 29: explain how to use just the header recommendations from the Best Practices – complete
- issue 30: milestones occurring at div boundaries – complete
- issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once – complete
- issue 34: clarify where to encode <pb/>s: footnotes not entirely on same page as point of attachment – James will implement
medium implementation
- issue 3: rewrite section on @rend and @rendition to account for @style – assigned to Peter to implement
- issue 4: clarify representations of milestones – assigned to Elli to investigate further
- issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data – need to reconsider
- issue 8: consider adding <width> and <height> as children of <extent> – Kevin will review notes from 2016-05-02 meeting for other ideas of how to better handle this and add a revised proposal as a comment on the issue.
- issue 15: add <distinct> to Level 4?
- issue 18: rework Level 1 and Level 2 structure?
- issue 24: tagging events
- issue 25: Cover MARC records and TEI body
hard implementation
- issue 2: update the tie to a specific version of P5
- issue 9: intertwingled content in <editorialDecl>
- issue 13: update to take into account RDA
- issue 27: Coordinated OCR in BPTL
Could be controversial
easy implementation
medium implementation
- issue 14: how to record non-ASCII characters
- issue 17: how to indicate conformance to the BP?
- issue 31: ambiguity over use of <lb/>, <cb/>, and <pb/> in Level 4
hard implementation
- issue 10: indicating interviewers and interviewees
- issue 11: encoding <pb>s within <note>s
- issue 12: bibliographies and other lists of works cited
- issue 16: give guidance on encoding serials and composite documents
- issue 26: Add (or update) examples to show use of modern authorities