vf-graphql merge requestshttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests2024-02-21T16:30:38Zhttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/118Draft: Add all exchange reciprocals, exchange groupings2024-02-21T16:30:38ZLynn FosterDraft: Add all exchange reciprocals, exchange groupingsRemoved ProposedIntent, added reciprocal relationship instead. Should the bridging file exist any more?
Added other reciprocals to match: Agreement to Commitment, Agreement to EconomicEvent, RecipeExchange to RecipeFlow.
Added `purpos...Removed ProposedIntent, added reciprocal relationship instead. Should the bridging file exist any more?
Added other reciprocals to match: Agreement to Commitment, Agreement to EconomicEvent, RecipeExchange to RecipeFlow.
Added `purpose` to Proposal, to make more clear and explicit offer/request (and maybe other things in the future). Didn't change the existing logic, if it is shown somewhere.
Added ProposedList as a grouping of Proposals. Didn't do the params.
Added AgreementBundle as a grouping of Agreements. Didn't do the params.
Note: I've also added some explicit inverses to VF, and am not sure how to fit them into the graphql. Noting also the graphql spec will support different modeling in technologies (which is why the inverses). Perhaps some discussion, unless you feel confident?
Usual note: Please check that things are where they should be, and complete as needed for the graphql processing, etc. Thanks!pospipospihttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/117Draft: Update Actions per VF changes2024-02-21T15:27:32ZLynn FosterDraft: Update Actions per VF changesA number of behaviors were added, everything we know needed to make the action resource and UI effects data driven (optionally). Also, the id's and label's may have changed. See https://www.valueflo.ws/concepts/actions/ for details. A...A number of behaviors were added, everything we know needed to make the action resource and UI effects data driven (optionally). Also, the id's and label's may have changed. See https://www.valueflo.ws/concepts/actions/ for details. And/or see https://lab.allmende.io/valueflows/valueflows/-/blob/master/mkdocs/docs/assets/all_vf.TTL#L1291 for all the actions with their behaviors.
As always, please check for everywhere these changes should go.pospipospihttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/115Feature/104 unit query api2023-05-02T01:55:10ZpospiFeature/104 unit query apiDefines an optional core schema for `measurement.filtering` which extends `Query.units` with a `filter` parameter.
The intention with the design of this input type is to require minimal bindings to the OM2 ontology in order to facilitat...Defines an optional core schema for `measurement.filtering` which extends `Query.units` with a `filter` parameter.
The intention with the design of this input type is to require minimal bindings to the OM2 ontology in order to facilitate simpler implementation and reduce integration complexity. But, I would like a review on the chosen parameters to ensure we don't feel as though any flexibility or additional possibilities are being forfeited.pospipospihttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/114Draft: Added corrects method on EconomicEvent2023-02-02T22:25:08ZLynn FosterDraft: Added corrects method on EconomicEventAdded a recursive from EconomicEvent to another EconomicEvent when the first event requires a correction or needs to be backed out completely. Negatives are allowed on quantities in this case.
This can also be used when a number of eve...Added a recursive from EconomicEvent to another EconomicEvent when the first event requires a correction or needs to be backed out completely. Negatives are allowed on quantities in this case.
This can also be used when a number of events need to be combined into one visually, such as in the time clock start/stop app.
NOTE: I added the property to the initial EconomicEvent definition, did not add anywhere else.https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/113Draft: Ecological agent (start of)2023-02-02T22:17:37ZLynn FosterDraft: Ecological agent (start of)Added EcologicalAgent, and updated some definitions. (We brought Agent and all subclasses into the VF namespace.)
NOTE: I only did the top part, not the mutations/etc.Added EcologicalAgent, and updated some definitions. (We brought Agent and all subclasses into the VF namespace.)
NOTE: I only did the top part, not the mutations/etc.https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/109Draft: Include all queries and add definitions2023-10-26T20:23:18ZLynn FosterDraft: Include all queries and add definitionsThis will include adding all the defined inverse and other queries from https://www.valueflo.ws/specification/inverses/#agent-also-subclasses-person-organization, and adding definitions for each.
@Connoropolous I pushed just Agent to st...This will include adding all the defined inverse and other queries from https://www.valueflo.ws/specification/inverses/#agent-also-subclasses-person-organization, and adding definitions for each.
@Connoropolous I pushed just Agent to start with. Please review and let me know if you want anything done differently, while I'm in the graphql.
@pospi if you catch this, your review from the general vf-graphql perspective would be great also. I'm maintaining what is there already in its existing format.https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/104Draft: Add resourceContainedIn2022-05-24T18:58:02ZLynn FosterDraft: Add resourceContainedInSee also !100 .
The MR adds a new property to EconomicEvent used with `combine` action to explicitly assign the `EconomicResource.containedIn`. See also https://lab.allmende.io/valueflows/valueflows/-/merge_requests/693/.
@srfsh @posp...See also !100 .
The MR adds a new property to EconomicEvent used with `combine` action to explicitly assign the `EconomicResource.containedIn`. See also https://lab.allmende.io/valueflows/valueflows/-/merge_requests/693/.
@srfsh @pospi any comments, does this make sense to you?
Also, please double check I did everything needed for this change.pospipospihttps://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/100Remove "conformsTo", "containedIn", and "currentLocation" of EconomicResource...2022-05-24T18:58:03Zsrfshallmende@havu.chRemove "conformsTo", "containedIn", and "currentLocation" of EconomicResource{Create,Update}Params`conformsTo` can be set by `EconomicEventCreateParams.resourceConformsTo` and
`containedIn` is supposed to be set only by assemble and separate (it will set it to
`null`).
Similarly, `currentLocation` can be set using `toLocation` with ...`conformsTo` can be set by `EconomicEventCreateParams.resourceConformsTo` and
`containedIn` is supposed to be set only by assemble and separate (it will set it to
`null`).
Similarly, `currentLocation` can be set using `toLocation` with `raise` and `produce` events.
While at it, I'd like to ask whether having `classifiedAs` of `EcononomicResourceUpdateParams` make sense?https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/98Draft: stage and state added where needed2022-02-11T14:33:26ZLynn FosterDraft: stage and state added where neededThis is the start of this MR. It included properties stage and stage added where needed on the class definitions: EconomicEvent, EconomicResource (just updated), Commitment, RecipeFlow.
It doesn't include anything on parameters.
Notes...This is the start of this MR. It included properties stage and stage added where needed on the class definitions: EconomicEvent, EconomicResource (just updated), Commitment, RecipeFlow.
It doesn't include anything on parameters.
Notes on implementing resolvers, which I'll also add to the [wiki app guidance](https://lab.allmende.io/valueflows/valueflows/-/wikis/Application-specification-guidance) soon:
* On EconomicEvent, a state is only valid on an output event, and should update the EconomicResource.
* When an EconomicEvent that is an output of a Process, and the Process has a basedOn (ProcessSpecification), and creates or updates an EconomicResource, it should always populate the stage on the resource with the ProcessSpecification referenced by the Process.
* On Commitment and RecipeFlow, stage and state are valid only on input flows, and mean "these are part of the logical identifier of the EconomicResource the flow will be looking for".https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/89added role bevavior2022-01-18T13:00:06ZLynn Fosteradded role bevavior@pospi please review! Not sure what you want to do with the enum, for example. I modeled it after action in terms of what to include. Anyhow, it would be good it you take a close look.@pospi please review! Not sure what you want to do with the enum, for example. I modeled it after action in terms of what to include. Anyhow, it would be good it you take a close look.https://lab.allmende.io/valueflows/vf-schemas/vf-graphql/-/merge_requests/76Feature/external specifications2020-04-27T06:06:25ZpospiFeature/external specificationsPushing this in response to https://github.com/valueflows/valueflows/pull/520
Mainly need to confirm that the logic for external specifications makes sense like this, or if we should have `ExternalProcessSpecification` and `ExternalRe...Pushing this in response to https://github.com/valueflows/valueflows/pull/520
Mainly need to confirm that the logic for external specifications makes sense like this, or if we should have `ExternalProcessSpecification` and `ExternalResourceSpecification` distinct from `ExternalSpecification`. I don't think it will make much difference to implementors - they will likely store the external URIs internally in a way that disambiguates whether they are process or resource specs simply by the records they are attached to.pospipospi