Create Holo-REA system design guidelines / tutorial

[pospi]

We'll eventually need something like the setup and configuration tutorials @fosterlynn did for NRP:

• https://speakerdeck.com/mikorizal/configuring-nrp
• https://speakerdeck.com/mikorizal/2-nrp-organization-setup-tutorial
• https://speakerdeck.com/mikorizal/3-nrp-resource-type-setup-concepts-and-tutorial
• https://speakerdeck.com/mikorizal/4-nrp-exchange-types-concepts-and-tutorial
• https://speakerdeck.com/mikorizal/5-nrp-recipe-concepts-and-tutorial

For now, it's about answering the high-level questions needed to share an REA-based economic network together; namely these things minus the last few: https://speakerdeck.com/mikorizal/configuring-nrp?slide=2

It is these decisions around shared ontologies which will ultimately define where the boundaries of an economic network lie. This makes sense- you can only communicate with others if you're speaking the same language. So I imagine it like this:

• HoloREA is a network of related HoloREA networks
• Each network may have one or more independent components: observation, planning, knowledge etc
• Each network may be bound to several other related networks via bridging, and may choose to broadcast entries "through the boundary" to neighboring networks in order to share information
• Some of these networks will be "marketplace" networks, which will act as classification aggregators and translators that enable resources & processes from neighboring networks to be made compatible for trade
• Each network will be independently connected (strongly or weakly) to one or more external ontology networks (whether Holochain refs or web2.0 URLs), and these shared ontologies will influence which agents are willing / interested in participating in the network

Thus, the first design steps for a group considering collaborating via REA accounting should be choosing ontologies and modelling resource/process flows; and it would be amazing to have some words to guide others through this in the wiki (:

[pospi]

One goal for me here is to educate people about classifications and the semantic web and provide them with the tools they need to do a really good job of selecting a common vocabulary.

[fosterlynn]

One goal for me here is to educate people about classifications and the semantic web and provide them with the tools they need to do a really good job of selecting a common vocabulary.

Ping @elf-pavlik who has the most experience in this area.

[pospi]

Will share thoughts here as they come out of consulting experiences. An important guideline to mention is that not everything in an app needs to be represented in ValueFlows, which is where some modelling falls down. Important to note that the intention is for VF to be part of an application, and there will be things going on outside of the economic interactions which need to be considered and interplay with VF, but need not be represented as VF.