Content policy

[stuartpb]

opensets/domainprofiles describes objective data only, such as mechanisms and locations.

opensets/domainprofiles does not restrict what domains it profiles on the basis of content, nor does it attempt to describe a domain's content with subjective labels, such as "not safe for work".

Endpoints that want to filter, or otherwise profile, sites based on their content should look into an existing commercial product or service, such as WebSense or Blue Coat, that best fits their use case. Endpoints may also consider reading content keywords provided via meta tags when retrieving pages on the domain.

[stuartpb]

I will note that, while the ultimate goal and rule is to catalogue everything, there's kind of an unspoken soft diversity guideline, where merge activity is biased toward diversity and balance, so as to avoid pigeonholed perceptions of topical focus.

Like, for instance, there are already a few more Seattle/Washington-related domain profiles in the database than I'm really comfortable with: if I were to get pull requests for, like, twelve more, I'd want to hold off on starting to merging them until having either a dozen or so more profiles for places outside of Washington, or like fifty new profiles that aren't related to Seattle (so the disproportionateness would be a bit less glaring).

[stuartpb]

Moving to opws/opws-guidelines#5.