GitHub / decentralized-identity/presentation-exchange issues and pull requests
#100 - Consider separation of embed target and transport-specific examples into their own sections in appendix
Issue -
State: open - Opened by wyc almost 5 years ago
- 5 comments
#99 - Should Submission Requirements take precedence over Input Descriptors?
Issue -
State: closed - Opened by decentralgabe almost 5 years ago
- 4 comments
Labels: documentation
#98 - new type of criterion in request for proof: which ledger backs the cred?
Issue -
State: closed - Opened by dhh1128 almost 5 years ago
- 7 comments
Labels: needs discussion
#97 - Example of embedding Presentation Definition in a target data structure
Issue -
State: closed - Opened by Sakurann almost 5 years ago
- 3 comments
Labels: last-call
#96 - "Descriptor for ID Tokens" example in Section 5.2 is lacking context & definition
Issue -
State: closed - Opened by pamelatech almost 5 years ago
- 2 comments
#95 - JSON Schema updates for Cred Formats
Pull Request -
State: closed - Opened by decentralgabe almost 5 years ago
#94 - PE Spec defines a well known did configuration object schemas
Issue -
State: closed - Opened by OR13 almost 5 years ago
- 4 comments
#93 - Differentiate format and type
Pull Request -
State: closed - Opened by decentralgabe almost 5 years ago
#92 - Examples that show support for regular OIDC flow
Issue -
State: open - Opened by awoie almost 5 years ago
- 7 comments
#91 - Bump prismjs from 1.20.0 to 1.21.0
Pull Request -
State: closed - Opened by dependabot[bot] almost 5 years ago
- 1 comment
Labels: dependencies
#90 - Terminology needs work.
Issue -
State: closed - Opened by OR13 almost 5 years ago
- 14 comments
Labels: documentation, terminology
#89 - Create repo_process_guidelines.md
Pull Request -
State: closed - Opened by bumblefudge almost 5 years ago
- 9 comments
#88 - Add mechanism to express support of cred formats/algos
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
- 14 comments
#87 - Suggestions -- add target data structure examples for Presentation Definition and pointers to details about the target data structures
Issue -
State: closed - Opened by swcurran about 5 years ago
- 3 comments
#86 - Added DIDComm submission example for #58, fixed spelling of DIDComm
Pull Request -
State: closed - Opened by swcurran about 5 years ago
#85 - Predicates
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
- 5 comments
#84 - Add 'subject_is_issuer' and 'subject_is_holder'
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
- 21 comments
#83 - Massive issue-slaying PR to address ALL THE THINGS (well, many of them)
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
- 2 comments
#82 - Remove word 'proofing'
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
#81 - Add section about 'presentation request'
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
- 2 comments
#80 - Change Subject/Prover to Holder
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
#79 - Line length
Pull Request -
State: closed - Opened by brentzundel about 5 years ago
- 2 comments
#78 - Contributor Guidelines document needed to issue call for broader community input
Issue -
State: closed - Opened by bumblefudge about 5 years ago
- 8 comments
Labels: high priority
#77 - Add Presentation Definition Schema; Add Locale to Existing Schemas
Pull Request -
State: closed - Opened by decentralgabe about 5 years ago
- 1 comment
#76 - Updated JSON Schemas; Add Presentation Definition Schema
Pull Request -
State: closed - Opened by decentralgabe about 5 years ago
#75 - Add localization support (#53)
Pull Request -
State: closed - Opened by decentralgabe about 5 years ago
- 2 comments
#74 - The ability to explicitly state expectations around revocation
Issue -
State: closed - Opened by swcurran about 5 years ago
- 8 comments
#73 - Create usage document
Issue -
State: open - Opened by csuwildcat about 5 years ago
#72 - Point to JSONPath section to address Issue #54
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#71 - Clarify concern from Issue #55 in note
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#70 - Update submission requirements
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#69 - Add credential manifest pointer mechanism to Input Descriptors
Issue -
State: closed - Opened by csuwildcat about 5 years ago
- 2 comments
#68 - Example VCs of submissions doesnt make sense
Issue -
State: closed - Opened by vongohren about 5 years ago
- 2 comments
#67 - Bump lodash from 4.17.15 to 4.17.19
Pull Request -
State: closed - Opened by dependabot[bot] about 5 years ago
Labels: dependencies
#66 - Add top-level name/purpose fields
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#65 - Generate better test vectors
Issue -
State: open - Opened by OR13 about 5 years ago
- 2 comments
#64 - Add sample implementation template
Pull Request -
State: closed - Opened by OR13 about 5 years ago
- 3 comments
#63 - Per-branch previews of the hosted spec
Issue -
State: closed - Opened by wyc about 5 years ago
- 2 comments
#62 - Add a constraint that specifies needing a number of the same input
Issue -
State: closed - Opened by csuwildcat about 5 years ago
- 1 comment
#61 - What are the requirements for the attribute selection language?
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 3 comments
#60 - Use of "subject" as a role is misleading
Issue -
State: closed - Opened by pamelatech about 5 years ago
- 4 comments
#59 - presentation submission json schema
Pull Request -
State: closed - Opened by decentralgabe about 5 years ago
#58 - support for did comm
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 9 comments
#57 - matching field type as well as path
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 9 comments
Labels: needs discussion
#56 - Count property to support range, rather than integer
Issue -
State: closed - Opened by jischr about 5 years ago
- 33 comments
#55 - input descriptor iteration algorithm
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 2 comments
#54 - JSON Path support
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 3 comments
#53 - localization support for text fields
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 3 comments
#52 - presentation definition sent via presentation request
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 5 comments
Labels: envelop
#51 - do we cover signatures on objects?
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 4 comments
Labels: envelop
#50 - support terms of service
Issue -
State: open - Opened by brentzundel about 5 years ago
- 6 comments
#49 - allow requestor to specify that supplied attributes must be self-attested
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 2 comments
Labels: high priority
#48 - clarify uses of 'proofing' vs 'proving'
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 1 comment
#47 - how to allow verifiers to require multiple credential inputs to be about same subject
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 8 comments
#46 - support ZKP-style predicate requests and selective disclosure
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 2 comments
Labels: high priority
#45 - refine path descriptions
Issue -
State: closed - Opened by brentzundel about 5 years ago
- 3 comments
#44 - Update Presentation Definition w/ basic example
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#43 - Make submission_requirement an array, not an object, rename to submission_requirements
Issue -
State: closed - Opened by csuwildcat about 5 years ago
- 13 comments
#42 - OneOf for Submission Requirement instead of AnyOf
Pull Request -
State: closed - Opened by decentralgabe about 5 years ago
- 2 comments
#41 - Add JSONPath as imported syntax
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
#40 - If validation is out of scope, say so, and say how it happens
Issue -
State: closed - Opened by selfissued about 5 years ago
- 1 comment
#39 - Provide examples of requesting claims in all the supported verified claims formats
Issue -
State: open - Opened by selfissued about 5 years ago
- 3 comments
#38 - The introduction needs to be clearer about the breadth of the scope and goals
Issue -
State: closed - Opened by selfissued about 5 years ago
- 1 comment
#37 - Reduce complexity of request syntax and state machine by eliminating labels
Issue -
State: open - Opened by selfissued about 5 years ago
- 8 comments
#36 - Converge the multiple active draft verified claims request specs that have similar goals
Issue -
State: closed - Opened by selfissued about 5 years ago
- 3 comments
Labels: last-call
#35 - Terminology matters: Use names that help readers build the right mental model
Issue -
State: closed - Opened by selfissued about 5 years ago
- 6 comments
Labels: terminology
#34 - Missing Generic Vocabulary for Transport Request/Response
Issue -
State: closed - Opened by pamelatech about 5 years ago
- 1 comment
#33 - Typo when referring to input_descriptors
Issue -
State: closed - Opened by pamelatech about 5 years ago
- 1 comment
#32 - Presentation Submission Blob Decoding
Issue -
State: closed - Opened by wyc about 5 years ago
- 1 comment
#31 - `schema.uri` MUST be an Array
Issue -
State: closed - Opened by wyc about 5 years ago
- 1 comment
#30 - Add support for limited disclosure
Pull Request -
State: closed - Opened by csuwildcat about 5 years ago
- 2 comments
#29 - Describe how domain and challenge are sent to the holder
Issue -
State: closed - Opened by wyc about 5 years ago
- 17 comments
Labels: security, envelop
#28 - Demonstrate proof of link secret constraints for fields
Issue -
State: closed - Opened by wyc about 5 years ago
- 2 comments
Labels: zkp
#27 - Ensure spec language requires that all fields in an input object come from the same credential.
Issue -
State: closed - Opened by wyc about 5 years ago
- 1 comment
Labels: high priority
#26 - Missing JSON-LD vocabulary for presentation-submissions
Issue -
State: closed - Opened by llorllale about 5 years ago
- 16 comments
Labels: bug
#25 - Add a include/exclude flag to constraints
Issue -
State: closed - Opened by erickuhn19 about 5 years ago
- 1 comment
#24 - Is issuer/prover relationship information appropriate within Presentation Exchange?
Issue -
State: closed - Opened by wyc about 5 years ago
- 31 comments
#23 - Do Presentation Definition objects need a nonce?
Issue -
State: closed - Opened by wyc about 5 years ago
- 3 comments
Labels: envelop
#22 - Examine other Rules Expression Language before building our own for Submission Requirement
Issue -
State: closed - Opened by wyc about 5 years ago
- 5 comments
#21 - Update README: include instructions on what to do before pushing
Issue -
State: closed - Opened by wyc about 5 years ago
- 6 comments
Labels: good first issue
#20 - Regenerate HTML Output
Pull Request -
State: closed - Opened by wyc about 5 years ago
#19 - Extend Submission Requirement for Arbitrary Logic
Pull Request -
State: closed - Opened by wyc about 5 years ago
- 3 comments
#18 - Add various notes and suggestions
Pull Request -
State: closed - Opened by dhh1128 about 5 years ago
- 18 comments
#17 - Rename "Transport Integrations" => "Embed Targets"
Issue -
State: closed - Opened by OR13 about 5 years ago
- 2 comments
#16 - Accept input from a schema with multiple versions
Issue -
State: closed - Opened by decentralgabe about 5 years ago
- 2 comments
#15 - Provide a way to express the format/encoding of mapped inputs
Issue -
State: closed - Opened by wyc about 5 years ago
- 23 comments
Labels: high priority
#14 - Add CHAPI Example to Spec
Pull Request -
State: closed - Opened by OR13 about 5 years ago
#13 - Attribute source enforcement
Issue -
State: closed - Opened by dtmcg over 5 years ago
- 3 comments
#12 - Subject Holder restriction
Issue -
State: closed - Opened by dtmcg over 5 years ago
- 10 comments
#11 - Input Selection via pure JSON Schema
Issue -
State: closed - Opened by rado0x54 over 5 years ago
- 4 comments
#10 - It's the Final Namedown! (duh nuh nuh nuuuh, duh na-na-nuuuh)
Issue -
State: closed - Opened by csuwildcat over 5 years ago
- 31 comments
#9 - Should we specify what signature/ZKP schemes a verifier supports?
Issue -
State: open - Opened by csuwildcat over 5 years ago
- 8 comments
#8 - Allow mapping of different VC properties to a common field in Proof Submissions
Issue -
State: closed - Opened by csuwildcat over 5 years ago
- 2 comments
#7 - Input Types: VC Type
Issue -
State: closed - Opened by dtmcg over 5 years ago
- 5 comments
#6 - add wg tag for dif website
Issue -
State: closed - Opened by OR13 over 5 years ago
#5 - Input Types: Raw Data
Issue -
State: closed - Opened by csuwildcat over 5 years ago
- 2 comments
#4 - Formatting changes
Pull Request -
State: closed - Opened by brentzundel over 5 years ago
- 3 comments
#3 - What existing presentation definition implementations are there?
Issue -
State: closed - Opened by brentzundel over 5 years ago
- 6 comments
Labels: question
#2 - Set-based selection logic vs boolean algebra selection logic
Issue -
State: closed - Opened by rado0x54 over 5 years ago
- 9 comments
#1 - Change Proof Definition to Presentation Definition
Pull Request -
State: closed - Opened by brentzundel over 5 years ago
- 3 comments