Matt Garrish

> * This is a significant and highly error-prone process, and I am not sure it is worth the effort. That's what we need to look at, too. We are...

> Requirements on humans are outside the scope. That an EPUB Creator must include a property in a metadata section is not a requirement that involves testing a human, though,...

> My first shot at it is: Ya, that's the general idea I had, too, when I looked at it again. > I do _not_ think it is worth the...

> I like this I would also include "conversion vendor" I think this is similar to what @murata2makoto mentioned about other parties changing an EPUB. I don't want to introduce...

Is it normal to keep updating these "registrations" even though we never update the actual registrations?

No, the substance of these registrations does not match the [IANA registry](https://www.iana.org/assignments/media-types/media-types.xhtml). The package registration in IANA references RFC4839, which in turn references EPUB 2.0.1. All there is for the...

> But we should keep them up-to-date nevertheless... That's fine, so long as we aren't creating new issues by not going back to IANA with these. But we'll also need...

As noted in #1403, these registrations also reference the linking registry. We'll have to return to fix those references once their new location is settled.

I think this issue can be closed now. The links to the linking registry were replaced with a specific mention of EPUB CFI since that's all it was ever referring...

> @mattgarrish is this something you generate? Or should I make an edit somewhere as part of the PR? The change logs have to be updated manually. You have to...