Difference between revisions of "BP revision ticket triage"
Jump to navigation
Jump to search
(→easy implementation: status from July meeting) |
m (→medium implementation) |
||
| 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] – Paul will review Kevin's prose. | * [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] – Paul will review Kevin's prose. | ||
* [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?] – | + | * [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/15 issue 15: add <distinct> to Level 4?] – complete |
* [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. Andrew will try to dig up some past discussion of event tagging to share for consideration. | * [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. Andrew will try to dig up some past discussion of event tagging to share for consideration. | ||
Revision as of 04:06, 1 August 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 – Paul will review Kevin's prose.
- issue 8: consider adding <width> and <height> as children of <extent> – After reflection, Kevin has withdrawn this.
- issue 15: add <distinct> to Level 4? – complete
- 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. Andrew will try to dig up some past discussion of event tagging to share for consideration.
- issue 25: Cover MARC records and TEI body – BPTL group think this is out of scope. Since Stuart hasn't added anything, we've closed the issue.
hard implementation
- issue 2: update the tie to a specific version of P5 and issue 37: ODDs are invalid – wait to discuss till Syd attends a call
- issue 9: intertwingled content in <editorialDecl> – Andrew will implement by September call
- issue 13: update to take into account RDA – Kevin has recruited a cataloger colleague to help
- issue 27: Coordinated OCR in BPTL – waiting on Stefan
- issue 38: build process broken – assigned to Syd
Could be controversial
easy implementation
- issue 36: specify how to encode sigla – Paul will summarize our options
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
