Wikidata:Property proposal/login/signup page

login page

Originally proposed at Wikidata:Property proposal/Computing

   Done: login URL (P11903) (Talk and documentation)

Description	webpage used to log into a service
Represents	login page (Q2139769)
Data type	URL
Domain	website (Q35127), online service (Q19967801), organization (Q43229), video game (Q7889)
Example 1	Google Search (Q9366)login/signup pagehttps://accounts.google.com/signinobject has role (P3831)login page (Q2139769)
Example 2	TikTok (Q48938223)login/signup pagehttps://www.tiktok.com/loginobject has role (P3831)login page (Q2139769)
Example 3	Minecraft (Q49740)login/signup pagehttps://www.minecraft.net/loginobject has role (P3831)login page (Q2139769)
Example 4	Internal Revenue Service (Q973587)login/signup pagehttps://sa.www4.irs.gov/eauth/pub/login.jspobject has role (P3831)login page (Q2139769)
Planned use	large scale addition of property to online services
See also	official website (P856)
Wikidata project	WikiProject Websites (Q15831464)

registration page

Originally proposed at Wikidata:Property proposal/Computing

   Done: registration page URL (P11904) (Talk and documentation)

Description	webpage used to sign up for a service
Represents	registration page (Q116762009)
Data type	URL
Domain	website (Q35127), online service (Q19967801), organization (Q43229), video game (Q7889)
Example 1	Google Search (Q9366)login/signup pagehttps://accounts.google.com/signupobject has role (P3831)registration page (Q116762009)
Example 2	English Wikipedia (Q328)login/signup pagehttps://en.wikipedia.org/wiki/Special:CreateAccountobject has role (P3831)registration page (Q116762009)
Example 3	Internal Revenue Service (Q973587)login/signup pagehttps://api.id.me/en/registration/newobject has role (P3831)registration page (Q116762009)
Planned use	large scale addition of property to online services
See also	official website (P856)
Wikidata project	WikiProject Websites (Q15831464)

Motivation

This will further expand our coverage of websites. Helpful information to include. -wd-Ryan (Talk/Edits) 22:14, 11 February 2023 (UTC)

Discussion

• julle (talk) wd-Ryan (talk/edits) Arlo Barnes (talk) WT20 (talk) Zblace (talk) applsdev RampantSpirit (talk)
  Notified participants of WikiProject Websites -wd-Ryan (Talk/Edits) 22:14, 11 February 2023 (UTC)

•  Comment what are the delimitations of what sorts of pages would be in / not in scope for this property? For example, would https://4chan.org/pass count? Arlo Barnes (talk) 22:41, 11 February 2023 (UTC)

  Probably not that page as it looks like the purchase page, but https://sys.4chan.org/auth I would say yes. This would be the scope:

  1. Webpage to authenticate the user's existing account to access features.
  2. Webpage to create a new account on the service.

  -wd-Ryan (Talk/Edits) 22:59, 11 February 2023 (UTC)

•  Support. Nomen ad hoc (talk) 23:01, 11 February 2023 (UTC).
•  Support Laftp0 (talk) 03:07, 12 February 2023 (UTC)
•  Question regarding scope of modeling: Based on the examples I’m assuming this is geared toward
  • human website users. But wouldn’t it be perhaps even more helpful to have this information as relevant for bots, since for humans the login/signup page is usually just one click away from the landing/home page, whereas bots might have difficulties identifying the relevant links? And if we are thinking about bots, how are we modeling API endpoints more generally?
  • websites with in-page login forms. What about websites that support or require authentication via client certificate, Kerberos, HTTP Basic authentication and similar? ―BlaueBlüte (talk) 01:30, 14 February 2023 (UTC)

  We could greatly expand our coverage of API endpoints, but right now we don't model them very much. This goes in line with the other URL properties. -wd-Ryan (Talk/Edits) 03:59, 14 February 2023 (UTC)

•  Question regarding modeling choices: What is the advantage of using qualifiers to distinguish between signup and login pages, as compared to using two distingt properties, one for ‘signup page’ and one for ‘login page’? ―BlaueBlüte (talk) 01:30, 14 February 2023 (UTC)

  They are very similar, and both logging in and signing up can be at the same URL. If others think we need two separate ones I'd be okay with that, but it seems unnecessary. -wd-Ryan (Talk/Edits) 03:56, 14 February 2023 (UTC)

•  Weak support I’d more strongly support splitting this into two properties for signup and login respectively. ―BlaueBlüte (talk) 19:21, 9 March 2023 (UTC)

  Does anyone else agree? I can do that. -wd-Ryan (Talk/Edits) 20:41, 9 March 2023 (UTC)

   Support --Horcrux (talk) 11:44, 20 July 2023 (UTC)

•  Support. This sounds like a sensible extension of our existing coverage of websites. However, as mentioned directly above, it seems most logical to have two properties to cover this, which would make it simple to find the specific page you need and avoids the clunky wording of "login/signup". BEANS X2 (talk) 10:17, 23 April 2023 (UTC)
• I also support creating two properties. If the login page is the same as sign up page, then they simply have the same value. Midleading (talk) 02:16, 3 July 2023 (UTC)
• I split the property into two based on feedback. -wd-Ryan (Talk/Edits) 16:26, 20 July 2023 (UTC)

@Arlo Barnes, BEANS X2, BlaueBlüte, Horcrux, Laftp0, Mahir256: @Midleading, Nomen ad hoc, Tinker Bell, Wd-Ryan: login URL (P11903) and registration page URL (P11904)  Done. Good contributions, Ederporto (talk) 09:30, 21 July 2023 (UTC)