Fwd: Verifiable Credentials Data Model 1.0 is a W3C Candidate Recommendation (Call for Implementations)

---------- Forwarded message ---------
From: xueyuan <xueyuan@w3.org>
Date: Thu, Mar 28, 2019 at 6:01 AM
Subject: Verifiable Credentials Data Model 1.0 is a W3C Candidate
Recommendation (Call for Implementations)
To: <w3c-ac-forum@w3.org>
Cc: <chairs@w3.org>



Dear Advisory Committee Representative,
Chairs,

I am pleased to announce that Verifiable Credentials Data Model 1.0 is a
W3C Candidate Recommendation:
https://www.w3.org/TR/2019/CR-verifiable-claims-data-model-20190328/

The approval and publication are in response to this transition request:
   https://lists.w3.org/Archives/Member/chairs/2019JanMar/0143.html

Please provide feedback by 25 April 2019 as follows:
Raise an issue on GitHub:
   https://github.com/w3c/vc-data-model/issues/

A document with the test suite, how to test, etc. is at:
   https://github.com/w3c/vc-test-suite/

Patent disclosures relevant to this specification may be found on the
Verifiable Claims Working Group's patent disclosure page in conformance
with W3C policy:
   https://www.w3.org/2004/01/pp-impl/98922/status

This Call for Implementations follows section 6.4 "Candidate
Recommendation" of the W3C Process Document:
   https://www.w3.org/2019/Process-20190301/#candidate-rec

Thank you,

For Tim Berners-Lee, Director, and
Philippe Le Hégaret, Project Management Lead;
Xueyuan Jia, W3C Marketing & Communications

==============================================
Quoting from
Verifiable Credentials Data Model 1.0
W3C Candidate Recommendation 28 March 2019

This version:
https://www.w3.org/TR/2019/CR-verifiable-claims-data-model-20190328/
Latest published version:
   https://www.w3.org/TR/verifiable-claims-data-model/

Abstract:
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.

Status of This Document:
This section describes the status of this document at the time of its
publication. Other documents may supersede this document. 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/.

Comments regarding this document are welcome. Please file issues
directly on GitHub, or send them to public-vc-comments@w3.org
(subscribe, archives).

The Working Group seeks implementation feedback, having set the
requirement of at least two implementations of each feature as the exit
criteria for the Candidate Recommendation phase. The group aims to
obtain reports from two producers and two consumers for each feature if
possible. For details, see the test suite and sample implementation report.

The following features are considered at risk of removal due to
potentially insufficient implementation experience (reports):
credentialSchema property, refreshService property, evidence property,
zero-knowledge proof support, disputedClaim property, JWT support,
nonTransferable property.

Changes since the last publication of this document include:

* Editorial modifications to group similar information together and make
the document flow easier to navigate.
* Added a Concrete Lifecycle Example.
* Modified conformance statements to ensure that all conformance
statements are testable.
* Renamed subject to credentialSubject.
* Clarified that verifiable credentials and verifiable presentations
MUST include the @context property and that for a VC or VP to be
verifiable at least one proof mechanism MUST be expressed: external or
embedded.
* Clarified that a VC MUST contain the issuer and issuanceDate properties.
* Significant clarifying text added for Zero-Knowledge and JWT use.
* Added section on Proof Formats.
* Clarified JSON-LD Context URLs and their cache-ability.
* Refactored Verification section to a non-normative Validation section.
* Marked a number of features as features at risk and documenting
implementation details that may change based on feedback from implementers.
* Privacy, Security, Accessibility, and (new) Internationalization
Considerations all promoted to top level.
* Moved some content out to an Implementation Guidance document.

This document was published by the Verifiable Claims Working Group as a
Candidate Recommendation. This document is intended to become a W3C
Recommendation.

GitHub Issues are preferred for discussion of this specification.
Alternatively, you can send comments to our mailing list. Please send
them to public-vc-comments@w3.org (archives).

W3C publishes a Candidate Recommendation to indicate that the document
is believed to be stable and to encourage implementation by the
developer community. This Candidate Recommendation is expected to
advance to Proposed Recommendation no earlier than 25 April 2019.

Please see the Working Group's implementation report.

Publication as a Candidate Recommendation 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.

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 contains Essential
Claim(s) must disclose the information in accordance with section 6 of
the W3C Patent Policy.

This document is governed by the 1 March 2019 W3C Process Document.
==============================================