The Verifiable Credentials Guide W3C Community Note is TODO

TODO sotd = song of the day? The Marvelous Toy - Peter, Paul and Mary ;-)

TODO This paragraph is here to demonstrate that it is possible to add a completely custom piece of HTML inside the SotD.

TODO This document was published by the People Who Like To Write Specs Help Group as an Editor's Draft. If you wish to make comments regarding this document, please send them to spec-writers-anonymous@w3.org (subscribe, archives). All feedback is welcome.

TODO Publication as a Editor's Draft does not imply endorsement by the W3C Membership. 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.

TODO This document was produced by a group operating under the 5 February 2004 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 contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

Purpose

The intended audience for the [VC-GUIDE] ("Guide") is a broad range of professionals interested in furthering the application of Verifiable Credentials technology for use in software apps, agents, and services. The primary audience includes software architects, application developers, and user experience (UX) specialists; as well as other people involved in a broad range of standards efforts related to decentralized identity, verifiable credentials, and secure storage.

The purpose of the Guide is to satisfy the following goals and non-goals in a way that meets the needs of the intended audience.

Goals

    The primary goal of the Guide is to provide a first entry point or landing area to help readers:

  1. Locate each of the documents that are part of the collection of [VCWG] deliverables that, in turn, describe what Verifiable Credentials are and how to use them ("Documentation"); as well as how to test conformance of a Verifiable Credential implementation against the Documentation.
  2. Understand the purpose of each deliverable in the Documentation as well as understand the relationships between each pair of the deliverables (as appropriate).
  3. For specific key topics, understand where in the Documentation to look for help; for example, key topics might include Data Model, Conformance, Use Cases, Specific Data Platform Considerations, External Resources, etc.
  4. Project the Documentation as a comprehensive body of knowledge about Verified Credentials (or at least a great starting point).

Non-Goals

  1. The guide is not a Primer in the classic W3C sense. A list of Primer examples is available in the CCG mailing list.

Drivers

  1. TODO

Organization of the Document

TODO

Verifiable Credentials Documentation

TODO

Key Topics

TODO

Data Model

TODO

Use Cases

TODO

Data Platform Bindings

TODO

Data Platform Bindings

JavaScript Object Notation (JSON)

TODO

Linked Data Serialization using JavaScript Object Notation (JSON-LD)

TODO

JavaScript Object Notation Web Token (JWT)

TODO

JavaScript Object Notation (JSON)

TODO

Linked Data Serialization using JavaScript Object Notation (JSON-LD)

TODO

JavaScript Object Notation Web Token (JWT)

TODO

External Resources

TODO

Experimental Data Bindings

TODO

X.509 Public Key Certificates

TODO

Exchangeable Image File Format (EXIF) Compliant Media Files (e.g. JPEG photos)

TODO

C#/.NET Plain Old Class Objects (POCOs)

TODO

Next Steps

TODO