Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/vc-wg-charter issues and pull requests
#126 - Removed the reference to an HTTP spec from the "Other deliverables" list
Pull Request -
State: closed - Opened by iherman 5 months ago
- 1 comment
#125 - Checking the liaison statements
Pull Request -
State: closed - Opened by iherman 5 months ago
- 1 comment
#124 - Changes asked for by Digital Bazaar during AC review
Pull Request -
State: closed - Opened by iherman 6 months ago
Labels: AC Review Comment
#123 - Add liaison statement for SPICE
Pull Request -
State: closed - Opened by brentzundel 6 months ago
- 2 comments
#122 - Adding an entry of coordination with the FedId WG.
Pull Request -
State: closed - Opened by iherman 8 months ago
- 2 comments
#121 - Sync with official charter template + removal of irrelevant parts
Pull Request -
State: closed - Opened by iherman 8 months ago
- 4 comments
#120 - Added the introduction of BBS into the history table
Pull Request -
State: closed - Opened by iherman 8 months ago
#119 - Adding at risk features to charter exception on class 4 changes
Pull Request -
State: closed - Opened by iherman 9 months ago
- 1 comment
#118 - Updated the document admin entries
Pull Request -
State: closed - Opened by iherman 9 months ago
- 1 comment
#117 - Added the reference to the controller document
Pull Request -
State: closed - Opened by iherman 9 months ago
- 1 comment
#116 - Conditional Normative Specifications table items
Issue -
State: closed - Opened by iherman 10 months ago
- 3 comments
#115 - Should the Controller Document specification be in scope for the revised charter?
Issue -
State: closed - Opened by decentralgabe 10 months ago
- 5 comments
#114 - Two years continued restrictions on deliverables is problematic
Issue -
State: closed - Opened by jandrieu 10 months ago
- 16 comments
#113 - Extension 2024
Pull Request -
State: closed - Opened by iherman 11 months ago
- 1 comment
#112 - Extension proposal for the coming two years
Pull Request -
State: closed - Opened by iherman 11 months ago
- 3 comments
#111 - Request for Explicit Interop Test Suites from Mozilla
Pull Request -
State: closed - Opened by mprorock over 2 years ago
- 10 comments
#110 - Added coordination with APA
Pull Request -
State: closed - Opened by iherman almost 3 years ago
- 1 comment
#109 - Adding registry content reference
Pull Request -
State: closed - Opened by iherman almost 3 years ago
#108 - APA would like a liaison statement
Issue -
State: closed - Opened by iherman almost 3 years ago
- 4 comments
#107 - updating algorithms-related reference documents for jwt-vcs
Pull Request -
State: closed - Opened by Sakurann almost 3 years ago
- 2 comments
#106 - Editorial fix: Remove an unnecessary period
Pull Request -
State: closed - Opened by shigeya almost 3 years ago
- 1 comment
#106 - Editorial fix: Remove an unnecessary period
Pull Request -
State: closed - Opened by shigeya almost 3 years ago
- 1 comment
#105 - Add Koblitz ECDSA Recovery Cryptosuite
Pull Request -
State: closed - Opened by clehner almost 3 years ago
- 5 comments
#104 - Clean up capitalization.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 2 comments
#104 - Clean up capitalization.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 2 comments
#103 - remove redundant registry section
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
#103 - remove redundant registry section
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
#102 - renaming a deliverable to "Securing Verifiable Credentials 1.0"
Pull Request -
State: closed - Opened by Sakurann almost 3 years ago
- 1 comment
#102 - renaming a deliverable to "Securing Verifiable Credentials 1.0"
Pull Request -
State: closed - Opened by Sakurann almost 3 years ago
- 1 comment
#101 - Registries and standardized entries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 5 comments
#100 - A non-exhaustive set of possible input documents for registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 3 comments
#100 - A non-exhaustive set of possible input documents for registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 3 comments
#99 - A non-exhaustive set of possible registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 5 comments
#99 - A non-exhaustive set of possible registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 5 comments
#98 - The WG may produce registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 3 comments
#98 - The WG may produce registries
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 3 comments
#97 - Definition of all key formats are left out of scope of the VC data model and crypto suites
Issue -
State: closed - Opened by kdenhartog almost 3 years ago
- 4 comments
Labels: future VCWG conversation
#97 - Definition of all key formats are left out of scope of the VC data model and crypto suites
Issue -
State: closed - Opened by kdenhartog almost 3 years ago
- 4 comments
Labels: future VCWG conversation
#96 - Clarify that DI should focus on VCs but ensure generality.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 14 comments
#96 - Clarify that DI should focus on VCs but ensure generality.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 14 comments
#95 - Add conditional normative deliverables for post-quantum crypto and other externally standardized primitives
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 1 comment
#94 - Rename a duplicated id
Pull Request -
State: closed - Opened by jyasskin almost 3 years ago
- 1 comment
#93 - Complete the list of known cryptosuites of interest for standardization.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 1 comment
#93 - Complete the list of known cryptosuites of interest for standardization.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 1 comment
#92 - Add input documents column to conditional deliverables
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 2 comments
#92 - Add input documents column to conditional deliverables
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 2 comments
#91 - Fix botched merge to main for "Other Deliverables" section.
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 1 comment
#90 - conditional deliverables section should have an input documents section
Issue -
State: closed - Opened by brentzundel almost 3 years ago
#90 - conditional deliverables section should have an input documents section
Issue -
State: closed - Opened by brentzundel almost 3 years ago
#89 - Environmental, Ethical and Social Implications of the Work
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 7 comments
Labels: future VCWG conversation
#89 - Environmental, Ethical and Social Implications of the Work
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 7 comments
Labels: future VCWG conversation
#88 - algorithms-related input documents for all proofs of integrity types
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 12 comments
#87 - rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0"
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 6 comments
#87 - rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0"
Issue -
State: closed - Opened by Sakurann almost 3 years ago
- 6 comments
#86 - Refactor "Other Deliverables" section
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 2 comments
#85 - Add Deliverables section on Registries
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 6 comments
#85 - Add Deliverables section on Registries
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 6 comments
#84 - Add JwtProof2020 to the charter
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 11 comments
Labels: future VCWG conversation
#84 - Add JwtProof2020 to the charter
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 11 comments
Labels: future VCWG conversation
#83 - New PR needed if did:key/multibase is going to be in scope
Issue -
State: closed - Opened by bumblefudge almost 3 years ago
- 6 comments
#83 - New PR needed if did:key/multibase is going to be in scope
Issue -
State: closed - Opened by bumblefudge almost 3 years ago
- 6 comments
#82 - Normatively defined crypto suites MUST fully define both public and private key representations
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 38 comments
#82 - Normatively defined crypto suites MUST fully define both public and private key representations
Issue -
State: closed - Opened by OR13 almost 3 years ago
- 38 comments
#81 - This should be LEVEL 2 not VERSION 2
Issue -
State: closed - Opened by nadalin almost 3 years ago
- 11 comments
#80 - Clarify IETF liaison
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 5 comments
#79 - Clarify Acronyms
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 2 comments
#79 - Clarify Acronyms
Pull Request -
State: closed - Opened by brentzundel almost 3 years ago
- 2 comments
#78 - Clarification on supported proof types
Issue -
State: closed - Opened by awoie almost 3 years ago
- 6 comments
Labels: has-pr
#78 - Clarification on supported proof types
Issue -
State: closed - Opened by awoie almost 3 years ago
- 6 comments
Labels: has-pr
#77 - Refactor WG inputs and outputs to follow (approved) WebApps Charter style
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 9 comments
#77 - Refactor WG inputs and outputs to follow (approved) WebApps Charter style
Pull Request -
State: closed - Opened by msporny almost 3 years ago
- 9 comments
#76 - Simplify VCDI deliverable
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 9 comments
#76 - Simplify VCDI deliverable
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 9 comments
#75 - Add links to VC Data Model for intro
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 3 comments
#75 - Add links to VC Data Model for intro
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 3 comments
#74 - Add clarification to description of non-normative deliverables
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 3 comments
#74 - Add clarification to description of non-normative deliverables
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 3 comments
#73 - Add links from stalled prs
Pull Request -
State: closed - Opened by OR13 about 3 years ago
- 6 comments
#72 - Some of the "other deliverables" raise patent concerns
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 8 comments
Labels: future VCWG conversation
#72 - Some of the "other deliverables" raise patent concerns
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 8 comments
Labels: future VCWG conversation
#71 - Add a link to the test suite for VC-JWT & JsonWebSignature2020
Issue -
State: closed - Opened by OR13 about 3 years ago
- 1 comment
#71 - Add a link to the test suite for VC-JWT & JsonWebSignature2020
Issue -
State: closed - Opened by OR13 about 3 years ago
- 1 comment
#70 - Normative specification of APIs or protocols is out of scope
Pull Request -
State: closed - Opened by selfissued about 3 years ago
- 2 comments
#69 - Add ACLU as liaison.
Pull Request -
State: closed - Opened by msporny about 3 years ago
- 5 comments
#69 - Add ACLU as liaison.
Pull Request -
State: closed - Opened by msporny about 3 years ago
- 5 comments
#68 - Be clear that defining some fields means defining the ceremonies they point to
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 14 comments
#68 - Be clear that defining some fields means defining the ceremonies they point to
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 14 comments
#67 - Each registry should include at least one standardized entry
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 25 comments
Labels: has-pr
#67 - Each registry should include at least one standardized entry
Issue -
State: closed - Opened by jyasskin about 3 years ago
- 25 comments
Labels: has-pr
#66 - Clarify some non-normative deliverables, as well as explicit not in scope items
Pull Request -
State: closed - Opened by mprorock about 3 years ago
- 17 comments
#65 - Meta issue on the VCDI deliverable
Issue -
State: closed - Opened by iherman about 3 years ago
- 3 comments
Labels: has-pr
#65 - Meta issue on the VCDI deliverable
Issue -
State: closed - Opened by iherman about 3 years ago
- 3 comments
Labels: has-pr
#64 - v2 Test Suite
Issue -
State: closed - Opened by OR13 about 3 years ago
- 5 comments
Labels: pending close
#64 - v2 Test Suite
Issue -
State: closed - Opened by OR13 about 3 years ago
- 5 comments
Labels: pending close
#63 - Add ECDSA secpr1 cryptosuite to VCWG input documents.
Pull Request -
State: closed - Opened by msporny about 3 years ago
- 15 comments
#63 - Add ECDSA secpr1 cryptosuite to VCWG input documents.
Pull Request -
State: closed - Opened by msporny about 3 years ago
- 15 comments
#62 - Data Integrity Crypto Suite Registry
Issue -
State: closed - Opened by OR13 about 3 years ago
- 7 comments
Labels: has-pr
#62 - Data Integrity Crypto Suite Registry
Issue -
State: closed - Opened by OR13 about 3 years ago
- 7 comments
Labels: has-pr
#61 - Proposed work mode for charter development
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 1 comment
#61 - Proposed work mode for charter development
Pull Request -
State: closed - Opened by brentzundel about 3 years ago
- 1 comment