- From: Leigh Dodds <leigh.dodds@theodi.org>
- Date: Fri, 29 Jun 2018 18:46:31 +0100
- To: public-openactive@w3.org
- Message-ID: <CAJsy4=Ow-jMckq2Wec9OHH=D21rD2nDu=83uG1g4EmaNk0_HyA@mail.gmail.com>
Hi, Over the past few months, with support from a number of members of the OpenActivity community, we've been making progress on the Booking API specification. The process so far has been: * early prototyping and rapid development of a specification, producing a 0.3 draft * revisions and review of the specification to explore additional requirements, producing a 0.4 draft Both of these have been google docs to facilitate rapid feedback and edits. Based on that we've learned from those exercises we've now created a more formal Editors Draft of the booking API. Version 0.5 of the API can be found here: https://www.openactive.io/open-booking-api/EditorsDraft/index.html The project board for ongoing development can be found here: https://github.com/openactive/open-booking-api/projects/1 The plan is to now iterate on this spec using github issues, our regular community group calls and, hopefully, through continued prototyping and testing by the community. We think this specification is stable enough for people to explore implementations and want to actively encourage that to help us collect useful implementation feedback. If you implemented version 0.3 of the specification, or are planning some projects where booking is required, it would be helpful if you could consider moving to this specification and give feedback on any potential issues. As always we need to give the caveat that details will change, but we've had a lot of good feedback on it so far. Don't get caught up on the version numbering, its more of a progress indicator than a sense of how much we need to do to get to 1.0. My feeling is that we're actually close to completing a version 1.0 that will support booking of Events based on our original set of requirements. Now that we have facilities in the modelling specification we'll able to quickly implement booking support for those too. Cheers, L. -- Leigh Dodds, Data Infrastructure Programme Lead, theodi.org @ldodds The ODI, 65 Clifton Street, London EC2A 4JE
Received on Friday, 29 June 2018 17:46:57 UTC