Clarify the rule on OCF resources not declared in Package Documents?

[rdeltour]

Strictly speaking, EPUB 3.0.1 says this is allowed (or rather, it doesn't say otherwise). However, people (legitimately IMO) asked that EpubCheck reports that as warnings.

Can the spec try to be clearer on which resource it allows being undeclared? e.g. introduce a safe place to put such resources, like in a top-level directory which doesn't contain a Package Document, and disallow undeclared resources in other locations.

See also the thread "validation issue with ancillary resources" in the epub-working-group mailing list, and also w3c/epubcheck#58

[mattgarrish]

Now that we're saying foreign resources are allowed without fallbacks so long as they aren't used in the direct rendering does that make this issue go away?

There's no need to hide a foreign resource to avoid a fallback requirement anymore, in other words, so we should report "other stuff" as warnings by requiring all resources be listed in the manifest unless they have a specific spec exemption somewhere.

It might need to be run past the ESC group, though, as they're using that exemption to hide configuration files, but I don't think they need to do that with this change, either.

[mgylling]

@rdeltour: in addition to the changes Matt reference above, we also have a suggestion for a property to help EpubCheck distinguish between intentional and non-intentional files in the package.

[mattgarrish]

Closing this issue as the working group resolved on the July 6 call not to change the rules but that epubcheck should be changed to only emit a info message about resources that are not in the manifest, linked or "manifest free" (rendition mapping doc).