I was thinking about a bunch of systems that I need for different contexts I am in and I came to a thought that many of my needs can be abstracted to somthing like a ticket.
With a Ticket I mean an entry that has a description of an agreement, with a Timeslot when it is to take place and a possible payment
Examples of where this would be needed:
- orders of many kinds, for instance food orders in a Cloud Kitchen app
- Delivery Package Details, “a package going to X adress, at Y time, for this Z payment”
- Tickets for an event, course, festival whatever (description, time of event, payment)
- Timeslot at a washroom machine in the apartment building
So what I was wondering is, does it make sense to build this as a module, or is this something that is simply implemented by calling HoloREA straight since this is kind of what it is for (resources, events, agents) agreements and all that.
Still feel like I’d love to see an example of how this kind of implementation of REA might work. Does this make sense? Is it useful to make a module like this outside of REA? @pospi @guillemcordoba any thoughts?