Per #677 - Update definition for Act of Funding#744
Closed
Conversation
APCox
requested changes
Sep 16, 2025
Contributor
APCox
left a comment
APCox
left a comment
There was a problem hiding this comment.
These changes need to be made to the Artifact Ontology (not the merged file).
Since the provider (funder) gets to make stipulations on how their funds are used, the focus should be on the funder's interest. Perhaps:
"An Act of Financial Instrument Use in which an Agent (the Funder) provides some Financial Instrument to another Agent (the Fundee) as a resource pool that is earmarked by the Funder for a future transaction."
APCox
added
the
Reviewed by CCO WG
Contributor
|
This has been addressed by PR #749 and is therefore being closed without merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added an updated definition for Act of Funding based on issue #677 and the CCO sprint meeting from last month where this was discussed.