├── DWebSummit ├── DecentralizedWeb20160607pt1_0487.jpg ├── DecentralizedWeb20160607pt1_0488.jpg ├── DecentralizedWeb20160607pt3_0055.jpg ├── IMG_4530.JPG ├── IMG_4531.JPG ├── IMG_4533.JPG ├── IMG_4616-2.JPG └── InteroperabilityBreakoutGroup ├── LICENSE └── README.md /DWebSummit/DecentralizedWeb20160607pt1_0487.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/DecentralizedWeb20160607pt1_0487.jpg -------------------------------------------------------------------------------- /DWebSummit/DecentralizedWeb20160607pt1_0488.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/DecentralizedWeb20160607pt1_0488.jpg -------------------------------------------------------------------------------- /DWebSummit/DecentralizedWeb20160607pt3_0055.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/DecentralizedWeb20160607pt3_0055.jpg -------------------------------------------------------------------------------- /DWebSummit/IMG_4530.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/IMG_4530.JPG -------------------------------------------------------------------------------- /DWebSummit/IMG_4531.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/IMG_4531.JPG -------------------------------------------------------------------------------- /DWebSummit/IMG_4533.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/IMG_4533.JPG -------------------------------------------------------------------------------- /DWebSummit/IMG_4616-2.JPG: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/d-w3c/dsm/719f35de730adab4c24336797cdfb27bd97048c6/DWebSummit/IMG_4616-2.JPG -------------------------------------------------------------------------------- /DWebSummit/InteroperabilityBreakoutGroup: -------------------------------------------------------------------------------- 1 | The DSM paper is an action-item that emerged from the #DWebSummit 2016 (http://decentralizedweb.net) Interoperability break-out session. 2 | 3 | The group had 45 minutes to discuss "The Decentralized Web & Interoperability". Since there are so many layers and starting points for this broad topic we decided to simply take a few minutes for each participant to describe their decentralization technology. We had representatives from IPFS, LibP2P, Solid (SirTBL reprezenting), Mediachain, Matrix, WebTorrents, CertBot, Interledger, as well as Cory Doctorow with interest in licensing & rights management, and Peter Van Garderen with interest in information provenance/authenticity and archival permanence. 4 | 5 | Each project participant was asked to think how they could leverage solutions from the projects around the table. We drew a dependency diagram on the whiteboard. We were pleasantly surprised to see how complimentary many of the projects were. [insert whiteboard photo] 6 | 7 | The participants' short project descriptions were captured on whiteboard as draft functional requirement statements. [insert whiteboard photo] These can be grouped under functional components from which interoperability requirements could be mapped. 8 | 9 | We briefly considered using the Open Systems Interconnection (OSI) model as a reference point but decided that its categories were too vague. We made a rough mapping to: "PIPE" layer => Transport layer => Application layer. We also decided that any corresponding layers weren't necessarily hierarchically-organized in the Decentralized system stack. We decided to refer to "domains" instead of "layers". 10 | 11 | This resulted in the following short-list: 12 | 13 | APPLICATION domain 14 | user interface 15 | identity 16 | authentication 17 | immutable consensus (see blockchain) 18 | PKI Interoperability 19 | rights/licensing 20 | metadata/context/provenance 21 | 22 | TRANSPORT domain 23 | P2P storage 24 | P2P networking (e.g. peer discovery) 25 | Storage incentivization/compensation 26 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | CC0 1.0 Universal 2 | 3 | Statement of Purpose 4 | 5 | The laws of most jurisdictions throughout the world automatically confer 6 | exclusive Copyright and Related Rights (defined below) upon the creator and 7 | subsequent owner(s) (each and all, an "owner") of an original work of 8 | authorship and/or a database (each, a "Work"). 9 | 10 | Certain owners wish to permanently relinquish those rights to a Work for the 11 | purpose of contributing to a commons of creative, cultural and scientific 12 | works ("Commons") that the public can reliably and without fear of later 13 | claims of infringement build upon, modify, incorporate in other works, reuse 14 | and redistribute as freely as possible in any form whatsoever and for any 15 | purposes, including without limitation commercial purposes. These owners may 16 | contribute to the Commons to promote the ideal of a free culture and the 17 | further production of creative, cultural and scientific works, or to gain 18 | reputation or greater distribution for their Work in part through the use and 19 | efforts of others. 20 | 21 | For these and/or other purposes and motivations, and without any expectation 22 | of additional consideration or compensation, the person associating CC0 with a 23 | Work (the "Affirmer"), to the extent that he or she is an owner of Copyright 24 | and Related Rights in the Work, voluntarily elects to apply CC0 to the Work 25 | and publicly distribute the Work under its terms, with knowledge of his or her 26 | Copyright and Related Rights in the Work and the meaning and intended legal 27 | effect of CC0 on those rights. 28 | 29 | 1. Copyright and Related Rights. A Work made available under CC0 may be 30 | protected by copyright and related or neighboring rights ("Copyright and 31 | Related Rights"). Copyright and Related Rights include, but are not limited 32 | to, the following: 33 | 34 | i. the right to reproduce, adapt, distribute, perform, display, communicate, 35 | and translate a Work; 36 | 37 | ii. moral rights retained by the original author(s) and/or performer(s); 38 | 39 | iii. publicity and privacy rights pertaining to a person's image or likeness 40 | depicted in a Work; 41 | 42 | iv. rights protecting against unfair competition in regards to a Work, 43 | subject to the limitations in paragraph 4(a), below; 44 | 45 | v. rights protecting the extraction, dissemination, use and reuse of data in 46 | a Work; 47 | 48 | vi. database rights (such as those arising under Directive 96/9/EC of the 49 | European Parliament and of the Council of 11 March 1996 on the legal 50 | protection of databases, and under any national implementation thereof, 51 | including any amended or successor version of such directive); and 52 | 53 | vii. other similar, equivalent or corresponding rights throughout the world 54 | based on applicable law or treaty, and any national implementations thereof. 55 | 56 | 2. Waiver. To the greatest extent permitted by, but not in contravention of, 57 | applicable law, Affirmer hereby overtly, fully, permanently, irrevocably and 58 | unconditionally waives, abandons, and surrenders all of Affirmer's Copyright 59 | and Related Rights and associated claims and causes of action, whether now 60 | known or unknown (including existing as well as future claims and causes of 61 | action), in the Work (i) in all territories worldwide, (ii) for the maximum 62 | duration provided by applicable law or treaty (including future time 63 | extensions), (iii) in any current or future medium and for any number of 64 | copies, and (iv) for any purpose whatsoever, including without limitation 65 | commercial, advertising or promotional purposes (the "Waiver"). Affirmer makes 66 | the Waiver for the benefit of each member of the public at large and to the 67 | detriment of Affirmer's heirs and successors, fully intending that such Waiver 68 | shall not be subject to revocation, rescission, cancellation, termination, or 69 | any other legal or equitable action to disrupt the quiet enjoyment of the Work 70 | by the public as contemplated by Affirmer's express Statement of Purpose. 71 | 72 | 3. Public License Fallback. Should any part of the Waiver for any reason be 73 | judged legally invalid or ineffective under applicable law, then the Waiver 74 | shall be preserved to the maximum extent permitted taking into account 75 | Affirmer's express Statement of Purpose. In addition, to the extent the Waiver 76 | is so judged Affirmer hereby grants to each affected person a royalty-free, 77 | non transferable, non sublicensable, non exclusive, irrevocable and 78 | unconditional license to exercise Affirmer's Copyright and Related Rights in 79 | the Work (i) in all territories worldwide, (ii) for the maximum duration 80 | provided by applicable law or treaty (including future time extensions), (iii) 81 | in any current or future medium and for any number of copies, and (iv) for any 82 | purpose whatsoever, including without limitation commercial, advertising or 83 | promotional purposes (the "License"). The License shall be deemed effective as 84 | of the date CC0 was applied by Affirmer to the Work. Should any part of the 85 | License for any reason be judged legally invalid or ineffective under 86 | applicable law, such partial invalidity or ineffectiveness shall not 87 | invalidate the remainder of the License, and in such case Affirmer hereby 88 | affirms that he or she will not (i) exercise any of his or her remaining 89 | Copyright and Related Rights in the Work or (ii) assert any associated claims 90 | and causes of action with respect to the Work, in either case contrary to 91 | Affirmer's express Statement of Purpose. 92 | 93 | 4. Limitations and Disclaimers. 94 | 95 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 96 | surrendered, licensed or otherwise affected by this document. 97 | 98 | b. Affirmer offers the Work as-is and makes no representations or warranties 99 | of any kind concerning the Work, express, implied, statutory or otherwise, 100 | including without limitation warranties of title, merchantability, fitness 101 | for a particular purpose, non infringement, or the absence of latent or 102 | other defects, accuracy, or the present or absence of errors, whether or not 103 | discoverable, all to the greatest extent permissible under applicable law. 104 | 105 | c. Affirmer disclaims responsibility for clearing rights of other persons 106 | that may apply to the Work or any use thereof, including without limitation 107 | any person's Copyright and Related Rights in the Work. Further, Affirmer 108 | disclaims responsibility for obtaining any necessary consents, permissions 109 | or other rights required for any use of the Work. 110 | 111 | d. Affirmer understands and acknowledges that Creative Commons is not a 112 | party to this document and has no duty or obligation with respect to this 113 | CC0 or use of the Work. 114 | 115 | For more information, please see 116 | 117 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # DSM: The Decentralized Systems Map 2 | 3 | ## Abstract 4 | 5 | This paper reviews the various technologies which make up the 6 | decentralized web movement and classifies them in terms of their 7 | responsibilities within an OSI-style conceptual model called DSM: the 8 | Decentralized Systems Map. 9 | 10 | 11 | The desired outcome of this paper is six-fold. (1) To promote 12 | collaboration, cooperation, and mutual-understanding between those 13 | parties creating decentralized web technologies, (2) to clarify the 14 | purpose, statuses, and relationships of decentralized web 15 | technologies, (3) to better inform and educate the general public, (4) 16 | to obtain a more hollistic understanding of which necessary 17 | decentralization components are present and which are missing, (5) to 18 | conduct a meta experiment of producing a decentralized, reproducible 19 | research document and, above all (6) bringing the decentralized web 20 | movement closer to solidarity and to becoming an official w3c working 21 | group. 22 | 23 | ## Technologies 24 | 25 | IPFS, Dat, StrongLink, MediaChain, WebTorrents, BitTorent, Bitcoin, Solid 26 | --------------------------------------------------------------------------------