W3C VC API
Ayrıca şöyle anılır VC API, Verifiable Credentials API, CCG VC API
VC API describes HTTP endpoints for issuing, verifying and managing verifiable credentials. It is the most commonly cited thing in this space whose status is routinely misdescribed.
Community Group is not Working Group
W3C Community Groups are open to anyone and publish reports. Working Groups operate under the Patent Policy and produce Recommendations. VC API comes from a Community Group, so it carries neither the process guarantees nor the patent commitments a Recommendation does. That does not make it worthless; it makes "W3C standard" the wrong phrase for it.
Why an implementer might still skip it
Because the same operations already have widely deployed definitions in OID4VCI and OID4VP, and implementing two HTTP surfaces for one capability doubles the surface without doubling the reach.
Where Solidus sits
Not implemented, deliberately. Worth restating whenever a requirement cites it: the underlying request is interoperability, and that is answerable with the protocols we do implement.
Nereden geliyor
Bunu başkası belirtti. Solidus bir araya getiriyor.
Produced by the W3C Credentials Community Group, which is a Community Group and not a Working Group. The distinction is load-bearing: its output is a CCG draft report, not a W3C Recommendation, and it is not on the Recommendation track. Anyone citing it as a W3C standard is overstating its status.
Bunu nasıl doğrularsınız
Solidus bunu inşa etmedi. Girdi kavramı açıklıyor.
The draft is public on the CCG's GitHub. Its status line is the checkable part: it says Draft Community Group Report, which is what distinguishes it from the Recommendation-track documents in this Lexicon.