Service Oriented Network

First of all, this needs a better name.

Components

• Users
• Local Identity Server
• Remote Identity Server
• Data and Application Servers
• Repositories
• Reputation
• Arbitration

Users

The end users of the system.

Local Identity Server

This is a small server that sits on the local machine and manages the master keyring.

Remote Identity Server

This is a server that manages valet keyrings for many users. The RIS is the concierge - its single objective is to make interacting with the network easier on users. The RIS is responsible for billing and 'always on' services.

Data and Application Servers

DA servers do the heavy lifting. They store user data and run applications.

Repositories

Repos store code. Developers put their code in a public repo and a DA server can launch it as a service. The DA is responsible for paying the developer.

Reputation

Every component of the system can review every other part of the system. If servers (ID or DA) are engaging in shady behavior, it will effect their reputation. Possibly most important, repositories can be reviewed and endorsed. These reviews can be paid, but payment must be disclosed. The idea is a sort of agency - some individuals can build a reputation reviewing repos, even users who don't understand code can learn to trust these reviews or at least the aggregate of the reviews. Hopefully, the best of these agents will be paid by the ID&DA servers so there is no conflict of interest, though I would also like to see developers pay into a pool.

Arbitration

The protect copyright and enforce payment, arbitration can be called in. This process is meant to be very open. Arbitration can be administered by many people (a jury). Particularly for copyright, it is meant to represent the aggregate position of the network rather than any hard and fast rules. The line between fair use, imitation, parody and infraction is hard to separate, so rather than trying to do so with rigor, we do so by the majority of opinion.

Convention

• Encrypt user data
• Service and Ads should be seperate
• A la carte
• Expire copyrights in reasonable time

Structures

This are structures I hope or suggest. I'm sure others will arise and that some of these will prove infeasible or inferior to others I have not considered. These are simply meant as a starting point.

Agency Pools

Pools of agents, formed into an organization to review services and repos. The funding for these pools should be public and diverse to avoid conflicts of interest.

Developer Investments

Individuals or groups can invest in developer projects and get a cut of any profits they may make.