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

BookingService #147

Open
nickevansuk opened this issue Sep 5, 2018 · 0 comments
Open

BookingService #147

nickevansuk opened this issue Sep 5, 2018 · 0 comments
Labels
attn-chair proposal Proposed changes to the specification

Comments

@nickevansuk
Copy link
Contributor

Proposer

ODI / Google Reserve

Use Case

Allow booking systems to include details about themselves in feeds, to provide additional brand exposure and information for data consumers.

Why is this not covered by existing properties?

The organizer property is for the organiser of the event rather than the system providing the booking service.

Proposal

Define a new type BookingService which subclasses WebAPI, and a new property bookingService on Event to reference it.

Note organisations can and do use more than one BookingService, so the BookingService must be specified per Event.

Example

  "bookingService": {
    "type": "BookingService",
    "name": "Plus 2",
    "url": "https://www.gladstonesoftware.co.uk/multi-sites",
    "documentation": "https://api.gladstonesoftware.co.uk",
    "provider": {
      "type": "Organization",
      "name": "Gladstone MRM Ltd",
      "url": "https://www.gladstonesoftware.co.uk/",
    }
    "termsOfService": { "type": "TermsOfService", "url": "url", "content": "text" }
  }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn-chair proposal Proposed changes to the specification
Projects
Development

No branches or pull requests

1 participant