Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor typos #150

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Minor typos #150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -803,7 +803,7 @@ <h3>Cross-platform User-driven Sharing</h3>
syndicated, the payments are automatically sent using information associated with Sahar's DID without anyone involved thinking
much about who exactly the contract
refers to as “anonymous ghostwriter X” or “translator of appendix C”. Using a DID as her identifier, rather than her name, allows
Sahar to retain psuedonymity but provide a means for others to pay the right person.</p>
Sahar to retain pseudonymity but provide a means for others to pay the right person.</p>
<p class="reqList"><span class="reqListbefore">Requirements:</span>
<span data-reqid="privacyPreserving"></span>,
<span data-reqid="minRent"></span>,
Expand Down Expand Up @@ -832,7 +832,7 @@ <h3>Cross-platform User-driven Sharing</h3>
competitors to know the actual source of the ingredients or components in its products. Different parties will be interested in different things too. For
example, a retailer may be interested in knowing where a particular shipment is and when it is expected to arrive; a consumer of a food product is more likely
to be concerned about the original source of the item and the total number of food miles in the product.</p>
<p>Decentralized Identifiers could be generated by sending and receiving parties at each stage in the chain. This would preserve psuedonymity yet prove control
<p>Decentralized Identifiers could be generated by sending and receiving parties at each stage in the chain. This would preserve pseudonymity yet prove control
of the identified shipment at each stage and, via the DID Document, provide access to data (subject to authorization) pertaining to each transaction without
enabling correlation across multiple shipments or other sensitive information.</p>
<p class="reqList"><span class="reqListbefore">Requirements:</span>
Expand Down Expand Up @@ -1460,9 +1460,9 @@ <h4>Description</h4>
publicly record the assertion of probate and to replace the DID's master
key with a new key, controlled by Miyake, who lives in Japan (Kathy,
Gloria, and Mike live in the United States). Now, any system using
Kathy's DIDs for authentication can programmatically recognized Miyake's
Kathy's DIDs for authentication can programmatically recognize Miyake's
authority <em>and</em> specifically know that Kathy's credentials were
modified under a assertion of probate.
modified under an assertion of probate.
</p>

</section>
Expand Down Expand Up @@ -1546,7 +1546,7 @@ <h4>Background</h4>
<li>Exposes a DID through her agent in order to set up a secure communication channel.</li>
<li>The car rental company tells Alice’s agent that they will need license, insurance, and bank info for the purpose of
renting a car in France.</li>
<li>Alice’s agent has a policy that saying that any company as large as her chosen car rental company can get whatever
<li>Alice’s agent has a policy saying that any company as large as her chosen car rental company can get whatever
they explicitly ask for. Smaller companies, or large ones on a blacklist may need Alice to give explicit permission
&mdash; which the agent will ask for using a text message.</li>
<li>Alice’s agent offers three signed bearer tokens authorizing release of her personal information from three specific
Expand Down Expand Up @@ -1795,7 +1795,7 @@ <h4>Distinction</h4>
reqObjectList.push(new ReqObject("noVendorLock", "No vendor lock in", "These identifiers are not dependent on any given vendor. Vendor-specific identifiers restrict usage to that which is acceptable to the vendor and may allow vendors to extract disproportionate rents for usage.", ['antiExploit', 'sustainability']));
reqObjectList.push(new ReqObject("limitTrack", "Preempt/limit trackable data trails", "As cookies and other session/state-tracking mechanisms were gradually turned into scaffolding for unwanted or collusive tracking in the evolution of the web stack, so too might any new data exchange or communication systems unwittingly facilitate unwanted tracking based on new data trails. Resistance to these kinds of surveillance exploits need to be designed into new systems.", ['antiCensorship', 'antiExploit', 'privacy']));
reqObjectList.push(new ReqObject("cryptoFuture", "Cryptographic future proof", "These identifiers are capable of being updated as technology evolves. Current cryptography techniques are known to be susceptible to quantum computational attacks. Future-proofed identifiers provide a means to continue using the same identifier with updated, advanced authentication and authorization technologies.", ['antiExploit', 'sustainability']));
reqObjectList.push(new ReqObject("orgMort", "Survives issuing organization mortality", "These identifiers survive the demise of the organization that issued them. They usefulness of these identifiers survive organizations going out of business, being purchased (and potentially losing domain names or root credentials), and even the internal decay of an organization that no longer has the ability to verify the authenticity of records they once issued.", ['sustainability']));
reqObjectList.push(new ReqObject("orgMort", "Survives issuing organization mortality", "These identifiers survive the demise of the organization that issued them. The usefulness of these identifiers survive organizations going out of business, being purchased (and potentially losing domain names or root credentials), and even the internal decay of an organization that no longer has the ability to verify the authenticity of records they once issued.", ['sustainability']));
reqObjectList.push(new ReqObject("deployEnd", "Survives deployment end-of-life", "These identifiers are usable even after the systems deployed by requesting parties move past their useful lifetime. They are robust against technology fads and can seamlessly work with both legacy and next-generation systems.", ['antiCensorship', 'sustainability']));
reqObjectList.push(new ReqObject("survivesRel", "Survives relationship with service provider", "These identifiers are not dependent on the tenure of the relationship with a service provider. This contrasts with identifiers like service-centric emails, e.g. [email protected], which, when used as identifiers in other systems, can cause problems when individuals no longer use the service provider.", ['antiExploit', 'sustainability']));
reqObjectList.push(new ReqObject("cryptoAuthComm", "Cryptographic authentication and communication", "These identifiers enable cryptographic techniques to authenticate individuals and to secure communications with the subject of the identifier, typically using public-private key pairs.", ['antiCensorship', 'antiExploit']));
Expand Down