# 2018-10-10 - Booking API Update and Feedback

## Summary

A quick progress update on new developments:

* We have published the [V2.0 data model specification](https://www.openactive.io/modelling-opportunity-data/EditorsDraft/)
* Our [Validator ](https://www.validator.openactive.io)is up to date and conforms with the specification&#x20;
  * Open source, to be updated by the community as we continue to update the specifications
* We've launched our [Developer ](http://developer.openactive.io)site
  * Acts as a reference point for people who are starting to publish and use data as part of OpenActive
  * Aimed at developers, people looking to build applications against existing data feeds (knowledge of JSON and data model)
* We've made progress on our Booking API ([Booking 1.0 draft](https://www.openactive.io/open-booking-api/EditorsDraft/)), and understand that the community needs more time to explore the specification.&#x20;
  * We would like to collate feedback from practical use

We had a discussion on how to structure and approach the booking API flow, exploring anonymous leases, 2-phase commit options, alternative 2-phase commits, and two-step payment options. The discussion centred around community feedback and thoughts on how to approach the booking API flow. More detailed notes on the call can be found [on this link](https://docs.google.com/document/d/1lhPdIK3tcn3dV27DMvAhYU_7p9FcErQhaO65hEmEYpY/edit?usp=sharing).

## &#x20;Slides

{% embed url="<https://docs.google.com/presentation/d/1nBBwhY0MhqCWVA_pcrimjo9iWfXFC_lBeKZapJYQCRg/edit#slide=id.p3>" %}

## Video

{% embed url="<https://www.youtube.com/watch?v=HaswQ6T2hio>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://w3c.openactive.io/meetings-archive/2018-10-10-booking-api-update-and-feedback.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
