Metadata-editor error?

[elibrarian]

When using this construction in the .opf:

<?xml version="1.0" encoding="utf-8"?>
<package version="3.0" unique-identifier="BookId" xml:lang="en" xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/">
  <metadata>
    <dc:identifier id="BookId">urn:isbn:9788779797215</dc:identifier>

the metadata editor in Sigil seems to ignore the identifier. If I remove the id="BookId" from the <dc:identifier id="BookId"> the metadata editor will recognise the identifier.

Is this an error? (I think it must be, since the id="whatever"-construction is legal according to the specs.)

Regards,

Kim

[KevinH]

Unfortunately that was designed behaviour as we did not want metadata editors users to play with any dc:identifier that was designated as the unique identifier of the book because if changed this needs to be properly updated in any ncx uid metadata and can have an impact on font obfuscation.

So the only intended way for users to play around with the book unique dc:identifier was for them to directly edit it in the opf and ncx.

This was all designed and coded up when even epub3's were forced to keep an ncx for epub2 backward compatibility.

I will look into changing this at some future point.

Originally Posted by elibrarian

When using this construction in the .opf:

<?xml version="1.0" encoding="utf-8"?>
<package version="3.0" unique-identifier="BookId" xml:lang="en" xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/">
  <metadata>
    <dc:identifier id="BookId">urn:isbn:9788779797215</dc:identifier>

the metadata editor in Sigil seems to ignore the identifier. If I remove the id="BookId" from the <dc:identifier id="BookId"> the metadata editor will recognise the identifier.

Is this an error? (I think it must be, since the id="whatever"-construction is legal according to the specs.)

Regards,

Kim

[elibrarian]

Originally Posted by KevinH

This was all designed and coded up when even epub3's were forced to keep an ncx for epub2 backward compatibility.

Yes, thought it might be an old one. I found it when fiddling with updating some old epub2's to epub3. (I don't use backward compatibility any more. Too limiting in other aspects.)

Originally Posted by KevinH

I will look into changing this at some future point.

I shall look forward to that

Regards,

Kim