From cc9be34742a77acc3541f18ea7f9dcd521f1ca71 Mon Sep 17 00:00:00 2001
From: rhiaro
Date: Tue, 22 Oct 2019 21:44:07 +0100
Subject: [PATCH 1/4] Editorial rephrasing towards #48
---
index.html | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/index.html b/index.html
index a6d0cd94..60da81bc 100644
--- a/index.html
+++ b/index.html
@@ -937,11 +937,11 @@
-It is desirable that we enable tree-based processing of DIDs that include
-DID fragments (which resolve directly within the DID document) to locate
-metadata contained directly in the DID document 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 DID documents
+to locate metadata contained in the DID document when the DID includes
+a DID fragment. Tree-based processing can be used instead.
+
Implementations SHOULD NOT prevent the use of JSON Pointer ([[!RFC6901]]).
@@ -2026,8 +2026,8 @@
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:
From 9cd6649309755d4652cf2e2847ccc048d598132d Mon Sep 17 00:00:00 2001
From: rhiaro
Date: Tue, 22 Oct 2019 22:34:18 +0100
Subject: [PATCH 2/4] Editorial tweaks to abstract, for #38 and #40
---
index.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/index.html b/index.html
index 60da81bc..264f96e3 100644
--- a/index.html
+++ b/index.html
@@ -139,8 +139,8 @@
are designed to enable the controller of a DID to prove control over
it and to be implemented independently of any centralized registry,
identity provider, or certificate authority. DIDs are URLs that relate
-a DID subject to means for trustable interactions with that subject.
-DIDs resolve to DID documents — simple documents that describe how
+a DID subject to means for trustable interactions with that subject by way
+of a DID document. DID documents are simple documents that describe how
to use that specific DID. Each DID document may express cryptographic
material, verification methods, and/or service endpoints. These provide
a set of mechanisms which enable a DID controller to prove control of the
@@ -148,8 +148,8 @@
subject.
-This document specifies a common data model, format, and operations that
-all DIDs support.
+This document specifies a common data model, a URL format, and a set of operations for
+DIDs and related components.
From 5111c1c5802e13e86f6b04589ecafc86dc6180db Mon Sep 17 00:00:00 2001
From: Amy Guy
Date: Sat, 26 Oct 2019 19:23:25 +0100
Subject: [PATCH 3/4] Editorial
Co-Authored-By: Ted Thibodeau Jr
---
index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/index.html b/index.html
index 264f96e3..0bbece78 100644
--- a/index.html
+++ b/index.html
@@ -149,7 +149,7 @@
This document specifies a common data model, a URL format, and a set of operations for
-DIDs and related components.
+DIDs, and related components.
From ee4c5e84b14a6e2a002fa7494bcba30f81e8cadb Mon Sep 17 00:00:00 2001
From: rhiaro
Date: Sat, 26 Oct 2019 19:39:34 +0100
Subject: [PATCH 4/4] More specific in abstract
---
index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/index.html b/index.html
index 0bbece78..e3e05a92 100644
--- a/index.html
+++ b/index.html
@@ -149,7 +149,7 @@
This document specifies a common data model, a URL format, and a set of operations for
-DIDs, and related components.
+DIDs, DID documents, and DID methods.