Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
m (→easy implementation: status of issue 33) |
(→easy implementation: issue 34 assigned to James) |
||
| Line 10: | Line 10: | ||
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – pending resolution of issue 33, Kevin will implement | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/30 issue 30: milestones occurring at div boundaries] – pending resolution of issue 33, Kevin will implement | ||
* [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] – consensus reached during conf call, Kevin will implement if no objections raised. But then Martin M. raised this on TEI-L, so we might take into account those responses | * [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] – consensus reached during conf call, Kevin will implement if no objections raised. But then Martin M. raised this on TEI-L, so we might take into account those responses | ||
| − | * [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] – | + | * [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 |
=== medium implementation === | === medium implementation === | ||
Revision as of 18:24, 2 May 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 – pending resolution of issue 33, Kevin will implement
- issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once – consensus reached during conf call, Kevin will implement if no objections raised. But then Martin M. raised this on TEI-L, so we might take into account those responses
- 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
- issue 4: clarify representations of milestones
- issue 5: rewrite discussion of @key and @ref to discuss magic tokens and Linked Data
- issue 8: consider adding <width> and <height> as children of <extent>
- 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
