...
- JSON Responses for the Registration Data Access Protocol (RDAP)
- Verifiable Credentials Data Model v2.0
| Info |
|---|
|
Status: ToIP Task Force Draft
This version
Latest published version
Latest editor's draft
Editors
Authors
Feedback |
Scope - required
Short introductory paragraph
Examples:
| Expand |
|---|
|
This document describes JSON data structures representing
registration information maintained by Regional Internet Registries
(RIRs) and Domain Name Registries (DNRs). These data structures are
used to form Registration Data Access Protocol (RDAP) query
responses. This document obsoletes RFC 7483. |
...
| Expand |
|---|
|
Credentials are a part of our daily lives; driver's licenses are used
to assert that we are capable of operating a motor vehicle, university
degrees can be used to assert our level of education, and government-issued
passports enable us to travel between countries. This specification
provides a mechanism to express these sorts of credentials on the Web in a
way that is cryptographically secure, privacy respecting, and machine-verifiable. |
Foreword - required
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/.
The Working Group is actively seeking implementation feedback for this specification. In order to exit the Candidate Recommendation phase, the Working Group has set the requirement of at least two independent implementations for each mandatory feature in the specification. Please see the implementation report for more details.
Comments regarding this specification are welcome at any time. Please file issues directly on GitHub, or, if that is not possible, send them to public-vc-comments@w3.org (subscribe, archives).
This document was published by the Verifiable Credentials Working Group as a Candidate Recommendation Draft using the Recommendation track.
Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Draft integrates changes from the previous Candidate Recommendation that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes containsEssential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is governed by the 03 November 2023 W3C Process Document.
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/.
The Working Group is actively seeking implementation feedback for this specification. In order to exit the Candidate Recommendation phase, the Working Group has set the requirement of at least two independent implementations for each mandatory feature in the specification. Please see the implementation report for more details.
Comments regarding this specification are welcome at any time. Please file issues directly on GitHub, or, if that is not possible, send them to public-vc-comments@w3.org (subscribe, archives).
This document was published by the Verifiable Credentials Working Group as a Candidate Recommendation Draft using the Recommendation track.
Publication as a Candidate Recommendation does not imply endorsement by W3C and its Members. A Candidate Recommendation Draft integrates changes from the previous Candidate Recommendation that the Working Group intends to include in a subsequent Candidate Recommendation Snapshot.
This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document was produced by a group operating under the W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes containsEssential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document is governed by the 03 November 2023 W3C Process Document. |
| Expand |
|---|
|
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/owf-contributor-license-agreement-1-0-copyright. 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.
| Code Block |
|---|
[1]. Smith, Samuel M., Meta-Platforms and Cooperative Network-of-Networks Effects: Why Decentralized Platforms Will Eat Centralized Platforms. 2019/03/25 https://medium.com/selfrule/meta-platforms-and-cooperative-network-of-networks-effects-6e61eb15c586
[1]: https://medium.com/selfrule/meta-platforms-and-cooperative-network-of-networks-effects-6e61eb15c586 |
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.
