I’m not clear when you’d use set instead of series. The example shown puts a Harry Potter book in a set, but would that have been the right decision when the books were still being released? How about a book series whose final length is not known at the moment?
Note that group-position is “A single xsd:unsignedInt or series of decimal-separated numbers (e.g., 1 or 2.2.1).”)
The specs recommend also giving the collection an identifier, e.g.,
@jeffmcneill, since the “new” EPUB3 is mostly a reversion to EPUB 3.0.1, that’s the model to follow. See https://w3c.github.io/publ-epub-revision/epub32/spec/epub-packages.html#sec-belongs-to-collection for the spec, though the examples at https://w3c.github.io/publ-epub-revision/epub32/spec/epub-packages.html#group-position are perhaps a bit more complete. Basically:
Caveats:
set
instead ofseries
. The example shown puts a Harry Potter book in aset
, but would that have been the right decision when the books were still being released? How about a book series whose final length is not known at the moment?group-position
is “A singlexsd:unsignedInt
or series of decimal-separated numbers (e.g.,1
or2.2.1
).”)but I have no idea whether any reading system implemented actually cares about that. Probably can’t hurt, though.
Originally posted by @jcsalomon in https://github.com/w3c/publ-epub-revision/issues/326#issuecomment-441413635