-
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
Places feed #307
Comments
|
Updates to the model and validator have been made to support the above, given consensus on the W3C call on 16 February 2022. |
Additionally, note that an example is available for guidance within the validator. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposer
W3C call on 16 February 2022, and subsequently OpenPlay
Use Case
A separate feed for
Place
s would significantly reduce the volume of data in the other feeds, and also ensure thatPlace
s that do not have any upcoming sessions or slots are still available to data users.Proposal
Model changes required to facilitate this are as follows:
location
property to be an@id
reference to another feedserviceOperator
property on thePlace
type to reference the Seller - as thePlace
may not necessarily have any sessions or slots associated with it, so this data may not be included elsewhere.Additional documentation updates are required to make the guidance clear around the use of these feeds..
The text was updated successfully, but these errors were encountered: