Ed Summers

I like WACZ Aggregation better than WACZ Collection, and have just updated some of the text above.

I guess my point is that if someone is building a WACZ client, as we want people to do, they will want to be clear about what their viewer needs...

That's a useful comparison @DiegoPino! It might be helpful to think about the WACZ specification as the equivalent of the [Image API](https://iiif.io/api/image/3.0/) and this Aggregated WACZ view as the equivalent...

I noticed an inconsistency in the Frictionless DataPackage specification around URLs in Resources. The [Data Resource specification](https://specs.frictionlessdata.io/data-resource/#data-location) says: > path MUST be a string – or an array of strings...

If aggregation isn't core to using WACZ then I agree it should be a separate specification, or perhaps just be in the description of how a specific tool works, and...

After some conversation @ikreymer decided that the Multi-WACZ or WACZ Aggregations is best served by a separate specification. This issue can stay open until that new repo & specification exist.

Any update on this?

This is probably off topic for this issue, but it came up recently in the context of using [mailbagit](https://github.com/UAlbanyArchives/mailbagit) that it would be useful to know if a record is...

Can this be closed now that `hopsFromSeed` is documented [in the Community Annotations](https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1-annotated/#metadata)? Or is the motivation here that it should be in a new version of the specification?

Yeah, I'm not sure. I had thought it might be useful to provide an [atom/electron](https://github.com/atom/electron) package for bagger-js to run it as a desktop app. But it doesn't sound like...