RE: Other files than the "reserved files" in META-INF?

Hi Leonard,

 

It doesn't matter how configuration files come to be there. So long as they
aren't publication resources and don't collide with the reserved files,
they're valid in the META-INF directory.

 

I would just put the file in the root unless you're expecting to group
multiple files. I'll hazard a guess that the likelihood of a future naming
collision with the spec is pretty low.

 

Matt

 

From: Leonard Rosenthol <lrosenth@adobe.com> 
Sent: Wednesday, October 4, 2023 9:08 PM
To: public-epub3@w3.org
Subject: Other files than the "reserved files" in META-INF?

 

Context: I am finishing up support for EPUB for C2PA and the logical place
to put the Content Credentials (aka C2PA Manifest Store) is in META-INF.

 

Reading over the 3.3 spec, it is clear in 4.2.2 that the publication itself
can't put additional files inside META-INF.  However, it is not clear
(either there or in 4.2.6) if there is any restriction on a processing
system can place files there that are not referenced.

 

So any problem with my putting our `content_credentials.c2pa` file in there?
If there is, any other recommendations - just the root?

 

Thanks,

Leonard