-
Notifications
You must be signed in to change notification settings - Fork 30
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
Framing of fields with the same IDs #44
Comments
@kdimak thanks for reporting. The trouble is that in order to bring the library to better compliance with Framing 1.1 spec, the framing implementation requires a full rewrite. It's not a huge job, a couple of days of coding, but it's not done yet. Until then, I wouldn't recommend using the library for any framing beyond the 1.0 logic. I see you have a workaround. How critical is it for you to get this issue fixed? Are you using framing extensively? |
hi @kazarena ! thank you for your input! We are using the framing for the generation of Selective Disclosures for Verifiable Credentials. JSON-LD framing suits perfectly for this purpose. Yes, we already have a very simple workaround - to rename duplicated IDs with some unique random strings, execute the framing and then restore the IDs. We can for sure wait for the proper rewrite from your side, and just thank you very much for your fast feedback and friendly approach! |
@kdimak, it sounds like a worthy cause. I'll prioritise the framing update. |
If the input JSON-LD document contains two sibling fields with the same
id
, then it's possible that framing is applied on the wrong element.Example test code (note that
issuer
andcredentialSubject
have the sameid
did:example:b34ca6cd37bbf23
:The output JSON-LD is wrong and looks like the following:
Here all the fields from
credentialSubject
got copied to theissuer
without proper framing, whileissuer
is empty.It works properly at JSON-LD playground though (link).
The text was updated successfully, but these errors were encountered: