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

Editorial updates #86

Merged
merged 4 commits into from
Oct 27, 2019
Merged

Editorial updates #86

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cc9be34
Editorial rephrasing towards #48
rhiaro Oct 22, 2019
9cd6649
Editorial tweaks to abstract, for #38 and #40
rhiaro Oct 22, 2019
5111c1c
Editorial
rhiaro Oct 26, 2019
ee4c5e8
More specific in abstract
rhiaro Oct 26, 2019
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
20 changes: 10 additions & 10 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,17 +139,17 @@
are designed to enable the controller of a <a>DID</a> to prove control over
it and to be implemented independently of any centralized registry,
identity provider, or certificate authority. <a>DIDs</a> are URLs that relate
a <a>DID subject</a> to means for trustable interactions with that subject.
<a>DIDs</a> resolve to <a>DID documents</a> &mdash; simple documents that describe how
a <a>DID subject</a> to means for trustable interactions with that subject by way
of a <a>DID document</a>. <a>DID documents</a> are simple documents that describe how
to use that specific <a>DID</a>. Each <a>DID document</a> may express cryptographic
material, verification methods, and/or <a>service endpoints</a>. These provide
a set of mechanisms which enable a <a>DID controller</a> to prove control of the
<a>DID</a>. <a>Service endpoints</a> enable trusted interactions with the <a>DID
subject</a>.
</p>
<p>
This document specifies a common data model, format, and operations that
all <a>DIDs</a> support.
This document specifies a common data model, a URL format, and a set of operations for
<a>DIDs</a> and related components.
rhiaro marked this conversation as resolved.
Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"DIDs and related components" doesn't make much sense to me; what are those "related components"? Syntax components like DID path or DID query? Or architectural components like DID registry and DID resolver?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant like DID documents and DID methods. I can change it to that.

</p>
</section>

Expand Down Expand Up @@ -937,11 +937,11 @@ <h2>
</p>

<p>
It is desirable that we enable tree-based processing of <a>DIDs</a> that include
<a>DID fragments</a> (which resolve directly within the <a>DID document</a>) to locate
metadata contained directly in the <a>DID document</a> or the service resource
given by the target URL without needing to rely on graph-based processing.
Implementations need not rely on graph-based processing of <a>DID documents</a>
to locate metadata contained in the <a>DID document</a> when the <a>DID</a> includes
a <a>DID fragment</a>. Tree-based processing can be used instead.
</p>

<p>
Implementations SHOULD NOT prevent the use of <a>JSON Pointer</a> ([[!RFC6901]]).
</p>
Expand Down Expand Up @@ -2026,8 +2026,8 @@ <h2>
this approach is to provide a low barrier to entry while still ensuring global
interoperability between a heterogeneous set of software systems. This section
describes some of these approaches, which will likely go unnoticed by most
developers, but whose details will be of interest to implementers. The most
noteworthy syntactic sugars provided by JSON-LD are:
developers, but whose details will be of interest to implementers.
Noteworthy features provided by JSON-LD are:
</p>

<ul>
Expand Down