-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add EventMovedOnline to valid eventStatus values / use affiliatedLocation #227
Comments
Suggestion of two different rules that could be applied here: A)
B)
Both A and B are compatible with schema.org, and B is more directly in line with schema.org, however data collection for B seems more ambiguous? |
Noting concerns that that existing data users may not yet support this as an enumeration value for Default behaviour for unrecognised
|
It seems to me that the intended use case of this new enumeration can be inferred already in the context of an RPDE feed for any feed consumer that tracks the state of Events. For any that do not track this information, the only loss of clarity is whether the Event was always online versus moved online. For instance: If an Event has been updated in the feed, retains an This aligns well with Events that have #225 set to |
Further to this, as noted by Bookwhen: they don't retain any indication of whether an event has been "moved online" or whether it has always been online, so won't be able to give a valid representation as to whether it was or wasn't online before. How much value is there in knowing that an event has "moved online", is the key question here? Who would be interested to know that it was once offline? What would the user experience be for this? |
Leaving aside the user-experience for this, I think there are in fact two points that would be useful.
To accommodate this we'd need to associate the eventStatus with a Date or Schedule. |
Noting that this property would need to live at |
Relevant points from the summary of the W3C call on 25 March 2020:
|
Updated proposal
Additionally when Example
|
@nickevansuk sorry it's taken me so long to spot this but my actual intention was that Could it just mean "affiliated location"? Even if the session has always been virtual, but wants to associate itself with some borough/town/city so that it can participate in some local campaign, it could do this with the If so, then there are two reasons to have this as a separate field from
Otherwise, we should call the field Admittedly, there is a problem with this proposal:
My hunch is that this should be fine. For example, try getting the latitude / longitude for "Bath, UK" here: https://opencagedata.com/demo. It returns |
Great feedback @lukehesluke, and agree with relaxing the constraints for the However luckily this exact issue is already being addressed for The more general Have updated the description of the beta field to "The physical location affiliated with the virtual event, for example the original location of the event before it was moved online." to hopefully capture this more fully. Further feedback welcome! |
Great! Thanks @nickevansuk - makes lots of sense! |
This proposal has been added to the Beta namespace as follows:
|
Proposer
@nickevansuk (imin/ODI), seconded by @thill-odi (ODI)
Use Case
An event organiser needs to indicate that an event previously scheduled for physical participation now has an online option available, or is only available online.
Why is this not covered by existing properties?
This property only becomes relevant with the addition of
virtualLocation
to the specification (see issue #224).In addition, this property was only recently added to
pending
in the schema.org vocabulary.Please provide a link to example data
See e.g. https://www.cococollective.co.uk/booking/ for a yoga studio that has recently moved to online events to replace physical ones.
Proposal
In addition to the values currently defined as valid for
eventStatus
, the valueEventMovedOnline
should be included.The text was updated successfully, but these errors were encountered: