HackMD
Design, Product, Service - VF support
Jan 19, 2023
What is a Product, Service, Design?
In other words, what is a "Project"? What I understand, please correct as needed.
Projects get entered after they are complete. They are not planned in the software. After they are complete, they can be edited, they can be related in another project.
The resource created (design, product) might be consumed in another project, might be transferred to an agent outside the network, etc. So, I don't think the Project is the resource. Unless the Project disappears from the UI in all ways after it leaves the network. But even so, that doesn't seem right; VF doesn't keep the resource at all stages of existence, there is just one, with derived data. And services don't have a resource, but it would be preferable to treat them the same way since they are all "projects".
In VF, the planning layer has a similar concept that encapsulates everything planned (and done) to produce a resource or deliver a service. Or multiple related resources/services. The Project seems like a similar concept, but it was never planned, and the doing is all entered after the fact.
VF could create a similar concept for just the observation layer. Or possibly just use vf:Plan, which already knows all the processes in it, so VF would work as is, with slightly confusing semantics.
Or possibly we could look for produce and deliverService events and consider them the key into a project. (You need to find a project to relate it as an input to another project; and to edit it.)
I lean towards vf:Plan, because if you did do planning, that is what you would use for the Project, and eventually when it was done, the observation layer stuff would connect into that already. And it is one table to search in. It is the right concept, just in the wrong layer. Possibly we would need to add the vf:independentDemandOf against an event, if there would be multiple produce events in the flow sequence.
However, when picking "Relations" in the UI, I think that needs to be an EconomicResource for product or design, and the deliverService event for the service. Or if it needs to be the Project (which is fine), the relationship between Projects won't be stored, that will be a new event in the case of designs and products referencing the resource; and update of the existing deliverService event in case of a service.
Questions:
- What can be edited on a project?
- Do you want to think of a project as one process? Or do you want to be able to represent multiple processes feeding into one another until the final assembly? Like the steps in the maker documentation
