Re: Competitions calendar

Thanks, Andy.

My comments inline.

[snip]


>
> What would we provide (eventually!)
> ===========================
> Free crowdsourced database, open data
>    - database table(s)
>    - API for querying (open to all) so you can embed listings in your web
> site
>    - API for add/edit/delete, for trusted parties
>    - Easy "competition setup wizard" to add a competition
>    - Nice web page for querying
>    - notifications ?
>    - regular nightly exports to Excel, CSV, JSON
>    - able to export content into more flexible, self-describing JSON-LD
>
>
Suggestion: a unique URL (IRI) for each event. (I think it is 'url' in DB
fields)


> Database fields
> ============
>
> id:  we assign a UUID
> slug: user may supply a short URL component which is mnemonic
> url:  https://data.opentrack.run/x/<year>/<country></slug>
>
> start_date
> end_date   (if more than one day)
>
> entries_open_date:
> entries_close_date
> # OR entries_status = [NOT_OPEN_YET|OPEN|CLOSED]   ?
>
> names:   we think we need 4 fields:
>    1. long_name, 2. short_name in each of:
>          A. english
>          B. local language (may be latin, Greek, Cyrillic, Japanese...)
>

C.? -> ISO tag of the local language (es, fr, …)


>
> description_text:  (english + local language)
>
> address    # geocodable string
> city   # can be derived by geocoding APIs
> country   # can be derived by geocoding APIs
>

What about this similar structure for address? It will be easier to geocode
afterwards.
- streetAddress
- addressLocality -> more generic than city
- postalCode
- addressRegion -> (for instance, state in the US)
- country


>
> performance_level:   yes/no for each that is expected.  Some meetings
> go all the way up/down
>     - world class   (age grade 90% +)
>     - national class   (age grade 80% +)
>     - club class   (age grade 70% +)
>     - active  (60%)
>     - couch potato (50%)
>
>
I like this ^. The problem I see is the age grade. For instance, this is
not popular in Spain, so it's difficult to measure.



> disciplines:  which of TF (outdoor), TF (indoor), Road, XC, Mountain,
> Walks  (boolean field each?)
>    # you must supply at least one! you ought to know...
>
>
How deep we should go in this? I.e., the 2018 European Championships is a
TF (outdoor) competition, but includes also Road competitions. The European
Throwing Cup is a TF (outdoors) competition, and the Offenburg Javelin
Throw Meeting is also a TF (outdoor).

What about a hierarchical structure of checkboxes? From the abstract (TF
Throws -> parent) to the concrete (Javelin Throws -> leave of the tree).


> events:   list of athlib event_codes offered.  May not be known
>     # could be add two levels:
>     # high level:  each event offered, comma-separated results
>     # detailed:  events in each category, more detailed structure.
>     #    could only be provided through some human effort or by
>     #     entry systems.
>
>
Is this similar to disciplines? :


>
> age_groups:  subset of U12, U14, U16, U18, U20, U23, SEN, Masters
>    # we suggest to use the IAAF ones as an approximation, even though
>    # many countries have their own systems.
>    # adult looking for races can then 'filter out' kids meetings
>    #  possibly accent parseable ranges e.g. "U14,U16" or "U16+" or
> "M35-M60"
>
>
My proposal to be universally interoperable:
- Possibility to select the IAAF + WMA categories by default.
- If you need other category, several fields to describe 'your category':
   - Your denomination + acronym
   - maxAge, minAge
   - gender
   - other? (perhaps just text)

No comments on the rest.

Best,

Martin