Dynamic update-ability of Render Methods.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- backend-api-design
Research direction
No files, tests, or entry points are named. Start by reviewing the Render Method specification and the existing discussions about remote resources and digestMultibase, then define the documentation requirement and architecture decision before implementation.
Written by the indexing model from the issue text.
Description
One of the common use cases and expectations for remotely referenced render methods is that they could be updated dynamically if/when branding or designs changed. However, that does not seem possible--even if remotely referenced--as the specific Render Method template resource is always bound to the credential at issuance time. This is certainly true if the template is stored "statically" within the credential, but it is also true for remote resources if/when a digestMultibase is included for stability or security.
So, if a render method includes both a remote URL and a digest, that credential MUST be reissued if/when the Render Method for it needs to be altered.
First, we should call out that requirement--and the risks of not including a digestMultibase value.
Second, we may also want to consider an alternative architecture where Render Methods are provided relative to credential types and context URLs vs. directly "within" the credential. Such an architecture would give more control over render method distribution--tying it to context publication (most likely)--and could lean on our other work such as VC Recognized Entities for the "authority" (and provenance and security) of those renderers.
This feels like an essential point that we've overlooked during our other conversations.
Cheers!
🎩
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from w3c/vc-render-method
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
w3c/vc-render-method#71 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
w3c/vc-render-method#81 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
w3c/vc-render-method#79 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/vc-render-method#78 · 2 comments · 1 reaction ·
-
discuss
Difficulty 5/5 Over a week Newbie friendliness 25/100
w3c/vc-render-method#77 ·
All issues in w3c/vc-render-method
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100