Alex Osborne

Yes. My interpretation and implementation is that "shall not be repeated ... except as noted" is setting up a default so that each named field doesn't need a statement disallowing...

I support this. It would go some way to resolving the first problem in #40. I also think its important the standard gives clear guidance that WARC-Date on a conversion...

So the issues Ilya raised in #4 about lack record-id indexes apply here equally. Should we define `-Target-URI` and `-Date` variants of every new field that could point at an...

Server push is being removed from Chromium https://groups.google.com/a/chromium.org/g/blink-dev/c/K3rYLvmQUBY/m/vOWBKZGoAQAJ?pli=1 "Almost five and a half years after the publication of the HTTP/2 RFC, server push is still extremely rarely used." "Server push...

The documentation of Heritrix's discovery path is in Heritrix's [Glossary](https://github.com/internetarchive/heritrix3/wiki/Glossary#discovery-path) but indeed it wasn't very discoverable. I have slightly expanded the explanation and added a mention of hopsFromSeed so hopefully...

> Maybe we could say, please file a github issue here to propose a new protocol id, before you use it. I think that's a great idea. I've updated the...

h2c and h2 are obvious odd ones out in the list as they don't follow the general name/version form and h2 vs h2c is somewhat redundant with specifying the TLS...

After proposing in #52 that WARC-Software-Version follow the format of HTTP User-Agent I find myself thinking WARC-Protocol as also a list of version numbers should also be consistent with it....

I just realized I missed the 'revisit' record type in the WARC-Protocol proposal, so have edited it to be included. After this edit WARC-Protocol is allowed on the same record...

> Are there other WARC headers that allow repetition currently? WARC-Concurrent-To is the only one in the standard: > As an exception to the general rule, several WARC-Concurrent-To fields may...