Overview#Data Provenance is Provenance information relevant or pertaining to evaluating the source or author of the data
Origin#The Origin element conveys the legal name of the entity that established the initial data value. This may or may not be an authoritative Entity, or the provider; if, for example, the Attribute Provider generates the attribute value through a derivation process, then the Attribute Provider would be the origin. The key distinction between the origin and the provider is the act of initially generating, capturing, or provisioning the attribute’s value, rather than just asserting the attribute’s value to an Relying Party. Inclusion of this metadata element provides the Relying Party with substantial insight, but at a potential cost to the individual as it may also reveal additional information about the subject to whom the attribute value is bound.
For example, this value could reveal employment status and location, socio-economic information, or even health history; all of which may have unintended and potentially negative consequences. Selection and use of this metadata element should be carefully considered based on both authorization needs as well as privacy requirements.
For example, when leveraging attributes for access to moderate assurance level services that involve customers (i.e., non-enterprise users) it may be sufficient for the Relying Party to request an attribute value's verification method without the origin element-which can reveal unnecessary information about a subject. The original source of the information may not be essential as long as the value has been verified using an acceptable method.
Provider#This specifies the legal name of the entity that supplies the attribute value to the Relying Party. This element enables RPs to understand and evaluate individual attribute values that may be included in a bundle of attributes.
For example, if a full service credential provider generates an assertion with several identity attributes provided by multiple Attribute Providers, the provider element enables the RP to understand, at a granular level, where each has come from and determine whether or not that value can be used for access to specific resources. In instances where a single attribute is asserted directly to the Relying Party, this element may not be necessary since the assertion itself will carry the provider information as well as a certificate or Digital Signature. The privacy considerations for this element are similar to those for origin. Divulging an individual’s relationship with a particular provider allows for broader profiling, and the sharing of information that an individual might not know is being passed on, and might not want to be passed on.Data Pedigree to the data relationship to an authoritative Entity. entity's relationship with a particular Authoritative Entity which could allow for broader Identity Correlation and the sharing of data that the entity might not know is being passed on and might not consent to be passed on.