Thanks for the info.
Series name goes into <sequence> tag.
1. I see the sequence tag now. Very clever! Are non-numerics a problem there? There can often be some very strange issue "numbers", as in the recent "Fantastic Four #6AU" (
http://www.comicvine.com/fantastic-four-5au-the-death-of-the-family-richard/4000-395247/)2. Regarding volume number, it's true that Comic Vine doesn't store them, but it's info that the indicia of serialized comics commonly had in the past, such as "Avengers No. 4 Vol. 3". They're hard to rely on in cataloging databases, since they're not consistently used, and I guess that's why Comic Vine and GCD reference start year heavily. Regardless, volume numbers show up often in filenames, and ComicTagger app tries to parse that info out.
(As a feature request for ACBF: It might be nice to see optional attributes of the sequence tag to allow for "volume_number" and "start_year". Also maybe a boolean attribute "primary"?)
3. Splitting names like you suggest is possible but is essentially creating information about the name boundaries and can often be wrong. For example. in the cases I mentioned, "Van Lente" is the last name, and (I think) "Kellie Sue" is a first name. I guess this not so much of an issue for ComicTagger, and converting to other tag formats from ACBF, as it all flattens out. But going the other way, if the ACBF reader is using the "last name" tag for sorting, it could run into problems. (I like how the Calibre app has a field for author name, and then a transformed version for sorting i.e. "Fred Van Lente" and "Van Lente, Fred". It's a bit redundant, but no info is lost if a programmatically generated sorting name is wrong.)
I probably won't get around to adding this soon, but I definitely have ACBF on the radar now. I imagine that in the case of non-existent ACBF file, CT would create a minimal version with only meta-data section, and very basic body section, listing only the order of images. If it already exists, trying to preserve all other data will present a small challenge with the current design, as the other formats it knows about are fully converted internally, and I don't know it that would be worth it for ACBF. Nothing insurmountable, but worth taking slowly, when I get around to it.
-------------------
On a related topic, I know it's a chicken-egg thing trying to get a standard in use. What sort of acceptance/use of ACBF is there now? Any third-party readers, third-party content generation?
