MobileRead Forums - View Single Post - OPF inside OEBPS folder

Diegnum · 06-15-2012, 10:22 AM

We work for publishers receiving and distributing their ePubs. I have a disagreement about a technical point with a coworker.

We received an ePub that has the opf directly at the root level and NOT inside the OEBPS folder, as almost every other ePub does.

PROBLEM is that we tried a software that watermarks ePubs but it doesn't work if you input an ePub for which the *.opf file is not inside the OEBPS. So :

epub.epub/OEBPS/content.opf <-- An epub like this works fine in the watermarking software

epub.epub/content.opf <-- An epub like this does not work when we use the watermarking software.

The second ePub DOES have a META-INF/container.xml that points to the OPF, using this code :

<rootfile full-path="content.opf" media-type="application/oebps-package+xml"/>

So our disagreement is :

Is it ok for the publisher to make such an ePub ???

We know it is "technically" correct, according to IDPF's standard.

One of us says the publisher should not contruct his ePubs this way, as he takes a risk that some software or devices show problems for this ePub and that we should tell him to put the *.opf inside OEBPS.

The other one says that it is ok for him to do like that and that the software SHOULD support such a construction, so the publisher is in his right to construct the ePubs in such a way.

What do you think ?

06-15-2012, 10:22 AM	#1
Diegnum Junior Member Posts: 5 Karma: 10 Join Date: Jun 2012 Device: None	OPF inside OEBPS folder - Obligatory or strongly recommended ?? We work for publishers receiving and distributing their ePubs. I have a disagreement about a technical point with a coworker. We received an ePub that has the opf directly at the root level and NOT inside the OEBPS folder, as almost every other ePub does. PROBLEM is that we tried a software that watermarks ePubs but it doesn't work if you input an ePub for which the .opf file is not inside the OEBPS. So : epub.epub/OEBPS/content.opf <-- An epub like this works fine in the watermarking software epub.epub/content.opf <-- An epub like this does not work when we use the watermarking software. The second ePub DOES have a META-INF/container.xml that points to the OPF, using this code : <rootfile full-path="content.opf" media-type="application/oebps-package+xml"/> So our disagreement is : Is it ok for the publisher to make such an ePub ??? We know it is "technically" correct, according to IDPF's standard. One of us says the publisher should not contruct his ePubs this way, as he takes a risk that some software or devices show problems for this ePub and that we should tell him to put the .opf inside OEBPS. The other one says that it is ok for him to do like that and that the software SHOULD support such a construction, so the publisher is in his right to construct the ePubs in such a way. What do you think ?