Re: Clarification requested regarding "Customer Experience Digital Data Layer 1.0" Revision Dec 10, 2013

I am on vacation this week but let me take a look and see if I cannot 
clarify the document or at least answer questions.  There has been some 
turnover and apologies if the questions have gone unanswered.

Thanks,

Hutch White   

Partner Solutions Manager
IBM ExperienceOne


11501 Burnett Rd. 
Bldg. 905, 2nd Floor 
Austin, TX 78758-3400   
 
Phone:  720.395.3682
Email  :  hutchwh@us.ibm.com



 


 

 



From:   "Ash, David (STL)" <DAsh@express-scripts.com>
To:     André Mafei <andremafei@gmail.com>
Cc:     "public-custexpdata@w3.org" <public-custexpdata@w3.org>, "Ogden, 
Mike L. (STL)" <MLOgden@express-scripts.com>, André Mafei 
<andremafei@upmize.com>
Date:   12/15/2017 12:35 PM
Subject:        Clarification requested regarding "Customer Experience 
Digital Data  Layer 1.0" Revision Dec 10, 2013



Thank you for your feedback! :-)

________________________________
From: André Mafei <andremafei@gmail.com>
Sent: Friday, December 15, 2017 4:53:13 AM
To: Ash, David (STL)
Cc: public-custexpdata@w3.org; Ogden, Mike L. (STL); André Mafei
Subject: [EXTERNAL] Re: Clarification requested regarding "Customer 
Experience Digital Data Layer 1.0" Revision Dec 10, 2013

Hi David,

I would like to add to your comment that 2 years ago when I started 
implementing this in real World e-commerces I noticed problems with the 
examples and mainly gaps of unanswered questions about how to integrate 
this approach of tagging with the systems that will read and write data 
into the data layer.
So I consider this document as a great idea but too open to be considered 
as "instructions to follow".

André Mafei

Founder & Data Engineer Consultant
Brasil: +55 (11) 95486-3310  |  USA: +1 (415) 230-0375
LinkedIn<
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_in_andremafei&d=DwMFaQ&c=TRM22a2q2ENZDxdZ_Nz-0OCGEspXTWPuaB6Jil0RfKE&r=7iKrj56ijKYKshJ9esCdxKdqcIPK0RAPi_MMv-ZLjgw&m=aV6ex__HnkcLY1SoFzgssKwDhKFrEZZpY8LEkyd8dZw&s=AmUG06TXcGPVJVgurok3sjZR_td2XaszPV3aS9lc5N4&e=
>   |   Twitter<
https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_andremafei&d=DwMFaQ&c=TRM22a2q2ENZDxdZ_Nz-0OCGEspXTWPuaB6Jil0RfKE&r=7iKrj56ijKYKshJ9esCdxKdqcIPK0RAPi_MMv-ZLjgw&m=aV6ex__HnkcLY1SoFzgssKwDhKFrEZZpY8LEkyd8dZw&s=s6BaleVih9uaCmnBG4kllsEzGU866sS8V4m98iClslg&e=
>   |    www.upmize.com<
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.upmize.com_&d=DwMFaQ&c=TRM22a2q2ENZDxdZ_Nz-0OCGEspXTWPuaB6Jil0RfKE&r=7iKrj56ijKYKshJ9esCdxKdqcIPK0RAPi_MMv-ZLjgw&m=aV6ex__HnkcLY1SoFzgssKwDhKFrEZZpY8LEkyd8dZw&s=w0mDXqjdGqapMSnxHiDHJhl1KdFnyTVOUG5aX48RrXU&e=
>

Upmize - Tableau, Google Analytics, Tag Manager Consulting


On Thu, Dec 14, 2017 at 5:16 PM, Ash, David (STL) 
<DAsh@express-scripts.com<mailto:DAsh@express-scripts.com>> wrote:
Dear Customer Experience Digital Data Community Group members,


I am writing regarding the "Customer Experience Digital Data Layer 1.0" 
with revision date December 10, 2013 located at 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2013_12_ceddl-2D201312.pdf&d=DwIFAw&c=jf_iaSHvJObTbx-siA1ZOg&r=qiYeX9ob-K3O7gsXozJHB3cFEUYOp6dP53AONRS82ec&m=tHeM67CQMgSI4WU6aJ28n50uqZSsqFYSiF5lzUDYtKs&s=NtLoRWTBOh0TA683RxInABsGnfF6Mg6s27lSxd4LpBw&e=
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2013_12_ceddl-2D201312.pdf&d=DwMFaQ&c=TRM22a2q2ENZDxdZ_Nz-0OCGEspXTWPuaB6Jil0RfKE&r=7iKrj56ijKYKshJ9esCdxKdqcIPK0RAPi_MMv-ZLjgw&m=aV6ex__HnkcLY1SoFzgssKwDhKFrEZZpY8LEkyd8dZw&s=YQbRckKV0q6-LEtLsZGghTS6oxIy1WqZf0Th7XB_u4Y&e=
>.  In this document, under the section digitalData.transaction..total, 
there is a disparity between the example and reserved words. Specifically, 
basePrice is listed in the example but not the reserved words, and 
totalPrice is listed in the reserved words but not the example.


[cid:04eec762-b3b6-4b5c-a1c8-327cc543f90a]


It is also the case that basePrice is used consistently with the same peer 
attributes throughout the rest of the document, and that totalPrice is not 
used anywhere else.  This leads me to believe that the example is correct 
but that the reserved terms is incorrect.


I am requesting a clarification, and would urge your committee to either 
revise the document or issue errata that is accessible from the document 
linked to above or from 
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_community_custexpdata_&d=DwIFAw&c=jf_iaSHvJObTbx-siA1ZOg&r=qiYeX9ob-K3O7gsXozJHB3cFEUYOp6dP53AONRS82ec&m=tHeM67CQMgSI4WU6aJ28n50uqZSsqFYSiF5lzUDYtKs&s=kViVTnwTsToM37Pln8LetHyR_2OJu1wLJCzHiVHLEcM&e=
<
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_community_custexpdata_&d=DwMFaQ&c=TRM22a2q2ENZDxdZ_Nz-0OCGEspXTWPuaB6Jil0RfKE&r=7iKrj56ijKYKshJ9esCdxKdqcIPK0RAPi_MMv-ZLjgw&m=aV6ex__HnkcLY1SoFzgssKwDhKFrEZZpY8LEkyd8dZw&s=Xz-BmFlWjKL4fJkB8jci3ZRYKIUwKRou0jkfUDhqlAI&e=
> .



Thank you for your time,


David Ash