This page is to answer most of the questions I heard about this project.
This will help people to understand the nature of the project, as well as its limitation.
It will provide some hint of the philosophy around the Simple Object Manager.
Why Not using an EDDL ?
You should use the EDDL structure to manage a clean Object structure representation for tracking if you can.(it has been inspired from it).
That would be the best course of action but there are 3 main reasons why this project can be interesting:
-
Many websites / owner do not have the capacity to change their Data Layer structure, moving from their legacy CEDDL to EDDL.
-
In case of AEP Web SDK, your EDDL may not be containing "XDM compatible" data. XDM is specific to Adobe, you may want a more neutral representation of your data in your EDDL. Therefore, you may need to change the structure.
-
You want to manipulate data representation in an object but without the boiler plate of event management, natively attached to EDDL structure. It means that the event listener and event pushing is not covered by the
Somobject.
Who is going to maintain it?
The community ? The code would be open-source (like everything I do) so if you are not happy about it, you can fork it, you can generate your own version of the library.
Also, the idea is to have a minimum amount of methods available that are quite basic so the support should be minimal after the first edge cases are solved.