CODEBASE-361: Justin Coyne has sent a pull request [1] to remove the UnAPI [2] endpoint from Blacklight -- apparently it does not/cannot produce valid HTML5, and the unapi maintainers are uninterested in any further support for the standard (from #code4lib, "mjgiarlo: I see no reason unapi should live on into the HTML5 era. deprecate and suggest folks do Linked Data "). Much of the functionality is redundant with the Document Extension Framework metadata in
, and for most material, COinS should be able to provide an equivalent experience.
I propose to apply the patch and immediately remove UnAPI support. If there's sufficient interest in continuing to support UnAPI or providing a deprecation period, I would instead propose to revive the separate blacklight_unapi plugin.
CODEBASE-361: Justin Coyne has sent a pull request [1] to remove the UnAPI [2] endpoint from Blacklight -- apparently it does not/cannot produce valid HTML5, and the unapi maintainers are uninterested in any further support for the standard (from #code4lib, "mjgiarlo: I see no reason unapi should live on into the HTML5 era. deprecate and suggest folks do Linked Data "). Much of the functionality is redundant with the Document Extension Framework metadata in
, and for most material, COinS should be able to provide an equivalent experience.I propose to apply the patch and immediately remove UnAPI support. If there's sufficient interest in continuing to support UnAPI or providing a deprecation period, I would instead propose to revive the separate blacklight_unapi plugin.
[1] https://github.com/projectblacklight/blacklight/pull/10 [2] http://unapi.info