Planned for August 17, 2018
Fixed Issues
- #364 Video Analytics additions for ExperienceEvent
- PR #417 Added Timed Media schemas to
Experience Event
based schemas PR
- PR #417 Added Timed Media schemas to
- #409 Fix campaign extension bugs
- PR #410 Issue409-Fix campaign extension bugs
- #413 WebPageDetails.server shouldn't be constrained to a hostname
- PR #414 Removed hostname format constraint from context/webpagedetails.xdm:server
- #419 Change Identity schema identifier to unstructured string from URI
- PR #420 Change
Identity
Schema@id
property renamed toxdm:id
- PR #420 Change
- #425 Added datasourceID to the ExperienceCloud Extension for Experience Event.
- PR #426 add dataset id as part of event
Merged Pull Requests
- #391 📝 Clarify CLA section of contribution guidelines.
- #416 Remove definition of xmp:numberOfPixels
- #423 Add post office box to align with Microsoft CDM
- #431 Create RELEASING.md file
- #436 Update Changelog preparing for V0.9.3 release
- #437 Fixing RELEASING.md
xdm:dataSource
inExperienceEvent
is no longer required #363- Changed and added new concepts
Organizational Unit
andGeographical Unit
. Existing links with theProfile
schema updated. InProfile
,xdm:orgUnitID
is nowxdm:orgUnit
, and a simple reference to theOrganizational Unit
schema. #323 - Added Phone Number and Email Address to EndUserIDs. #381
- Changed Adobe Analytics Extension - Alter analytics custom lists to allow keys #376
- Added
"meta:extends": true
to the schemas that can be extended incontext
#332 - Changed extension
extensions/adobe/experience/implementations.schema.json
properties to include the nameimplementation
#403 - Added Reporting Events to Experience Event in the Campaign Extension #307
- Improved the representation of Extensibility to
context\*
schemas #332 - Changed a circular reference introduces in the Campaign Extension to Experience Event #377 / #378
- Added Segment Membership and related schemas for
context\profile.schema.json
#380 - Added searchEngineID field to search schema to Experience Event #394
- Added the created/modified dates from auditable for
context\profile.schema.json
, address and person schemas #393 - Adding relationship descriptor #388
- Introduced Point of Interest details and metrics. #285
- Renamed all
Metric
schemas toMetric Definition
#254 - Moved web metrics used in ExperienceEvent
metrics
to the webinteraction and webpageview contexts #316 - Renamed web metrics to
xdm:*
compressed type property names #316 - Moved
commerce
metrics used in ExperienceEventmetrics
to thecommerce
context #317 - Renamed
commerce
metrics toxdm:*
compressed type property names #317 abandons
metric field name change tocartAbandons
. #317- The
commerce
schema is now extensible to allow for additional dimensions and metrics. #317 - Removed the required constraint from
schemas/external/schema/geo*.schema.json
#315 - Moved
direct-marketing
metrics used in ExperienceEventmetrics
to a newxdm:directMarketing
contexts #331 - Introduced advertising context to ExperienceEvent #280
- Introduced advertising and viewability metrics under the advertising context #280
- Moved impressions and clicks metrics under advertising context #280
- Added
xdm:primary
flag toschemas/context/identity.schema.json
#335 - Corrected naming of EndUserIDs by making them consistent (aaid and acid)
schemas/external/schema/geo*.schema.json
#333 - Renamed
webPageView
towebPageDetails
e.gcontext/webpagedetail.schema.json
#336 - Added application and mobile context via
context\application.schema.json
#318 - Fixed issue where
context\experienceevent
xdm:application
referred to the 'application.schema.json' inchannels
#318 xdm:application
incontext\experienceevent
@id
renamed toxdm:id
#318- Changed
xdm:channel
inExperienceEvent
to be a reference toChannel
#289 - Changed
xdm:pageDepth
data type from number to integer incontext\search.schema.json
#346
- Release 0.9 is preview release which updates the
ExperienceEvent
schema to 'stabilizing' status, along with many of the schemas it depends on. This release is intended to get early feedback from implementers and the community before a 1.0 release.