Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disallow empty content for the four required "dc:" metadata items in OPF #1

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

For full description see:

http://www.daisy.org/epub/issues/use-relax-ng-text-pattern-schema-title-identifi
er-and-others

When we're drafting OPF language this time around, it seems likely we should 
disallow empty content in the four required "dc:" metadata elements (e.g. 
dc:title, dc:identifier); we already have required content verbiage for 
dc:language.


Original issue reported on code.google.com by garthcon...@gmail.com on 19 Aug 2010 at 12:44

@GoogleCodeExporter
Copy link
Author

In practice it will mean people will stick garbage there (e.g. "Unknown 
Title"). And people already faking it for dc:language marking all document as 
English. The problem is that when you write a converter of some source format 
to EPUB and your source document does not have data for those you do not have 
good options. I think not requiring them would match reality better. 

This does not apply to dc:identifier, it is easy to generate UUID or some other 
identifier, even there is nothing better available.

Original comment by soroto...@gmail.com on 6 Oct 2010 at 5:47

@GoogleCodeExporter
Copy link
Author

Because these elements are required it seems appropriate to disallow empty 
content. ImplementationProposalMetadata wiki page has been updated accordingly.

Original comment by bkasd...@apexcovantage.com on 5 Nov 2010 at 8:57

@GoogleCodeExporter
Copy link
Author

Original comment by bkasd...@apexcovantage.com on 5 Nov 2010 at 9:05

  • Changed state: Answered

This was referenced Oct 24, 2020
This was referenced Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant