You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As introduced in the meeting in March, we would need a mechanism to indicate who are the intended participants in a competition. This intended audience was defined as official categories based on age and sex, but a more descriptive and non-technical term (like a tag) would be more suitable for a general audience.
In terms of the vocabulary could be described with the property audience.
Athletes are used to the SEN, M35, W40 terminology, but beginners may not. So, why we don't define a qualitative taxonomy like:
for all ages
suitable for kids
women-friendly race
serious athletes
...
Comments?
The text was updated successfully, but these errors were encountered:
I've seen in the OpenActive specification a similar way to categorize events, including general information on the intensity and suitability of sports events.
category is used for tagging the event and level should be used with a deterministic set of concepts.
{
"name": "Tai chi Class",
"description": "A tai chi class intended for beginners",
"startDate": "2017-03-22T20:00:00-05:00",
"duration": "PT60M",
"category": [
"Suitable For All", "Low Intensity"
],
"level": [{
"type": "Concept",
"prefLabel": "Beginner"
}]
}
As introduced in the meeting in March, we would need a mechanism to indicate who are the intended participants in a competition. This intended audience was defined as official categories based on age and sex, but a more descriptive and non-technical term (like a tag) would be more suitable for a general audience.
In terms of the vocabulary could be described with the property
audience
.Athletes are used to the SEN, M35, W40 terminology, but beginners may not. So, why we don't define a qualitative taxonomy like:
for all ages
suitable for kids
women-friendly race
serious athletes
Comments?
The text was updated successfully, but these errors were encountered: