Difference between revisions of "BP revision ticket triage"

From TEIWiki
Jump to navigation Jump to search
m (easy implementation: issues 30 and 33 done)
(medium implementation: issue 8 not to be fixed)
Line 17: Line 17:
 
* [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] – need to reconsider
 
* [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] – need to reconsider
* [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/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?]
 
* [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 20:38, 3 June 2016

Probably not controversial

easy implementation

medium implementation

hard implementation

Could be controversial

easy implementation

medium implementation

hard implementation

Postpone