-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
270 lines (220 loc) · 6.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
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'>
<title>Web Contracts v0.1</title>
<script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
<script class='remove'>
var respecConfig = {
specStatus: "CG-DRAFT",
editors: [{
name: "Melvin Carvalho",
url: "https://melvincarvalho.com/#me",
mailto: "melvincarvalho@gmail.com"
}],
authors: [{
name: "Melvin Carvalho",
url: "https://melvincarvalho.com/#me",
mailto: "melvincarvalho@gmail.com"
}],
wg: 'W3C Payments Community Group',
wgURI: 'https://www.w3.org/community/webpayments/',
wgPublicList: "public-webpayments",
processVersion: 2019,
edDraftURI: "https://github.com/solidpayorg/webcontracts/",
shortName: "webcontracts",
issueBase: "https://github.com/solidpayorg/webcontracts/"
};
</script>
<style>
.turtle .hll {
background-color: #ffffcc
}
pre .highlight {
font-weight: bold;
color: green;
}
pre .comment {
color: SteelBlue;
-webkit-user-select: none;
-moz-user-select: none;
-ms-user-select: none;
user-select: none;
}
</style>
</head>
<body>
<section id='abstract'>
<i><b>Enforcable Contracts for the Web</b></i>.
<p>
Web Contracts is a way to create a contracts using URIs as keys on the web.
<p>
Web Contracts are a new type of system for contracts across the web. These new contracts are
designed to enable contracts across different platforms, and acts as a glue between eco systms.
</p>
<p>
This document specifies a format, interoperability guide lines, and operations that Web Contracts may support.
</p>
</p>
</section>
<section id='sotd'>
<p>
This document in an informal draft discussed in the <a href="https://www.w3.org/community/webpayments/">w3c web
payments
community group</a>.
</p>
</section>
<section>
<h2>Introduction</h2>
<p>A contract is a set of rules that influences web contracts, credits and vouchers.
</p>
<p>
This document specifies a format, and operations that Web Contracts may support.
</p>
<section>
<h3>Overview</h3>
This spec is a work in progress.
</section>
<section class="informative">
<h2>
Design Goals
</h2>
<p>
Web Contracts are a component of larger systems, such as
the Linked Data ecosystem [[LINKED-DATA]], which have driven
the design goals for this specification. This section summarizes the
primary design goals for this specification.
</p>
<table class="simple">
<thead>
<tr>
<th>
Goal
</th>
<th>
Description
</th>
</tr>
</thead>
<tbody>
<tr>
<td>
Decentralization
</td>
<td>
The contract should not be server specific, though it may be.
</td>
</tr>
<tr>
<td>
Control
</td>
<td>
Only the entities that know the contract URN can use it.
</td>
</tr>
<tr>
<td>
Privacy
</td>
<td>
The Voucher URN is kept private between those that honor it.
</td>
</tr>
<tr>
<td>
Security
</td>
<td>
Transmission of a URN will be over encrypted formats.
</td>
</tr>
<tr>
<td>
Proof-based
</td>
<td>
Using PKI, hash, or other trap door function, it is possible to identify a URN without being able to spend
it.
</td>
</tr>
<tr>
<td>
Discoverability
</td>
<td>
It may be possible to discover more information about a URN in a proof based network, or using an
authoritative server.
</td>
</tr>
<tr>
<td>
Interoperability
</td>
<td>
URIs and URNs are used to provide wide interoperability with existing systems on the web.
</td>
</tr>
<tr>
<td>
Portability
</td>
<td>
Be system and network-independent and
enable entities to use their digital identifiers with any
system that supports Web contracts.
</td>
</tr>
<tr>
<td>
Simplicity
</td>
<td>
Favor a reduced set of simple features in order to make the technology
easier to understand, implement, and deploy.
</td>
</tr>
<tr>
<td>
Extensibility
</td>
<td>
When possible, enable extensibility
provided it does not greatly hinder interoperability,
portability, or simplicity.
</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="design" class="informative">
<h3>Data Model</h3>
<section>
<h3>Terminology</h3>
</section>
<section>
<h3>Contracts</h3>
</section>
<section>
<h3>Currency</h3>
</section>
</section>
<section id="implementations" class="informative">
<h3>Implementations</h3>
</section>
<section id="examples" class="appendix informative">
<h2>Examples</h2>
<h3>JSON</h3>
</section>
<section id="examples" class="appendix informative">
<h3>Acknowledgements</h3>
</section>
<p>
The editor would like to thank the Web Payments Community Group.
</p>
<p>
Thanks to the following individuals, in order of their first name, for their input on the specification:
</p>
</body>
</html>