Pass/Fail and States
This is related to https://github.com/valueflows/valueflows/issues/603 but I think involves a different decision point. That one is about how to define measurement and test events themselves; this is to reconsider how to define the implications of measurements and tests in terms of economic events and economic resources.
Noting that we currently have pass
and fail
actions, which become the state of the resource referenced by the event. And noting that we have an active use case of a beef supply chain which includes longish transportation and various quality or validity tests, some of which go beyond pass or fail. For example, various tolerances of temperature readings may not "fail" the resource, but change the expiration date, which changes the price (and possibly the product, but that is part of this discussion, and we don't have full details on how they look at it).
So some questions:
- What actions do we want?
- Do we want states, and if so how and by whom are they defined?
- What are the increment/decrement processing rules for something that fails or tests not optimal in some way?
- What causes a new resource?
- What causes a new resource specification?