TAG Meeting 2017-08-09

See agenda in meeting slide deck to see information reviewed.

On publishing API specifications.

Some members expressed agreement that alternative implementations inevitable, so should be specified. No one raised issues with timing when that question was raised.
This work was also connected to ecosystem growth, in terms of expressing to client developers exact specifications for interoperability.
Question of how APIs would be versioned, and if those would have an independent version, was raised. Current direction is unclear - needs to be researched.

On the question of more flexible query mechanisms (topic 5, on historical TAG API discussions):

A technology like Graph QL could considerably raise the bar for API implementers.
It was noted as well that current composite APIs do some of the "flattening" and "navigation" tasks that technologies like Graph QL do.
Raises the bar for clients
It was also noted that the Event API work (under the described requirements) would be incompatible with a technology like Graph QL! So it might be that the Events API would only be available in specific circumstances (e.g. on particular paths or with particular queries).

Ed-Fi Governance