...
- JSON Responses for the Registration Data Access Protocol (RDAP)
- Verifiable Credentials Data Model v2.0
Info | ||
---|---|---|
| ||
Status: ToIP Task Force Draft |
Scope - required
Short introductory paragraph
...
New text to be defined by this TF
Examples:
Expand | ||
---|---|---|
| ||
Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. |
Expand | ||
---|---|---|
| ||
This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at https://www.w3.org/TR/. |
Expand | ||
---|---|---|
| ||
These materials are made available under and are subject to the The Open Web Foundation Agreements (This specification is subject to the OWF Contributor License Agreement 1.0 - Copyright available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfaowf-contributor-license-agreement-1-0) THESE MATERIALS ARE PROVIDED “AS IS.” The Trust Over IP Foundation, established as the Joint Development Foundation Projects, LLC, Trust Over IP Foundation Series ("ToIP"), and its members and contributors (each of ToIP, its members and contributors, a "ToIP Party") expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the materials. The entire risk as to implementing or otherwise using the materials is assumed by the implementer and user. IN NO EVENT WILL ANY ToIP PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THESE MATERIALS, ANY DELIVERABLE OR THE ToIP GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE |
...
If source code is included in the specification, that code is subject to the Apache 2.0 license unless otherwise marked. In the case of any conflict or confusion within this specification between the OWF Contributor License and the designated source code license, the terms of the OWF Contributor License shall apply. These terms are inherited from the Technical Stack Working Group at the Trust over IP Foundation. Working Group Charter |
Conventions - required
Expand | ||
---|---|---|
| ||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. |
Terms and Definitions - recommended
The following terms are used to describe concepts in this specification.
decentralized identifier (DID)
definition
key event log (KEL)
definition
Info |
---|
Terms are listed in lower case, alphabetical order and used inside the specification in lower case, unless being referred to by a defined acronym. Linking back to the definition of a term using the spec-up [[ref: ]] macro is left to the authors discretion.A suggested use would in a new section, or where the term has been previous defined and context may have been lost to the reader. |
Content Title
Wonderful specification content.
...
Considerations - recommended
Info |
---|
May include but not limited to IANA/Security Considerations listed by title in alphabetical order |
References - recommended
Info | ||
---|---|---|
| ||
Reference should use the Markdown . (period) : (colon) syntax.
These can then be used inline by using [1]. |
Revision History - recommended
format TBD
Annex - optional
a supplementary document or section that is added to the main document to provide additional information that is not included in the main body. An annex can be a separate document or a part of the main document, but it is always attached at the end of the document.
Appendix - optional
a section that is added to the end of a document to provide additional information that is related to the main body of the document. An appendix can contain any type of information that supports the main content, such as charts, graphs, tables, images, or detailed descriptions.