Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
(→easy implementation: added new issue 30) |
(→medium implementation: added issue 31) |
||
| Line 36: | Line 36: | ||
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/14 issue 14: how to record non-ASCII characters] | ||
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/17 issue 17: how to indicate conformance to the BP?] | ||
| + | * [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] | ||
=== hard implementation === | === hard implementation === | ||
Revision as of 04:27, 10 March 2016
Contents
Probably not controversial
easy implementation
- issue 6: revisit encoding of ISBNs
- issue 19: pb@xml:id and METS
- issue 20: revised "display examples" for levels 3 and 4
- issue 22: a corrigible error to fix (accidentally referring to Tite!)
- issue 29: explain how to use just the header recommendations from the Best Practices
- issue 30: milestones occurring at div boundaries – created after we passed this point
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
