consider new name for SbolService

[mgaldzic]

service as is not an intuitive name

SbolService contains many methods for creating and adding new SBOL objects to the Entity Manager
What is the appropriate name for this class.
or What better design should we consider for the library so that it is more convenient for users of the library?
ie For me the decision lies in what will be a little easier for a new user to expect from a name of a class.

A conversation about this began early on:

Tim said: SomethingService implies (at least to me) some
asynchronous operation with a third party server (usually over the
internet). Servers provide Service. Perhaps that's just me.

Mike said: I adopted the term from a JPA example, http://www.java2s.com/Code/Java/JPA/UpdateAnEntity.htm
see ProfessorService
In their case they pass the EntityManager to the Service.
The "service" term comes from offering the transaction methods it performs in managing the store or other persistence object.
So the other options would be SbolManager, SbolEntityManager, or LibraryEntityManager.

The Sbol prefix is generic, however our outer container is a Library. There can be no Thing outside of a Library.
So LibraryService may work, too.