BP revision ticket triage: Difference between revisions

From TEIWiki
Jump to navigation Jump to search
Kshawkin (talk | contribs)
m added section for issues to postpone
Kshawkin (talk | contribs)
added existing tickets, removed section numbering
Line 1: Line 1:
== A. Probably not controversial ==
== Probably not controversial ==


=== 1. easy implementation ===
=== easy implementation ===


=== 2. medium implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/6 issue 6: revisit encoding of ISBNs]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/19 issue 19: pb@xml:id and METS]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/20 issue 20: revised "display examples" for levels 3 and 4]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/22 issue 22: a corrigible error to fix (accidentally referring to Tite!)]


=== 3. hard implementation ===
=== medium implementation ===


== B. Could be controversial ==
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/3 issue 3: rewrite section on @rend and @rendition to account for @style]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/4 issue 4: clarify representations of milestones]
* [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]
* [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/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/24 issue 24: tagging events]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/25 issue 25: Cover MARC records and TEI body]


=== 1. easy implementation ===
=== hard implementation ===


=== 2. medium implementation ===
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/9 issue 9: intertwingled content in <editorialDecl>]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/13 issue 13: update to take into account RDA]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/27 issue 27: Coordinated OCR in BPTL]


=== 3. hard implementation ===
== Could be controversial ==


== C. Postpone ==
=== easy implementation ===
 
=== medium implementation ===
 
* [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?]
 
=== hard implementation ===
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/10 issue 10: indicating interviewers and interviewees]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/11 issue 11: encoding <pb>s within <note>s]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/12 issue 12: bibliographies and other lists of works cited]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/16 issue 16: give guidance on encoding serials and composite documents]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/26 issue 26: Add (or update) examples to show use of modern authorities]
 
== Postpone ==
 
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/7 issue 7: give guidance on incorporating outside metadata into a header]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/21 issue 21: reconsider rend="keep-hyphen"]
* [https://github.com/kshawkin/Best-Practices-for-TEI-in-Libraries/issues/23 issue 23: relation of BP to TEI Simple]

Revision as of 21:14, 31 January 2016

Probably not controversial

easy implementation

medium implementation

hard implementation

Could be controversial

easy implementation

medium implementation

hard implementation

Postpone