Agreed, that a generic "Account" naming convention might be best to handle 100% of all use cases from the highest level. I'd rather switch the semantics of "social" presence to just the 1960's view of ... a "login presence". My personal definition of "Account" type would be defined as: "An identifier for a login presence of a Person, Organization, or Thing that represents them within a site or app" (the key semantic difference in my definition is that it says it's an "identifier for the presence" of a Person, Organization, Thing on a site or app...and not necessarily the physical entity) The idea is further stretched into Drupal terms, (correct me if I'm wrong, St�phane) such as forums, etc, where "Account" is pseudo for "login" or "login presence" that holds properties of "accountName" and "password", etc. In machine terms, an "Account" is attached to a "login" typically, with all it's relevant properties that are usually provided with an "Account" type... username, password, full name, address, bank account #, account_id, other_Accounts_on_the_web_that_you_want_to_link_to_this_Account, etc, etc, etc. An "Account" 's username property is not necessarily their "identifier for their presence", but typically is established in such a way nowadays. (Login with your Facebook Account instead, blah, blah) -- -Thad +ThadGuidry <https://www.google.com/+ThadGuidry> Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>
Received on Friday, 24 January 2014 14:54:07 UTC