Closed ahdinosaur closed 5 years ago
while subclassing was mentioned before, i'm wondering if traits would be a more appropriate pattern. each trait would describe the behavior, and each resource type could have many such traits. may or may not be related to #2, idk.
Traits are an interesting idea. They seem also related to faceted classification. I first ran into them in Smalltalk, which was the language of the original version of what has now evolved into NRP and now wants to evolve into a web of LOD. But I never actually used them, just heard other Smalltalk programmers talk about them.
Do you see modeling of Port(Input/Output) somehow similar to modeling of Intent(Want/Offer)? https://github.com/valueflows/valueflows/issues/62 :mag:
@elf-pavlik - similar but at a previous stage of evolution. Here's a fairly typical outline of the evolution:
Offer and Want are on the top Propose Idea row. Input and Output are on or close to the Commit or Fulfill row, depending on whether they have happened or not.
For example, the Mutual Aid Network wants to advertise needs for projects (skills, materials, money, etc). Those are Wants, but they would be stated fairly specifically. If somebody offers a match, they will evolve to the Commit stage, where the doer and the timing may become known.
People who post on their marketplace often Want something much more vague, defined only by text, or text and a category or two and maybe a tag. Those Wants will either evolve through the funnel, or not. And if they do, they will become increasingly clearly defined.
Thanks @bhaugen for sharing your insights!
Do you think that we could find certain degree of isomorphism between
And see them as Qualified Relations?
Similar as with roles and verbs currently it seems to me that
direct: Agent - wants -> Resource qualified: Agent <- subject - Want - object -> Resource ( relationship/property: wants )
direct: Process - takes -> Resource qualified: Process <- subject - Input - object -> Resource (relationship/property: takes )
direct: Agent - offers -> Resource qualified: Agent <- subject - Offer - object -> Resource ( relationship/property: offers )
direct: Process - yields -> Resource qualified: Process <- subject - Output - object -> Resource (relationship/property: yields )
@elf-pavlik - glad you are taking the evening off :relieved:. I will comment on this tomorrow some time, after I study your recent diagrams and examples.
another list in the wild at https://github.com/elf-pavlik/currency/issues/3#issuecomment-217310310:
equipment "consumables" work, skills, factors of human labor liquids, powders, etc vs discrete pieces like nuts and bolts ideas, designs, citables
also related to the recent conversation about monetary currencies being resource types with pecularities
@ahdinosaur thank you for your recent curation efforts. They help.
harvested from https://github.com/valueflows/valueflows/issues/10.