Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
(→medium implementation: issue 5: assigned to Kevin to investigate) |
(→medium implementation: clarification on issue 5, status of issue 8) |
||
| Line 16: | Line 16: | ||
* [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/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] – assigned to Elli to investigate further | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones] – assigned to Elli to investigate further | ||
| − | * [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] – Kevin will ask for clarification from Council on practice in P5 | + | * [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] – Kevin will ask for clarification from Council on practice in P5. Then we can reconsider. |
| − | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 issue 8: consider adding <width> and <height> as children of <extent>] | + | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/8 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. |
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] | ||
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/18 issue 18: rework Level 1 and Level 2 structure?] | ||
Revision as of 21:53, 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 – Kevin will implement along with issue 33.
- issue 33: clarify where to encode <pb/>s: at a point where more than one div is opened or closed at once – Kevin will implement along with issue 30.
- 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 – Kevin will ask for clarification from Council on practice in P5. Then we can 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
