Moving terms and statements into a general "Legal" list

[stuartpb]

Continuing from where #22 left off.

[stuartpb]

Putting this on v0.1.0 because every time I've profiled "Terms & Conditions" as "terms.service" I've died a little inside

[stuartpb]

I'm agonizing over what to call the second-level property... I think I'm going to go with documents. That seems like the best plan for now.

[stuartpb]

Anyway, I want to do this now, because I'm reviewing npm right now and they have an EULA, and calling that "Terms of Service", fuggheddabout it

[stuartpb]

Also, these might get a set of governs: [] tags at some point, or stipulates or something, though that is veering dangerously into out-of-scope ToSDR territory.

Something like governs tags could make sense for a dumb-presentation use case, though, ie. "what should I make handy on the registration page".

[stuartpb]

There should definitely be a Profile Style Guide about this, something that prioritizes consistency, a la #194. So, for instance, GoDaddy's "Universal Terms of Service Agreement" is just called "Terms of Service", because everything else is just dressup.

[stuartpb]

Likewise, "Terms and Conditions" will be written like that, regardless of ampersands, because, well, ampersands can be tricky, and if we're going to fall one way or the other, it might as well be the one with fewer edge case issues.

[stuartpb]

So, when it comes to picking a name, the priorities go:

• Pick whatever's more common. For example, Double Fine links to "Registration Terms" as "Terms of Use", so it's titled as the latter, even though the former is what's on the page.
• If both names are common, pick whatever's highest on the page. So, for instance, Makerbot links to their Terms of Use as "Terms of Service": since the page says Terms of Use, that's the one that wins.

[stuartpb]

And, of course, those rules aren't hard and fast. For instance. the page title (technically the highest thing in the HTML) on https://www.redditgifts.com/privacy/ calls it a "Privacy Policy", and that would be the most common name for it, but the document itself refers to it as "the Notice", and refers to Reddit's "Privacy Policy" using that term to denote a separate document - so, in this case, it really should be Privacy Notice, because there's a significant meaning to the distinction.

[stuartpb]

Like, the "Title" field for legal documents follows the rules for name on profiles, ie. it's how the document would be referred to in a sentence (by somebody other than the people who wrote it - for instance, GoDaddy doesn't get a pass just because they actually spell out "Universal Terms of Service Agreement" every time they refer to their Terms of Service).

In fact, I'm thinking of redubbing it name, for that exact reason.

[stuartpb]

Yep, I'm going that way, for the same reason I picked name on the root. Titles are formal, names are practical. Maybe some day title will return for these documents, so they can also assert that the document commoners would call "Terms of Service" is truly entitled "The Honorable Sir Archduke Universal Terms of Service Agreement Policy Statement Mazie (Mazie? Mazie!) Awesome Sauce and Conditions von Lichtenstein III, Slayer of Tiamat and King of the First Men - Revised".

However, it's name in a list and not a pre-assigned field because there is some practical use in preserving the differences in the core of the name (especially as how sometimes, for instance, there's a Site Terms of Use and an API Terms of Use).

[stuartpb]

Also, they work the same way as name in that they are not localized, under reasoning laid out in https://github.com/opws/domainprofiles/issues/12#issuecomment-280604792.

[stuartpb]

Reminding myself here that Upwork's profile is already out of date somehow with its legal documents, and the URLs should be updated in the next review (as well as adding the rest of the documents it lists).