Quote:
Originally Posted by Hitch
What, using SCHEMA to create all books?
Yes, books are simple enough matter to be described by an XML schema.
all use HTML/XHTML, not XML straight up.
That is just the matter of format. Generating HTML from XML source is so trivial it can be done on an E-ink Linux device easily.
which assumes arguendo that the book creators would TAG that element for you.
It is always 'tagged' in colophon; it would be in proper metadata if such existed.
that someone making eBooks with XML would fill in ALL the semantic metadata that you'd want?
People make books with WYSIWYG editors, that provide nice toolbars and forms for filling this kind of stuff in.
So instead of styling/formatting a book as a BOOK, you'd be stuck with a set of specifications, created by somebody ELSE, that you'd have to use for "mystery,"
You would create a book like a BOOK, not like a webpage with options for form fields and buttons, but none for footnotes, chapters or scene breaks.
pretty much all eBook readers understand and will display <em> just fine.
And book producers have a myriad of options of imitating the <em> with spans and CSS. With a real format, there is only one way to do that, which all readers, converters and editors support.
what XML eBook format are you proposing that already exists?
We need a new format, that's quite clear.
|
Quote:
Originally Posted by eschwartz
"Martin, George R. R." is not author metadata, it is "author sort" metadata, and once again, this is an objective standard.
|
EPUB metadata standard does not provide for autors' names, surnames, normative references and other logical parts in any way. It is just an arbitrary string with an arbitrary sort key. You cannot order the book list for authors' surnames, as it is impossible to know
what is the surname. Same with genres, annotations, etc. etc.