WebXray domain ownership list - Revision history

Podehaye: /* What the database contains */

2019-10-22T21:12:11Z

What the database contains

Podehaye at 08:16, 2 August 2019

2019-08-02T08:16:44Z

Podehaye at 07:51, 2 August 2019

2019-08-02T07:51:26Z

Pm88: /* Why it is important */

2019-08-01T14:17:45Z

Why it is important

Pm88 at 10:59, 31 July 2019

2019-07-31T10:59:03Z

Pm88: /* Wishlist WebXRay side */

2019-07-31T10:56:58Z

Wishlist WebXRay side

Pm88: /* Wishlist WebXRay side */

2019-07-31T10:56:44Z

Wishlist WebXRay side

Pm88: /* Wishlist WebXRay side */

2019-07-31T10:56:31Z

Wishlist WebXRay side

Pm88 at 10:55, 31 July 2019

2019-07-31T10:55:35Z

Pm88 at 10:54, 31 July 2019

2019-07-31T10:54:57Z

@@ Line 9: / Line 9: @@
 The list is a JSON file. Each entry in the list has the following fields:
-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.
+* '''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 (This should become the label on here, but also added in the {{P|27}} property)
+* '''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') (These should become aliases under {{P|27}}, note that we can have many entries for each)
+* '''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 ({{P|33}}, maybe {{P|15}})
+* '''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. 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.
+* '''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 ({{P|126}})
+* '''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. 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?
+* '''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. I suggest {{P|127}} and not {{P|10}}, it's more precise.
+* '''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'. 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/???.
+* '''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 {{P|118}}
+* '''domains''': an array of domian names (strings) which are owned by the given service or company {{P|118}}
 ==Why it is important==

@@ Line 4: / Line 4: @@
 ==What the database contains==
 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
-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==

@@ Line 8: / Line 8: @@
 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
-parent_id: 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

@@ Line 29: / Line 29: @@
 ==Why it is important==
-* adtech sucks!
+* The domain ownership list needs to be populated to offer an index of simply where personal data is being sent, and where the legal ownership of the domains rests.
-* third party tracking is the worst
+* Without these fields, the filing of SARs is far more time consuming, and mass inspections of websites are barely intelligible.
 ==Why it is important to build it collaboratively==
 * can do SARs, and build the whole pipeline of support around that

← Older revision		Revision as of 10:59, 31 July 2019
Line 1:		Line 1:
−	Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.	+	Drawn from the [https://www.webxray.org webXray project], this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.

	The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].		The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].

@@ Line 41: / Line 41: @@
 ==Wishlist WebXRay side==
 * Framework for contributions and easy format for submission.
-* Bulleted list item
+* contributions!

← Older revision		Revision as of 10:56, 31 July 2019
Line 40:		Line 40:

	==Wishlist WebXRay side==		==Wishlist WebXRay side==
−	* ~~???~~	+	* Framework for contributions and easy format for submission.
		+	- contributions!

← Older revision		Revision as of 10:55, 31 July 2019
Line 1:		Line 1:
		+	Drawn from the webXray project, this list provides a hierarchical accounting of what entities own commonly found third-party domains on the web.
		+
	The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].		The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].

← Older revision		Revision as of 10:54, 31 July 2019
Line 1:		Line 1:
−	~~==What the database contains==~~
	The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].		The database is hosted at [https://github.com/timlib/webXray_Domain_Owner_List Github].

		+	==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: