# 2018-02-28 - Facilities, Booking, Validation

## **Summary**

### **Facilities**

I discussed a slightly revised proposal around handling of Facilities. The changes were mostly around how to approach the modelling. The revised proposal is based on describing opportunities to book facilities (including equipment), rather than describing the facilities themselves.

There's a brief summary in the slides, but I've also documented the proposal on github here:

<https://github.com/openactive/modelling-opportunity-data/issues/62>

Please have a read through and add your comments. We had a good discussion on the call which highlighted some useful additions and helped us test out the thinking.

I aim to publish a draft of the 1.1 opportunity model specification tomorrow.

### Booking

The latest working draft of the booking API that the early implementers are testing can be found here:

<https://docs.google.com/document/d/1QMj_w2tuOvxRfctu70JjSv1WgFKvNfU5URCmIB4sSu8/edit?usp=sharing>

Please take a look and add you comments.

### Data Validation

We ran out of time to discuss approaches to improving quality of the published data by tightening up the specification and creating some validation tools. There are some notes in the slides.

We'll discuss this in a future call.

## Slides

{% embed url="<https://docs.google.com/presentation/d/11UIB-1vmZCXlNFh1QgBI9mL3R7OQeyofTQIo7EL6mv8/edit>" %}

## Video

{% embed url="<https://youtu.be/sSYAcbFn6uk>" %}


---

# 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-02-28-facilities-booking-validation.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.