Reduce Duplicate Effort on Lower Level Fundamentals

This is a verbatim copy of the document 'Reduce duplicate effort on lower level fundamentals' created by participants in the Collaborative Technology Alliance: https://cta.hackpad.com/Reduce-duplicate-effort-on-lower-level-fundamentals-cOydIAOSdFP

"Reduce duplicate effort on lower level fundamentals

What lower level functionalities do we need again and again, across the many different apps?

   Sign in - user verification

   Data persistence

   permissions to do things within groups

   taxonomy

   version control

   ratings and a way to make posts more prominent

   comments

   custom forms / surveys

   personas and the ability to channel content.

   social graphs

   offer-acceptance protocols for agreeing on intents (offers and wants) between different people using different apps, fulfilling agreements, and evaluating results (interactive explanation: http://conversationsforaction.com/cfa-playground)

What are the ways that we could approach reducing the duplication of efforts in these different areas?

Sign In - User verification

   have a single sign on system

   have each person operate in all contexts from their own agent app (part of the original Open Apps Ecosystem vision, according to some participants)...

Data persistence

   use a decentralized database system such as the blockchain

   use the linked open data approach (which is compatible with any of the other approaches)

   Work is going on (slowly) toward this approach in the https://valueflo.ws/ project which others could join and speed the plow.

   use a centralized graph database with a flexible schema and a fantastic api

   write code libraries that handle a bunch of the heavy lifting of data persistence using one of these methods

   down the road... CEPTR?"