opws/opws-dataset

Removing notes that won't migrate in v0.2

stuartpb opened this issue · 2 comments

Following the procedure described in opws/opws-schemata#1 (comment), this issue will track all the "notes" properties that aren't getting a formalized location in schema v0.2, which will instead be removed altogether (until such time as a better way of codifying their information is introduced in the schema).

In the future, this kind of stuff will probably be tracked closer to the schemata issue tracker and/or pull requests for a running draft branch of the dataset here, but this is a special case due to the way v0.1 shipped with a hole in validation for notes, and many of the discussions around the properties described in these notes have lingering schema-discussion issues here (to be migrated to the schemata issue tracker in accordance with #308).

That list of removals, from opws/opws-schemata#1 (comment), is:

  • google.com: username.notes (""Username" here describes the name for Gmail addresses. Users do not have to set up a Gmail account name if they use their own email address.\n")
  • google.com: registration.notes ("Registration accepts either an existing email address or a new Gmail address to register.")
  • hrblock.com: password.reset.flow.request.form.notes ("Also accepts a combination of first name, last name, Social Security number, and date of birth.")
  • hrblock.com: username.reminder.request.form.notes ("Also accepts a combination of first name, last name, Social Security number, and date of birth.")
  • linkedin.com: password.reset.flow.submit.destination.notes ("The stub page includes a "Sign In" link, even though you are signed in after submitting the new password.")
  • linkedin.com: password.reset.flow.submit.sessions.notes ("The form to submit the password includes a checkbox to control whether other sessions should be logged out or not.")
  • linkedin.com: password.change.sessions.notes ("The form to submit the password includes a checkbox to control whether other sessions should be logged out or not.")
  • mammothhq.com: password.reset.flow.response.email.notes ("Sender address is a long random name starting with "bounce" and ending with @email.mammothhq.com")
  • netflix.com: password.reset.flow.request.form.notes ("Also accepts a combination of first name, last name, and credit card number.")
  • ultrahook.com: registration.notes (""username" is technically "webhook namespace".\n")

OK, that's the lot of 'em, closing this issue and proceeding with the rest of opws/opws-schemata#1.