w3ctag/packaging-on-the-web
OBSOLETE: Guidance about how to provide packages of information on the web.
HTML
Issues
- 9
Please "un-gut" this specification
#35 opened by BigBlueHat - 0
Indicate the spec isn't being worked on
#34 opened by xfq - 9
- 0
Nested packages
#33 opened by Munter - 1
Why not the non-zip formats?
#31 opened by jyasskin - 1
Turn on HTTPS
#32 opened by jyasskin - 0
- 0
Package signing and key continuity for trusted apps
#29 opened by tanx - 2
What's the origin of a signed package?
#24 opened by jyasskin - 7
Security use cases for packaging
#21 opened by diracdeltas - 0
Multiple pages in a package
#28 opened by dimich-g - 0
Link headers as an alternative?
#26 opened by triblondon - 0
Reflect the discussion in the April 2015 F2F
#25 opened by torgo - 0
Consider manifest~like approach instead of SPF
#23 opened by igrigorik - 1
Icon container as use case
#22 opened by marcoscaceres - 0
Vary header use
#16 opened by yoavweiss - 1
- 3
Is it safe to deploy over plain-text HTTP?
#19 opened by yoavweiss - 1
Streaming Packaging Format
#12 opened by cconcolato - 3
- 2
Why not use `Content-Encoding`?
#17 opened by yoavweiss - 2
Zip CAN be streaming
#14 opened by stain - 1
"scope" attribute
#9 opened by mnot - 2
Populating Caches
#10 opened by mnot - 0
IETF review
#11 opened by mnot - 1
Use new archive/ top-level media type?
#13 opened by stain - 3
- 2
maybe use EPUB as a scenario?
#6 opened by dret - 2
Package Contents Header Field?
#5 opened by dret - 2
tarballs
#7 opened by max-mapper - 1
Caching and delta updates to packages
#3 opened by marcoscaceres