Changes

==What the database contains==

==What the database contains==

The list is a JSON file. Each entry in the list has the following fields:

The list is a JSON file. Each entry in the list has the following fields:

id: a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable

id ({{P|124}}): a numeric identifier (integer) for the entry, this will change whenever the list is expanded and reindexed, do not count on it remaining stable. It will be stored as a string under {{P|124}}, and each statement here will need to be qualified with a version number.

parent_id ({{P|123}}): if the entity has a parent owner, the id of the parent

parent_id ({{P|123}}): if the entity has a parent owner, the id of the parent

owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain

owner_name: a string which is the name of the service (eg. 'Google Analytics') or the company ('Google') which owns the domain (This should become the label on here, but also added in the {{P|27}} property)

aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube')

aliases: an array of strings representing possible alternate spellings of the owner_name (eg. 'YouTube' and 'You Tube') (These should become aliases under {{P|27}}, note that we can have many entries for each)

homepage_url: a string which is the url of the homepage of the service or company

homepage_url: a string which is the url of the homepage of the service or company ({{P|33}}, maybe {{P|15}})

privacy_policy_url: a string which is the url of the privacy policy of the service or company

privacy_policy_url: a string which is the url of the privacy policy of the service or company. Best is I think (({{P|32}} - {{Q|29}}, and then a qualifier with {{P|33}}). Because then we can add {{P|32}}-{{Q|412}}, with links to the Privacy Shield commitment, for instance. It's a better pattern that repeats.

notes: a string which has pertinent information as to why a domain was assigned to a given owner

notes: a string which has pertinent information as to why a domain was assigned to a given owner ({{P|126}})

country: the ccTLD for the country in which the service or company is based

country: the ccTLD for the country in which the service or company is based. We have {{P|55}}, so that should be used, but I think the utility of such a thing is fairly limited because the companies are so complex. Isn't what you want a property "ccTLD" ? Isn't this associated to the domains rather than the owner??? What are your assumptions there?

uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing.

uses: what a first-party uses the service for, note that first-party use may be different than the ultimate third-party use. For example, a site may use audience measurement tools from a third-party to gain insights into traffic, but the third-party may use this data for marketing. I suggest {{P|127}} and not {{P|10}}, it's more precise.  

platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'

platforms: where the domain has been observed, so far 'web', 'mobile', and 'email'. We will want to complexify those (mobile --> {Android, iOS}; or an industry) so it makes sense to make the target an item. I don't like the link "platforms". We want a more generic word, but not too generic either. prevalence/presence/scope/???.

domains: an array of domian names (strings) which are owned by the given service or company

domains: an array of domian names (strings) which are owned by the given service or company {{P|118}}

==Why it is important==

==Why it is important==