From ce9ef28cf9a73dc919e5e0dc92892d8821d21c81 Mon Sep 17 00:00:00 2001
From: Markus Sabadello Service Endpoints
-A DID document SHOULD include a created
property.
-
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" -} --
-Standard metadata for identifier records includes a timestamp of the most recent -change. -
- -
-A DID document SHOULD include an updated
property.
-
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" -} --
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
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.
+ -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.
From afd303ea36d8d241d93454fc455be07b5c582312 Mon Sep 17 00:00:00 2001 From: Markus Sabadello+The next example demonstrates a JSON-encoded metadata structure that might be +used as DID document metadata to +describe timestamps of the DID document. +
+ ++{ + "created": "2002-10-10T17:00:00Z", + "updated": "2016-10-17T02:41:00Z" +} ++ +
+This example corresponds to a metadata structure of the following format: +
+ ++«[ + "created" → "2002-10-10T17:00:00Z", + "updated" → "2016-10-17T02:41:00Z" +]» ++ From 02a2465e2fa04193f590c53062bf9c01bda90c1c Mon Sep 17 00:00:00 2001 From: Markus Sabadello
The next example demonstrates a JSON-encoded metadata structure that might be used as DID document metadata to -describe timestamps of the DID document. +describe timestamps associated with the DID document.
From 6663b3810595400190d94bebaf25e5851171895a Mon Sep 17 00:00:00 2001 From: Markus SabadelloDate: Mon, 10 Aug 2020 15:40:06 +0200 Subject: [PATCH 4/4] More meaningful example dates, suggested by @msporny --- index.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/index.html b/index.html index 32cc2b56..fb2ecbbd 100644 --- a/index.html +++ b/index.html @@ -3497,8 +3497,8 @@
{ - "created": "2002-10-10T17:00:00Z", - "updated": "2016-10-17T02:41:00Z" + "created": "2019-03-23T06:35:22Z", + "updated": "2023-08-10T13:40:06Z" }@@ -3508,8 +3508,8 @@
«[ - "created" → "2002-10-10T17:00:00Z", - "updated" → "2016-10-17T02:41:00Z" + "created" → "2019-03-23T06:35:22Z", + "updated" → "2023-08-10T13:40:06Z" ]»