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

Dance Events API #3

Open
razbakov opened this issue Jul 31, 2020 · 3 comments
Open

Dance Events API #3

razbakov opened this issue Jul 31, 2020 · 3 comments
Assignees

Comments

@razbakov
Copy link
Contributor

There are a lot of dance projects on the web and none of them has an API so that other developers can easy connect those projects together. Let's define some common standard for dance events API.

@razbakov razbakov self-assigned this Jul 31, 2020
@dereuromark
Copy link

What did you gather so far on this one?

From my experience it seems the following are useful:

  • title [required]
  • slug (URL version of it)
  • type [required] (Workshop, Festival, Marathon, Class, ...)
  • dances (list of e.g. Salsa, Bachata, Zouk, ...)
  • country/city/location/place (if applicable)
  • online (bool, pure virtual event)
  • url (with additional info, or FB event)
  • address, lat, lng
  • description [required] (longer text, maybe markdown or bbcode, or HTML)
  • status (active, canceled)
  • beginning/end [required] (timestamps, datetime)
  • cost
  • size (people max limit)
  • ticket_status (not open yet, open, sold out, ...)
  • level (beginner, medium, advanced, can be also multi-select)

And covid specific (maybe not part of the main API specification):

  • covid_safe (bool, opt in for guarantee of basic protocol)
  • covid_details (explaining the implementated protocols)

What do you think?

@razbakov
Copy link
Contributor Author

razbakov commented Oct 15, 2020

Hi @dereuromark thanks for your interest!

Great input! Especially I like the covid addition, it's very relevant now :)

I think the best starting point would be to follow https://schema.org/Event specification, as it will provide and enhance SEO possibilities included as microdata or RDFa or JSON-LD in rendered html.

See also schemaorg/schemaorg#1842 (comment)

@dereuromark
Copy link

https://schema.org/DanceEvent also exists
But I think in the end we need this + some own fields on top probably.
They also move very slow, so it wouldn't be wise to lock in on their fields available.

We could still expose through json-ld
but in general, maybe we should also have an easier internal way of syncing data, e.g. through a basic JSON API.

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