But I'm publishing multiple Bibles under one kind and one npub.
Discussion
it seems to me like there needs to be a new single letter tag put to use
there is fully 52 possible ones, each alphabetic letter in lower and upper case, and hardly any of them have been used
might take a while to scan all the PRs hanging on the repo to find what is being bagsed to try and avoid a conflicting semantic, should be fine to use the same letter as another with a different meaning in a different kind (or even syntax, such as multiple fields like title, author, isbn, etc
Books aren't wikis or articles, but this third thing. Hence the new event.
There can be n number of editions, translations, versions of the same book. Someone interested in a particular book might publish multiple ones.
Not just the Bible, but also "Tom Sawyer" or "Faust II" or "Plato's Republic", etc.
i think you need to create a new tag with a new defined set of fields
if they are single letter they should come up on index searches, just as i mention best to avoid a direct conflict with one that is in use so a simple tag search doesn't pull up useless stuff that overlaps too much with another differently formatted tag (though people really should be using kind + tag for this)
I think so, too. #[4] #[5]
yeah, just need to structure them from more abstract to less abstract, eg, ["t","the bible","1 john", "3"] so each subsequent tag field drills down
just keep in mind that only single letter tag prefixes are guaranteed to be indexed for searching, a client can process multi-letter tags in other ways, such as metadata