Registry for renderSuite values
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9
- Forks
- 8
- Avg merge
- 14d 42m
- Merged PRs (30d)
- 2
Description
With dispatch moving from type to renderSuite (#54), new render suites can be defined without touching the core VC @context. That means the suite values themselves need a home:
- Where are the values defined by this specification (data, html, nfc) registered -- a registry section in this spec, the VC Specs Directory, or both?
- How do third parties register extension suites? Are extension values plain strings (collision risk, needs a registry) or URLs (self-namespacing, no registry needed)?
- What are the matching rules (exact, case-sensitive string comparison)?
Related: what a consumer does with an unrecognized renderSuite value (presumably skip that renderMethod entry).
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.
Research direction
Review the dispatch change in issue #54 and the specification's current renderSuite values: data, html, and nfc. Compare the registry options in the issue with the VC Specs Directory, then document a decision for extension naming, matching rules, and handling unrecognized values.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100