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.

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

Move "created" and "updated" from Core Properties to DID document metadata #365

Merged
merged 4 commits into from
Aug 11, 2020
Merged
Changes from all commits
Commits
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
109 changes: 53 additions & 56 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -2248,60 +2248,6 @@ <h2>Service Endpoints</h2>
</p>
</section>

<section class="normative">
<h2>Created</h2>

<p>
A <a>DID document</a> SHOULD include a <code><a>created</a></code> property.
</p>

<dl>
<dt><dfn>created</dfn></dt>
<dd>
If a <a>DID document</a> includes a <code>created</code> property, the value
of the property MUST be a valid XML datetime value, as defined in section
3.3.7 of <a href="https://www.w3.org/TR/xmlschema11-2/">W3C XML Schema
Definition Language (XSD) 1.1 Part 2: Datatypes</a> [[XMLSCHEMA11-2]]. This
datetime value MUST be normalized to UTC 00:00, as indicated by the trailing
"Z".
</dd>
</dl>

<pre class="example nohighlight">
{
"created": "2002-10-10T17:00:00Z"
}
</pre>
</section>

<section>
<h2>Updated</h2>

<p>
Standard metadata for identifier records includes a timestamp of the most recent
change.
</p>

<p>
A <a>DID document</a> SHOULD include an <code><a>updated</a></code> property.
</p>

<dl>
<dt><dfn>updated</dfn></dt>
<dd>
If a <a>DID document</a> includes an <code>updated</code> property, the value
of the property MUST follow the same formatting rules as the
<code><a>created</a></code> property (see Section <a href="#created"></a>).
</dd>
</dl>

<pre class="example nohighlight">
{
"updated": "2016-10-17T02:41:00Z"
}
</pre>
</section>

</section>

<section class="normative">
Expand Down Expand Up @@ -3435,6 +3381,33 @@ <h3>
This specification defines the following common properties.
</p>

<dl>
<dt>
created
</dt>
<dd>
DID document metadata SHOULD include a <code>created</code> property
to indicate the timestamp of the <a href="#create">Create operation</a>.
This property MAY not be supported by a given <a>DID method</a>.
The value of
the property MUST be a valid XML datetime value, as defined in section 3.3.7 of
<a href="https://www.w3.org/TR/xmlschema11-2/">W3C XML Schema Definition
Language (XSD) 1.1 Part 2: Datatypes</a> [[XMLSCHEMA11-2]]. This datetime value
MUST be normalized to UTC 00:00, as indicated by the trailing "Z".
</dd>
<dt>
updated
</dt>
<dd>
DID document metadata SHOULD include an <code>updated</code> property
to indicate the timestamp of the last <a href="#update">Update operation</a>.
This property MAY not be supported by a given <a>DID method</a>.
The value of
the property MUST follow the same formatting rules as the <code>created</code>
property.
</dd>
</dl>

</section>

</section>
Expand Down Expand Up @@ -3516,6 +3489,30 @@ <h2>
</pre>

<p>
The next example demonstrates a JSON-encoded metadata structure that might be
used as <a href="#did-document-metadata-properties">DID document metadata</a> to
describe timestamps associated with the DID document.
</p>

<pre class="example" title="JSON-encoded DID document metadata example">
{
"created": "2019-03-23T06:35:22Z",
"updated": "2023-08-10T13:40:06Z"
}
</pre>

<p>
This example corresponds to a metadata structure of the following format:
</p>

<pre class="example" title="DID document metadata example">
«[
"created" → "2019-03-23T06:35:22Z",
"updated" → "2023-08-10T13:40:06Z"
</pre>

</section>

</section>
Expand Down Expand Up @@ -3703,8 +3700,8 @@ <h2>
</ul>

<p>
Non-repudiation is further supported if timestamps are included (see Sections
<a href="#created"></a> and <a href="#updated"></a>) and the target <a>DLT</a>
Non-repudiation is further supported if timestamps are included (see Section
<a href="#did-document-metadata-properties"></a>) and the target <a>DLT</a>
system supports timestamps.
</p>
</section>
Expand Down