Difference between revisions of "Resource"
Line 35: | Line 35: | ||
* DAOs know how to perform secure onchain operations | * DAOs know how to perform secure onchain operations | ||
− | A sea of material resources accessible by free agents in dynamic processes. | + | A sea of material resources accessible by free agents in dynamic processes. Material assets need to be: |
− | |||
* organization agnostic and capture resistent | * organization agnostic and capture resistent | ||
* allowing various property regimes, including nondominium (no one owns but everyone has access under certain rules) | * allowing various property regimes, including nondominium (no one owns but everyone has access under certain rules) | ||
Line 49: | Line 48: | ||
* able to interact with processes, in events like: create, comsume, use, contribute with) | * able to interact with processes, in events like: create, comsume, use, contribute with) | ||
** processes need to be organization agnostic as well | ** processes need to be organization agnostic as well | ||
− | |||
− | |||
=See also= | =See also= |
Revision as of 00:32, 9 November 2023
Resources (or assets) are things that agents can create, use, consume, exchange, share, cite... They are inputs and outputs to processes. Their flows through processes are recorded as economic events (using the REA language), and are traced by NRP-CAS.
Resources are treated as primitives in the REA ontology, which is used to model the economic of OVNs.
When we apply access rules to a resource, or pout in under a given property regime, we talk about assets.
See Resource Type page for an in-dept characterization of resources.
Property regime
All resources are under some type of property regime. See more on property.
Governance of resources
Rules that govern access to resources for their consumption or use. They are related to property regime and the rights associated with them. These rules also dependent on the resource type. See more on Physical resource governance. See also Sensorica's governance document
Resources in the NRP-CAS
Resources are the primary building blocks of the NRP-CAS, which is based on the REA ontology (resources, events, agents). They are grouped into Resource Types within the NRP-CAS. Furthermore, resources are listed in an inventory in the NRP-CAS. See the Inventory page for more.
The idea in NRP-CAS is to decouple resources from venture or project and treat them as composable, independent building blocks across the network. The economic argument is to reduce costs to innovation and production by recycling and reusing resources, reducing idle time of resources (latent or unused capacity) and to increase potential by providing a large number of permutations for assembling resources into creative and productive activity.
In Sensorica we also talk about accent possible, proposed by Helene Finidori, which means a new thing that can be made by adding just a bit of work / effort on top of what already exists. In other words, using a combination of existing resources one can figure out a new use / function, thus increasing innovation potential.
This idea of decoupling Resources from organizational context can be take further with p2p infrastructures, making resources exist as independent building blocks on a global network. This is related to identity, individual profile and transaction. See work on Vallueflows and h-REA.
Resources and Blockchain
Representing material assets in the virtual space, in a way that is usable by open / permissionless networks.
- Use ricardian contracts -> see Matterium
- Sensorica knows how to steward material assets as an open network
- DAOs know how to perform secure onchain operations
A sea of material resources accessible by free agents in dynamic processes. Material assets need to be:
- organization agnostic and capture resistent
- allowing various property regimes, including nondominium (no one owns but everyone has access under certain rules)
- shearable by default
- location
- access control (credentials, governance)
- custody (responsability)
- maintenance (obligations)
- fully specified: function, architecture, standards (dimensions, tolerances, quality), …
- composable (aggregate into larger assets)
- able to interact with processes, in events like: create, comsume, use, contribute with)
- processes need to be organization agnostic as well
See also
External links
- On resource flows - Tibi
- What is the connection and difference between a Resource Type and a Resource?
- From material scarcity to artificial abundance – The case of FabLabs and 3D printing technologies; Primavera De Filippi, Peter Troxler
- How to think about Resources and Resource Types from the UDML perspective - see Ampie's doc
- Describing Resources and Systems by Greg Cassel]