Re: Verifiable Credentials Data Model v1.2 ready for review

(Cc Philippe)

Manu, all,

this document will be published under the 2021 process, coming into effect on the 2nd of November:

https://www.w3.org/2021/Process-20211102/ <https://www.w3.org/2021/Process-20211102/>

This means that the relevant sections are 

https://www.w3.org/2021/Process-20211102/#revised-rec-substantive <https://www.w3.org/2021/Process-20211102/#revised-rec-substantive>
https://www.w3.org/2021/Process-20211102/#last-call-review <https://www.w3.org/2021/Process-20211102/#last-call-review>

although, I believe, the changes are cosmetic (eg, change in terminology: we are talking about candidate and proposed amendments…). Better check, though.

I also believe that, for the Proposed Amendment, what is necessary for review is not a full diff, but a version where all the markup and editorial changes are incorporated into the document and would only show the substantive changes. On practical terms, the document to review should look as the final document (eg, final status, etc) but would include the diff for the substantive changes.

Philippe, did I get this right?

Ivan


> On 26 Oct 2021, at 05:02, Manu Sporny <msporny@digitalbazaar.com> wrote:
> 
> Hi all,
> 
> The Verifiable Credentials Data Model v1.2 specification is ready for review.
> The latest version, which is targeted for a 2022-01-18 publication, can be
> viewed here:
> 
> https://htmlpreview.github.io/?https://github.com/w3c/vc-data-model/blob/main/REC/2022-01-18/index.html
> 
> The diff-marked version (with all changes highlighted) can be viewed here:
> 
> https://htmlpreview.github.io/?https://github.com/w3c/vc-data-model/blob/main/REC/2022-01-18/diff.html
> 
> Per the new W3C Process for Revising a Recommendation with Substantive
> Changes[1], we are required to request a Last Call for Review of Proposed
> Changes[2] to the W3C Advisory Committee.
> 
> Specifically:
> 
> 1. This is a Last Call for Review of Proposed Corrections.
> 
> 2. The proposed changes (proposed corrections) include:
> 
> * Update previous normative references that pointed to
>  RFC3339 for datetime details to now normatively
>  reference the datetime details described in
>  XMLSCHEMA11-2 which more accurately reflects the usage
>  in examples and libraries.
> 
> * Loosen the requirement to use URLs to use URIs in the id
>  property of the credentialStatus and refreshService
>  sections of the data model.
> 
> * Loosen normative statements in the zero-knowledge proofs
>  section to enable compliance of new zero-knowledge proof
>  schemes, such as BBS+, that have been created since the
>  v1.0 specification was published as a Recommendation.
> 
> * Update all references to point to the latest version of
>  the referenced specifications. Fix broken links to
>  papers that have become unavailable to updated locations
>  where the papers are available.
> 
> 3. Review comments are expected by December 31st 2021.
> 
> 4. This document reflects the latest implementation
>   experience as reported to the VCWG and accepted
>   based on the consensus of the group. Please review the
>   document and provide feedback before December 31st
>   2021.
> 
> -- manu
> 
> [1]https://www.w3.org/2020/Process-20200915/#revised-rec-substantive
> [2]https://www.w3.org/2020/Process-20200915/#last-call-review
> 
> -- 
> Manu Sporny - https://www.linkedin.com/in/manusporny/
> Founder/CEO - Digital Bazaar, Inc.
> News: Digital Bazaar Announces New Case Studies (2021)
> https://www.digitalbazaar.com/
> 
> 


----
Ivan Herman, W3C 
Home: http://www.w3.org/People/Ivan/
mobile: +33 6 52 46 00 43
ORCID ID: https://orcid.org/0000-0003-0782-2704