-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathindex.html
1050 lines (1004 loc) · 34.1 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!DOCTYPE html>
<html>
<head>
<title>Decentralized Ratings & Reviews (DR) v0.1</title>
<meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline.
-->
<script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
<!--script src='./respec-w3c-common.js' class='remove'></script-->
<script src="./common.js"></script>
<script type="text/javascript" class="remove">
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "dr",
// subtitle
subtitle: "Data Model and Syntaxes for Decentralized Ratings & Reviews (DRs)",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
// previousPublishDate: "1977-03-15",
// previousMaturity: "WD",
// extend the bibliography entries
localBiblio: ccg.localBiblio,
github: "https://github.com/ChluNetwork/decentralized-Ratings & Reviews-spec",
includePermalinks: false,
// if there a publicly available Editor's Draft, this is the link
// edDraftURI: "https://github.com/ChluNetwork/decentralized-Ratings & Reviews-spec",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2009-08-05",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "Brian McSweeney", url: "https://www.linkedin.com/in/bmcsweeney/",
company: "Chlu", companyURL: "https://www.chlu.io/"},
{ name: "Kulpreet Singh", url: "https://www.linkedin.com/in/zapfmann/",
company: "Chlu", companyURL: "https://www.chlu.io/" }
],
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
authors:
[
{ name: "Brian McSweeney", url: "https://www.linkedin.com/in/bmcsweeney/",
company: "Chlu", companyURL: "https://www.chlu.io/"},
{ name: "Samuel Smith", url: "https://www.linkedin.com/in/samuel-m-smith-phd-4652751/",
company: "ConsenSys", companyURL: "https://www.consensys.net"},
{ name: "Kulpreet Singh", url: "https://www.linkedin.com/in/zapfmann/",
company: "Chlu", companyURL: "https://www.chlu.io/" }
],
// name of the WG
wg: "Verifiable Claims Working Group",
// URI of the public WG page
wgURI: "https://www.w3.org/2017/vc/WG/",
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-credentials",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: "https://www.w3.org/community/about/agreements/cla/",
maxTocLevel: 4,
inlineCSS: true
};
</script>
</head>
<body>
<section id='abstract'>
<p>
Decentralized Ratings & Reviews (DRR) is a new standard for Ratings & Reviews ownership, portability and verifiability online.
Decentralized Ratings & Reviews takes online ratings and reviews into the full control of the Ratings & Reviews owner enabling them to leverage their online Ratings & Reviews across any supporting platform.
Decentralized Ratings & Reviews leverages the <a href="https://w3c-ccg.github.io/did-spec/">Decentralized Identifier</a> or DID specification and the associated <a href="https://www.w3.org/TR/verifiable-claims-data-model/">Verifiable Claims</a> model.
As such, DRR is independent from any centralized registry or authority.
</p>
<p>
Decentralized Ratings & Reviews consists of at least two things: A <a href="https://w3c-ccg.github.io/did-spec/">DID</a> which is the subject/owner of the Ratings & Reviews (e.g. an individual or a business) plus
a list of zero or more ratings and reviews that conform to the specification of this document. Each rating and review provides following key information:
<ul>
<li>the source of the rating and review - ie, the service on which the rating and review originated.</li>
<li>a proof of verifiability, if one is available, and if so, the method of verification - eg, is there traceability of the associated payment history.</li>
</ul>
</p>
<p>
This document specifies a common data model, format, and operations that all Decentralized Ratings & Reviews implementations support.
</p>
</section>
<section id='sotd'>
<p>
Comments regarding this document are welcome. Please file issues
directly on <a href="https://github.com/ChluNetwork/decentralized-Ratings & Reviews-spec/issues/">GitHub</a>,
or send them to
<a href="mailto:[email protected]">[email protected]</a>
(<a href="mailto:[email protected]?subject=subscribe">subscribe</a>,
<a href="https://lists.w3.org/Archives/Public/public-credentials/">archives</a>).
</p>
<p>
Work on this specification has also been supported by...
</p>
</section>
<section>
<h1>Introduction</h1>
<section>
<h2>Overview</h2>
<p>
Online Ratings & Reviews are often a critical factor to digital commercial success in today's economy. Understanding this, companies and individuals spend significant amounts of time and effort building up their Ratings & Reviews on large online platforms.
The emergence of blockchain or distributed ledger technology (DLT), enables decentralized Ratings & Reviews systems that can address three major problems with current systems.
<p>
<b>Ratings & Reviews Ownership</b>
</p>
<p>
Given the importance of Ratings & Reviews to the commercial success of businesses and individuals online, in addition to the recent highly publicized <a href="https://en.wikipedia.org/wiki/Facebook%E2%80%93Cambridge_Analytica_data_scandal">data ownership scandals</a> and the advent of the European <a href="https://www.eugdpr.org">GDPR legislation</a> aimed to address online data ownership rights, the need to address the flaws in current online Ratings & Reviews ownership is clear.
Decentralized Ratings & Reviews takes the ownership of Ratings & Reviews data out of the pervue of large walled gardened platforms and places it squarely in the control of the Ratings & Reviews recipient.
</p>
<p>
Decentralized Ratings & Reviews solves the ownership issue by leveraging <a href="https://w3c-ccg.github.io/did-spec">Decentralised Identifiers</a>, also known as DIDs. With Decentralized Ratings & Reviews, the Ratings & Reviews owner or subject is the DID and the associated ratings and reviews are linked to the DID as instances of <a href="https://www.w3.org/TR/verifiable-claims-data-model/">Verifiable Claims</a>.
</p>
<p>
<b>Ratings & Reviews Portability</b>
</p>
<p>
While online Ratings & Reviews is a key commercial factor on the web, ease of Ratings & Reviews portability is effectively non-existant today.
Online Ratings & Reviews portability is a well documented, sizeable problem as <a href="https://medium.com/doteveryone/exploring-portable-ratings-for-gig-workers-5632fd9b262e">recently stated</a> by <a href="https://doteveryone.org.uk">DotEveryone</a>, the London based, fairer internet think tank, by <a href="https://www.wired.com/story/how-to-fix-ratings-in-the-gig-economy/">Wired magazine</a> and also by the <a href="https://www.ft.com/content/a72f7e56-3724-11e8-8b98-2f31af407cc8">Financial Times</a> amongst others.
</p>
<p>
The need for Ratings & Reviews portability is an explicit recommendation of <a href="https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/627671/good-work-taylor-review-modern-working-practices-rg.pdf">the 2017 'Taylor Report'</a>, an independent assessment of the UK economy commissioned by the UK government, where it specifically states:
</p>
<p>
<em>Government should strongly encourage gig platforms to enable individuals to be able to carry their verified approval ratings with them when they move from the platform and to share them with third parties.
</em>
</p>
<p>
In addition to the Taylor Report, broader pan European legislation dealing with digital data ownership for EU citizens known as the General Data Protection Regulation or GDPR, which becomes effective on the 25th of May 2018, has a specific article focused on ensuring companies enable <a href="https://www.i-scoop.eu/gdprarticle/gdpr-article-20-right-data-portability/">digital data portability</a> for EU citizens.
</p>
<p>
To solve the Ratings & Reviews data portability issue this specification outlines three core items that must be addressed by Decentralized Ratings & Reviews systems - Ownership, Portability and Verifiability.
In addition, Decentralized Ratings & Reviews implementations should be <a href="#permissionless">Permissionless</a>, offer <a href="#decentralizedstorage">Decentralized Storage</a> and conform to the <a href="#datamodel">Decentralized Ratings & Reviews Data Model</a> outlined in this specification. The Decentralized Ratings & Reviews Data Model normalizes the ratings scores associated with historical Ratings & Reviews from centralized services in order to faciliatate portability and uniformity of ratings and reviews.
</p>
<p>
<b>Ratings & Reviews Verifiability</b>
</p>
<p>
In addition to addressing the major issue of Ratings & Reviews ownership and portability, Decentralized Ratings & Reviews also aims to address the significant problem of Ratings & Reviews verifiablility - tackling fake ratings and reviews. Online ratings and reviews have a long history of manipulation and with continued well documented, widespread gaming/manipulation on all of the major online marketplaces.
<sub><a href="http://fortune.com/2017/12/10/tripadvisor-london-shed-fake-restaurant/">1</a></sub>
<sub><a href="https://www.marketwatch.com/story/20-of-yelp-reviews-are-fake-2013-09-24">2</a></sub>
<sub><a href="http://www.bbc.com/news/technology-43907695">3</a></sub>
<sub><a href="https://www.buzzfeed.com/nicolenguyen/amazon-fake-review-problem?utm_term=.wpoB3DgV1#.qjrK48mGl">4</a></sub>
<sub><a href="https://www.npr.org/sections/money/2018/04/27/606528176/episode-838-a-series-of-mysterious-packages">5</a></sub>
</p><p>
Fake Ratings and Reviews can be either biased as incentivized positive fake reviews aimed to boost sales, or biased on the negative side, often from a competitor, aimed to lower sales.
The issue is so important to online commercial success that it has spawned an entire industry dedicated to generating fake reviews. Known as "Brushing" in China, to avoid suspicion, incentivized fake reviewers may still pay for the product, through a valid online account, thus making the fake reviews even more difficult to detect.
This complexity means there is no simple solve, and associated well known researched problems such as <a href="https://en.wikipedia.org/wiki/Sybil_attack">Sybill Attacks</a> exist.
</p>
<p>
Decentralized Ratings & Reviews approaches the problem by creating an open extensible standard, enabling different forms of proofs of verifiability to be associated with a specific rating and review.
Verifiability is not a hard requirement for every rating and review in Decentralized Ratings & Reviews, but in the case when it is, the method or methods of verifiability are listed.
Current forms of or weightings towards verifiable review proof include:
<ul>
<li>Proof by confirmed payment</li>
<li>Proof by payment amount</li>
<li>Proof by review text analysis</li>
<li>Proof by reviewer location</li>
<li>Proof by reviewer historical Ratings & Reviews</li>
<li>Proof by reviewee historical Ratings & Reviews</li>
<li>Proof by community consensus</li>
</ul>
</p>
<p>
</section>
<section>
<h1>Purpose of This Specification</h1>
<p>
The primary purpose of this specification is to define the conformance requirements for a Decentralized Ratings & Reviews implementation.
That includes both the Decentralized Ratings & Reviews scheme and set of operations.
</p>
</section>
</section>
<section>
<h2>Design Goals</h2>
<p>
This section summarizes the design goals and principles of Decentralized Ratings & Reviews architecture.
</p>
<table class="simple">
<thead>
<tr>
<th>Goal</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Decentralized Ownership
</td>
<td>
DRR architecture should give entities, both human and non-human, the power to directly own and control their digital Ratings & Reviews without the need to rely on external authorities.
</td>
</tr>
<tr>
<td>
Cryptographic Proof of Ownership
</td>
<td>
DRR architecture should enable an entity to provide cryptographic proof of authentication and proof of authorization rights.
</td>
</tr>
<tr>
<td>
Decentralized Storage
</td>
<td>
Decentralized Ratings & Reviews architecture should eliminate the requirement for centralized authorities or single points of failure in Ratings & Reviews
storage, including the creation, editing and deletion of conforming decentralized Ratings & Reviews instances and associated metadata.
</td>
</tr>
<tr>
<td>
Ratings & Reviews Portability
</td>
<td>
Decentralized Ratings & Reviews should be system and network independent and should enable the portability of Ratings & Reviews from platform to platform, conforming to the normalized Ratings & Reviews schema outlined in this document.
</td>
</tr>
<tr>
<td>
Ratings & Reviews Verifiability
</td>
<td>
DRR architecture should enable one or more methods of proof of verifiability of Ratings & Reviews.
</td>
</tr>
<tr>
<td>
Extensibility
</td>
<td>
When possible, DRR architecture should enable extensibility provided it does not greatly hinder ownership, interoperability, portability, verifiability or
simplicity.
</td>
</tr>
</tbody>
</table>
</section>
<section>
<h2>Simple Examples</h2>
<p>
This is a simple example of a Decentralized Identifier (DID) Document and associated Decentralized Ratings & Reviews (DRR) Document. The DID and DRR are associated via the <a href="https://www.w3.org/TR/verifiable-claims-data-model">Verifiable Claims Model</a>
</p>
<p>
Sample DID Document
</p>
<pre class="example nohighlight" title="A simple example of a Decentralized Identifier (DID)">
{
"@context": "https://w3id.org/did/v1",
"id": "did:chlu:4936b9f8-5311-4ff8-bb7e-777e65122d21",
"publicKey": [
{
"id": "did:chlu:4936b9f8-5311-4ff8-bb7e-777e65122d21#keys-1",
"type": "RsaVerificationKey2018",
"owner": "did:chlu:4936b9f8-5311-4ff8-bb7e-777e65122d21",
"publicKeyPem": "-----BEGIN PUBLIC KEY-----\r\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkxWBxBIo0DMp3B0KyitA\r\nrJPXirRGXuB7b0o48gWbbN9WXo2ZcZKGBz01F+LS1yAgOvea8TjpsvYAoX1YezUP\r\n9fNsE1aAOrZmIAoBPINgCq/HmLLKwonZuIc4PF88weggSgjxs3MGVw9QQwJQo5+1\r\n3ZdKisuJHM+0/4UvXFGgdZeN27abN9JPGkDu3vT7nIzk6lmfyXpPPHOHY1rGPK3u\r\nGZWBIOZoJgNYn52tCYd0PvoqMhuH9B+DBI+mEfp0asToVjaWW6MiAh2lK90Pv7Dz\r\nns2buQBexT/btoRJejfQ82gQAKkum/MbBdy/Ae1KmcrI0ueKV6n1OlTj0WZppo9I\r\nmQIDAQAB\r\n-----END PUBLIC KEY-----\r\n"
}
],
"authentication": [
{
"type": "RsaSignatureAuthentication2018",
"publicKey": "did:chlu:-----BEGIN PUBLIC KEY-----\r\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkxWBxBIo0DMp3B0KyitA\r\nrJPXirRGXuB7b0o48gWbbN9WXo2ZcZKGBz01F+LS1yAgOvea8TjpsvYAoX1YezUP\r\n9fNsE1aAOrZmIAoBPINgCq/HmLLKwonZuIc4PF88weggSgjxs3MGVw9QQwJQo5+1\r\n3ZdKisuJHM+0/4UvXFGgdZeN27abN9JPGkDu3vT7nIzk6lmfyXpPPHOHY1rGPK3u\r\nGZWBIOZoJgNYn52tCYd0PvoqMhuH9B+DBI+mEfp0asToVjaWW6MiAh2lK90Pv7Dz\r\nns2buQBexT/btoRJejfQ82gQAKkum/MbBdy/Ae1KmcrI0ueKV6n1OlTj0WZppo9I\r\nmQIDAQAB\r\n-----END PUBLIC KEY-----\r\n#keys-1"
}
]
}
</pre>
<p>
Sample Associated DRR
</p>
<pre class="example nohighlight" title="A simple example of an associated Decentralized Reputation (DR)">
{
"issued": "2018-05-25T21:19:10Z",
"issuer": "did:chlu:ebfeb1f712ebc6f1c276e12ec21",
"subject": {
"did": "did:chlu:138aae15ec44b1832fdfbab064e91505ae7047cb",
"name": "Victor Vendor",
"address": "W1A1AA, London, UK",
"telephone": "001 171 1717 717",
"categories": ["chinese", "restaurant", "asian"],
"location": {
"lat": "118.100",
"lng": "72.200"
},
"url": "https://restaurant.com"
},
"platform": {
"name": "yelp",
"url": "yelp.com",
"subject_url": "https://yelp.com/path_to_restaurant"
},
"author": {
"name": "Carol Customer",
"platform_url": "https://yelp.com/reviewers/carol"
},
"review": {
"date_published": "2018-05-25T21:19:10Z",
"url": "https://yelp.com/path_to_review/details",
"title": "Excellent food and service",
"text": "Enjoyed the entire evening. The service was outstanding, and food exceptional"
},
"rating": {
"min": 1,
"value": 5,
"max": 5
},
"detailed_review": [
{
"rating": {
"min": 0,
"value": 5,
"max": 5
},
"review": "The soups and stir fry we got were just perfectly done.",
"category": "Food"
},
{
"rating": {
"min": 0,
"value": 5,
"max": 5
},
"review": "Pleasant staff. Helpful and prompt.",
"category": "Service"
},
],
"verifiable": true,
"verification": [
{
"method": "ConfirmedPayment",
"provider": "https://chlu.io"
},
{
"method": "ReviewerHistoricalReputation",
"provider": "https://example.com",
"proof": {
"type": "LinkedDataSignature2015",
"created": "2018-05-24T22:20:00Z",
"creator": "did:example:8e95e8ccac6c8eb91b8a7a8f02bca2fa2268d4b2:#keys-1",
"nonce": "1b0d65",
"signatureValue": "722551b39bcc478810d...5fe81="
}
}
]
"signature": {
"type": "LinkedDataSignature2015",
"created": "2018-05-25T21:19:10Z",
"creator": "did:chlu:ebfeb1f712ebc6f1c276e12ec21#keys-1",
"nonce": "598c63d6",
"signatureValue": "BavEll0/I1zpYw8XNi1bgVg...sCneO4J="
}
}
</pre>
</section>
<section>
<h1>Terminology</h1>
<div data-include="terms.html"
data-oninclude="restrictReferences"></div>
<section>
<h2>Base Specifications</h2>
<p>
This specification is dependent on a number of base specifications. The
dependencies and their purpose are listed below.
</p>
<dl>
<dt>[[JSON]]</dt>
<dd>
The JSON specification provides the base data format that this specification
uses.
</dd>
<dt>[[JSON-LD]]</dt>
<dd>
The JSON-LD specification enables the layering of data semantics on top of
JSON data.
</dd>
<dt>[[DID]]</dt>
<dd>
The DID specification provides the base data format associated with idenity management that this specification
uses.
</dd>
<dt>[[Verifiable Claims]]</dt>
<dd>
The Verifiable Claims data model specification provides the association mechanism between the DID and the DR.
</dd>
</dl>
</section>
</section>
<section>
<h1>Core Specification Requirements</h1>
<p>Decentralized Ownership, Portability and Verifiability are core elements of the Decentralized Ratings & Reviews Specification</p>
<h2>Decentralized Ratings & Reviews Ownership</h2>
<p>Decentralized Ratings & Reviews leverages the <a href="https://w3c-ccg.github.io/did-spec/">Decentralized Identifier</a> or DID specification and the associated <a href="https://www.w3.org/TR/verifiable-claims-data-model/">Verifiable Claims</a> model to move reptutation ownership from centralized large platforms to the Ratings & Reviews recipient.
Rather than focusing on building a new decentralized identity mechanism, the DR specification leverages the current defacto decentralized identity management system today - the DID model. However, in the future, additional identity management systems may be added.</p>
<section>
<h3>Decentralized Ratings & Reviews and DIDs</h3>
<p>To be COMPLETED</p>
</section>
<section>
<h3>Decentralized Ratings & Reviews and DID Association via Verifiable Claims</h3>
<p>
Decentralized Ratings & Reviews leverages the <a href="https://w3c.github.io/vctf/">verifiable claims</a> model to associate to a DID subject.
To do....
</p>
</section>
<section>
<h3>Simple Examples</h3>
<p>To be COMPLETED</p>
</section>
<section>
<h2>Decentralized Ratings & Reviews Portability</h2>
<p>Decentralized Ratings & Reviews leverages decentralized storage and normalized ratings and reviews to facilitate Ratings & Reviews portability.</p>
<section>
<h3>Decentralized Ratings & Reviews Storage</h3>
<p>Decentralized storage should eliminate the requirement for centralized authorities or single points of failure in Ratings & Reviews
storage, including, but not limited to, the creation, editing and deletion of conforming decentralized Ratings & Reviews instances and associated metadata. In addition, decentralized storage should facilitate automatic encryption and replication of Ratings & Reviews data.
All candidate implementation systems of Decentralized Ratings & Reviews should provide decentralized storage implementations that deliver these requirements.
Potential example decentralized storage implementation technologies could include, but are not limited to, <a href="https://en.wikipedia.org/wiki/Distributed_ledger">Distributed Ledger Technologies</a>, encrypted <a href="https://en.wikipedia.org/wiki/Clustered_file_system#Distributed_file_systems">distributed file systems</a> such as <a href="https://en.wikipedia.org/wiki/InterPlanetary_File_System">IPFS</a> etc</p>
</section>
<section>
<h3>Decentralized Ratings & Reviews Normalization</h3>
<p>
For the broadest interoperability, Decentralized Ratings & Reviews normalization should be as simple
and universal as possible. This section summarizes the properties associated with the normalized Decentralized Ratings & Reviews specification, designed to standardize and simplify the way decentralized Ratings & Reviews is rendered online.
</p>
<table class="simple">
<thead>
<tr>
<th>Property</th>
<th>Description</th>
<th>Data Type</th>
<th>Required</th>
</tr>
</thead>
<tbody>
<tr>
<td>
id
</td>
<td>
The identifier of the review. Can be the URI for where the review is available.
</td>
<td>
URI
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Issued
</td>
<td>
The timestamp of when the review was issued on the decentralised repository
</td>
<td>
DateTime
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Issuer
</td>
<td>
The DID of the service, platform, entity that made this review availabe on decentralised repository
</td>
<td>
DID
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Subject DID
</td>
<td>
The DID of the subject, i.e. the entity receiving the review
</td>
<td>
DID
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Subject Name
</td>
<td>
Name of the subject entity
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Subject Address
</td>
<td>
Address of the subject entity
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Subject Telephone
</td>
<td>
Telephone number of the subject entity
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Subject Categories
</td>
<td>
Categories that subject entity identifies itself with
</td>
<td>
List of Strings
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Subject Location
</td>
<td>
Latitude and Longitude of where the subject entity can be found
</td>
<td>
Pair of strings
</td>
<td>
No
</td>
</tr>
<tr>
<td>
URL
</td>
<td>
The URL of the primary source of information about the subject. E.g. the subject's website.
</td>
<td>
URL
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Platform Name
</td>
<td>
The name of the platform where the review was received by the entity
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Platform URL
</td>
<td>
The URL where information is available about the platform
</td>
<td>
URL
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Platform Subject URL
</td>
<td>
The URL where information about the subject can be found on the platform
</td>
<td>
URL
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Author Name
</td>
<td>
The Name of the entity that created the review
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Author Platform URL
</td>
<td>
The URL where more information can be found about the Author on the platform
</td>
<td>
URL
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Review Date Published
</td>
<td>
The timestamp when the reivew was published on the platform. Note, this is different from "issued"
</td>
<td>
DateTime
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Review URL
</td>
<td>
The URL where the review is available on the platform
</td>
<td>
URL
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Review Title
</td>
<td>
The title associated with the review, if the platform supports it
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Review Text
</td>
<td>
The review text description
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Rating Min
</td>
<td>
The minimum value of ratings on the platform where the review is from
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Rating Value
</td>
<td>
The value of rating associated with this review
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Rating Max
</td>
<td>
The maximum value of ratings on the platform where the review is from
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Detailed Reviews
</td>
<td>
A list of "Detailed Review". Includes category, review and rating. See next table.
</td>
<td>
JSON
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Verifiable
</td>
<td>
Flag if the review is independently verifiable or not.
</td>
<td>
Boolean
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Verification
</td>
<td>
An array of various verification methods available to verify this decentralised review
</td>
<td>
Array of JSON objects. See Verification Methods table
</td>
<td>
Yes. The array should have at least one object
</td>
</tr>
<tr>
<td>
Signature
</td>
<td>
Signature to verify the issuer has provided this review on decentralised repository
</td>
<td>
JSON
</td>
<td>
Yes
</td>
</tr>
</tbody>
</table>
<section>
<h4>Verification Methods</h4>
<table class="simple">
<thead>
<tr>
<th>Property</th>
<th>Description</th>
<th>Data Type</th>
<th>Required</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Verification Method
</td>
<td>
Identifies the method used for verifying the review
</td>
<td>
String
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Verification Provider
</td>
<td>
The platform/system/protocol that provides verification method
</td>
<td>
String
</td>
<td>
Yes
</td>
</tr>
<tr>
<td>
Verification Proof
</td>
<td>
A signature by a the verification provider's key
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
</tbody>
</table>
</section>
<section>
<h4>Detailed Review JSON properties</h4>
<table class="simple">
<thead>
<tr>
<th>Property</th>
<th>Description</th>
<th>Data Type</th>
<th>Required</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Rating Min
</td>
<td>
The minimum value of ratings on the platform where the review is from
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Rating Value
</td>
<td>
The value of rating associated with this review
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Rating Max
</td>
<td>
The maximum value of ratings on the platform where the review is from
</td>
<td>
Integer
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Review
</td>
<td>
Text overview of the review for the category
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
<tr>
<td>
Category
</td>
<td>
The category of the detailed review
</td>
<td>
String
</td>
<td>
No
</td>
</tr>
</tbody>
</table>
</section>
</section>
<section>
<h3>Simple Examples</h3>
<p>To be COMPLETED</p>
</section>
</section>
<section>