# 2017-03-13 - Modelling Events, Activities

## Summary

Topics covered:

* Summary of latest specification releases and plans
* Moving forward with activity lists, e.g. sharing in a common formats, identifying overlaps
* How we provide extra detail around describing events to support discovery
* Making outputs of the group more visible
* Scheduling more regular meetups

Couple of key discussion points and actions:

* Next series of community hangouts are now in our [shared calendar](https://lists.w3.org/Archives/Public/public-openactive/2017Mar/0012.html)
* We should develop a "Getting Started" guide to supplement the Modelling Opportunity Data specification to help developers implement the specification with clear examples. Any further technical specification will be added to the existing spec
* We can promote the output as a deliverable from this group on the W3C site and then on the OpenActive website
* I agreed to convert the activity lists shared so far into a common format for further review/analysis, with a view to starting to identify a common list
* There was consensus that we need some extra descriptive properties for events, but that we shouldn't spend too much time refining this or trying to develop controlled vocabularies for now. These were in two categories:
  * simple numeric ranges, e.g. age, height, weight
  * properties to allow free text/tags, e.g. category, purpose

This would help identify the Who/What/Where/When around events.

## Slides

{% embed url="<https://docs.google.com/presentation/d/1Uxdld1ntsctPCcYp6WABz5Td1kD4Uj_aGg1Yr9NLn34/edit?usp=sharing>" %}

## Video

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


---

# 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/2017-03-13-modelling-events-activities.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.
