Considering a Recipe class?
Should we consider adding a class to represent a Recipe? It is not required probably, but might give some advantages.
Pros:
- If we allow a Recipe to specify which recipe processes it contains, then people can create a self-contained recipe that doesn't require a choice at planning time for every process encountered in the value flow, which process to use that creates the same output, or make vs buy decisions. If we are in a situation of finding recipes on the web, that could get overwhelming.
- It could even include multiple recipe processes/transfers so an interface could present a more controlled choice
- It could have informative notes.
- It could explicitly define that it is a fork or gr:isVariantOf another recipe.
Cons:
- One more thing to define, and it is not strictly needed because you can already trace back from a ResourceClassification to find all possible recipe processes (or recipe agreements for transfer sourcing) that create or transfer the resource classification you need.
Other pros or cons?