Internal referencing and internal only resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Question related to the "bundling" spec draft: https://github.com/WICG/webpackage/pull/98
Are there plans to include an internal referencing mechanism similar to MHTML's use of Content-ID or the TAG's previous Packaging on the Web's use of fragment identifiers?
For instance, book (et al) publishers are coming from EPUB where "everything" is built using internal references and internal-only resources. Additionally, there may be other use cases where "internal only" package contents might be needed and beneficial.
If that seems out of scope for this sort of bundling, though, no worries. Just wanted to check. 😃
We'll be exploring that need in the Publishing WG via https://github.com/w3c/pwpub/issues/24
Thanks!
🎩
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
Start by reviewing the bundling spec draft in WICG/webpackage#98, then compare its treatment of internal references and internal-only resources with MHTML Content-ID and the TAG Packaging on the Web fragment-identifier approach. Check the related Publishing WG discussion in w3c/pwpub#24; done means reaching a clear decision on whether this mechanism belongs in the bundling scope and how it should be defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100