-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inline @context
in examples
#86
Comments
Yes, agreed.
Yes, agreed, it's unfortunate the tests include inline contexts. We should try to remove these if possible from the test vectors and the test suites. That said, we also don't want to destabilize implementations. /cc @BigBlueHat @PatStLouis @Wind4Greg -- what's the plan here? I suggest we switch to a driver's license, or PRC/EAD/NatCert example. |
another option could be |
Hi @filip26, @msporny, and all. Currently the VC-DI-ECDSA contains three selective disclosure examples/test vectors:
At this point I'd recommend dropping the windsurfing example which uses the "incline context" stuff. It did feature arrays and nesting that tested the SD primitives a bit more. However it also confused some folks resulting in another issue to be resolved. @filip26, @msporny, @dlongley and all let me know what you think. |
@Wind4Greg I'm fine with any solution that removes the inline contexts. The examples you listed could be retained with the example context, which would benefit the specification. (some related examples/vectors will need to be updated accordingly) |
+1 to removing the windsurfing example (as much as I like it)... the inline context is throwing some people. |
I think it's fine to remove the example that uses the inline context. |
PR #96 has been merged to address this issue; closing. |
Hi,
examples related to selective disclosure contain inline
@context
.Please see this discussion
w3c/vc-data-integrity#272
@vocab
should not be used in a production. Having it in examples, test vectors, could lead to confusion and security issues.(BTW an inline
@context
should be banned, it only adds complexity to processing that is vulnerable to issues, nothing else)The text was updated successfully, but these errors were encountered: