Booking use cases and requirements

Hi,

I've put together a set of use cases and requirements for a Booking API. I
think this captures the discussion and recommendations from our recent
workshop [1] and last working group call.

The document is divided into:

* high-level use cases from perspective of user, third-party and platform
* a list of requirements that should inform design of the specificaiton
* an indication of which requirements will be addressed in version 1

We'll review the main elements of the doc in our call tomorrow, but please
feel free to start adding comments and feedback. This is an initial draft
so we can include additional use cases and clarify requirements as we go.

https://docs.google.com/document/d/1fsCr071V12i_2g0DK818OAGlEAJFLWwkBp9bpgx4fo8/edit?usp=sharing

I'm aware that there are various API projects currently running, I'm keen
to make sure that where possible that work aligns with our objectives so
that we can maintain a common direction. Obviously this doesn't stop people
exploring a variety of implementation options.

Cheers,

L.

[1].
https://lists.w3.org/Archives/Public/public-openactive/2018Feb/0000.html

-- 
Leigh Dodds, Data Infrastructure Programme Lead, theodi.org
@ldodds
The ODI, 65 Clifton Street, London EC2A 4JE