Microsoft Word fidis-wp2-de models doc
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
Yüklə 0,65 Mb. Pdf görüntüsü
|
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 67 6.5.3.1 References: Liberty Alliance project http://www.projectliberty.org/
6.5.4 Biometrics (XCBF) XCBF (OASIS XML Common Biometric Format) aims at providing a standard to describe information that verifies identity based on human characteristics such as DNA, fingerprints, iris scans, and hand geometry. Biometric types defined in NISTIR 6529.
Multiple Biometrics Used Facial Features Voice
Fingerprint Iris
Retina Hand Geometry Signature Dynamics Keystroke Dynamics Lip Movement Thermal Face Image Thermal Hand Image Gait
Body Odor DNA
Ear Shape Finger Geometry Palm Geometry Vein Pattern
XCBF (OASIS XML Common Biometric Format http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xcbf
NIST (2001); “NISTIR 6529, Common Biometric Exchange File Format (CBEFF)”, January 3, 2001, http://www.itl.nist.gov/div895/isis/bc/cbeff/
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 68 6.6 Customer information with CIQ CIQ (OASIS Customer Information Quality) aims at delivering global, application- independent, open XML specifications for party/customer information and profile management. It is still under construction. The objective of CIQ (OASIS Customer Information Quality) is to deliver a set of XML specifications for defining and managing customer (also called "Party") information/profile (including customer/party relationships) that are open, vendor neutral, application independent and importantly, "Global". The definition of "Global" here means that the CIQ family of specifications are designed to handle customer/party data (eg. name and address) of any country at an abstract (simple representation of data) or detailed (complex representation, i.e. breaking the data into atomic elements) level. A customer/party can be one or more persons or organisations. An organisation can be a private/public company, educational institute (e.g., school, college, University), association, club, not for profit, government, consortium, group, etc. To achieve interoperability of customer/party information within and across an organisation, the optimal approach is to use a "single base customer/party information standard" throughout the organisation to define and represent customer/party data that can support different application requirements (e.g., parsing, matching, validation, verification, postal services, profiling, billing, shipping, customer views, customer relationships, customer segmentation, etc). This standard can then be extended to support specific application needs.
The committee has developed three XML Standards for Customer Information/Profile Management: •
xNAL: extensible Name and Address Language To describe the name and the address of the person •
To describe the characteristics of the customer. •
xCRL: extensible Customer Relationships Language To describe the relationship with this customer (such as transaction history)
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.
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 69 6.6.1.2 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: 1.
2.
Customer Identifier 3.
Organisation Details (Branches, Stocks, etc) 4.
Birth Details 5.
Age Details 6.
Gender 7.
Marital Status 8.
Language Details 9.
Nationality Details 10.
Occupation Details 11.
Qualification Details 12.
Passport Details 13.
Religion Details 14.
Ethnicity 15.
Telephone Details 16.
Facsimile Details 17.
Cellular Phone Details 18.
Pager Details 19.
E-mail Details 20.
URL 21.
Financial Account Details 22.
Identification card Details 23.
Person Physical Characteristics 24.
Tax number Details 25.
Vehicle Information Details 26.
Family Member Details 27.
Income Details 28.
Reference Contact Details 29.
Hobbies 30.
Habits 31.
Residency Details 32.
Visa Details 6.6.1.3 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. FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 70 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 Mrs Mary Johnson and Mr. Patrick Johnson, where Mary is the "Wife" of Patrick and Patrick is the "Husband" of Mary Mrs Mary Johnson and Mr. Patrick Johnson "IN TRUST FOR" Mr. Nick Johnson, where Mary and Patrick are the trustees of Nick and Nick is the beneficiary Mrs. Mary Johnson, Care of Mr. Patrick Johnson, where Mary is dependent on Patrick Complete Organisation Structure (Employee-Employee Relationship) Some examples of Person to Organisation relationships Mrs. Mary Johnson and Mr. Patrick Johnson "DOING BUSINESS AS" Johnson & Associates, where Mary and Patrick are persons who are jointly doing a business under the name of a company called Johnson & Associates Mrs and Mr. Johnson "IN TRUST FOR" Mr. Patrick Johnson "DOING BUSINESS AS" Johnson & Associates Mrs and Mr. Venkatachalam "IN TRUST FOR" Mr Ram Kumar and Mr Laxmana Samy "ADMINISTRATORS OF" Sakthisoft Pty. Ltd "TRADING AS" Mantra Corporation Mr. Ram Kumar, Care of MSI Business System Pty. Ltd, where Ram is the person and MSI Business Systems is the company.
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.
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ciq
6.7.1 FOAF (friend of a friend) FOAF allows the expression of personal information and relationships, and is a useful building block for creating Information Systems that support online communities. FOAF is an RDF format intended to provide "a way of representing information about people in a way that is easily processed, merged and aggregated" and is primarily concerned with allowing an author to provide a detailed personal description, as well as provide machine- readable links to, and information about, other people.
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 71 6.7.1.1 Example: The following listing represents an example of the description of the Edd Dumbill person, as well as the establishment of the acquaintance of people Edd Dumbill with Simon St.Laurent, using the foaf:knows property.
rdf:resource="http://xml.com/" />
rdf:resource="http://heddley.com/edd/images/edd-shoulders.jpg" />
Note: the relationship between Edd and Simon is done via Simons mailbox address. http://www.foaf-project.org/
and blogrolls have become the fastest growing area of the Web. XFN enables web authors to indicate their relationship(s) to the people in their blogrolls simply by adding a 'rel' attribute to their "a href" tags. 6.7.2.1 Example: Adam and Brad have met each other through mutual acquaintances, and had a few interesting conversations at parties where they found they had several interests in common. They have linked to each other in their respective blogs as follows:
// in Adam blog: Brad
// in Brad blog: Adam FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 72
6.7.2.2 References http://gmpg.org/xfn/
Other specifications helping to capture social information can be mentioned. For instance the FTML (Family Tree Markup Language) 16 is used to represent genealogical information, and therefore the relationships that can exist between family members.
The primary purpose of the OASIS HumanMarkup Technical Committee, and thus, the HumanMarkup initiative overall, is to represent human characteristics through XML and interoperable public standards designed for structured information processing, and to enhance the fidelity of human communication, most specifically in digital Information Systems. HumanML ( http://www.humanmarkup.org/ ) represents a holistic approach for representing human characteristics. This is very much to be considered as a work in progress (and probably not very active). HumanML is creating schemas to represent the following human characteristics: •
Emotion •
Intention •
Gesture •
Political
Practically the human schema is the following:
ATTRIBUTE GROUPS: (non-cap camel) •
humlTemporalAtts •
humlIdentifierAtts •
humlCommAtts •
physicalDescriptors o
height o
weight o
hairColor 16 FTML (Family Tree Markup Language) http://www.geocities.com/SiliconValley/Lab/6125/genealogy/
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 73 o
eyeColor o
build o
scarsMarksTattoos •
age o
dateOfBirth o
dateOfDeath •
gender o
genderAtBirth o
currentGender o
impersonator •
bodyPart •
[arm, leg,
head] •
intensity
COMPLEX TYPES (Capitalized camel) •
Address o
[postal, residential, email, previous, current] •
Artifact o
humlIdentifierAtts o
humlCommAtts o
humlTemporalAtts •
Belief o
humlIdentifierAtts •
BodyLocation o
bodyPart o
location Locator o
humlIdentifierAtts •
Channel: {sight, hearing, touch, taste, smell, kinesthetic} o
humlCommAtts o
strength of signal
FIDIS Future of Identity in the Information Society (No. 507512) D2.3
File: fidis-wp2-del2.3.models.doc Page 74 7 Glossary
Acronym comment
Standards & Technologies CC/PP Composite Capability/Preference Profiles mobility
Customer Information Quality commerce
Friend Of a Friend Social networking
Family Tree Markup Language Genealogy
Global Positioning System location
Human Resource XML Human resources
Human Markup language Holistic
Identity Management System
IMS Global / Learner Information Packaging e-learning
Global Justice Extensible Markup justice
Lightweight Directory Access Protocol directory
Liberty Alliance Identity Service Interface Specifications -CB (Contact book); -GL (Geo-Location) Identity management
Learning Management System e-learning
Platform for Privacy Preferences
Public-Key Cryptography Standards authentication
Public-Key Infrastructure (X.509) authentication
Security Assertion Markup Language authentication
Session Initiation Protocol
Social Security Number
User Agent PROFile mobility
Virtual Card ? Electronic business card
XHTML Friends Network Social networking
XML Common Biometric Format (OASIS) biometric
XML Extensible Markup Language Information technology
Extended Name and Address Standard
Organizations ANSI American National Standards Institute http://www.ansi.org/
(Association promoting the intelligent use of information technology in education) http://www.educause.edu/
Internet Engineering Task Force http://www.ietf.org/
Instructional Management Systems Global Learning Consortium http://www.imsglobal.org/
International Organization for Standardization http://www.iso.org/
Liberty Alliance (identity management) http://www.projectliberty.org/
Organization for the Advancement of Structured Information Standards http://www.oasis-open.org/
World Wide Web Consortium http://www.w3.org/
Yüklə 0,65 Mb. Dostları ilə paylaş:
|