January 2018 Hackathon review and feedback on further iterations of the Knowledge Beacon API

[RichardBruskiewich]

Time to review the good, the bad and the ugly of the overall objectives, big picture design and implementation priorities of the Knowledge Beacon API. After 9 months of working with the concept and the specific initial implementation, what would we do differently now? What is missing (e.g. Provenance)? What is less useful or awkward to use? Is there a better way to specify it? Is the data representation optimal (e.g. REST/JSON) or would a RDF/LOD standard work better? What specific standards should be enforced (e.g. data type semantics? relation predicate semantics?) Are there any practical operational issues (e.g. standards for dealing with problematic queries? Exception/error reporting)?