clarification on device disclosure doc of wildcard applicability to root domain

[a2intl]

It would be a useful clarificiation in the https://github.com/InteractiveAdvertisingBureau/GDPR-Transparency-and-Consent-Framework/blob/master/TCFv2/Vendor%20Device%20Storage%20%26%20Operational%20Disclosures.md#domains-array document if the use of the wildcard *.domain.com also covers (or, alternatively, specifically does not cover) the root domain domain.com, in the specific places where a domain wildcard can be used.

[HeinzBaumann]

@a2intl I will discuss this within the FSWG.

[HeinzBaumann]

@a2intl we discussed this at the FSWG meeting. There is an asked for you: Can you please elaborate on the reason for this suggestion? Thanks

[a2intl]

We just wanted to know if we needed to list both quantserve.com and *.quantserve.com in our JSON file, or if just the wildcard version would do, since the spec wasn't clear.

[HeinzBaumann]

Thanks @a2intl! I have this passed to the FSWG.

[HeinzBaumann]

Standard is to declare domain.ext and *.domain.ext separately. The MO will double check how vendors currently declare this. It is assumed that most do *.domain.ext only. I will double check how we handle this in our compliance check (in our crawlers).

[HeinzBaumann]

I propose to follow w3c spec: "The Domain attribute specifies which server can receive a cookie. If specified, cookies are available on the specified server and its subdomains. For example, if you set Domain=mozilla.org from mozilla.org, cookies are available on that domain and subdomains like developer.mozilla.org." (https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cookies#define_where_cookies_are_sent)
If you specify *.domain.ext it will not include domain.ext.

@ jdelhommeau