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

Consider supporting Venues as a component #126

Open
JJJ opened this issue Oct 9, 2020 · 0 comments
Open

Consider supporting Venues as a component #126

JJJ opened this issue Oct 9, 2020 · 0 comments

Comments

@JJJ
Copy link
Contributor

JJJ commented Oct 9, 2020

Problem

The iCalendar specification only provides a single (but flexible) LOCATION parameter for Event locations. There is also a GEO parameter, but that is for latitude and longitude and can largely be derived from the Location if an address is provided.

This makes the experience of holding a virtual Event feel like a secondary application, since the "Location" is technically a URI (say, to Zoom, Twitch, or elsewhere). URIs are completely valid locations, but it doesn't feel obvious to use it that way.

One Solution

Some other WordPress calendar plugins have used post types for storing Venues for repeat use. This way, the location can be saved one time and picked from a list rather than needing to be reentered each time. I'm uncertain that this exact implementation makes sense for our use (maybe a taxonomy is better?) but I can see why this approach is attractive.

Why?

Our Calendar Feeds add-on would benefit from supporting the VVENUE iCalendar component. It's been in draft status since 2007, but appears to be largely supported by major calendar softwares.

See: See: https://tools.ietf.org/html/draft-norris-ical-venue-00

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

1 participant