distance about modelling-opportunity-data HOT 4 OPEN

Another approach here is to say that a ride follows a specific route or course. The distance would then be a property of the route, which might also define its start and end points.

Some related discussion: schemaorg/schemaorg#1666

from modelling-opportunity-data.

Hi @nickevansuk - Why are we not using minValue/maxValue and instead going with a bespoke range property for this?

These would seem to stay within the schema.org spec to me:

// 0-5
"distance": {
  "type": "QuantitativeValue",
  "minValue": 0,
  "maxValue": 5,
  "unitCode": "KMT"
}

// 5
"distance": {
  "type": "QuantitativeValue",
  "value": 5,
  "unitCode": "KMT"
}

// 50+
"distance": {
  "type": "QuantitativeValue",
  "minValue": 50,
  "unitCode": "KMT"
}

from modelling-opportunity-data.

A new eventDistance property would be nice for lots of Events (annual pilgrimages, hikes) and not just SportsEvent (race).

Wikidata has now added this property as well:

• event distance - distance over which a race or other event is conducted or was achieved

We already have duration so this seems a natural gap that needs filled.

from modelling-opportunity-data.

Makes sense to me, please do implement minValue and maxValue - these are more consistent with schema.org than my suggestion above.

from modelling-opportunity-data.