Intents - validations
This is to define the validations required for the first iteration of Intents (offers and requests). As previously defined:
- action is required
- provider or receiver is required
- (I don't think anything else is required, in combination or singly, in deference to the simplest implementations of intents, which are basically text)
Perhaps for CommonsPub the backend should conform to that; but UI or some other app-based piece can require more fields to allow more flexible for the various apps. Suggestions for the initial apps for intents:
- name required (only if no Proposal with a name)
- resourceClassifiedAs or resourceConformsTo required (although we may want to think more about this as we see how the taxonomies develop)
- resourceQuantity or effortQuantity or availableQuantity required (resource or available quantity is for items, effort is for work or usage -- and I'm not sure if we do want to actually require a quantity, let's explore the requirements a bit more too; but quantity will be needed to more accurately match or simulate potential flows)
- finished (would be good to initialize to false in the backend if not provided, which it wouldn't be on create)
- inScopeOf required for any app which has intents always in the context of a group (only if Proposal.inScopeOf not there)