Ed Summers
Ed Summers
I like the idea of having the use case document live here in this repository with the spec, but be a separate document like https://www.w3.org/TR/did-use-cases/
Once we've entered the use cases we have as issues, and collected new ones, we can then pull them out into a Use Cases document.
I put together a Github Action for this in https://github.com/edsu/respec-action/ and configured webrecorder/specs to use it. You can see that the WACZ-IPFS spec is now presented using ReSpec: https://specs.webrecorder.net/wacz-ipfs/latest/ I'll...
I don't think this is relevant anymore.
Whoops I don't think I should have closed this since there has been conversation over on the #112
@ikreymer for nesting would we need a new file name and extension for nested WACZ files that is distinct from WACZ? If not won't WACZ viewers need to account for...
In the use case [above](https://github.com/webrecorder/specs/issues/129#issue-1429978056) where each WACZ is individually signed, is the issue that the cert that is being used to sign each WACZ needs to be different? Or...
Since effort is now underway to make WACZ into more of a standard I think working towards an IETF media type might actually be a good idea. Registering a media...
I think we should add some preliminary text about it to the spec yes--so that people reading know we are thinking about it. But before we do that maybe it...
I don't think it should be separate. Unless I am misunderstanding (which is very possible) an understanding of a WACZ Aggregation without an understanding of WACZ would be pretty much...