Wikidata

Wikidata:Property proposal/Identifiant itch.io

< Wikidata:Property proposal

ID on itch.io

edit

Originally proposed at Wikidata:Property proposal/Authority control

   Not done
DescriptionURL of the game on itch.io
Data typeURL
Domainvideo game (Q7889)
Allowed values\S+:\S+
Example 1Night in the Woods (Q19383244) → finji:night-in-the-woods
Example 2Pikuniku (Q60774329) → devolverdigital:pikuniku
Example 3Anodyne (Q16267613) → sean-han-tani:anodyne
Sourceitch.io (Q22905933)
Planned useAdding link to a few games to itch.io
Number of IDs in source> 152 000, but most are likely not in wikidata, so I guess much less
Expected completenessalways incomplete (Q21873886)
Formatter URLhttp://tools.wmflabs.org/wikidata-externalid-url/?p=XXX&id=$1
Robot and gadget jobsnone planned

Motivation

edit

Completeness along GOG application ID (P2725) or Steam application ID (P1733), also would be useful combined with Visual Novel Database ID (P3180) since there is a few VN on itch.io Misc (talk) 19:42, 11 February 2019 (UTC)[reply]

Discussion

edit

  Notified participants of WikiProject Video games

I propose to use the full URL here, since itch.io has 1 website per creator, so using a external_id would requires some more complex transformation than just a prefix (like gog.com allow). A regexp matching would be fine, not sure if this can be done (something like https://$1.itch.io/$2 with external_id matched against (\S+)/(\S+) ). 

# All itch.io URLs 
SELECT ?item ?itemLabel (SAMPLE(?typeLabel) as ?nature) ?propertyLabel ?url
WITH {
  SELECT ?property WHERE {
    ?property rdf:type wikibase:Property.
    ?property wikibase:propertyType wikibase:Url .
  }
} AS %properties
WITH {
  SELECT ?item ?url ?property WHERE {
    INCLUDE %properties .
    ?property wikibase:directClaim ?wdt.
    ?item ?wdt ?url.
    FILTER regex (STR(?url), "itch.io").
  }
} AS %items
WHERE {
  INCLUDE %items.
  ?item wdt:P31 ?type.
  SERVICE wikibase:label {
    bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". 
    ?type rdfs:label ?typeLabel.
    ?item rdfs:label ?itemLabel.
    ?property rdfs:label ?propertyLabel.
  }
} GROUP BY ?item ?itemLabel ?propertyLabel ?url
Try it!
  •   Comment If we use both, wouldn't it mean we can't enforce constraint (like making sure distribution format (P437) has a value of itch.io (Q22905933), since this wouldn't make sense for a developer ? Misc (talk) 23:28, 3 March 2019 (UTC)[reply]
  •   Comment So, wouldn't it make more sense to have a separate "profil on itch.io", for developper/studio, and keep this property for game ? Then the 2nd one can just be a simple url ($1.itch.io). This would also permit to extract informations such as the twitter account associated with the developper/studios, since that's in the webpage in a parsable format (a meta tag). I see also there is a numerical ID for both games and developpers in the same meta tag, not sure how to use it except injecting in some query url like https://itch.io/games-like/XXX ), so I think this might not be that useful. --Misc (talk) 20:32, 8 March 2019 (UTC)[reply]
  •   Support Developers and video games needs their own seperate identifiers. --Trade (talk) 13:15, 1 June 2019 (UTC)[reply]
  •   Oppose proposed format. Use URL-datatype instead. --- Jura 22:02, 1 June 2019 (UTC)[reply]
  • The proposed format is not an identifier used on that site nor does it allow to generate urls directly at Wikidata. The only advantage I see it that it might save 15 bytes per value. --- Jura 07:42, 4 June 2019 (UTC)[reply]
  •   Support either way (URL or compound ID). Another small advantage of using this compound ID method is that if they change their URL format somewhere down the track, we can adapt more easily. --99of9 (talk) 03:20, 3 July 2019 (UTC)[reply]
  •   Comment I have been thinking a lot about this, and I see more and more where Jura1 is coming from. I’m not sure I care either way − I think I’m just more "used" to the idea of IDs and compound IDs (pun intended ;)) than URLs. I wonder if this would be worth bringing to the Project chat to get more opinions involved? Jean-Fred (talk) 09:34, 3 July 2019 (UTC)[reply]
  •   Comment I think this really ought to be a URL, let's not invent our own formats and use a proxy to transform that into a URL. That is really against the philosophy of the semantic web I would say. − Pintoch (talk) 21:00, 23 July 2019 (UTC)[reply]
  • Marking as not ready while the datatype and the examples do not match. − Pintoch (talk) 21:10, 23 July 2019 (UTC)[reply]
  • I would prefer it as external ID even if the content of the property is an url. On the pages of items the external IDs are sorted at the bottom and I think this belongs at the place where all the other IDs are listed. Listing some stores in the external ID section while listing others in the regular section is inconsistent. ChristianKl ❪✉❫ 13:12, 20 August 2019 (UTC)[reply]
    • I don't think we should use external-ids for URLs merely because Wikidata's GUI is (currently) suboptimal. Maybe you could just follow up on the requests to improve this. --- Jura 15:54, 20 August 2019 (UTC)[reply]

@Misc, ChristianKl, Jura1: Another proposal was made at Wikidata:Property proposal/Itch.io ID and the property now created at itch.io URL (P7294). Jean-Fred (talk) 21:08, 8 September 2019 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Identifiant_itch.io&oldid=1010341881"