Implement Bookings

[hammar]

A request from Akademiska Hus, mirrored by @PeteHart: we need a way of representing room bookings in REC. Possibly the Lease semantics could be reused or extended. Approximate time-frame version 3.3, this autumn. A modeling workshop ought to include the above mentioned + any other interested stakeholders.

[hammar]

Putting this on REC TC agenda for October meeting.

[PeteHart]

Reflection: In applications for properties much more than rooms are bookable; I've for instance seen paddle courts and bicycles in the coworking domain, and barbeques in the multi dwelling domain. So having bookables and the representation of a specific booking appears to be a broader scope than just property related bookables (eg rooms). Wonder if other ontologies for bookings exist. Will check...

[hammar]

Per REC TC call 7 november: this is a post REC4 GA feature. Keeping it on the list, to be revisited at later date.

[baardl]

Hi. At NMBU we need "Bookable Resource" and Bookings.
Our thought might be that Bookable Resouce could have been a derivation of Lease Contract. Unforteneately the Tennant requirement will obstruct, or confuse the use-case. A more accurate term would similate to Sensor, or Actuator as these logigally linkes to Space or Equipment.
Bookings might be something like Observations. A Booking is a concrete instance, that might better fit in a database, rather than a graph. This is due to the large number of writes and reads to Booking. Whereas the graph for Bookable Resource will change more seldom.

@hammar or @erikoskarwallin do you have any thoughts or directions? We will of course create PR on our changes, if wanted.