Review JNDI-based naming conventions for services
We currently have a number of names for the osgi.jndi.service.name values: acrepobroker, inference, jsonld, etc. It would be good to come up with some naming conventions -- maybe there are patterns for this? Should the names include edu.amherst.acdc or acrepo?
This applies to all of the acrepo-services-* modules, which then are used by many of the acrepo-exts-* and acrepo-connector-* modules.