The CCG document in referred to (VC-API) is very normative like, and the CCG might consider it as the subject of a new WG. If published as a WG Note, the Rec-track evolution becomes also impossible.
The issue was discussed in a meeting on 2024-09-26
no resolutions were taken
View the transcript
#### 1.2. Removed the reference to an HTTP spec from the "Other deliverables" list (pr vc-wg-charter#126)
_See github pull request [vc-wg-charter#126](https://github.com/w3c/vc-wg-charter/pull/126)._
**Ivan Herman:** this one refers specifically to the reference to a CCG document on HTTP API for digital credentials, it was said that this document is normative looking, either it should be listed as a deliverable/rec track document or be removed.
… we have discussed this separately, it turned out the CCG intends to potentially submit that document to either this WG or a later incarnation as a rec track document, which for me means that it must be removed from the charter as is right away.
… in the last change of W3C process, it's no longer a real thing to create a WG note which then is turned into a rec track document later, for some reason that is now frowned upon.
… counterproductive to have this doc as a deliverable/WG note.
… should immediately remove this.
… also would satisfy commenter.
… any pros/cons?
**Manu Sporny:** +1 to remove it, the intention is to take it rec track, cannot publish as note.
**Ivan Herman:** I will merge this PR.
The CCG document in referred to (VC-API) is very normative like, and the CCG might consider it as the subject of a new WG. If published as a WG Note, the Rec-track evolution becomes also impossible.
Preview | Diff