This page tracks open questions / issues related to org.symphonyoss.obj.contact [E]. See also the discussion on Sharing Contacts.

Organizations

How should a given Contact connect with or relate to the concept of an Organization (aka Account aka Company)?

The current draft proposes the creation of a separate Organization object, such as org.symphonyoss.fin.organization. Is this a good idea?

Start and End Properties

The current draft proposes start and end properties for each organization relationship object in the organizations collection. This could be useful to track historical affiliations, such as prior employment. However, often this information is relatively imprecise. CRM systems like LinkedIn model this at the Year and Month granularity.

So perhaps org.symphonyoss.time.rfc3339 is not an appropriate type for these properties? If so, what type or types should be proposed?

Roles / Title Standardization / Levels

A common use case for CRM-style systems is to convey the role or level of the person within an organization. For example, it is common to separate "executives" from "non-executives". However introducing a notion of role or level is problematic for a few reasons:

• Job titles convey different meanings in different countries / cultures
• Building and maintaining a ranked list of standardized roles is nontrivial

What are possible solutions here?