So if there were an application that took a character from RPG game that had skills/abilities and they’d have prequisites between each other and purpose behind app would involve processing characters in interests of publishing characters that a user would like (as in filtering). Wouldn’t that make a case for where you would label every possible variety of a character in order to enable quick filtering of character database where a new character is availabe for say 3k user base at which point you’d have to determine if it’s relevant to a user? Additionally you could send the “indexer” code base to the client at which point if they were to open skills/abilities viewer they’d hopefully be able to reverse engineer what that particular index stands for without having to actually reproduce the whole index base.
I imagine the algorithm for this would hardly be justified for sole purpose of saving bandwidth and IO reads that would go with having to send an array of skills/abilities potentially doing so pre-emptively before user opens the skills/abilites viewer, yet I imagine cross referencing what user has subscribed to (set of abilities he’d be interested in a character) and what the new published character has would be fairly expensive? PS I clearly am not aware of how such an algorithm would “look” like.
I’d also like to enable for user to provide flexible criteria that would match a bunch of indexes, at which point the purpose of exercise would be defeated if there weren’t enough constraints within skills and abilities to really make for easy cross referencing via indexing.