The objective of the data identification community is to allow resources to be identified and retrieved in a global domain. The data identification should not be in the enterprise viewpoint as location-independent identification/retrieval should be a transparency (and hence not visible). Further identification and retrieval should be considered part of the data management community and the data provision community.
Community Summary
The roles and behaviour of the data identification community can be summarized as follows:
A registrant wants its resources to be identified for purposes of management and referral. The registrant mints an identifiers and registers it with the identity or location in the resolver, and re-registers these if these change. A identifier consumer can use the identifier to determine the identity or location by requesting this from the resolver.
The following roles are identified in the Data Identification Community:
Data Identification subsystem (passive role): the community component representing the data identification community.
Registrant (active/passive role): an agent that is responsible for registering assigned identifiers
Resolver (active/passive role): a system that is responsible for registering and providing the identity or location of identified resources.
Identifier consumer (active/passive role): an agent that retrieves the identity or location of an identified resource.
The following behaviour is identified in the Data Identification Community:
Maintain identifier: a behaviour performed by the registrant and the resolver to mint, assign and update an identifier to a resource-location and register these with the resolver.
Resolve identifier: a behaviour performed by the resolver and the identifier consumer to retrieve the a resource’s identity or location using its identifier.
Communities that typically collaborate with the data identification community related are: data management community for assigning identifiers to research data, data provisioning community for providing the location and the identified research data (or landing page), data processing community as an identifier consumer to locate a data source and user authentication community to authenticate registrants.