Create 0035-unambiguous-created-updated-attribute-descriptions.md

[bhadley]

ADR to address ambiguous created and update attribute descriptions

[bhadley]

Per discussion in PACT Tech Working Group 9 August:

• If the new definition is purely technical, then what is the value of having these fields in the data model (a given system can maintain these fields themselves, they don't need to be in the data model)? The community did not see a value in sharing the fields between systems, if the definition of created and updated becomes purely technical.
• We need to clarify what is the use of the updated attribute as it relates to versioning. There would be value in the updated field being shared between systems, if we have clarity regarding how the updated field needs to be updated (i.e. on every version update). The current tech specs specify this clearly (see https://wbcsd.github.io/data-exchange-protocol/v2/#lifecycle), but as we know TfS and CX do not use versioning (they default version number to v1, and create a new PCF for each change). We have planned this as a topic of alignment this Fall. Therefore we propose to pause on this ADR until we have further clarity on how we will address versioning.
• Interoperability with other initiatives is critical, therefore we should not just remove these attributes (especially the mandatory created attribute) until we reach initiative consensus.