Resources
- Identity Use Cases & Scenarios.
- FIDIS Deliverables.
- IDIS Journal.
- FIDIS Interactive.
- Press & Events.
- In-House Journal.
- Booklets
- Identity in a Networked World.
- Identity R/Evolution.
D2.3: Models
Name and address, as a data type, have unique characteristics, which make it very difficult to manage them. This data is often volatile: customers come and go, addresses change, names change. This data is often cluttered when entered. Name and address fields on front-end screens are usually free format and ripe for users to enter comments and extra data, without any edits.
Name and address, as a data type, have unique characteristics, which make it very difficult to manage them. This data is often volatile: customers come and go, addresses change, names change. This data is often cluttered when entered. Name and address fields on front-end screens are usually free format and ripe for users to enter comments and extra data, without any edits.
xCIL: extensible Customer Information Language
Although name and address data is the key identifier of a customer, other data helps to uniquely identify a customer. Customer addresses frequently change and it is not trivial to link the customer across multiple addresses with just name information.
In the example below, a customer can have two completely different addresses and it is nearly impossible to uniquely identify the customer with the name alone. Customer centric data such as telephone numbers, e-mail addresses, account numbers, credit card numbers etc. will be necessary to achieve this. This helps in achieving single customer view, customer relationship management strategies, understanding customer profiles, etc.
Following are the customer data elements that xCIL Standard supports:
Customer Name and address Details
Customer Identifier
Organisation Details (Branches, Stocks, etc)
Birth Details
Age Details
Gender
Marital Status
Language Details
Nationality Details
Occupation Details
Qualification Details
Passport Details
Religion Details
Ethnicity
Telephone Details
Facsimile Details
Cellular Phone Details
Pager Details
E-mail Details
URL
Financial Account Details
Identification card Details
Person Physical Characteristics
Tax number Details
Vehicle Information Details
Family Member Details
Income Details
Reference Contact Details
Hobbies
Habits
Residency Details
Visa Details
xCRL: extensible Customer Relationships Language
Customer relationship management is the key to build effective customer relationships.
Customer relationships could be categorised into the following:
Organisation to organisation relationship
Organisation to person relationship, and
Person to person relationship
A standard way to represent customer relationship helps to achieve interoperability between different systems, processes and platforms and in building effective single customer views. There are no standards for representing customer relationship and hence, this work attempts to define a standard in XML to capture and represent such relationships.
Some examples of Person to Person relationships |
|
|
|
|
Some examples of Person to Organisation relationships |
|
|
|
|
Contact Management
Examples of Contact Management could be, a person maintaining a list of personal contacts, an account manager of an organisation maintaining a list of potential and or existing business contacts, a list management service provider maintaining a list of customers subscribed to their services, etc.
Reference
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ciq
47 / 53 |