OAI / OAI/Overlay-Specification
Manifest file for multiple overlays
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 121
- Forks
- 38
- Avg merge
- 53m
- Merged PRs (30d)
- 6
Description
It is common to have multiple Overlays that can be applied, and order matters both within an Overlay document and between them. It would be useful to have a standard format to describe which Overlays should be used and in what order, that could be understood by tools that support Overlays. It would also allow more flexible Overlay design with more atomic, reusable Overlays which can be composed in different ways for different use cases.
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
No file, test, or entry point is identified; start by reviewing the existing Overlay Specification and the requirements in this issue. Define a standard manifest format for selecting and ordering multiple Overlays, with a result that tools supporting Overlays can understand and apply consistently.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100