PCT-Webizen-Notes

I've copied an old outdated version of the PCT notes, that had some webizen notes in it also; and have then deleted most of the content; other than the few notes left in this folder, which have some relevance; but are more than likely going to be either changed or removed.

Overall, sense, is being designed to became a vital part of the PCT & Webizen ecosystems.

Some legacy information provides an overview both in the contained docs as well as via the summary provided below. For more information see the Webizen Dev Docs.

Design Principals

1. Its got to be decentralised.
2. It must use Linked-Data (semantic web) related methods.
3. There is no single protocol that can support all usecases; nor is any single decentralised protocol able to be considered reliably safe forever. The protocol is about the carriage of information, not ownership of the information.
4. Legal Entities are defined as responsible parties for content; not things / software.
5. Any transaction should consider the cost incurred by the transaction; particularly in-terms of the amount of energy required to perform the transaction and/or populate availability.
6. No transaction should be considered to have less value than the cost of biosphere and sociosphere related caculations associated to the ability to make an information transaction; yet the creator is able to define the terms that outline how non-energy related costs are sought to be caculated via the network. (note; this requires ontologies, etc.)

General Requirements

5. There needs to be a way to cryptographically sign a document to make it tamper-evident; whilst including the information about the resource location of that document.

6. There needs to be a way to require multiple signatures for documents that have that requirement (ie: a vote in parliament).

7. There needs to be a way to run an agent, that is able to process requests from various protocols.

8. The unique identifier for a content asset that is the same as other copies of that artifact stored on other and/or across multiple protocols must be the same.

   The client shouldn't really care which protocol it gets a specified record from, so long as the specified record has the same data.

9. If a content artifact is different then it must have a different identifier.

10. If a content record relates to a series, then it should have a reference to the previous version and/or an index that provides information about all records in that series.

    For example; legislation changes, so an updated document reflecting new changes should be made, and in-turn reference both or either the previous version or the index for the document series.

11. Every participating node should have a capacity to support currencies. Whilst users may well define costs that results in a premium cost for obtaining information from that node - which would have the consequence of the network not making use of that node - unless they wanted to pay the premium.