IGF has the following four components:
-- CARML, the Client Attribute Requirement Markup Language, is an XML-based language used by application developers to define
contracts that specify how applications can use certain kinds of data.
-- CARML API is an Application Programming Interface that application developers can use to consume identity data in a way
that conforms to the policies that govern that data.
-- AAPML or Attribute Authority Policy Markup Language, defines policy rules regarding the use of identity-related information
from an identity source.
-- Identity Service is a service for securely accessing identity data from multiple identity sources based on established
policies.
Open source and standards groups, including Eclipse.org and OASIS, are also working on the problem of federating identity
information, but OASIS' SPML (Service Provisioning Markup Language) and Eclipse's Higgins Trust Framework are more about creating
consistent user identities that work between systems, rather than managing sensitive data, he said.
"Nobody's asking whether I can propagate a social security number outside my country boundary and put it into system somewhere
else," he said.
Still, Oracle believes that IGF properly belongs under the umbrella of some standards setting organization, he said.
The company plans to reach a deal to hand off its API, as well as AAPML and CARML work to such a group within the next 90
days or so. While Jasuja wouldn't say which group Oracle was considering. However, he acknowledged that a top concern is the
speed with which the group can shepherd the IGF specifications through to standards.
Both OASIS and Eclipse are possible partners for IGF. Notoriously slow IEEE is not high on the list of groups that might take
over Oracle's work, he said.
"Our goal is to take this into a standards organization as quickly as possible to get the (intellectual property) stuff figured
out, and not sit around and waste a lot of time and energy," he said.