opf:meta... change not accepted by Sigil - Page 2

Doitsu · 07-12-2026, 01:38 PM

With the following metadata section I'm getting the following error:

Code:

ERROR(RSC-005): Error while parsing file: Property "role" must refine a "creator", "contributor", or "publisher" property.

Spoiler:

Apparently the refines syntax is wrong and should be:

Code:

    <dc:creator id="creator">Crossway</dc:creator>
    <meta property="role" refines="#creator" scheme="marc:relators">pbl</meta>

It's also possible that the Google validator didn't like the older but perfectly vaild syntax of the Sigil version number metadata entry.

DiapDealer · 07-13-2026, 10:22 AM

It's very possible that either of those two things could trip up the Google validator. I mentioned the bad refine somewhere earlier. I agree that fixing the one and removing the other might fix the problem for the OP. It would be a good place to start anyway.

At this point, I just wish I could find a way to duplicate the EpubCheck error message the OP reported with the OPF content they provided.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
avoiding Sigil's meta in content.opf	sbin	Sigil	25	01-08-2016 03:51 PM
Embedding OPF meta-data for iBooks in Calibre	Guido Henkel	Conversion	7	05-21-2014 02:11 AM
Change opf filename from content.opf to title.opf	northstar7	Sigil	3	09-23-2013 12:44 PM
Could commercial Sigil be accepted?	eping	Sigil	17	04-11-2012 09:04 AM
ebook-meta --to-opf segfaults	gurmuq	Calibre	3	08-14-2010 09:36 PM

07-13-2026, 10:22 AM	#17
DiapDealer Grand Sorcerer Posts: 29,618 Karma: 212299010 Join Date: Jan 2010 Device: Nexus 7, Kindle Fire HD	It's very possible that either of those two things could trip up the Google validator. I mentioned the bad refine somewhere earlier. I agree that fixing the one and removing the other might fix the problem for the OP. It would be a good place to start anyway. At this point, I just wish I could find a way to duplicate the EpubCheck error message the OP reported with the OPF content they provided.