Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
(→medium implementation: issue 5: waiting on someone else to review) |
m (→medium implementation: Syd has finished issue 15) |
||
| Line 17: | Line 17: | ||
* [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 would like others to review his suggested prose before he implements. | * [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 would like others to review his suggested prose before he implements. | ||
* [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/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?] – Syd | + | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – Syd has implemented |
* [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/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] – In May 2016 meeting we felt that we should leave to Council to implement in P5 first, but subsequent discussion on the ticket questions this. | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/24 issue 24: tagging events] – In May 2016 meeting we felt that we should leave to Council to implement in P5 first, but subsequent discussion on the ticket questions this. | ||
Revision as of 18:42, 11 July 2016
Contents
Probably not controversial
easy implementation
- issue 6: revisit encoding of ISBNs – complete
- 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 – Kevin would like others to review his suggested prose before he implements.
- issue 8: consider adding <width> and <height> as children of <extent> – After reflection, Kevin has withdrawn this.
- issue 15: add <distinct> to Level 4? – Syd has implemented
- issue 18: rework Level 1 and Level 2 structure? – decided not to implement
- issue 24: tagging events – In May 2016 meeting we felt that we should leave to Council to implement in P5 first, but subsequent discussion on the ticket questions this.
- issue 25: Cover MARC records and TEI body – think this is out of scope for BPTL but will keep open in case Stuart clarifies something we missed
hard implementation
- issue 2: update the tie to a specific version of P5 and issue 37: ODDs are invalid
- issue 9: intertwingled content in <editorialDecl>
- issue 13: update to take into account RDA
- issue 27: Coordinated OCR in BPTL
- issue 38: build process broken – assigned to Syd
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
