Looking for a name for a Subjet-Entity-Role library

Hi, I'm developing a library based on the Object Role pattern. The library use the following concepts: Entity, Role, Subject, Cloture. Its main goal is to help on subjetive programming. I was started to name this library SER (for Subject-Entity-Role). Next follows some Entity-Role-Subject declarations class Person : public entity<Person> {...}; template <typename Base> class PersonRoleTmpl : public basic_role<Person, Base> {...}; class PersonRole : public PersonRoleTmpl<> {...};class Employee : public role<Employee,PersonRole> {...}; class Salesman : public Employee {...}; class Developer : public Employee {...}; class Manager : public Employee {...}; class Guarantor : public role<Customer, PersonRole> {...}; class Customer : public role<Customer, PersonRoleTmpl<entity<Customer> > > {...}; class CustomerRole : public basic_role<Customer> {...}; class Borrower : public role<Borrower, CustomerRole> {...}; class Investor : public role<Investor, CustomerRole> {...}; class CustomerAndEmployee : public subject<Person, roles<Customer,Employee> > { ... }; Any sugestions for the name of the library, 'Subjetive', 'SER'? Best, _____________________ Vicente Juan Botet Escribá

2009/10/4 vicente.botet <vicente.botet@wanadoo.fr>:
Hi,
I'm developing a library based on the Object Role pattern. The library use the following concepts: Entity, Role, Subject, Cloture. Its main goal is to help on subjetive programming. I was started to name this library SER (for Subject-Entity-Role).
Any sugestions for the name of the library, 'Subjetive', 'SER'?
Boost.Role Cheers, Joachim

Joachim Faulhaber wrote:
2009/10/4 vicente.botet <vicente.botet@wanadoo.fr>:
Hi,
I'm developing a library based on the Object Role pattern. The library use the following concepts: Entity, Role, Subject, Cloture. Its main goal is to help on subjetive programming. I was started to name this library SER (for Subject-Entity-Role).
Any sugestions for the name of the library, 'Subjetive', 'SER'?
Boost.Role
Cheers, Joachim _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Hi, Role should be OK. If the namespace is role, and as I have a role class, is the following readable class Employee: public boost::role::role<Employee, PersonRole>? Vicente -- View this message in context: http://www.nabble.com/Looking-for-a-name-for-a-Subjet-Entity-Role-library-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.

2009/10/5 Vicente Botet Escriba <vicente.botet@wanadoo.fr>:
Joachim Faulhaber wrote:
2009/10/4 vicente.botet <vicente.botet@wanadoo.fr>:
Hi,
I'm developing a library based on the Object Role pattern. The library use the following concepts: Entity, Role, Subject, Cloture. Its main goal is to help on subjetive programming. I was started to name this library SER (for Subject-Entity-Role).
Any sugestions for the name of the library, 'Subjetive', 'SER'?
Boost.Role
Cheers, Joachim
Hi,
Role should be OK.
Hi Vicente, with Boost.Role, I think you are in naming paradise :-) (1) Role is THE single word that is the most important aspect or the lib. Very intuitive. (2) Role is a natural word and no acronym. (3) Because of (1) and (2) it is extremely easy to memorize. (4) It is *short* so the namespace identifier is short (I hate long namespace qualified names). (5) It is almost it's own acronym role : *R*ole *O*bject *L*ibrary *e*h? Or more pathetic The Boost *R*ole *O*bject *L*ibrari*e*s How lucky you are, I wish I had such an ideal name as replacement for *itl*.
If the namespace is role, and as I have a role class, is the following readable
class Employee: public boost::role::role<Employee, PersonRole>?
Smart as you are you found a tiny drawback of the name. Well yes, readability suffers a little bit. But this is the *only* class name that is affected by this repetition effect. I could easily live with that... ... or you choose ... Boost.Roles The Boost *R*ole *O*bject *L*ibrari*es* Ha! class Employee: public boost::roles::role<Employee, PersonRole> Cheers, Joachim

Joachim Faulhaber escribió:
2009/10/5 Vicente Botet Escriba <vicente.botet@wanadoo.fr>:
If the namespace is role, and as I have a role class, is the following readable
class Employee: public boost::role::role<Employee, PersonRole>?
Smart as you are you found a tiny drawback of the name. Well yes, readability suffers a little bit. But this is the *only* class name that is affected by this repetition effect. I could easily live with that...
... or you choose ...
Boost.Roles
The Boost *R*ole *O*bject *L*ibrari*es*
Ha!
class Employee: public boost::roles::role<Employee, PersonRole>
According to Boost naming guidelines, the natural choice would be Boost.Role for the lib name and boost::roles as the associated namespace. That is, the suffixed s only goes to the namespace, not the lib name: http://www.boost.org/development/requirements.html#Naming_consistency Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

Hi, ----- Original Message ----- From: <joaquin@tid.es> To: <boost@lists.boost.org> Sent: Monday, October 05, 2009 12:29 PM Subject: Re: [boost] Looking for a name for a Subjet-Entity-Role library Joachim Faulhaber escribió:
2009/10/5 Vicente Botet Escriba <vicente.botet@wanadoo.fr>:
If the namespace is role, and as I have a role class, is the following readable
class Employee: public boost::role::role<Employee, PersonRole>?
Smart as you are you found a tiny drawback of the name. Well yes, readability suffers a little bit. But this is the *only* class name that is affected by this repetition effect. I could easily live with that...
... or you choose ...
Boost.Roles
The Boost *R*ole *O*bject *L*ibrari*es*
Ha!
class Employee: public boost::roles::role<Employee, PersonRole>
According to Boost naming guidelines, the natural choice would be Boost.Role for the lib name and boost::roles as the associated namespace. That is, the suffixed s only goes to the namespace, not the lib name: http://www.boost.org/development/requirements.html#Naming_consistency Joaquín M López Muñoz Telefónica, Investigación y Desarrollo _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost Thanks to both. I will take Role as library name, roles as namespace (even if I have a class named roles to list the roles of a subject, I could rename it to role_list or something else. Thanks again, Vicente

Thanks to both. I will take Role as library name, roles as namespace (even if I have a class named roles to list the roles of a subject, I could rename it to role_list or something else.
Hi, FWIW I think naming your "role_list" to "list" would look better, e.g boost::roles::list. Philippe

2009/10/5 vicente.botet <vicente.botet@wanadoo.fr>:
Thanks to both. I will take Role as library name, roles as namespace (even if I have a class named roles to list the roles of a subject, I could rename it to role_list or something else.
I am still amazed by the 'self acronymity' of this name. R Role O Object L Library or cLoture E Entity S Subject ... can be played around with like Role Objects Linking Entities and Subjects ;-) Cheers, Joachim
participants (5)
-
Joachim Faulhaber
-
joaquin@tid.es
-
Philippe Vaucher
-
Vicente Botet Escriba
-
vicente.botet