Identity schema authentication states should match DULE

harleensahni commented 6 years ago

What are the schemas that are affected by the issue

Identity

What are examples of products that are impacted by the issue

all of them that deal with login / CRM ids

Details

DULE appears to prescribe four identity states to three authentication states that ECID uses and that are being proposed on the identity schema (see https://github.com/adobe/xdm/blob/Add-authentication-states-to-Identity-Schema/schemas/context/identity.schema.json#L35). We should probably go with the DULE states. The DULE states are:

Not Provided (this should be the default if no other value in the enum is set)
Identified (corresponds to Authenticated in ECID Auth State?)
Incognito (corresponds to Logged out in ECID Auth State?)
Ambiguous (corresponds to Unknown in ECID Auth State?)

cdegroot-adobe commented 6 years ago

@kstreeter please add this to the June 29th milestone. It does not seem like it it critical for the June 15th milestone. I will submit a PF for it.

cdegroot-adobe commented 6 years ago

@harleensahni - Do we want to use the names you provided or the names currently used in the visitor id service?

The branch I had prepared earlier is here with the other naming and does not include Not Provided. https://github.com/adobe/xdm/blob/Add-authentication-states-to-Identity-Schema/schemas/context/identity.schema.json

lrosenthol commented 6 years ago

There appears to be a bunch of Adobe-centric stuff in this schema, but it's a public schema. Please remove it or move to extension.

trieloff commented 6 years ago

@harleensahni 👋 – do you have a link to DULE? When I search for "dule standard", I get autocorrected to "double standard".

If we adopt this, let's make sure that the link is in the description.

cdegroot-adobe commented 6 years ago

@lrosenthol @trieloff - The ultimate addition to XDM will be implementation neutral. DULE is an Adobe approach to the problem domain, the data being proposed here is an input to that and is generally applicable across vendors. This is a very important input to how behavioral data can be merged and used. It definitely will need to be in the core XDM standard.

lrosenthol commented 6 years ago

Then we will need to also publicly publish this "DULE" thing as well as any other normative references. Are we prepared to do that?

trieloff commented 6 years ago

If it's important and needed for XDM and you don't have any other place to publish it, we can include the parts that are relevant to XDM in XDM.

But we can't have any pointers to standards that are behind the firewall.

cdegroot-adobe commented 6 years ago

No, we are conflating two different but related things here. ExperienceEvents are observations of end user activities. Information about how the end user is authenticated at that moment is just data about the surrounding circumstances. We need to represent that data effectively, but do not make a directive on how it is to be used in the specification. Recording the Authenticated State (this issue) is just a representation of an aspect of state. DULE is a management framework in Adobe applications that allows data stewards to control when and how data is used, potentially using this state as an input. So they are two distinct things, we do not need to standardize both to have the first. DULE is not currently under consideration to be included in the XDM standard. As an aside DULE is publicly documented in product documentation: https://marketing.adobe.com/resources/help/en_US/analytics/gdpr/gdpr_labels.html

I think we really need to remove references from DULE from this issue, it does confuse the proposal. We are just trying to use the naming that was incorporated into DULE as they seems an improvement over what is implemented in the Visitor Service : https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-authenticated-state.html

adobe / xdm