XDM composition refactor #554
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added workaddress example Corrected syntax of context/workaddress schema
…ncorrect meta:extends, whch should have been a meta:intendedToExtend
…details.schema.json and expanded it to include all the work concepts.
Corrected meta:extends syntax in membersprofile.schema.json
kstreeter
reviewed
Nov 26, 2018
kstreeter
reviewed
Nov 26, 2018
kstreeter
reviewed
Nov 26, 2018
cdegroot-adobe
commented
Dec 3, 2018
cdegroot-adobe
commented
Dec 3, 2018
… the infrastructure for such examples.
Improved titles and descriptions Sync'd the meta:extends and allOf structures.
Converted uber experience event Class to Mix-in
kstreeter
approved these changes
Jan 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To better support the Composition semantics in the Experience Platform the Context and Experience Solution schemas are beings structured a little differently.
This PR covers a number of updates across many schemas but does not change the behaviour of the end schemas other than providing a method of not including all the fields in every case.