-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
define Claim #22
Comments
claims play role only in cases of exchange, never in just transfer scenarios (gitter chat)
|
based on food networks case discussed in https://github.com/valueflows/resource/issues/14#issuecomment-217022939 When farmers 'sell' crops before they harvest them, they make commitment. When person who 'purchases' the crops makes reciprocal vf:Transfer, this commitment becomes a claim. |
Thinking about Claim vs. Commitment. It seems that Claim has aspect of debt, which changes "You have promised me 5kg of apples" (Commitment) into "You owe me 5kg of apples" (Claim) |
If we have situation with a claim for particular resource, for example a bicycle which we can identify with an IRI. I don't see clear difference between having a Claim and having ownership rights over that bike. It seems that once we have a Claim in place it can automatically turn into ownership rights. Once again physical location of the bike doesn't matter, it can for example always stay parked in shared bikeshed which both of agents, involved in the trasfer of ownership over that bike, use. This bikeshed also don't have parking places assigned to a person and one just puts a bike in any of available slots. |
That, I think, is the position of Pavel Hruby and Christian Scheller in this email thread: From me to Pavel:
From Pavel to me:
|
We have moved the ValueFlows organization from GitHub to https://lab.allmende.io/valueflows. This issue has been closed here, and all further discussion on this issue can be done at If you have not done so, you are very welcome to register at https://lab.allmende.io and join the ValueFlows organization there. |
similar to #21 based on #14 (comment)
The text was updated successfully, but these errors were encountered: