Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define additional Event properties #3

Closed
ldodds opened this issue Dec 14, 2016 · 4 comments
Closed

Define additional Event properties #3

ldodds opened this issue Dec 14, 2016 · 4 comments

Comments

@ldodds
Copy link
Contributor

ldodds commented Dec 14, 2016

Schema.org doesn't currently have general terms to cover the following ways to categories events:

  • Restrictions: e.g. gender, age, membership restrictions
  • Suitability: e.g. level of fitness, experience
  • Pre-requisites: e.g. membership, equipment needed
  • Categorisation: e.g. intensity of session, activities involved, programme followed

We should work to define these within Schema.org

@MikeThacker1
Copy link

Properties to consider (and maybe reject) are:

  • data publisher
  • last updated date
  • commissioned by (programme may give this)
  • contact - Is this just the contact details of the organiser (ie not event specific)?
  • review - Any reference to independent reviews of teh activity

@ldodds
Copy link
Contributor Author

ldodds commented Feb 23, 2017

From Nick Evans:

In Active Lives we capture Setting, which describes where the activity is taking place - I.e. is it indoor or >outdoor? There is then a set of defined settings that you could allocate to the location, e.g. Indoor >examples are shown below:
At Home
Leisure/Fitness/Sport Centre or Gym
Community Centre or Village Hall
Specialist Facility

Should we be capturing setting as a descriptive property of an event? If so, then we should recommend a set of legal values. This would make it easier to filter/search by settings.

Alternatively, settings could be added as tags associated with an Event. This is simpler, but is more limited.

Related is:

Other event properties could include:
· Activity Style – e.g. Group, 1 to 1, Individual
· Activity Structure – e.g. formal or informal. Formal could include Club Training session, Coached >session, Competition, while Informal could include Holiday, Social
· Purpose – e.g. Leisure, Competition, Training, Commuting

From last CG call:

  • Surface: e.g. astro turf, etc.

@ldodds
Copy link
Contributor Author

ldodds commented Mar 22, 2017

At our last community hangout we decided to define a minimal set of property to help describe events, these were:

  • age - to be specified as a range
  • sex/gender - e.g. male, female, mixed
  • height - to be specified as a range (in metric)
  • weight - to be specified as a range (in metric)
  • category - a general purpose way to tag an event with a category. this can encompass many of the other requirements for now. After experience with seeing how it is used, we can define additional more specific properties and, if necessary, controlled vocabularies

@ldodds
Copy link
Contributor Author

ldodds commented Mar 27, 2017

Done. Defined in the Editors Draft schema and the vocabulary at https://www.openactive.io/ns/

@ldodds ldodds closed this as completed Mar 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants