diff --git a/docs/spec/index.html b/docs/spec/index.html
index d45c503518..0c00e26ded 100644
--- a/docs/spec/index.html
+++ b/docs/spec/index.html
@@ -236,8 +236,8 @@
- To contribute to this vocabulary or reference technical details related to
- the project, please reference the
+ To contribute to this specification or reference technical details related to
+ the project, please refer to the
primary README located on
GitHub.
@@ -345,24 +345,26 @@ Rules for Processing Data
informational processing.
- Identifiers
-
- Identifiers in objects exchanged using this specification are
- particularly important, not least in that they uniquely identify
- an object or network transaction, but also, given the
- asynchronous nature of this mode of data exchange, that they
- present an area where various attacks could arise by sending
- data with identifiers already in use with malicious intent to
- confuse a receiver of the data.
-
-
- Identifiers conformant with this spec MUST be
- [[rfc3986]] conformant URIs. Unless otherwise noted, an
- identifier MAY be a DID identifier per [[did-core]], a
- UUID v4 per [[rfc4122]], or a [[URL]] that identifies a resource
- directly.
-
-
+
+ Identifiers
+
+ Identifiers in objects exchanged using this specification are
+ particularly important, not least in that they uniquely identify
+ an object or network transaction, but also, given the
+ asynchronous nature of this mode of data exchange, in that they
+ present an area where various attacks could be made by sending
+ data with identifiers already in use with malicious intent to
+ confuse a receiver of the data.
+
+
+ Identifiers conformant with this specification MUST be
+ [[rfc3986]] conformant URIs. Unless otherwise noted, an
+ identifier MAY be a DID identifier per [[did-core]], a
+ UUID v4 per [[rfc4122]], or a [[URL]] that identifies a resource
+ directly.
+
+
+
Presentations
Presentations in this spec are
@@ -495,12 +497,12 @@
General Guidelines
As a rule, systems conforming with this specification SHOULD
leverage and comply with encryption and security guidelines as
listed in:
- FIPS 186-5 (DRAFT),
+ FIPS 186-5 Digital Signature Standard (DSS),
FIPS 180-4, and
+ rel="nofollow">FIPS 180-4 Secure Hash Standard (SHS), and
FIPS 197. This
+ rel="nofollow">FIPS 197 Advanced Encryption Standard (AES). This
effectively means that committers should be thinking along the lines of
P256 versus other competing
algorithms.
@@ -530,7 +532,7 @@ Encryption in Transport
interoperability
MUST utilize TLS and comply with
+ href="https://csrc.nist.gov/pubs/sp/800/52/r2/final">
NIST SP 800-52 rev2
or superseding publications for configuration and use of TLS in
transport of data over API or web endpoints.
diff --git a/docs/spec/sections/use-case-requirements.html b/docs/spec/sections/use-case-requirements.html
index 95dc98d7d1..51f9d8084a 100644
--- a/docs/spec/sections/use-case-requirements.html
+++ b/docs/spec/sections/use-case-requirements.html
@@ -67,11 +67,6 @@ Identifier Discovery
necessary to complete integration tests in postman with authentication.
-
-The current APIs exploit the well known DID configuration,
-which has some limitations, most notably regarding multi-tenant platforms.
-
-
Integration Considerations
@@ -221,16 +216,18 @@
verificationMethod
"did:web:platform.example:organization:123#key1"
],
"verificationMethod": [
- {
- "id": "did:web:platform.example:organization:123#key1",
- "type": "JsonWebKey2020",
- "controller": "did:web:platform.example:organization:123",
- "publicKeyJwk": {
- "kty": "OKP",
- "crv": "Ed25519",
- "x": "rfsiofZ3RcuMWZSoYbvNEZ_8oxeep8uapJDyT0ku8EM"
- }
+ {
+ "id": "https://university.example/issuers/565049#key-123",
+ "type": "JsonWebKey",
+ "controller": "https://university.example/issuers/565049",
+ "publicKeyJwk": {
+ "kty": "EC",
+ "crv": "P-384",
+ "alg": "ES384",
+ "x": "PxgAmVYOQvSNcMYL2tOzoLwSWn4Ta3tIMPEUKR8pxeb-gmR11-DyKHBoIiY-2LhM",
+ "y": "BZEBTkImVdpwvxR9THIRw16eblnj5-tZa7m-ww5uVd4kyPJNRoWUn2aT9ZuarAe-"
}
+ }
],
"service": [
{