Open nickevansuk opened 6 years ago
Further Proposal given https://github.com/openactive/modelling-opportunity-data/issues/98#issuecomment-421012557, https://github.com/openactive/modelling-opportunity-data/issues/161, https://github.com/openactive/modelling-opportunity-data/issues/160 - separating channels from payment methods
Suggest we add https://schema.org/acceptedPaymentMethod
to the OpenActive profile, with the following specifically recognised values, but with the option to use others from http://purl.org/goodrelations/v1 (including CheckInAdvance - American spelling of Cheque).
We should specify that in the OpenActive context acceptedPaymentMethod specifically relates to payment available at the Event (e.g. "cash on the door") rather than prepayment.
Note that the above use of acceptedPaymentMethod is already implemented in Open Sessions and EMD in this way.
acceptedPaymentMethod
MUST NOT be set if "prepayment": "https://openactive.io/Required"
acceptedPaymentMethod
MUST be set if "prepayment": "https://openactive.io/None"
Agree on updated proposal: that acceptedPaymentMethod specifically relates to payment available at the Event (e.g. "cash on the door") rather than prepayment
Proposer
EMD, Open Sessions, O2 Touch Rugby
Use Case
As a potential participant, I want to know what payment options are available for the session.
Why is this not covered by existing properties?
acceptedPaymentMethod exists in schema.org, but has not been well-defined for this usecase.
Example data
The following are defined by EMD:
Proposal
Add
acceptedPaymentMethod
to the OpenActive profile, and define additionalPaymentMethod
s to cover the options above (where they are not already defined by goodrelations).