diff --git a/index.html b/index.html index 260d6744..fb2ecbbd 100644 --- a/index.html +++ b/index.html @@ -2248,60 +2248,6 @@

Service Endpoints

-
-

Created

- -

-A DID document SHOULD include a created property. -

- -
-
created
-
-If a DID document includes a created property, the value -of the property MUST be a valid XML datetime value, as defined in section -3.3.7 of W3C XML Schema -Definition Language (XSD) 1.1 Part 2: Datatypes [[XMLSCHEMA11-2]]. This -datetime value MUST be normalized to UTC 00:00, as indicated by the trailing -"Z". -
-
- -
-{
-  "created": "2002-10-10T17:00:00Z"
-}
-      
-
- -
-

Updated

- -

-Standard metadata for identifier records includes a timestamp of the most recent -change. -

- -

-A DID document SHOULD include an updated property. -

- -
-
updated
-
-If a DID document includes an updated property, the value -of the property MUST follow the same formatting rules as the -created property (see Section ). -
-
- -
-{
-  "updated": "2016-10-17T02:41:00Z"
-}
-      
-
-
@@ -3435,6 +3381,33 @@

This specification defines the following common properties.

+
+
+created +
+
+DID document metadata SHOULD include a created property +to indicate the timestamp of the Create operation. +This property MAY not be supported by a given DID method. +The value of +the property MUST be a valid XML datetime value, as defined in section 3.3.7 of +W3C XML Schema Definition +Language (XSD) 1.1 Part 2: Datatypes [[XMLSCHEMA11-2]]. This datetime value +MUST be normalized to UTC 00:00, as indicated by the trailing "Z". +
+
+updated +
+
+DID document metadata SHOULD include an updated property +to indicate the timestamp of the last Update operation. +This property MAY not be supported by a given DID method. +The value of +the property MUST follow the same formatting rules as the created +property. +
+
+

@@ -3516,6 +3489,30 @@

]» +

+The next example demonstrates a JSON-encoded metadata structure that might be +used as DID document metadata to +describe timestamps associated with the DID document. +

+ +
+{
+  "created": "2019-03-23T06:35:22Z",
+  "updated": "2023-08-10T13:40:06Z"
+}
+        
+ +

+This example corresponds to a metadata structure of the following format: +

+ +
+«[
+  "created" → "2019-03-23T06:35:22Z",
+  "updated" → "2023-08-10T13:40:06Z"
+]»
+        
+ @@ -3703,8 +3700,8 @@

-Non-repudiation is further supported if timestamps are included (see Sections - and ) and the target DLT +Non-repudiation is further supported if timestamps are included (see Section +) and the target DLT system supports timestamps.