Skip to content
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

[To Discuss] Discuss PDF VCs #4

Open
kimdhamilton opened this issue Oct 3, 2020 · 7 comments
Open

[To Discuss] Discuss PDF VCs #4

kimdhamilton opened this issue Oct 3, 2020 · 7 comments
Assignees

Comments

@kimdhamilton
Copy link
Contributor

Discuss use of PDF as the verifiable credential wrapper, involving PDF with embedded JSON-LD/RDF

@kimdhamilton kimdhamilton transferred this issue from another repository Oct 3, 2020
@ottonomy
Copy link

  • Goal: We want something that can be consumed by a machine and by a human.
  • What is the relationship between the machine-readable data proposed to be embedded in the PDF and the data displayed to humans? There seems to be a strong potential for there to be different information stored in the JSON-LD layer vs in the human-readable layer. What would be the mechanism to prevent the human-readable and machine-readable data from diverging significantly? (because if they diverge, we're not getting the stated benefit of having both human and machine-readable data in one file)
  • "It is two separate pieces of data, they are just tightly bound to one another"
  • Brazilian Transcripts use case. There was an XML grammar that they define. "That data becomes displayed as well as machine readable."
    • Take a chunk of XML, put it inside a PDF/A-3 format
  • There was a slide showing CSV embedded in a PDF. How is the example CSV connected to the data shown in the visual display? Is it actually processed in producing the visual presentation of the table in the PDF? It seems no, that there is separate data that is linked from attachments to document sections.
  • If we try to solve the above problem and get the credential data itself to be visually displayed instead of copying it into a visual display, how do you avoid the necessity of putting extra junk only intended to control the visual display into the credential data?
  • Does combining PDFs break the signatures?
  • With PDFs, you can optionally declare a "relationship" string to describe the purpose for which attached data is embedded in the PDF.
  • You can also define a "schema" for data.
  • It is possible to search inside attachments.

@karask
Copy link

karask commented Oct 21, 2020

I am interested in this as well !

@kimdhamilton kimdhamilton transferred this issue from w3c-ccg/vc-ed-models Nov 9, 2020
@vickstar666
Copy link

vickstar666 commented Nov 9, 2020 via email

@kayaelle kayaelle added the question Further information is requested label Oct 4, 2021
@kayaelle
Copy link
Collaborator

@OR13 do you have suggestions on how to move this topic forward? It doesn't seem specific to EDU and it was mentioned that this topic is of interest to you. Related: #3

@kayaelle kayaelle added the help wanted Extra attention is needed label Oct 15, 2021
@OR13
Copy link

OR13 commented Oct 18, 2021

I've seen VC embedded in PDFs a view ways.

  1. CBOR-LD / optical encoding via QR code (of content)
  2. optical encoding via QR code (of link to content)
  3. embedding JSON directly
  4. encoding JSON as a table / decoding JSON again.

I would avoid attempting to embed a VC in PDF using PDF internals and I would stick to portable solutions (things that work for images generally).

@kayaelle kayaelle added review next Review next meeting and removed help wanted Extra attention is needed labels Dec 6, 2021
@kayaelle
Copy link
Collaborator

kayaelle commented Dec 6, 2021

Labeling to review at next meeting to gather feedback on OR13's answer.

@kayaelle
Copy link
Collaborator

The task force suggested that we reach back out to Leonard Rosenthol at Adobe to update us on this topic.

Discussed at these calls:

@kayaelle kayaelle added meeting topic and removed question Further information is requested review next Review next meeting labels Feb 16, 2022
@kayaelle kayaelle self-assigned this Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants