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

Add render property to a core VC data model #928

Closed
philarcher opened this issue Sep 15, 2022 · 9 comments
Closed

Add render property to a core VC data model #928

philarcher opened this issue Sep 15, 2022 · 9 comments
Assignees
Labels

Comments

@philarcher
Copy link

At TPAC 2022, we briefly discussed the need for a presentation layer, or a hook for a presentation layer, so that creds can be presented in a way the issuer wants (branding, layout etc). We may not need to define the presentation layer but we need to consider how they will be presented and may need to include one or more hooks.

@philarcher philarcher self-assigned this Sep 15, 2022
@msporny msporny removed the v2.0 label Oct 22, 2022
@msporny
Copy link
Member

msporny commented Oct 22, 2022

This issue is related to this RWOT11 pre-reading paper and this draft paper.

@decentralgabe
Copy link
Contributor

This is related to the Wallet Rendering work item in the DIF

@Sakurann Sakurann changed the title Presentation hook Add render property to a core VC data model Jan 18, 2023
@Sakurann
Copy link
Contributor

[editor's call] concrete proposals welcomed.

@OR13
Copy link
Contributor

OR13 commented Jan 18, 2023

We use JSON Schema Form and JSON Schema for this: https://w3c-ccg.github.io/traceability-vocab/#Template

@melvincarvalho
Copy link

Chiming in late, I hope that's OK

Good to see this discussed here. I raised this topic in the SWICG last week:

https://lists.w3.org/Archives/Public/public-swicg/2023May/0142.html

During the Social Web Working Group which started in 2014, there was a deliverable in the charter to deliver :

A document that defines a specification for a client-side API that lets developers embed and format third party information such as social status updates inside Web applications

IMHO, this was never fully realized, partly because tooling was not there back in 2016.

Do you think these two use cases could be merged into a joint effort, or are they too far apart?

@Sakurann Sakurann added the pending close Close if no objection within 7 days label Jun 22, 2023
@Sakurann
Copy link
Contributor

PR #1035 was closed

@brentzundel
Copy link
Member

This issue will be resolved when PR #1142 is merged.

@brentzundel brentzundel removed the pending close Close if no objection within 7 days label Jun 23, 2023
@Sakurann
Copy link
Contributor

Sakurann commented Jul 5, 2023

addressed in #1108

@Sakurann Sakurann closed this as completed Jul 5, 2023
@iherman
Copy link
Member

iherman commented Jul 6, 2023

The issue was discussed in a meeting on 2023-07-05

  • no resolutions were taken
View the transcript

2.7. (issue vc-data-model#928)

See github issue vc-data-model#928.

Orie Steele: I suggest closing, we have addressed this in the reserved terms table.

Manu Sporny: +1 to close, agree w/ Orie, we're done here.

Kristina Yasuda: I don't understand why this is dependent on a PR 1142.

Orie Steele: I will drop the confidenceMethod part of #1142 if CCG does not adopt the proposal.

Orie Steele: +1 manu, it adds links.

Brent Zundel: The PR does both confidence method and render method.

Manu Sporny: This issue is about adding render method to VCDM.
… I think we can close this issue.

Kristina Yasuda: Render method is already in as a reserved property.
… Closing it.

Manu Sporny: That's the PR we added renderMethod reservation in #1108.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants