-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First draft of values on segments in experience event with previous q… #2
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,20 @@ | ||
{ | ||
"xdm:segmentID": { | ||
"@id": "https://data.adobe.io/entities/identity/92312748749128", | ||
"xdm:namespace": { | ||
"xdm:code": "AAM" | ||
} | ||
}, | ||
"xdm:lastQualificationTime": "2017-09-26T15:52:25+00:00", | ||
"xdm:version": "1.0", | ||
"xdm:validUntil" : "2017-12-26T15:52:25+00:00", | ||
"xdm:status" : "realized" | ||
"xdm:segmentID": { | ||
"@id": "https://data.adobe.io/entities/identity/92312748749128", | ||
"xdm:namespace": { | ||
"xdm:code": "AAM" | ||
} | ||
}, | ||
"xdm:lastQualificationTime": "2017-09-26T15:52:25+00:00", | ||
"xdm:version": "1.0", | ||
"xdm:validUntil": "2017-12-26T15:52:25+00:00", | ||
"xdm:status": "realized", | ||
"xdm:previousQualificationTimes": [ | ||
"2017-12-25T12:00:15+00:00" | ||
], | ||
"xdm:payload": { | ||
"xdm:payloadValue": 0.5, | ||
"xdm:payloadType": "https://ns.adobe.com/xdm/context/segmentMembershipPropensityPayload" | ||
} | ||
} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -29,6 +29,42 @@ | |
"format": "date-time", | ||
"description": "The timestamp when the assertion of segment membership was made." | ||
}, | ||
"xdm:previousQualificationTimes": { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Will drop this field, if you need to show previous states of segment membership , just repeat the segment membership definition in the array. Don't need this on experience event either. |
||
"title": "Previous Qualification Times", | ||
"description": "The timestamp when the assertion of segment membership was made. DO WE WANT TO TRACK PREVIOUS PAYLOADS HERE", | ||
"type": "array", | ||
"items": { | ||
"type": "string", | ||
"format": "date-time" | ||
} | ||
}, | ||
"xdm:payload" : { | ||
"title" : "Payload", | ||
"description": "Values that are direclty related with the segment realization. This payload exists with the same validUntil as the segment realization.", | ||
"anyOf": [ | ||
{ | ||
"type": "string" | ||
}, | ||
{ | ||
"type" : "number" | ||
}, | ||
{ | ||
"type" : "object" | ||
}, | ||
{ | ||
"type" : "array" | ||
}, | ||
{ | ||
"type" : "boolean" | ||
}, | ||
{ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we want to force any structure on the payload? It will be difficult to validate correctly even if we force strict structure because the payload type is ultimately controlled by the schema definition and not really the schema membership. I put both ways here for the sake of discussion. |
||
"title": "Segment Membership Propensity Payload", | ||
"$ref": "https://ns.adobe.com/xdm/context/segmentMembershipPropensityPayload", | ||
"description": "The propensity score associated with this segment membership" | ||
} | ||
] | ||
|
||
}, | ||
"xdm:validUntil": { | ||
"title": "Valid Until", | ||
"type": "string", | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
{ | ||
"xdm:payloadValue": 0.5, | ||
"xdm:payloadType": "https://ns.adobe.com/xdm/context/segmentMembershipPropensityPayload" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We need someway to embed the payload type with the payload if we want to attempt to validate the structure is correct. |
||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
{ | ||
"meta:license": [ | ||
"Copyright 2017 Adobe Systems Incorporated. All rights reserved.", | ||
"This work is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) license", | ||
"you may not use this file except in compliance with the License. You may obtain a copy", | ||
"of the License at https://creativecommons.org/licenses/by/4.0/" | ||
], | ||
"$id": "https://ns.adobe.com/xdm/context/segmentMembershipPropensityPayload", | ||
"$schema": "http://json-schema.org/draft-06/schema#", | ||
"title": "Segment Membership Propensity Payload", | ||
"type": "object", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had tried to make this schema simply by not having it be an object type, but object type is enforced by XDM guidelines. The alternative would be for it to be a number and just define the min and max. |
||
"definitions": { | ||
"xdm:payloadValue": { | ||
"title": "Value", | ||
"type": "number", | ||
"description": "The propensity", | ||
"minimum": 0, | ||
"maximum": 1 | ||
}, | ||
"xdm:payloadType": { | ||
"title": "Type Identifier Service", | ||
"type": "string", | ||
"const": "https://ns.adobe.com/xdm/context/segmentMembershipPropensityPayload", | ||
"description": "The type of payload of the service that is used to identify the device type." | ||
} | ||
}, | ||
"description": | ||
"Tracks a propensity score on Segment Membership for an EndUser", | ||
"meta:status": "experimental" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alternative to explore later would be sparse profile embedded into experience event