Open main menu

Wikidata:Property proposal/Generic

< Wikidata:Property proposal(Redirected from Wikidata:Property proposal/Event)

See alsoEdit

This page is for the proposal of new properties.

Before proposing a property

  1. Check if the property already exists by looking at Wikidata:List of properties (research on manual list) and Special:ListProperties.
  2. Check if the property was previously proposed or is on the pending list.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
  4. Select the right datatype for the property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

  1. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the proposal, by a property creator or an administrator.
  3. See steps when creating properties.

  On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2019/07.

Contents

GeneralEdit

Digital audio workstationEdit

   Under discussion
Descriptiondigital audio workstation that a person uses
Representsdigital audio workstation (Q1060750)
Data typeItem
Domainhuman (Q5)
Example 1Basshunter (Q383541)FL Studio (Q740562), Steinberg Cubase (Q862505), Pro Tools (Q247670)
Example 2Alan Walker (Q21808729)FL Studio (Q740562)
Example 3Afrojack (Q349041)FL Studio (Q740562)
Sourceexternal reference
Expected completenessalways incomplete (Q21873886)
See alsoinstrument (P1303)

MotivationEdit

Property for digital audio workstation. Eurohunter (talk) 16:36, 20 July 2019 (UTC)

  •   Support David (talk) 06:44, 21 July 2019 (UTC)

Musiikkituottajat artist IDEdit

   Under discussion
Descriptionidentifier for an artist on Musiikkituottajat music site
RepresentsMusiikkituottajat (Q6401891)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Basshunter (Q383541)basshunter
Example 2Stromae (Q313453)stromae
Example 3Sean Paul (Q200577)sean+paul
Sourcehttps://www.ifpi.fi
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usePutting value to musical artists available from the Musiikkituottajat site.
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.ifpi.fi/lista/artistit/$1
See alsoOfficial Charts artist ID (P6559)

MotivationEdit

Property for artists included in Musiikkituottajat. There is also proposal for Musiikkituottajat artist ID for certyfications. Eurohunter (talk) 22:00, 29 June 2019 (UTC)

Qobuz artist IDEdit

   Ready Create
Descriptionidentifier for an artist on Qobuz music site
RepresentsQobuz (Q3412507)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Basshunter (Q383541)basshunter
Example 2Stromae (Q313453)stromae
Example 3Sean Paul (Q200577)sean-paul
Sourcehttps://www.qobuz.com
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usePutting value to musical artists available from the Qobuz site.
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.qobuz.com/fr-fr/interpreter/$1/download-streaming-albums
See alsoKKBox artist ID (P5154)

MotivationEdit

Property for artists included in Qobuz. Eurohunter (talk) 14:55, 12 June 2019 (UTC)

  •   Comment Is there a version of the formatter URL that is region-independent (i.e. that lacks a specifier such as 'fr-fr' in it)? Mahir256 (talk) 23:30, 12 June 2019 (UTC)
    • @Mahir256: Yes. I don't know if there is other way (international version). Eurohunter (talk) 07:18, 13 June 2019 (UTC)
  •   Support David (talk) 07:45, 13 June 2019 (UTC)
  •   Support Cwf97 (talk) 10:40, 28 June 2019 (EST)
  •   Support The fr-fr part of the link should be removed. The site will automatically find a suitable language. - Premeditated (talk) 17:20, 9 July 2019 (UTC)
@Eurohunter: After my experience it exists an artist pages for all languages (available on the site), they are just in a different language. Like if you click on https://www.qobuz.com/interpreter/sean-paul/download-streaming-albums the website will choose the language based on your public IP location. For me it's redirecting to the british language (/en-GB/). If you are in French, it should redirect to the french language website (/fr-fr/). - Premeditated (talk) 18:46, 9 July 2019 (UTC)
@Premeditated: Are you sure is it only language? iTunes for example has different releases in few countries. Eurohunter (talk) 19:23, 9 July 2019 (UTC)
That is for albums and songs. It's artist pages we discuss, right? - Premeditated (talk) 19:27, 9 July 2019 (UTC)
@Premeditated: Yes but if releases are country-dependent you could notice different releases on artist page and maybe other differences. Eurohunter (talk) 17:43, 13 July 2019 (UTC)

7digital United Kingdom artist IDEdit

   Under discussion
Descriptionidentifier for an artist on 7digital United Kingdom music site
Represents7digital United Kingdom (Q64556123)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Basshunter (Q383541)basshunter
Example 2Stromae (Q313453)stromae
Example 3Sean Paul (Q200577)sean-paul
Sourcehttps://uk.7digital.com
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usePutting value to musical artists available from the 7digital United Kingdom site.
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://uk.7digital.com/artist/$1
See alsoKKBox artist ID (P5154)

MotivationEdit

Missing property. Other properties needed include 7digital United Kingdom release ID or 7digital Sverige artist ID. Eurohunter (talk) 15:51, 11 June 2019 (UTC)

DiscussionEdit

  •   Support David (talk) 07:03, 12 June 2019 (UTC)
  •   Comment Is there a way to make the 7digital identifiers region-independent, or does each regional site have its own distinct identifiers for the same artists? Mahir256 (talk) 23:56, 12 June 2019 (UTC)
    • @Mahir256: It's like iTunes. Every country has their independent releases but with the same id. So as I said in motivation I think we need to have separate id for 7digital United Kingdom, 7digital Sverige, 7digital Deutschalnd, 7digital France, 7digital Italia etc. to distinguish se. uk. de. fr. it. in url. In addition iTunes on Wikidata need separate id for other countries like Sweden and UK because it has only US version of url so I never make it to work to add other versions like Swedish or British versions of iTunes. Eurohunter (talk) 07:35, 13 June 2019 (UTC)
If they have the same ID, then we should have only one property. You can set several formatter URL's with qualifiers (not that the UI understands this, but it's at least human-interpretable) or use the third-party formatter URL property if that makes more sense. ArthurPSmith (talk) 17:30, 18 June 2019 (UTC)
@ArthurPSmith: Can you show example? Eurohunter (talk) 18:34, 18 June 2019 (UTC)
The properties listed here are ones where the third-party formatter URL is used, for example Library of Congress authority ID (P244). Tennis Temple player ID (P4544) is an example of a property with different formatter URL's for different languages. ArthurPSmith (talk) 20:10, 18 June 2019 (UTC)
@ArthurPSmith: But there is no example for French version at Tennis Temple player ID. Eurohunter (talk) 20:14, 18 June 2019 (UTC)
@Eurohunter: ArthurPSmith is right, we could make only one property with different formatter URL's for different languages. Even no need use third-party formatter URL property. Regards, ZI Jony (Talk) 06:54, 2 July 2019 (UTC)
@ZI Jony: Can you show example? Eurohunter (talk) 14:48, 2 July 2019 (UTC)

lexemeEdit

   Done: lexeme (P7018) (Talk and documentation)
Description(qualifier) lexeme version of monolingual text
Data typeSense
Domainall names stored in Q-items as Monoligual text which represent notable lexemes
Example 1Bombyx mori (Q134747) taxon common name (P1843) Polish: jedwabnik morwowy → "stored as lexeme" jedwabnik morwowy (L38523-S1)
Example 2Slovakia (Q214) demonym (P1549) Polish: Słowak applies to part (P518) masculine (Q499327) → "stored as lexeme" Słowak (L38296-S1)
Example 3English (Q1860) native label (P1705) English: English → "stored as lexeme" English (L35189-S1)
Example 4Germany (Q183) short name (P1813) French: Allemagne → "stored as lexeme" Allemagne (L22302-S1)
See also

MotivationEdit

Now, when we have lexemes in Wikidata, some monolingual texts could be replaced by lexeme datatype. This however is not easy step. This property could simplify in the future transition by providing direct link to lexeme and its sense. KaMan (talk) 11:54, 1 December 2018 (UTC)

DiscussionEdit

  Support Linking to senses would probably be hard to do automatically, I think this is a great idea. ArthurPSmith (talk) 19:21, 3 December 2018 (UTC)
  Support Useful linkage, and valuable step for any future transition. Jheald (talk) 17:00, 4 December 2018 (UTC)
  •   Oppose proposed label seems inconsistent with others at Wikidata. Usual naming could be "subject of lexeme" --- Jura 06:57, 10 December 2018 (UTC)
    @Jura1: Could you please give plenty of examples of these "others at Wikidata"? I don't think there is many from one namespace to another. KaMan (talk) 07:03, 10 December 2018 (UTC)
    • Do you have any property label that follows the proposed naming? Any property value is obviously "stored" at Wikidata. Comparing to print dictionaries, one might think it's interesting to repeat, but it's implied once you are at Wikidata. Possibly it's a translation issue from Polish. --- Jura 07:06, 11 December 2018 (UTC)
    • @Jura1: "subject of" makes sense when we are referring to a regular property on an item, but this proposal is for a qualifier, so a different context. "subject of lexeme" certainly does not seem right to me to describe a piece of monolingual text that is some value for a statement on an item. "stored as lexeme" makes sense, but there may be a better label. "subject of lexeme" is not better though. ArthurPSmith (talk) 19:06, 10 December 2018 (UTC)
    • it's the qualifier value that is the subject of the lexeme. It probably doesn't even need to be limited to use as a qualifier, as some names have items for themselves. --- Jura 07:06, 11 December 2018 (UTC)
      • Can you give an example? I don't see how that would work with Wikidata's multilinguality. ArthurPSmith (talk) 17:11, 11 December 2018 (UTC)
        • See below. --- Jura 04:39, 14 May 2019 (UTC)
  •   Support NMaia (talk) 02:30, 28 February 2019 (UTC)
  •   Support @KaMan, Jura1, ArthurPSmith: I think this is an important property. Maybe we could change the name to just "as lexeme", so as to keep it between conceptual entities, rather than referring to the actual storage of data in a 'meta' way. Liamjamesperritt (talk) 06:53, 13 May 2019 (UTC)
    • Or just perhaps lexeme ? ArthurPSmith (talk) 12:15, 13 May 2019 (UTC)
    • That would be better. --- Jura 04:39, 14 May 2019 (UTC)
  •   Comment There was some concern about using subject lexeme (P6254) on items like Plus at – en ny konjunktion i dansk (Q58482429) or singular they (Q3437264). Maybe we could use it for that as well. @Fnielsen:. Personally, I still think we could use P6254 for both. --- Jura 04:39, 14 May 2019 (UTC)
  •   Neutral Can't this be a build-in feature of Wikibase interface? --Liuxinyu970226 (talk) 05:00, 26 May 2019 (UTC)
    • @Liuxinyu970226: It should become a feature one day, but it is not one at the moment, and it will require a lot of effort to implement and may take some time. As stated in the 'Motivation' section above, this property will let us describe that information now, and help make the implementation of the feature easier in the future. Liamjamesperritt (talk) 08:49, 30 May 2019 (UTC)
  • @KaMan: Are you ok with the label for this property being just lexeme (which I just edited it to be in the proposal)? ArthurPSmith (talk) 18:23, 1 July 2019 (UTC)

located in the constituencyEdit

MotivationEdit

This property will describe a place which is located in a certain constituency or electoral district. Bodhisattwa (talk) 05:37, 4 March 2019 (UTC)

Sample electoral districts. --- Jura 10:57, 10 March 2019 (UTC)

DiscussionEdit

  • A prior property proposal is at Wikidata:Property proposal/District. @Mdmahir: as proposer, @Jura1: as supporter of that proposal, and @Pigsonthewing, ChristianKl, Pasleim, ArthurPSmith, Yair rand: as opponents of that proposal. Mahir256 (talk) 06:08, 4 March 2019 (UTC)
  •   Comment The relationship between administrative divisions and electoral divisions has been neglected for some time, and most certainly deserves some way of being modeled here on Wikidata. I do think that rather than completely supporting or completely opposing this proposal, changes to this proposal such that the result can handle different political situations will be necessary. To those of you I named above who opposed it, for example, help us handle the situation of countries in which gerrymandering prevails (like in Five Eyes countries). To those of you who support this proposal as written, for example, help us handle the situation of countries in which constituency delimitations follow existing administrative boundaries somewhat well (like in India and Bangladesh). Mahir256 (talk) 06:08, 4 March 2019 (UTC)
  • Intuitively, I would prefer a property that's more general and can be also used for census districts as well as electoral districts.

ChristianKl Oravrattas Tagishsimon Jacksonj04 Owenpatel Markcridge Louisecrow Nomen ad hoc Tubezlob Siwhitehouse Mhl20 Alexsdutton Danadl Teester Zache a_ka_es Hasive Nat965 masti Papuass Jklamo ProtoplasmaKid Jmmuguerza Graemebp Pete Forsyth Jelabra Rfitzel Davidpar Canley Bodhisattwa CYAN Masssly MJL tdombos salgo60 Daniel Mietchen

  Notified participants of WikiProject every politician ChristianKl❫ 08:32, 4 March 2019 (UTC)

  •   Support Good idea, located in the administrative territorial entity (P131) is not appropriate place for constituencies.--Jklamo (talk) 10:10, 4 March 2019 (UTC)
  •   Support Yes. depending on electoral law per country it can or cannot have the same boundaries as administrative regions Masti (talk) 10:57, 4 March 2019 (UTC)
  •   Oppose (as currently written, though I'm supportive of the larger idea). Allocating every city, town, village etc to specific electoral districts (as well as to an administrative district) doesn't seem either sensible, or particularly useful. The example given above, of Sarbari (Q60292834) being in both Bankura Lok Sabha constituency (Q4856799) and Raghunathpur Vidhan Sabha constituency (Q7283039) doesn't seem like the best way of being able to say that. I agree that we definitely need a good way of relating electoral districts and administrative districts, but this doesn't seem to be it.
    • More generally, there are four scenarios that we generally need to cover here, for each type of electoral district (and, of course, most places are in multiple different electoral districts simultaneously as they elect people to multiple different bodies: e.g. a city council, county council, state legislature, national legislature, and supranational legislature (some which which can separate constituencies for lower houses vs upper houses). These certainly can neatly nest within each other in some places, but my experience is that that's the exception, rather than the norm.)
      1. Where electoral districts have a one-to-one match to administrative districts (e.g. the US, or Australia, where the constituencies of the Senate are the States).
      2. Where electoral districts neatly contain one or more administrative districts, e.g. in Finland the constituencies of the Eduskunta mostly match the regions of Finland, other than a couple that combine multiple, e.g. South-Eastern Finland (Q18691231) which is made up of South Karelia (Q5691), Southern Savonia (Q5693), and Kymenlaakso (Q5698)
      3. Where an administrative areas neatly contain multiple electoral districts: e.g. each Canadian state contains one, or more than one, Senate division. However, it also often useful to break things down to a higher level of precision, e.g. to say that each the city of Bristol (Q23154) is represented in the UK Parliament by Bristol West (Q1072698), Bristol East (Q1070148), Bristol South (Q578636), and Bristol North West (Q3137955)
      4. Where there is essentially no mapping from an electoral district to an administrative district, other than it being within something at a larger scale (e.g. some of the common examples of heavily gerrymandered districts, or places with complex borders, such as Baarle-Nassau (Q9811), Baarle-Hertog (Q244959), where some of the electoral difficulties are described at http://news.bbc.co.uk/1/hi/world/europe/8027086.stm)
    • A key issue is also that, even when dealing only a single "type" of constituency (and quite a few legislatures explicitly have multiple types) it is not always possible to map all the electoral districts in a given jurisdiction using only one of these methods. This can then make it very difficult to know how to formulate queries to get useful/relevant information back out again, even where you have good knowledge of the underlying structure of that jurisdiction+elected body, and close to impossible if you don't. --Oravrattas (talk) 11:24, 4 March 2019 (UTC)
  • Thinking about this some more, I believe the best way to model this is to provide electoral district maps (i.e. in Commons I guess) for each district, and then you can in principle retrieve relevant districts for any location via those maps. But that doesn't make retrieval of relevant districts for a location easy from the query angle, so it would be helpful to have a secondary (derived) relation that represents the relationship of locations to districts. However, "in" is the wrong word for this, because there are far too many cases (even in the US) where one type of location is not wholly contained within the other type in either direction. So I think a looser secondary "related district" or "overlaps with geographic object" or something like that would be the right sort of property for this. ArthurPSmith (talk) 14:00, 4 March 2019 (UTC)
    @ArthurPSmith: See territory overlaps (P3179). I don't like the increasing number of "located in area of type X" properties. Plenty of countries have many types of regional divisions, some of which aren't administrative territorial entities. Should there be a property for every type? Something else to consider: Is Mexico (Q96) located in the constituency Second constituency for French residents overseas (Q3025246)? --Yair rand (talk) 04:03, 5 March 2019 (UTC)
    Ok,   Oppose this one - use territory overlaps (P3179)! ArthurPSmith (talk) 14:39, 5 March 2019 (UTC)
  •   Oppose Whilst I agree that "located in the administrative territorial entity" is not the ideal property to use to explain the hierarchy of electoral districts, as this stands it seems far too prone to confusing usage. I think @ArthurPSmith: pretty much sums up my concerns, and that the correct solution is to both add spatial data to the Commons (for those who know how to query it, and this is good practice anyway for anything with a boundary) and to be able to say "related to district" for expressing more concrete terms such as "this district is explicitly defined as being a part of this district" and vice-versa. --jacksonj04 (talk) 09:35, 6 March 2019 (UTC)
  •   Support I don't really see another working solution. P131 might seem to be working for countries where they more or less fit between existing administrative layers, but even there it tends to lead to the mistaken assumption that electoral districts actually are administrative layers. --- Jura 10:57, 10 March 2019 (UTC)

inverse label itemEdit

   Ready Create
Descriptionitem with labels of the inverse relationship of a property
Data typeItem
Domainproperties with item datatype
Example 1instance of (P31) → item with label "has instance" (en)
Example 2subclass of (P279) → item with label "superclass of" (en)
Example 3place of birth (P19) → item with label "born here" (en)

MotivationEdit

While some properties have an inverse property it is unlikely that we will ever have for all properties with item datatype an inverse. Nevertheless, some tools display inverse relationships even if an explicit inverse property is missing, e.g. reasonator, sqid, derivedstatements. In future, such a functionality could even be implemented in Wikidata itself. To improve these tools it would be good to store the label of the inverse relationship on the property page, see examples above. --Pasleim (talk) 17:03, 14 January 2019 (UTC)

DiscussionEdit

On problem of this solution is that we might end up with 20 values in different languages. That takes up space. Additionally if we need qualifiers we have to copy them again for every language. ChristianKl
ArthurPSmith
d1g
JakobVoss
Jura
Jsamwrites
MisterSynergy
Salgo60
Micru
Pintoch
Harshrathod50
Wildly boy
ZI Jony
Ederporto
99of9
Danrok
Eihel
Emw
Fralambert
GZWDer
Ivan A. Krestinin
Jonathan Groß
Joshbaumgartner
Kolja21
Kristbaum
MSGJ
Mattflaschen
MichaelSchoenitzer
Nightwish62
Pablo Busatto
Paperoastro
PinkAmpersand
Srittau
Thierry Caro
Tobias1984
Vennor
Yellowcard
Ivanhercaz


  Notified participants of WikiProject PropertiesChristianKl❫ 09:40, 16 January 2019 (UTC)

I agree that this will take up some space but I don't think this is sever. Property pages like Europe PlayStation Store ID (P5971) and Wolfram Language entity code (P4839) have far more statements. --Pasleim (talk) 10:05, 16 January 2019 (UTC)
On space - is this what the proposed "multilingual text" datatype was supposed to cover? It does seem like it would be sensible to allow a property to have values that work like the label and description values, allow for one string value in each language. ArthurPSmith (talk) 18:27, 16 January 2019 (UTC)
Yes, that was the point of the "multilingual text" datatype that we still don't have. ChristianKl❫ 19:20, 17 January 2019 (UTC)
  • We would probably also want to be able to store inverse aliases. Maybe each property should just have a dedicated item for storing inverse name data? --Yair rand (talk) 00:52, 21 January 2019 (UTC)
    • That's a great idea - 'inverse item' rather than 'inverse label'? ArthurPSmith (talk) 17:35, 22 January 2019 (UTC)
      • Sounds good to me. --Pasleim (talk) 10:00, 23 January 2019 (UTC)
      •   Support. updated it accordingly --- Jura 11:17, 3 March 2019 (UTC)
      • tweaked label/description it a bit further. --- Jura 11:53, 10 March 2019 (UTC)

arcade system motherboardEdit

   Ready Create
DescriptionArcade system hardware board the system motherboard used by a hardware device
Representscomputer hardware (Q3966)
Data typeItem
Template parameter|placa base= and |sistema arcade= in Ficha de hardware and Ficha de videojuego
Domainproperty
Example 1Tempest (Q1340846) Atari Vector (Q63109245)
Example 2Killer Instinct (Q973459) Killer Instinct arcade motherboard (Q63109134)
Example 3F-Zero GX (Q1940315) Triforce (Q1324477)
Example 4Open Desktop Workstation (Q838593) Pegasos (Q2067286)
Planned useAlmost inmediately, to be used in (Arcade) videogames infobox

MotivationEdit

I want to create this as a series of properties to be used in Videogames infoboxes. This would be an alias for "Motherboard" instead. Namely, this is intended for the motherboard codename, specially in arcade machines, wich several ones uses the same motherboard. Amitie 10g (talk) 22:01, 1 April 2019 (UTC)

ΛΧΣ21 Vacation9 John F. Lewis (talk) Bene* talk #Reaper (talk) Josve05a (talk) Chris Mason (talk) FunPika Arthena (talk) Wangxuan8331800 (talk) Sjoerd de Bruin (talk) Zerabat (talk) Nicereddy (talk) Syum90 (talk) DrakeCaiman (talk) --George (Talk · Contribs · CentralAuth · Log) Andreasburmeister (talk) Danrok (talk) 18:20, 30 October 2015 (UTC) Macrike (talk) Dispenser (talk) 16:56, 7 July 2017 (UTC) --Zache (talk) 13:34, 12 July 2017 (UTC) Mohammed Adam (T) SharkD  Talk  06:41, 9 November 2017 (UTC) ZebaX2010 (talk) 00:49, 21 November 2017 (UTC) Sight Contamination (talk) Lewis Hulbert (talk) 20:26, 13 December 2017 (UTC) Jean-Fred (talk) 10:48, 28 February 2018 (UTC) Santer (talk) Cloaker416 (talk) 22:18, 12 June 2018 (UTC) Rampagingcarrot (talk) 19:57, 28 June 2018 (UTC) Diggr (talk) 08:07, 3 July 2018 (UTC) Harsh Rathod Poke me! 09:42, 7 July 2018 (UTC) Kirilloparma (talk) 00:30, 5 August 2018 (UTC) Sir Lothar (talk) 10:10, 10 August 2018 (UTC) Cwf97 (talk) 14:33, 22 October 2018 (UTC) Esteban16 (talk) 00:08, 27 October 2018 (UTC) Peterchanws Brasig Le Yota de Mars YotaMoteuchi (talk) 08:09, 22 May 2019 (UTC)   Notified participants of WikiProject Video games --Jean-Fred (talk) 17:04, 8 April 2019 (UTC)

DiscussionEdit

  Comment Can you fix the examples? NMaia (talk) 01:12, 2 April 2019 (UTC)

I've added the proposed value. Is this a right value for items already existing in Wikidata (ej. the motherboard used in an arcade system)?
If I understand correctly, you would like to express Star Wars (Q54317) Atari Star Wars Vector (Q17462637)?
If so, I have been wondering − shouldn’t we just use Star Wars (Q54317) platform (P400) Atari Star Wars Vector (Q17462637)? This is already used in the wild:
SELECT ?item ?itemLabel ?platform ?platformLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P31 wd:Q7889.       # All video games...
  ?item wdt:P400 ?platform.     # ...whose platform...
  ?platform wdt:P31 wd:Q631229. # is an arcade system board.
}

Try it!

Jean-Fred (talk) 17:15, 8 April 2019 (UTC)

  Oppose Agree that platform (P400) could be used instead. Thadguidry (talk) 22:33, 8 April 2019 (UTC)

  • platform (P400) refers to the platform in general (Arcade, Nintendo 64, etc, wich is used already), while "Arcade system" refers to the details of the hardware (generic or codename of the motherboard). arcade system board (Q631229) is a statement, not a property, what we need for the infobox. "Hardware" could be also a name for this property. --Amitie 10g (talk) 15:44, 9 April 2019 (UTC)
    Well, at some level we get to decide what platform (P400) means :). You could argue the same way for console and PC games, that we should do something like:

Metal Gear Solid (Q6582527) platform (P400) video game console (Q8076)
Metal Gear Solid (Q6582527) <Hardware> PlayStation (Q10677) or
Star Wars: The Old Republic (Q737308) platform (P400) personal computer (Q16338)
Star Wars: The Old Republic (Q737308) operating system (P306) Microsoft Windows (Q1406)

  • The layout of the downstream infobox which will use the data is somewhat irrelevant: as far as I know, there is no need for 1-1 mapping between infobox fields and Wikidata statements − I think the infobox could be coded either way in the Lua.
    (Not entirely sure what you mean by « arcade system board (Q631229) is a statement, not a property » − based on the definitions used here, it’s neither ;-))
    Jean-Fred (talk) 08:51, 12 April 2019 (UTC)
Thanks for fixing the example ; however one question: we can’t model free-text like « Proprietary MIPS based hardware system ». In this case, would it make sense to create an item for that particular hardware? Jean-Fred (talk) 08:52, 12 April 2019 (UTC)
Well, as no way to create free text, I'll take care to create new elements for missing ones, as you mentioned (see the examples above, I fixed them). --Amitie 10g (talk) 12:12, 12 April 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics

  •   Support --Tinker Bell 22:39, 14 April 2019 (UTC)
  •   Support Sir Lothar (talk) 10:20, 23 April 2019 (UTC)
  •   Support.--Vulphere 02:41, 28 May 2019 (UTC)
  •   Comment Would it not make more sense to have a more generic "hardware" property and then use a qualifier to specify if it is the motherboard or another piece of hardware? --SilentSpike (talk) 20:20, 7 July 2019 (UTC)

audio systemEdit

   Under discussion
Descriptionaudio system hardware
Representscomputer hardware (Q3966)
Data typeItem
Template parameter|audio= in Ficha de hardware and Ficha de videojuego
Domainproperty
Example 1Central Park (Q5061601) bell (Q101401)
Example 2Star Wars (Q54317) POKEY (Q753671)
Example 3Super Nintendo Entertainment System (Q183259) SPC700 (Q1368119)
Planned useAlmost inmediately, to be used in (Arcade) videogames infobox

MotivationEdit

Part of my series for requesting properties for Videogame and hardware infoboxes, namely the audio system for consoles and arcades. --Amitie 10g (talk) 23:50, 1 April 2019 (UTC)

ΛΧΣ21 Vacation9 John F. Lewis (talk) Bene* talk #Reaper (talk) Josve05a (talk) Chris Mason (talk) FunPika Arthena (talk) Wangxuan8331800 (talk) Sjoerd de Bruin (talk) Zerabat (talk) Nicereddy (talk) Syum90 (talk) DrakeCaiman (talk) --George (Talk · Contribs · CentralAuth · Log) Andreasburmeister (talk) Danrok (talk) 18:20, 30 October 2015 (UTC) Macrike (talk) Dispenser (talk) 16:56, 7 July 2017 (UTC) --Zache (talk) 13:34, 12 July 2017 (UTC) Mohammed Adam (T) SharkD  Talk  06:41, 9 November 2017 (UTC) ZebaX2010 (talk) 00:49, 21 November 2017 (UTC) Sight Contamination (talk) Lewis Hulbert (talk) 20:26, 13 December 2017 (UTC) Jean-Fred (talk) 10:48, 28 February 2018 (UTC) Santer (talk) Cloaker416 (talk) 22:18, 12 June 2018 (UTC) Rampagingcarrot (talk) 19:57, 28 June 2018 (UTC) Diggr (talk) 08:07, 3 July 2018 (UTC) Harsh Rathod Poke me! 09:42, 7 July 2018 (UTC) Kirilloparma (talk) 00:30, 5 August 2018 (UTC) Sir Lothar (talk) 10:10, 10 August 2018 (UTC) Cwf97 (talk) 14:33, 22 October 2018 (UTC) Esteban16 (talk) 00:08, 27 October 2018 (UTC) Peterchanws Brasig Le Yota de Mars YotaMoteuchi (talk) 08:09, 22 May 2019 (UTC)   Notified participants of WikiProject Video games --Jean-Fred (talk) 17:06, 8 April 2019 (UTC)

DiscussionEdit

  • Yep, most of the early Atari machines (arcades and home consoles) used the POKEY audio chipset. Please be aware the older pinballs like Gottlieb's "Central Park" used "bells" as their "audio system", therefore, this property is not limited to electronics. --Amitie 10g (talk) 15:53, 9 April 2019 (UTC)
    Ok, thanks for the explanation. Some additional questions:
    • Would you mind giving additional/different examples with different values?
    • I see in es:Quantum_(videojuego) that the value is “POKEYx2” ; how would should we model this « x2 »?
    • I see that Star Wars (Q54317) has: « 4x Atari POKEY (música y efectos sonoros), Texas Instruments TMS5220 (síntesis de voz) ». How should we model that?
    • Digging around on en.wp for more examples: 3-D Thunder Ceptor II (Q17042246) has « 1x Yamaha YM2151 @ 3.57958 MHz, 1x Namco CUS30 @ 96 kHz, 1x DAC » − how should we model that?
    Sorry for asking all these questions − I’m not that knowledgeable about arcade game machines/systems and I’m trying to understand the use case better :)
    Jean-Fred (talk) 09:01, 12 April 2019 (UTC)

Ok, been thinking about the Star Wars (Q54317) use case ; would that work?

P<audio system>
  POKEY   edit
quantity 4
object has role music
object has role sound effect
▼ 0 reference
+ add reference
  TMS5220   edit
quantity 1
object has role speech synthesis
▼ 0 reference
+ add reference
+ add value

(Not sure whether object has role (P3831) is best here, or whether use (P366) would be better…)

Hope that helps :) Jean-Fred (talk) 09:19, 12 April 2019 (UTC)

  • The "Sound system" property can have more than 1 value, and the template will reflect that correctly. However, I'm finding ways to add a multiplier value if more than a one unit of a specific chip (eg. POKEY x2) has, in the template (reflecting the "number" parameter given above. --Amitie 10g (talk) 12:17, 12 April 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics ChristianKl❫ 13:49, 17 July 2019 (UTC)

WMF short URLEdit

   Under discussion
Descriptionslug of a short URL for a web page, from the official Wikimedia URL Shortener
Data typeExternal identifier
Domainpages on WMF projects
Allowed values[3-9A-HJ-NP-Za-km-z$][2-9A-HJ-NP-Za-km-z$]*
Example 1Wikidata (Q2013)d
Example 2Wikipedia (Q52)w
Example 3Wikisource (Q263)s
Example 4Arabic Wikipedia (Q199700)HU
Example 5French Wikisource (Q15156541)Yj
Formatter URLhttps://w.wiki/$1
See alsoWikidata:URLShortener

MotivationEdit

The official WMF URL shortener is due to launch on 11 April. The format of the URL is w.wiki/ followed by a string of letters and numbers. The examples shown above have been pre-populated, but longer URL slugs will be generated once the system is available to all editors.

Would this be better as an external-ID type property, with a formatter URL of https://w.wiki/$1? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:48, 3 April 2019 (UTC)

Note: consensus seems to be tending towards an external-id datatype; I've modified the proposal accordingly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:07, 4 April 2019 (UTC)

DiscussionEdit

  •   Support as an external ID so long as there is only one possible short URL domain (w.wiki) that the WMF provides. Mahir256 (talk) 15:42, 3 April 2019 (UTC)
  •   Support --Mehman 97 16:08, 3 April 2019 (UTC)
  •   Support ~ Nahid Talk 16:22, 3 April 2019 (UTC)
  •   Support -- Ajraddatz (talk) 18:21, 3 April 2019 (UTC)
  •   Support preferably as external ID; do you have a reference on what characters are allowed in the URL's (i.e. no upper-case letters, no '-', _', etc?) ArthurPSmith (talk) 18:55, 3 April 2019 (UTC)
    Hmm, the '$' ID listed on the documentation page already breaks this regex. ArthurPSmith (talk) 18:57, 3 April 2019 (UTC)
    That appears to be a one-off, so I'd add a constraint-exception. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:24, 3 April 2019 (UTC)
  • How many items for distinct single pages on WMF projects do we have? I feel like this property would only have about 15 uses total... --Yair rand (talk) 20:54, 3 April 2019 (UTC)
  •   Support as external-id NMaia (talk) 02:00, 4 April 2019 (UTC)
  •   Support as external-id. ··· 🌸 Rachmat04 · 06:23, 4 April 2019 (UTC)
  •   Support David (talk) 07:09, 4 April 2019 (UTC)
  •   Support though it seems only stewards will manage the URL themselves.AldNonUcallinme? 13:00, 4 April 2019 (UTC)
    • Not so, any editor in good standing (i.e. not blocked on meta) may create a short URL using this service; only stewards may delete them. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:59, 5 April 2019 (UTC)
  •   Wait Will this be used as a qualifier for links to wikimedia sites? It seems the current proposal doesn't address whether or not that's intended. ChristianKl❫ 07:58, 5 April 2019 (UTC)
  •   Support external identifier John Samuel (talk) 18:19, 5 April 2019 (UTC)
  • I have to echo the concern of Yair Rand: I don't see enough usage beside few designated shortcuts: rest are randomly created. — regards, Revi 04:57, 6 April 2019 (UTC)
    • You don't see "enough usage" because the service is not yet live. As my proposal says, it is due to launch on 11 April. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 06:58, 6 April 2019 (UTC)
      • I don't think we should be storing all the short links for all the wikidata articles, all the wikipedia articles, and then we only have a limited small set of link. That qualifies for "not enough usage", IMO. (In case someone has uncertainty in my comment, interpret my message as firm no.) — regards, Revi 14:45, 13 April 2019 (UTC)
        • Where has anyone proposed "storing all the short links for all the wikidata articles [and] , all the wikipedia articles"? Regardless, it has already been established that there will be more then sufficient short URLs ("1000 or more"), relevant to storage in Wikidata, to justify a new property. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:51, 13 April 2019 (UTC)
  •   Comment seems unclear how this should be used. In general, I think redirecting urls should be avoided. If this property just repeats the interwiki link table (Special:Interwiki), that table might be worth being stored directly. --- Jura 17:25, 7 April 2019 (UTC)
    • "In general, I think redirecting urls should be avoided." The Wikidata community; the wider Wikimedia commmunity, and the WMF all seem to disagree with you. To reiterate: The official WMF URL shortener is due to launch on 11 April. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:44, 7 April 2019 (UTC)
  •   Oppose   Comment @Pigsonthewing: I support the short URL extension and think it will be useful, but I'm not as sure about the proposed property. As written, the property is to be used on the Wikidata items for the projects/sites which the URLs redirect to, rather than the Wikidata items which describe the same entities as the pages which the URLs redirect to (and I suspect it might end up getting incorrectly used for the latter, including people pointlessly generating short URLs for Wikidata items and then circularly adding those short URLs to the Wikidata items). Almost none of the possible IDs will ever have their own items (e.g. "Alan Turing's English Wikipedia article" probably doesn't need an item), and because the targets are limited to pages within the Wikimedia projects, only notable parts of the Wikimedia movement (e.g. Women in Red) would ever get IDs in the first place. Furthermore, the use of a property for this is sort of pointless given that WMF owns and operates the actual database. It doesn't actually seem to have much utility, other than to advertise that the URL shortener exists. (By the way, The Guardian article ID (P6085) – the only existing property for short URLs – is still nominated for deletion for related reasons.) Jc86035 (talk) 17:02, 8 April 2019 (UTC)
    I've struck out the oppose, since a majority of the current short URLs are now redirects to current or possible project home pages. Jc86035 (talk) 17:07, 13 April 2019 (UTC)
  •   Comment I agree with those who think this might be confusing, though I'm not withdrawing my "support" vote above as it still seems a useful thing to record within Wikidata. I would note that per Yair rand's question which Andy failed to answer in a reasonable manner, there is a wikidata entry for every language wikipedia (for example Albanian Wikipedia (Q208533)) so that, with the wiktionaries, wikisources, etc. probably adds up to 1000 or more. ArthurPSmith (talk) 18:20, 10 April 2019 (UTC)
    • Alert readers will note that I had already addressed that point in my answer of 10:05, 4 April 2019; in the light of which, my subsequent answer was perfectly reasonable. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:40, 11 April 2019 (UTC)
  • @ChristianKl: I don't understand your comment about waiting. Can you clarify? As I noted just above, the main purpose I see for this property would be to add this property as a statement, for example Albanian Wikipedia (Q208533) with value whatever the shortener ID for "https://hy.wikipedia.org/" is. This seems particularly useful as the shortener works in one direction (from the shortened ID to the wikimedia page) but there's no obvious reverse, so Wikidata could provide that at least for these main pages.
  • @Yair rand: You didn't state an opinion for or against here, do you have anything further to comment, given that this should be applicable to 1000+ wikidata items? ArthurPSmith (talk) 19:27, 12 April 2019 (UTC)
    • @ArthurPSmith: Wikidata contains plenty of links to Wikimedia websites. It's possible to add a WMF short URL link whenever there is such a link as a qualifier. This discussion till now has had no position on whether adding the property as a qualifier should be allowed. ChristianKl❫ 15:09, 14 April 2019 (UTC)
    • I'm going to abstain on the main proposal (I'm unsure about the value of listing shortened URLs in general), but I   Oppose using this instead of or in addition to normal links in qualifiers/references. --Yair rand (talk) 18:23, 14 April 2019 (UTC)
  •   Oppose WMF already decided to store this elsewhere, similarly to their other short-url scheme. As stated before, Wikidata doesn't generally store url shorter addresses. Besides, there don't seem to be enough uses for these, unless someone makes them for every item (I doubt that is desirable). --- Jura 06:35, 13 April 2019 (UTC)
    • "WMF already decided to store this elsewhere" is, of course, irrelevant to Wikidata - which in any case already has properties for other data which the WMF stores elsewhere. That the quantity of values relevant to our items will be in at least four figures has already been established. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:15, 13 April 2019 (UTC)
      • @Pigsonthewing: Pardon, but is your "WMF already decided...irrelevant to Wikidata" meaning that, in one day future, Wikidata should be splitted from WMF (not only we should have separated server clusters, but also build Privacy Policy, Terms of Use, Code of Conduct... ourselves)? --Liuxinyu970226 (talk) 22:08, 27 May 2019 (UTC)
  • @Pigsonthewing: I've used a shell script to create most of the possible homepage redirects (1,594, although this includes 653 Incubator, Beta Wikiversity and Multilingual Wikisource projects, other currently non-functioning redirects and various other subdomains). I've put them in a Commons data page so that they can be imported if the property is created. Jc86035 (talk) 17:07, 13 April 2019 (UTC)
  •   Comment Some possible issues:
    • Which URLs are to be treated as "canonical" (e.g. https://zh-yue.wikipedia.org/ vs. http://zh-yue.wikipedia.org/ vs. https://yue.wikipedia.org/ vs. https://zh-yue.wikipedia.org vs. https://zh-yue.wikipedia.org/wiki/頭版)? Each of these would be given different redirects by the current version of the software, and at least four variations (5k, 5m, K6 and K7) already exist.
    • How will each URL's target be indicated, if that is done? This would be helpful for more easily filtering incorrect or inappropriate values.
    • What would start time (P580) indicate as a qualifier? Would it indicate the time that the target became valid, the time that the redirect was created, or either?
    Jc86035 (talk) 17:07, 13 April 2019 (UTC)
  •   Oppose I do not see the benefit of adding a dedicated property for a URL shortener - shortened URLs are URLs themselves, so why cannot we use our existing URL properties for them? It is not clear to me why URL (P2699) and its sub-properties are not sufficient. I do not think it is useful to indicate a shortened URL in addition to a longer one: by design, they are equivalent and one can easily convert one into the other, so storing both would not be very useful. Also, shortened URLs are not necessarily unique as explained by Jc86035 above - they are not designed to be used as identifiers at all. So, I very much welcome the introduction of the Wikimedia URL shortener, but I do not think this property would be useful. I also note that Pigsonthewing has been very insistently asking admins to create this property and I do not think this is appropriate. @Pigsonthewing: if you are not satisfied with the property creation delays, feel free to give a hand yourself by creating other property proposals marked as ready (there are 47 of them at the moment, so you have plenty of choice). − Pintoch (talk) 12:40, 26 April 2019 (UTC)
  •   Oppose Per Pintoch. We already have properties for URLs, I do not see the benefit of adding a dedicated property for a URL shortener, although the URL shortener itself is a great tool.--Jklamo (talk) 17:23, 14 May 2019 (UTC)
  • Comment: "shortened URLs are URLs themselves, so why cannot we use our existing URL properties for them?" for the same reason we do not use them for official blog (P1581), archive URL (P1065), or interwiki prefix at Wikimedia (P6720), or any of our identifier properties with a formatter URL. We have ample precedence. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:26, 16 May 2019 (UTC)
    • Each of the properties you mention have a specific reason to be different from URL (P2699), yes. But invoking that "precedence" does not actually give a reason for this particular property to be separate - could you come up with an argument that is actually related to the proposal? − Pintoch (talk) 12:33, 18 May 2019 (UTC)
  •   Support as external-id.--Vulphere 12:31, 27 May 2019 (UTC)
  •   Support Non of the oppose reasons are acceptable for me, there has even no BLP concerns, so why not? @Pintoch:? --Liuxinyu970226 (talk) 22:11, 28 June 2019 (UTC)
    • I am not sure what you mean? Are we talking about the same proposal? Yes this is not about human beings, so BLP concerns are indeed completely out of scope here. By the way, there is no Bonnie and Clyde problem either. Also, sitelinks for redirects should not conflict with this property. We can list many "problems" like these that are off-topic and therefore not a concern for this proposal. I have given my reasons for oppose above, which one do you want me to elaborate on, if any? − Pintoch (talk) 22:33, 28 June 2019 (UTC)

cache l1, cache l2, cache l3 and cache l4Edit

   Under discussion
DescriptionCPU cache memory
RepresentsCPU cache (Q352090)
Data typeQuantity
Template parameter|Cache L1=, |Cache L2= and |Cache L3= in Ficha de hardware infobox.
Domainprocessors
Example 1Core i7-6700 (Q28739510)
→ "Cache L1" → 256 KB
→ "Cache L2" → 1 MB
→ "Cache L3" → 8 MB
Example 2AMD Ryzen 5 1600 (Q28972980)
→ "Cache L1" → 384 KB
→ "Cache L2" → 3 MB
→ "Cache L3" → 16 MB
Example 3UltraSPARC III (Q2628825)
→ "Cache L1" → 64 KB
→ "Cache L2" → 1 MB
Planned useInmediately, for the given infobox

MotivaciónEdit

Part of my infobox improvements. CPU/SoC Cache L1, L2, L3 and L4 are missing in Wikidata and are relevant for CPU-related articles. --Amitie 10g (talk) 23:36, 12 April 2019 (UTC)

DiscussionEdit

  • I'll discusse at Wikipedia how to use qualifies for Lua-based infoboxes. Meanwhile, I'll leave this request opened. --Amitie 10g (talk) 20:46, 13 April 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics

  • The proposal has been withdrawn, in part, because the three properties should be requested at once. We have memory capacity (P2928), but once I find ways to add qualifiers to infoboxes, I'll request individual properties instead. --Amitie 10g (talk) 12:42, 14 April 2019 (UTC)
  •   Comment You're suggesting three properties here. I wonder if we need three separate discussion pages. John Samuel (talk) 09:24, 14 April 2019 (UTC)
  • This, because them represent the same. See my above answers. --Amitie 10g (talk) 12:42, 14 April 2019 (UTC)
  •   Comment instead of multiplying the properties "(Lx-cache)" , I’d prefer
    subject > has part (P527)   < L1 cache >
    size search < 64 KB >
    . So tend to   Oppose. author  TomT0m / talk page 18:22, 11 July 2019 (UTC)

supported metadataEdit

   Under discussion
Descriptionmetadata that the item can store
Representsmetadata (Q180160)
Data typeItem
Template parametermany parameters of Template:Infobox file system (Q10777901)
Domainfile system (Q174989), file format (Q235557), computer program (Q40056)
Example 1NTFS (Q183205)access control list (Q338966) (qualifier subject has role (P2868)filesystem permissions (Q1172314)), 'read-only file' (qualifier subject has role (P2868)file attribute (Q1144207)), 'archive file' (qualifier subject has role (P2868)file attribute (Q1144207)), 'system file' (qualifier subject has role (P2868)file attribute (Q1144207)), 'hidden file' (qualifier subject has role (P2868)file attribute (Q1144207))
Example 2ID3 (Q1054220)title (Q783521), music interpreter (Q3153559), album (Q482994), year of publication (Q38073102), music genre (Q188451)
Example 3MISSING
Planned useto be used in infoboxes
Expected completenessalways incomplete (Q21873886)

MotivaciónEdit

Organize Wikipedia infoboxes data. --Tinker Bell 05:57, 15 April 2019 (UTC)

DiscussionEdit

  • Can you add some more examples from different domains, or otherwise clarify the intended scope here? ArthurPSmith (talk) 17:21, 15 April 2019 (UTC)
  •   Support David (talk) 06:10, 16 April 2019 (UTC)
  •   Support ArthurPSmith (talk) 18:01, 16 April 2019 (UTC)
  •   Wait From reading the description it's not clear to me what the property does. Is it about metadata stored in the item or metadata stored by the subject that's represented by the item? ChristianKl❫ 13:23, 2 July 2019 (UTC)
    • ChristianKl, it is about metadata stored by the subject that's represented by the item. --Tinker Bell 23:17, 5 July 2019 (UTC)
      • Telling me what the property is about, does nothing to answer my concern besides suggesting that the current description is unfit. The description of it should be clear enough to be understood by people (and be able to be translated). ChristianKl❫ 07:26, 15 July 2019 (UTC)

expansions of videogameEdit

   Under discussion
DescriptionExpansions or DLC for videogames
Representsexpansion pack (Q209163)
Data typeItem
Template parameter|Expansión= or |DLC= in Ficha de videojuego infobox
Domainvideogames
Example 1Mario Kart 8 (Q13427106) "DLC 1"
Example 2Giana Sisters: Twisted Dreams (Q3762768) "Rise of the Owlverlord"
Example 3Sonic Mania Plus (Q50654688) Sonic Mania (Q25991770)
Planned useInmediately, for the given infobox

MotivaciónEdit

Part of my infobox improvements. This property is intended for expansion packs for such software (mostly videogames), as well as DLC  – The preceding unsigned comment was added by Amitie 10g (talk • contribs).

DiscussionEdit

ΛΧΣ21 Vacation9 John F. Lewis (talk) Bene* talk #Reaper (talk) Josve05a (talk) Chris Mason (talk) FunPika Arthena (talk) Wangxuan8331800 (talk) Sjoerd de Bruin (talk) Zerabat (talk) Nicereddy (talk) Syum90 (talk) DrakeCaiman (talk) --George (Talk · Contribs · CentralAuth · Log) Andreasburmeister (talk) Danrok (talk) 18:20, 30 October 2015 (UTC) Macrike (talk) Dispenser (talk) 16:56, 7 July 2017 (UTC) --Zache (talk) 13:34, 12 July 2017 (UTC) Mohammed Adam (T) SharkD  Talk  06:41, 9 November 2017 (UTC) ZebaX2010 (talk) 00:49, 21 November 2017 (UTC) Sight Contamination (talk) Lewis Hulbert (talk) 20:26, 13 December 2017 (UTC) Jean-Fred (talk) 10:48, 28 February 2018 (UTC) Santer (talk) Cloaker416 (talk) 22:18, 12 June 2018 (UTC) Rampagingcarrot (talk) 19:57, 28 June 2018 (UTC) Diggr (talk) 08:07, 3 July 2018 (UTC) Harsh Rathod Poke me! 09:42, 7 July 2018 (UTC) Kirilloparma (talk) 00:30, 5 August 2018 (UTC) Sir Lothar (talk) 10:10, 10 August 2018 (UTC) Cwf97 (talk) 14:33, 22 October 2018 (UTC) Esteban16 (talk) 00:08, 27 October 2018 (UTC) Peterchanws Brasig Le Yota de Mars YotaMoteuchi (talk) 08:09, 22 May 2019 (UTC)   Notified participants of WikiProject Video games

  •   Support David (talk) 06:28, 17 April 2019 (UTC)
  •   Oppose I think the inverse property («expansion of») would be better. --Tinker Bell 07:38, 19 April 2019 (UTC)
  •   Comment Whether this is approved or not, it needs a different name - when I saw it on the proposal list I was very confused what it was about. "video game expansion" perhaps, or for the inverse, "expansion of video game"? ArthurPSmith (talk) 18:17, 19 April 2019 (UTC)
  • @Amitie 10g: would you consider updating the label per Arthur's suggestion? --- Jura 04:03, 23 April 2019 (UTC)
I've updated the label name. --Amitie 10g (talk) 04:08, 23 April 2019 (UTC)
I think the English name should probably be 'expansion for video game' rather than 'of', and make sure 'expansion' is singular. Nicereddy (talk) 20:30, 1 May 2019 (UTC)
Amitie 10g, I see you've updated the name, but I think the property should be like "DLC 1" "expansion of videogame" Mario Kart 8 (Q13427106). Maybe it would be more difficult using it on infoboxes, but data is better organized. --Tinker Bell 03:51, 3 May 2019 (UTC)
  •   Support --Trade (talk) 15:35, 9 May 2019 (UTC)
  •   Support Misc (talk) 23:31, 14 May 2019 (UTC)
  •   Question Is this intended to be limited to video games or not? --Yair rand (talk) 03:13, 21 May 2019 (UTC)
    • As the proporsal says, it is only for videogames software. --Amitie 10g (talk) 21:49, 21 May 2019 (UTC)
  •   Support Cwf97 (talk) 15:07, 22 June 2019 (EST)
  •   Support With the new name change John Samuel (talk) 09:42, 18 July 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics ChristianKl❫ 13:48, 17 July 2019 (UTC)

Alfred P. Sloan Foundation Grant IDEdit

MotivationEdit

The Alfred P. Sloan foundation is a funder that financially supports open source projects with grants. Their grant database has close to 2000 grants at this moment. --Egon Willighagen (talk) 03:45, 20 May 2019 (UTC)

DiscussionEdit

  •   Support David (talk) 06:30, 20 May 2019 (UTC)
  •   Support I hope to do more to connect grants with projects with institutions with people. I am on the Scholia team which received funding for this organization to develop the WikiCite project including an exploration of the extent to which we can model grants here. Blue Rasberry (talk) 14:09, 20 May 2019 (UTC)
  •   Support Dhx1 (talk) 15:11, 20 May 2019 (UTC)
  •   Support Simon Cobb (User:Sic19 ; talk page) 15:35, 21 May 2019 (UTC)
  •   Support. YULdigitalpreservation (talk) 14:18, 23 May 2019 (UTC)
  •   Support.--Vulphere 16:46, 25 May 2019 (UTC)
  • While I support this property, I note that Daniel Mietchen (talkcontribslogs) is currently enquirying about the license of the Sloan data. There is also the further questions of (continuous) project vs. one-time grant, e.g., NumFocus is an organization, while I suppose the suggested identifier is for one-time grants. The ontology around organization/continuous project and one-time grant is still not quite resolved in Wikidata, if I understand correctly. People may want to correct me here. — Finn Årup Nielsen (fnielsen) (talk) 18:45, 27 May 2019 (UTC)
Yep. Will leave a note here when I hear back. --Daniel Mietchen (talk) 00:11, 28 May 2019 (UTC)
I got some initial response but this does not clarify whether creating this Wikidata property is the way to go forward. More discussion to follow — will come back here when there is anything sharable. --Daniel Mietchen (talk) 16:20, 11 June 2019 (UTC)
All, I'm making a few updates, to align the proposal with the DINGO standard, developed in at the Wikibase meeting in Berlin last year, see https://dcodings.github.io/DINGO/ which I should have done in the first place. Please hold off approval of the proposal just yet, thank. --Egon Willighagen (talk) 17:45, 19 June 2019 (UTC)
@Bluerasberry, ديفيد عادل وهبة خليل 2, Dhx1, Sic19, Vulphere, Daniel Mietchen: I have updated the description (Domain + Examples) according to the DINGO specification (it may need further tweaks), and I will like to invite you to reevaluate the proposal. @Vladimir_Alexiev, Considering.Different.Routes: your feedback is also most appreciated! --Egon Willighagen (talk) 15:08, 21 June 2019 (UTC)
It looks ok to me. The link from project to grant is via source of income (P2770) ?? ArthurPSmith (talk) 16:45, 21 June 2019 (UTC)
Yes, per DINGO specification: https://dcodings.github.io/DINGO/#wd.Project One loose end I am not sure about: DINGO specifies has quality (P1552) but I found that this properties doesn't take a value but points to another entity. I have flagged it: https://github.com/dcodings/DINGO/issues/3 --Egon Willighagen (talk) 07:27, 22 June 2019 (UTC)

Shape Expression for classEdit

   Ready Create
DescriptionShape Expression that members of a class should conform to
RepresentsShEx (Q29377880)
Data type⧼datatypes-type-EntitySchema⧽ (not available yet)
Domainclass
Example 1human (Q5)E10
Example 2film festival (Q220505)E11
Example 3film festival edition (Q27787439)E12
Example 4natural number (Q21199)E13

MotivationEdit

Property to link a class to the Shape Expression that members of it should conform to.

This will make it easier to query for Shape Expressions that exist, and quickly see what has been defined for a particular class. Jheald (talk) 16:56, 28 May 2019 (UTC)

Note: Implementation will require EntitySchema to be added to the set of data-types that can be values for Wikidata statements. There is a ticket for this on Phabricator, which Léa hopes should be resolved in the coming weeks.[1]. Jheald (talk) 07:54, 29 May 2019 (UTC)

DiscussionEdit

  • Proposed. Jheald (talk) 16:56, 28 May 2019 (UTC)
  •   Support - PKM (talk) 18:34, 28 May 2019 (UTC)
  •   SupportMisterSynergy (talk) 18:43, 28 May 2019 (UTC)
  •   Support Dhx1 (talk) 18:44, 28 May 2019 (UTC)
  •   Support Finn Årup Nielsen (fnielsen) (talk) 18:52, 28 May 2019 (UTC)
  •   Oppose This proposal needs to say much more about how it is supposed to work. Example 1 shows some of the problems. What does "member" mean here? Are only items that are an instance of (P31) to human (Q5) supposed to be covered, or are instances of subclasses (transistive-reflexive closure of subclass of (P279)) also covered? Then there are problems with the shape expression E11 as a shape for humans. The shape requires that the only instance of link for humans goes to human (Q5). The example shape needs to show at least some interesting conditions, such as requiring that children of humans are humans. Example 4 shows more problems. What items are covered here at all? Presumably natural numbers are not items at all, which means that they don't have any outgoing RDF triples. Even if they did, natural numbers should not be instances of instances of natural number. Peter F. Patel-Schneider (talk) 19:46, 28 May 2019 (UTC)
    • Comments:
      • Interestingness: "The example shape needs to show at least some interesting conditions, such as requiring that children of humans are humans" Yes absolutely, but note that ShEx are only a couple of hours old. I think we will gradually expand it these coming days.
      • Members: I do not think this proposal lays any interpretation on the membership and I suppose it would be up to the consensus (or ontology war) whether it should be transitive.
      • We have lots of natural numbers, e.g., 42 (Q812996) with outgoing triples. I should say they all should have a numeric value (P1181) which could be check with ShEx.
      • Natural number are not "instances of instances of natural number", they are instances of natural numbers.
      • A further remark: There are apparent a lack of possibility to keep track of which ShEx are created, e.g., at one point it looked like two ShEx was created for humans. I think a property to keep track of ShEx would benefit the ShEx, helping them to navigate the created schemas, i.e., if you are looking for the ShEx for human you can go to Q5 and follow the link to the ShEx page. — Finn Årup Nielsen (fnielsen) (talk) 20:03, 28 May 2019 (UTC)
    • The example is new, agreed, but that only makes the need for good examples higher. If there are no good examples of shapes to attach to classes then there is no reason to have this property. Peter F. Patel-Schneider (talk) 23:50, 28 May 2019 (UTC)
    • OK, there are "natural numbers" as items in Wikidata, but the shape says that these are instances of instances of natural number (Q21199), which is not correct. And, yes, there should be a check that their numeric value (P1181) is a natural number (if that is possible in ShEx). Peter F. Patel-Schneider (talk) 23:50, 28 May 2019 (UTC)
    • If the scope of a shape connected to a class is to be determined after the fact by the community then I'm completely opposed to this proposal. The scope needs to be nailed down explicitly before this property is allowed. Peter F. Patel-Schneider (talk) 23:50, 28 May 2019 (UTC)
      • Thanks for the note about "instance of instance of". This is actual not and "instance of instance of" and I think the way that people used this yesterday should be clarified. I would write the line "p:P31 @<instance-of-statement> ;" and similar the below line. In fact, I have changed the name now. I wonder if that clarify this issue? — Finn Årup Nielsen (fnielsen) (talk) 07:07, 29 May 2019 (UTC)
      • I think that there is a clash of philosophies here. Wikidata has been very much ontology-as-you-go with no overall coordination and no enforcing of consistency. We have had property suggestions which guide us to some form of consistency, that may also catch errors and vandalism. ShEx would be a next step. While one could imaging a ShEx-police appearing in Wikidata, that roams about enforcing the one and only scheme upon editors and items, I do not think that is what would be happening. I think that ShExs would be gradually built in an interplay with continuous development and refinement of Wikidata items. For instance, the E34 defines Danish nouns which a ShEx could say should always have a grammatical gender. It appears that proper nouns, plurale tantum and the word druk (L46327) form a problematic set where the grammatical gender might exist and can be set, or it might be unknown or have no value. To resolve this problem one should have an interplay between changes in the Wikidata items and the ShEx. Such problems could be discovered by other means, but I think ShEx would also be a help and steer us into a direction of consistency. — Finn Årup Nielsen (fnielsen) (talk) 09:38, 29 May 2019 (UTC)
  •   Support - NavinoEvans (talk) 09:28, 29 May 2019 (UTC)
  •   Support - Moebeus (talk) 11:20, 29 May 2019 (UTC)
  •   Oppose I'd rather make an item about a shape and link that. --- Jura 09:33, 30 May 2019 (UTC)
    • Which advantages do you see in such an approach, compared to this proposal? —MisterSynergy (talk) 09:35, 30 May 2019 (UTC)
    • One could describe the shapes in a structured way. Currently, we seem to be getting loads of # to do just that. Something we mostly avoided in any other part of Wikidata.--- Jura 09:38, 30 May 2019 (UTC)
      • @Jura1: As I understand it, the shapes themselves are meant to describe themselves in a structured, RDF-compliant, queryable way. Isn't that meant to be part of the point of them? Or perhaps that's SHACL (Q29377821) ?? Jheald (talk) 17:23, 30 May 2019 (UTC)
      • I'm still learning about the syntax .. maybe it's actually possible. Looking at it's current implementation at Wikidata, maybe we can't do it here, at least not with statements as we would usually do it. If we create a datatype for shapes, supposedly we could have several properties in addition to this one .. one could be "shape expression described in this item", "shape expression associated with list". --- Jura 07:02, 31 May 2019 (UTC)
        • @Jura1: Yes. I would hope we wouldn't need "shape expression described in this item", because I hope the shape expression (Exxx) would be its own item, and queryable in its own right. (That would depend on whether a ShEx has an RDF representation that could be included in WDQS -- that would certainly be the case for SHACL; I hope it's true for ShEx). But additional properties like "shape expression associated with list" I would certainly see as likely to be useful. I proposed "Shape Expression for class" first, as it seems likely to be the simplest and most common case, and worth a property in its own right. But there will be shape expressions for things identified other than as members of classes, and we will in turn want ways to point to them. Jheald (talk) 08:55, 31 May 2019 (UTC)
          • Two posters on Wikidata-l confirm that there is a standard RDF serialisation of ShEx [2]. So it should be straightforward to load this either into WDQS to describe a shape entity; or into an associated triplestore, that could service federated queries from WDQS. Jheald (talk) 16:46, 2 June 2019 (UTC)
          A phabricator ticket is open for this, phab:T225701 Jheald (talk) 09:59, 14 June 2019 (UTC)
        • Re "shape expression described in this item": Possibly, but I don't see a plan for that now and there might not be much added value in developing more GUI as it could already be done with Q-entities. --- Jura 10:21, 31 May 2019 (UTC)


apertureEdit

   Ready Create
DescriptionIn optics, an aperture is a hole or an opening through which light travels. More specifically, the aperture and focal length of an optical system determine the cone angle of a bundle of rays that come to a focus in the image plane. See also en:aperture for more details for background. As aperture is an important indicator for a lens. As there are lot of data bout lenses, it would be useful to add the value.
Representsaperture (Q6434802)
Data typeProperty
Template parameteren:template:Infobox photographic lens aperture
Allowed valuesA range with min and max value or a fixed value as both is possible.
Allowed unitsAperture is a numeric value without units.
Example 1Canon EF 800mm lens Q5033222; en:Canon EF 800mm lens
Example 2Samyang 500mm f/8 Q25038830; en:Samyang 500mm f/8
Example 3Canon EF 1200mm lens Q5033201; en:Canon EF 1200mm lens
Example 4Canon EF 70–200mm lens Q1358428; en:Canon EF 70–200mm lens
Sourceen:Aperture
Planned useI like to add the aperture to the lenses, which has wiki data item.
Number of IDs in sourceFor Canon we have currently lens items, where it would make sense to add this aperture.

MotivationEdit

I like to add this value to the photo lenses, which have an item in Wikidata. GodeNehler (talk) 17:06, 6 June 2019 (UTC)

DiscussionEdit

  •   Support --Tinker Bell 20:42, 8 June 2019 (UTC)
  •   Support NMaia (talk) 10:18, 10 June 2019 (UTC)
  •   Comment Make sure to distinguish this from Property:P6790 (f-number) or list it as a related property. Infomuse (talk) 03:32, 14 June 2019 (UTC)
  •   Comment @Infomuse Thank you for the hint. As I am not a nativ speaker for english, and checking this issue again, I got the impression that 'f-number' might be the better Property, as 'aperture' seams to be the mechanic, but 'f-number' is the value, which I like to add. But in the Lens articles, like mentioned above, and in the template is the term 'aperture'. So I am not sure what is correct. The second issue: I have just add the 'f-number' to the Samyang 500mm f/8. There I got the warning 'Entities using the f-number property should be instances of photograph (or of a subclass of it), but Samyang 500mm f/8currently isn't.' From that I got the Impression that the 'f-number' is the real value, with which a picture is taken. So not absolutely clear for me. --GodeNehler (talk) 07:51, 15 June 2019 (UTC)
  •   Comment After thinking about the issue, I got to the conclusion, that aperture is the correct term as aperture means the mechanical construct, which is correct for a lens. --GodeNehler (talk) 19:21, 20 June 2019 (UTC)
  •   Comment A range is not sufficient because there are 2 different kinds of aperture ranges. First, some zoom lenses have different maximum apertures depending on the selected focal length (for example, w:en:Sony FE 28-70mm F3.5-5.6 OSS). Second, at a given focal length, a lens has a minimum and maximum possible aperture that the photographer can select. So we really need 4 numbers to characterize lens aperture ranges as commonly specified (min/max aperture when zoomed wide/tele). 2620:0:1000:3216:5413:4AF0:7532:8655 22:30, 21 June 2019 (UTC)
  •   Comment The IP is right. This can be fixed with the possibility to add up to 4 values. Maybe there is a need to add infos like 'minimum aperture', 'maximum aperture' for prime lens, 'minimum aperture at maximum focal length', 'maximum aperture at maximum focal length', 'minimum aperture at minimum focal length', 'maximum aperture at minimum focal length' for zoom lenses and 'fixed aperture' e.g. for mirror lenses. --GodeNehler (talk) 16:38, 28 June 2019 (UTC)

number of pins, number of pin positionsEdit

   Under discussion
Description2 related properties:
  • number of pins: number of contacts that an electrical connector has (excluding any grounding shroud not used for communication)
  • number of pin positions: number of positions in an electrical connector, including empty or keyed positions
Representselectrical contact (Q394001)
Data typeQuantity
Template parameter"num_pins" in en:template:Infobox connector
Domainitem: Subclasses of electrical connector (Q2119531). optical fiber connector (Q2296938) could be added later, pending discussion of how to handle optical module (Q48740842)s (which have electrical contacts on one end and optical connections on the other).
Allowed valuespositive integers
Allowed unitsnone
Example 1USB-C connector (Q58051489)
→ "number of pins" → 24
→ "number of pin positions" → 24
Example 2NEMA 5-15 (Q24288456)
→ "number of pins" → 3
→ "number of pin positions" → 3
Example 36P2C modular connector (Q64831598)
→ "number of pins" → 2
→ "number of pin positions" → 6
Example 4Intel HD Audio connector (Q64764371)
→ "number of pins" → 9
→ "number of pin positions" → 10
citation: https://www.intel.com/content/www/us/en/support/articles/000005512/boards-and-kits/desktop-boards.html
Example 5Socket F (Q1475023)
→ "number of pins" → 1207
→ "number of pin positions" → 1225
Planned useAnnotating items for electrical connectors. They could also be generalized to optical fiber connectors, since it's fundamentally the same concept.
Expected completenesseventually complete (Q21873974)
Robot and gadget jobsWhen only "number of pins" is specified, "number of pin positions" can be populated with the same value.
See alsoeach should link to the other one
Type constraint - subclass ofQ2119531

MotivationEdit

For annotating items for electrical connectors (see connector (P2935)).

Why are 2 properties needed? Some connectors have additional positions which are not filled. For example, the RJ11 w:en:Modular connector has 6 physical positions, but only 2 of them are populated. Similarly, the Parallel ATA (Q230360) data connector has 40 positions but only 39 pins, since one position is keyed. The unfilled positions should be counted when the connector's conventional numbering includes them.

Aliases: replace "pin" with "contact" or "conductor"; same without the initial "number of" 2620:0:1000:3216:5413:4AF0:7532:8655 23:59, 21 June 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics 169.234.25.175 20:28, 5 July 2019 (UTC)

DiscussionEdit

  • In principle, we could do it by combining qualifiers with an entity for a pin; there are just some practical issues:
  • It's not totally obvious for an editor which combination to use, and I don't see a way to hint recommended values. For example, quantity (P1114) with applies to part (P518) looks just as plausible (even if you're not supposed to use it that way). Also, people might use other elements besides the intended "pins" and "pin positions", e.g. pogo pin (Q1400617), wire (Q551997), or lead (Q947546). This will make querying more difficult.
  • It's easier to express a constraint that the "pins" and "pin positions" should be specified together when they are expressed as a property.
  • We might want to generalize this to support w:en:optical connectors; we would then have to add some items for pretty abstract concepts that encompass "electrical contact", "termination of a single optical fiber" (is there even a term for that?), and positions thereof. These would be hard to find.
In any case, there are lots of existing "number of X" properties, where X is a domain-specific part that an item contains. 2620:0:1000:3216:5413:4AF0:7532:8655 20:39, 25 June 2019 (UTC)
  •   Support Seems like a fine idea. —Scs (talk) 11:18, 30 June 2019 (UTC)
  •   Oppose For the given examples, RJ11 is only valid for countries that only host 2 wires. You can find RJ11 with 4 wires in 6 positions. RJ45 can also be used to replace RJ11, so RJ11 and RJ45 will have several possibilities. In addition, you write "electrical connector" which is quite broad: you give an example of an IC, which enters the electronic domain. With an electronics training, you can find a multitude of cases (so number of pins variable) for a single component (therefore for a single manufacturer and a single function and sometimes with a single denomination). The differences are according to the use of the component: assembly, power, disposition, etc. For the multilingual side of WD and the complexity of the domain (electricity), I fear that this future property brings errors. Of course, in obvious cases, this property will work, but contributors will not stop there. —Eihel (talk) 17:15, 11 July 2019 (UTC)
  • Thanks for the feedback!
  • Regarding RJ11, the Wikipedia article explicitly says RJ11 requires a 2-wire connector (without citation); if you have better information please update that. I switched the example to 6P2C modular connector (Q64831598) for precision, which I forgot to do earlier.
  • I'm not sure what IC you're referring to, but assume you're talking about the CPU socket. I'm aware that a given IC can be packaged in multiple ways, but as far as I've seen, a given CPU socket necessarily has a well-defined number and arrangement of pins, so I don't see the issue.
  • Regarding the risk of misuse, would a property type constraint (should be used on connectors only and not ICs or other components) address this? I'll update the proposal.
73.202.12.249 23:22, 17 July 2019 (UTC)

2018 subscribersEdit

   Under discussion
Description(qualifier only) number of subscribers in 2018
Data typeQuantity
Domainqualifier for subreddit (P3984), etc.
Allowed values>1
Allowed unitsnone
Example 1Spain (Q29) subreddit (P3984): es → 10,677
Example 2Spain (Q29) subreddit (P3984): spain → 15,414
Example 3Internet Relay Chat (Q73) subreddit (P3984): irc → 6,206
Example 4Ariana Grande (Q151892) Instagram username (P2003): arianagrande → 147,023,953
Example 5Katy Perry (Q42493) Twitter username (P2002): katyperry → 107,659,952
Number of IDs in sourceNumber of ids with number of subscribers (P3744)-qualifier: Twitter 80000, Subreddit 2500
Robot and gadget jobschange 2018 data to the above
See alsonumber of subscribers (P3744)

MotivationEdit

We probably agree that the numbers are useful, but the current qualifier number of subscribers (P3744) doesn't work that well. We haven't really come up with a good solution for this yet. Maybe the following could work: we could store previous years in separate qualifiers. Above a proposal for 2018. If we have earlier data, we should create qualifiers for the relevant years as well. Recent project chat discussion here, another approach was discussed at Number of twitter follower. (Add your motivation for this property here.) --- Jura 06:32, 23 June 2019 (UTC)

Alternatives:

  • (B) overwrite number with new data
  • (C) add several statements for the same account, each with a different point in time qualifier (or retrieved date in reference): sample
  • (D) create an item for each account and add the number of subscribers there
    • (D0) for any number of subscribers
    • (D1) if the number of subscribers exceeds a threshold (e.g. 10,000,000 subscribers). Sample: Q42493#P2002 and Q65665844
  • (E) create a property "number of <service> users" and use point in time qualifier to differentiate them ( proposal)
  • (F) add multiple number of subscribers (P3744) qualifiers to the same statement. This would make it impossible to link them to a date.
  • (G) develop qualifiers on qualifiers. This is currently not planned and IMHO unlikely to happen.

--- Jura 15:22, 5 July 2019 (UTC)

DiscussionEdit

Sounds like the usual qualifiers of qualifiers problem. Generally we resolve this by creating an item - do we have/want items for youtube channels, twitter feeds, etc? ArthurPSmith (talk) 14:53, 24 June 2019 (UTC)
I think we don't, at least not for each that currently uses P3744 --- Jura 09:35, 25 June 2019 (UTC)
My first impulse would be that we don't want to store the data for the subscribers of the reddit about spain for every year. There's already a lot of data in the items of countries, more data increaes page loading time and few of the people who are looking at the item for the country care about the reddit followers. ChristianKl❫ 09:28, 25 June 2019 (UTC)
There are >2000 reddits with that data. I suppose we could skip the country ones. Btw, this isn't meant to be limited to reddit --- Jura 09:35, 25 June 2019 (UTC)
  Question The number of subscribers can change over a year. Will this property store the number at 01.01.2018 00:00:00 or at 31.12.2018 23:59:59 or at an arbitrary other point in the year? --Pasleim (talk) 11:30, 25 June 2019 (UTC)
The last, maybe even all three, but most reddit numbers are from May. I don't expect the numbers for previous years to change. --- Jura 11:48, 25 June 2019 (UTC)
  Oppose why not just use point in time (P585)? --DannyS712 (talk) 16:22, 28 June 2019 (UTC)
  •   Question @DannyS712: I'm not sure if I understand. Can you do a sample in a sandbox, e.g. with current and 2018 number of subscribers? --- Jura 16:25, 28 June 2019 (UTC)
@Jura1: if point in time (P585) were allowed to be used as a qualifier, then Special:Permalink/970594325 wouldn't show errors, and would work --DannyS712 (talk) 16:29, 28 June 2019 (UTC)
  • Even. I don't think it's a good idea to add P3984 (value "spain") several times. (BTW, this generates also a "distinct value" constraint violation). --- Jura 16:34, 28 June 2019 (UTC)
@Jura1: That violation was only because the value "spain" is used elsewhere - Special:Permalink/970611124 generates no such error --DannyS712 (talk) 17:12, 28 June 2019 (UTC)
Good point. I corrected my comment. The option was mentioned here, but not implemented. --- Jura 21:32, 28 June 2019 (UTC)
  Comment What is range of it? You can have different number of subscribers every year, month, day, hour and probably even minute. Eurohunter (talk) 21:34, 29 June 2019 (UTC)
  • The 2018 qualifier would be for data from January 1 to December 31, but as mentioned, I don't expect more than we already have, e.g. those from May for subreddit. --- Jura 17:21, 30 June 2019 (UTC)
  • In any case, that would prevent 2018 data from being overwritten by 2019 data [3]. --- Jura 17:05, 4 July 2019 (UTC)
  •   Comment Imho "number of subscribers" should only be used when it is accompanied by "point in time", otherwise it does not make much sense. But as soon point in time is used the number is valid. --Gereon K. (talk) 20:22, 4 July 2019 (UTC)
    • @Gereon K.: The earlier statement had the date in "retrieved [on]" [4]. Would you just overwrite all these numbers continuously? I find it a bit odd to use the qualifier "point in time" on statements where the main value is rarely subject to change. --- Jura 22:07, 4 July 2019 (UTC)
      • @Jura1: Yet the number of subscribers changes daily, so it is valid only at a certain point of time. This would be exactly the same date as "retrieved on", but "retrieved on" is meant for the source. And the source regarding the used name and the number of subscribers in this case is Twitter itself. --Gereon K. (talk) 06:12, 5 July 2019 (UTC)
        • @Gereon K.: According to your last sentence it is archived version for example in Wayback Machine, version you can access not directly Twitter. Eurohunter (talk) 15:00, 5 July 2019 (UTC)
        • I'm aware of that. As neither is optimal, I wrote this proposal. Also, above, I listed various other options that came up. --- Jura 15:17, 5 July 2019 (UTC)
  •   Comment Well, I'm already wondering why P3744 does not already have mandatory qualifier constraint (Q21510856). Since the property changes over time, a date must be mandatory (just as the fact that there is no "number of subscriber march 2018"). My choice: (F), but improved. —Eihel (talk) 19:44, 11 July 2019 (UTC)
    • @Eihel: mandatory qualifier constraint (Q21510856) wouldn't have any effect in the above use case, as here P3744 is used as a qualifier. To be sure what you have in mind, would you do a sample for "(F), but improved" in Q4115189, preferably using data that already exists on Wikidata? It seems to me that (F) is the least desirable solution. --- Jura 09:47, 13 July 2019 (UTC)
  •   Comment added another option: D1. --- Jura 12:45, 13 July 2019 (UTC)
  •   Comment I made a bot request for D1 at Wikidata:Bot_requests#Monthly number of subscribers. --- Jura 14:24, 19 July 2019 (UTC)

default description for instancesEdit

   Under discussion
Descriptiondescription that should be displayed/add by default to instances of this class (that it, to items which have a statement
< class > instance of (P31)   < {{{2}}} >
if the item « class » has a statement with this property. To include property value, use $ and the property, e.g. to include $P571 for placement of the value of P571.
Data typeItem
Domainitems with many instances, e.g. from Wikidata:Database reports/Popular items
Allowed valuesitems with suitable descriptions as labels, including $Pnn for property values
Example 1Wikimedia disambiguation page (Q4167410)Wikimedia disambiguation page (Q64875536) (applies to max. 1,326,946 of 57,662,380 items, 2.3%)
Example 2film (Q11424) → new item with "film"@en as label
Example 3film (Q11424)$P571 film by $P57 (Q64875670)
Example 4Wikimedia category (Q4167836) → new item with "Wikimedia category"@en, etc as label (applies to max. 4,309,102 of 57,662,380 items, 7.5%)
Example 5scholarly article (Q13442814) → new item with "article published $P571"@en, etc as label (applies to max. 21,731,437 of 57,662,380 items, 37.7%)
Example 6Wikimedia template (Q11266439) → .. (applies to max. 889,411 of 57,662,380 items, 1.5%)
Example 7human settlement (Q486972)human settlement in $P131, $P17 (Q64896833) (applies to max. 460,153 of 57,662,380 items, 0.8%) )
Planned use
  • store what bots currently use
  • (continue to) use by bots
  • phase 2: make available for a Wikibase function to display by default
Number of IDs in sourcemaybe 10-20 items that apply to > 30,000,000 items (50% Wikidata's items)

MotivationEdit

Initially bots could add the provided description (as they already do now). Eventually it's preferable that Wikibase displays/adds that by default, similar to what is being done for lexemes (based on language/lexical category).

The numbers above are just a rough estimate. If you have better ones, please add them.

Please add more samples above. (Add your motivation for this property here.) --- Jura 16:24, 29 June 2019 (UTC)

@Милан Јелисавчић, ValterVB, Emijrp, Edoderoo, Mr. Ibrahem: @Daniel Mietchen, Ivan A. Krestinin, Liridon, Renamerr: who operate bots working on some of the above. @Multichill: who started a discussion on project chat. @Lydia_Pintscher (WMDE): re possible phase 2, --- Jura 16:51, 29 June 2019 (UTC) @TomT0m: who brought it up (at least afaik) . --- Jura 17:02, 29 June 2019 (UTC)

DiscussionEdit

oh yeah that’s an old one I forgot. As far as I remember my proposal was a bit different and to use a wikitemplate as a pattern to do that, as there is already stuff to deal with linguistic issues like grammatical agreements in Mediawiki. Something possible would be to use an Special:ExpandTemplates API call to get the description. But it’s more complicated to create a template. author  TomT0m / talk page 18:06, 29 June 2019 (UTC)

  •   Oppose for several reasons:
  1. Description does not require examples of data type "item"
  2. There are already properties that explain the items:See here
  3. The labels of the proposed items in the examples match the labels of the original items David (talk) 06:47, 30 June 2019 (UTC)
    • (1) it shouldn't be a general requirement. It just applies to a series of frequent types. Compare, e.g. with lexeme entities where the description is entirely generated by structured data. (3) indeed, that's true for some. --- Jura 10:14, 30 June 2019 (UTC)
  • I'm a bit confused. We want to introduce a property for the description, while there is already a description for that. What problem do we try to solve here? People that create items already do not take the effort to add a description, why would we expect (hope?) that they would add a property with the description instead? Edoderoo (talk) 08:54, 30 June 2019 (UTC)
    • @Edoderoo: It’s just the opposite ! The proposal is not to put, in the example, this property on any movie item, it’s to put the property on the film (Q11424)     item. Then the statement can be used on any item with a
      < film (Q11424)     > instance of (P31)   < {{{2}}} >
      statement (or a subclass of it potentially) to autogenerate a description by data consumer if there is no description in the language for the item. It could be used for example by the autodesc project or templates like {{Autodescription}}. author  TomT0m / talk page 09:54, 30 June 2019 (UTC)
      • Right, basically that is what my bot does, on some cases with a bit more intelligence. We could integrate that in the wiki-software. But that also means that this is not a proposal for a property, but a proposal to change how the information in existing properties is (re)used. Edoderoo (talk) 11:15, 30 June 2019 (UTC)
        • @Edoderoo: Mmm no, that means that your bot or Magnus’ tool and other tools could reuse informations from this property in cases he does not know how to handle some item, if we choose the path of filling by bot. It does not imply anything on how information is reused by clients if they just choose to ignore it. If we choose to integrate automated descriptions on Mediawiki this property could as well be useful, for example if there is a Mediawiki configuration option (or special page, in the spirit of MediaWiki:Wikibase-SortedProperties which can trigger some special behavior by Mediawiki) that associates, say, an item with a shape expression (maybe the future property Wikidata:Property proposal/Shape Expression for class if it’s created) with a pattern. For example there could be a special page with content « Pdefault description for instances ; PShape Expression for class » and mediawiki would autocompute the descriptions for items that validates « PShape Expression for class ». To get something more robust and smarter as your bot can do, this could be instead of a raw string with « $ » symbols, a mediawiki template page that is specified to render the description however, as noted in my first comment. author  TomT0m / talk page 12:19, 30 June 2019 (UTC)
  •   Comment Thanks for your feedback. I expanded the samples a bit, maybe it's more clear now. @ديفيد عادل وهبة خليل 2, Edoderoo: --- Jura 10:14, 30 June 2019 (UTC)
    • I still do not convinced of your responses and do not see any benefit from the proposed property David (talk) 10:28, 30 June 2019 (UTC)
      • Well, the main benefit would be in phase 2. --- Jura 10:41, 30 June 2019 (UTC)
      • @ديفيد عادل وهبة خليل 2: The point is that there is already in use tools that generates autodescriptions, see the autodesc project (@Magnus Manske: who can probably say stuffs about this), that store the way the description is generated off wiki. Doing this storage « on wiki » would probably make them more useful as it would make the contribution way more accessible to non programmers. author  TomT0m / talk page 10:44, 30 June 2019 (UTC)
  • I'd like to see some input from people who have done auto-descriptions (like Magnus Manske). Is it really necessary to have a separate template for each class and language, or can something more general be done somehow? ArthurPSmith (talk) 15:08, 1 July 2019 (UTC)
    • I think there should be at least one template per class and possibly additional ones if the description is to include the label of another property (e.g. see the film sample above). @Magnus Manske: --- Jura 15:31, 1 July 2019 (UTC)
      • I think Magnus (without looking at the code) has additional « default » rule in the abscence of a template. That can be seen as a « default » template for any item : if the item has an instance of (P31) or subclass of (P279) statement, he just puts the label of the value of the statements as a default description, separated by commas or conjunctions like « and ». This could be implemented if we could express rules such as« if the item matches some shape expression [in this case there is a P31 or P279 statement] then generate [that kind of description].
        Maybe Magnus has also rules such as « if there is a author (P50)   statement, add « by [the statement value] » to the description previously created. author  TomT0m / talk page 15:46, 1 July 2019 (UTC)
  • I don't think this is necessary, since bots already sort of do this without the property. I also find that a lot of Wikipedians consider Wikidata descriptions generic and sterile, so forcing this to be connected solely to P31 might be detrimental even compared to the current situation. Jc86035 (talk) 16:39, 8 July 2019 (UTC)
  • A good default description uses what information is available. "article published $P571" would fail when there's no P571. We would need logic that says that in those cases the word "published" gets also ommitted. I currently think that ideally we would have a template system where templates can use complex lua logic. ChristianKl❫ 13:57, 17 July 2019 (UTC)
    • I think the item could specify which properties are required. I don't think coding the entire logic into every bot and every template is helpful. --- Jura 15:10, 19 July 2019 (UTC)

terms of serviceEdit

Descriptionterms of service of the subject
Representsterms of service (Q7214489)
Data typeURL
Domaincompany, website, software, etc.
Example 1GitHub (Q364)https://help.github.com/en/articles/github-terms-of-service
Example 2Google (Q95)https://policies.google.com/terms
Example 3Microsoft (Q2283)https://www.microsoft.com/zh-cn/legal/intellectualproperty/copyright/default.aspx
Expected completenessalways incomplete

MotivationEdit

(Add your motivation for this property here.) GZWDer (talk) 12:02, 4 July 2019 (UTC)

DiscussionEdit

privacy policyEdit

   Under discussion
Descriptionprivacy policy of subject
Representsprivacy policy (Q1999831)
Data typeURL
Domaincompany, website, software, etc.
Example 1GitHub (Q364)https://help.github.com/en/articles/github-privacy-statement
Example 2Google (Q95)https://policies.google.com/privacy
Example 3Microsoft (Q2283)https://privacy.microsoft.com/zh-cn/privacystatement
Expected completenessalways incomplete

MotivationEdit

Note there's some items (e.g. Uber privacy policy (Q59914866)) about individual privacy policies. We may either:

  • Create two properties, one URL and one item
  • Create only the URL property, link the item using statement is subject of (P805)
  • Create only item property, create items for all individual privacy policies linked

GZWDer (talk) 12:08, 4 July 2019 (UTC)

DiscussionEdit

specific absorption rateEdit

   Ready Create
Descriptionmeasure of the maximum energy absorbed by a unit of mass of exposed tissue of a person using a mobile phone, over a given time or more simply the power absorbed per unit mass.
Representsspecific absorption rate (Q914138)
Data typeQuantity
Template parameter"sar" in Template:Infobox mobile phone (Q5849853)
Domainelectronic device model (Q62008942)
Allowed unitsWatt per kilogram
Example 1Huawei Ascend Mate7 (Q18643709) → 1.54 W/kg [5]
Example 2Fairphone 2 (Q21000819) → 0.65 applies to part (P518) head (Q23640); → 1.1 applies to part (P518) body (Q170494); [6]
Example 3OnePlus 7 Pro (Q64262423) → 1.6 W/kg
Expected completenessalways incomplete (Q21873886)

MotivationEdit

The Specific Absorption Rate (SAR) is the rate at which the body absorbs electromagnetic waves when using electrical devices. This is a commonly used indicator for phones. There is a debate about which levels are deemed harmful for humans, but generally, with the increasing use of phones in all age groups, it's certainly something to pay attention to. There's certainly a question about the question of the source for the values, whether they come from the manufacturer or another agency. Sometimes there's just one value, or multiple for head and body (in this applies to part might help) For example: Samsung Galaxy Note 9: Head: 0.27 W/kg, Body: 0.76 W/kg, ST: 1.59 W/kg [7] Germartin1 (talk) 15:11, 4 July 2019 (UTC)

DiscussionEdit

unabbreviated textEdit

Description(qualifier) text in inscription with the abbreviations expanded in a fairly reliable way
Data typeMonolingual text
Example 1Arch of Constantine (Q5786) inscription (P1684) IMP · CAES · FL · CONSTANTINO · MAXIMOP · F · AUGUSTO · S · P · Q · RQUOD INSTINCTU DIVINITATIS MENTISMAGNITUDINE CUM EXERCITU SUOTAM DE TYRANNO QUAM DE OMNI EIUSFACTIONE UNO TEMPORE IUSTISREM PUBLICAM ULTUS EST ARMISARCUM TRIUMPHIS INSIGNEM DICAVIT
IMPeratori · CAESari · FLavio · CONSTANTINO · MAXIMO · Pio · Felici · AVGUSTO · Senatus · Populus · Que · Romanus · QVOD · INSTINCTV · DIVINITATIS · MENTIS · MAGNITVDINE · CVM · EXERCITV · SVO · TAM · DE · TYRANNO · QVAM · DE · OMNI · EIVS · FACTIONE · VNO · TEMPORE · IVSTIS · REMPVBLICAM · VLTVS · EST · ARMIS · ARCVM · TRIVMPHIS · INSIGNEM · DICAVIT
Example 2Family Vault of General Sir George Cockburn (Q65037297) inscription (P1684) Family Vault of Genl Sir George Cockburn
Family Vault of General Sir George Cockburn
Planned useuse where applicable
See alsoliteral translation (P2441)

MotivationEdit

The copy of the inscription should be literal. To be able to understand or search it, I think an unabbreviated version can be helpful. (Add your motivation for this property here.) --- Jura 09:22, 6 July 2019 (UTC)

DiscussionEdit

  •   Support David (talk) 06:33, 7 July 2019 (UTC)
  •   Support --Trade (talk) 21:52, 7 July 2019 (UTC)
  • Is needed I think. Proposal could be worked out more though. Has to be considered how to resolve abbreviations etc. Any epigraphers here? --Marsupium (talk) 13:16, 10 July 2019 (UTC)
    • As for any claim, if the unabbreviated version is questionable, a reference should be provided. --- Jura 17:45, 12 July 2019 (UTC)
  •   Comment The abbreviations (at least in these examples) seem to be related to a particular person - wouldn't it make more sense to add the abbreviation as an alternate label on that person? ArthurPSmith (talk) 20:55, 16 July 2019 (UTC)
    • I think that would be a different usecase. Some are about persons, others not. Also, even for persons, I don't think we have items for all of them. They might be good candidates for aliases though. --- Jura 19:13, 17 July 2019 (UTC)

Q-Codes IDEdit

   Under discussion
DescriptionQ-Codes ID is for indexing Family medicine related docs; with the ICPC 2, both form the Core Content Classification in General Practice/ Family Medicine (3CGP)
RepresentsQ-Codes ID (Q65072018)
Data typeExternal identifier
Template parameterOui pour Modèle:QCodes , Modèle:Infobox Maladie
DomainQ11190
Allowed valuesQ CDEHPRST 100-800
Allowed unitsQ CDEHPRST 100-800
Example 1Q-Codes QD441 → surmédicalisation Overmedicalization
Example 2Q-Codes QE42 → consentement éclairé : Informed consent
Example 3Q-Codes QD323 → Décision partagée ; Shared decision making
Example 4Q-Codes QD441 → échange en ligne de la connaissance Online knowledge sharing
Sourcehttps://www.hetop.eu/hetop/Q?la=fr&rr=CGP_CO_Q&tab=1

http://3cgp.docpatient.net/

http://www.ph3c.org/4daction/w3_CatVisu/fr/Articles.html?wCatIDAdmin=8
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useQcodes module for template:Infobox Maladie
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.hetop.eu/hetop/Q/fr/?q=$1

MotivationEdit

Complèter la création de référencement de la CISP2 dans les infobox Maladie par les Q-codes; par exemple avec l'évolution de la conceptualisation de surmédicalisation Médecine et environnement, et décions partagée.. Yves.bertin (talk) 15:00, 6 July 2019 (UTC)

DiscussionEdit

  • @Yves.bertin: can you please add examples? --DannyS712 (talk) 00:39, 18 July 2019 (UTC)
  • Yes thanks they didn' show up; on a beginning sister project of shared medical practise sharing in France wiKonsult.org i made a Qcodes Template to display Q-codes ID in Medical Infobox; It manually links to hetop.eu and might be automated; With the Q-codes property we can use that in medical condition infoboxes in english french..https://wikonsult.org/index.php/Décision_partagée is an example stub Yves.bertin (talk) 08:45, 18 July 2019 (UTC)

WikiApiary wikiEdit

   Ready Create
Descriptionentry of a MediaWiki site in WikiApiary
RepresentsWikiApiary (Q26252471)
Data typeExternal identifier
DomainMediaWiki website (Q15633582)
Allowed values.*
Example 1English Wikisource (Q15156406)Wikisource (en)
Example 2Spanish Wikipedia (Q8449)Wikipedia (es)
Example 3English Wikipedia (Q328)Wikipedia (en)
Sourcehttps://wikiapiary.com/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useevery MediaWiki sites
Number of IDs in sourceas of now, 269654 sites
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://wikiapiary.com/wiki/$1
Robot and gadget jobsmaybe
See alsoWikidata:Property proposal/Wikiapiary entry

WikiApiary extensionEdit

   Ready Create
Descriptionentry of a MediaWiki extension in WikiApiary
RepresentsWikiApiary (Q26252471)
Data typeExternal identifier
DomainMediaWiki extension (Q6805426)
Allowed values.*
Example 1Semantic MediaWiki (Q20728)Semantic MediaWiki
Example 2Extension:VisualEditor (Q21679100)VisualEditor
Example 3Wikipedia:Lua (Q6811431)Scribunto
Sourcehttps://wikiapiary.com/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useevery MediaWiki extensions
Number of IDs in sourceas of now, 269827 extensions
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://wikiapiary.com/wiki/Extension:$1
Robot and gadget jobsmaybe
See alsoWikidata:Property proposal/Wikiapiary entry

WikiApiary skinEdit

   Ready Create
Descriptionentry of a MediaWiki skin in WikiApiary
RepresentsWikiApiary (Q26252471)
Data typeExternal identifier
DomainMediaWiki skin (Q21996535)
Allowed values.*
Example 1Vector (Q22713102)Vector
Example 2MonoBook (Q22713043)MonoBook
Example 3Minerva Neue (Q22713032)Minerva Neue
Sourcehttps://wikiapiary.com/
External linksUse in sister projects: [de][en][es][fr][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useevery MediaWiki skins
Number of IDs in sourceas of now, 65535 skins
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://wikiapiary.com/wiki/Skin:$1
Robot and gadget jobsmaybe
See alsoWikidata:Property proposal/Wikiapiary entry

MotivaciónEdit

WikiApiary collects a lot of data, under a free license. --Tinker Bell 22:06, 6 July 2019 (UTC)

DiscussionEdit

typing disciplineEdit

MotivationEdit

This property is important for the classification of programming languages and to be compatible with the mentioned infobox. The Wikipedia article en:Type system has a box with a list of items that can be used within this property. It could be simplified to "typing" if the property could be useful in other areas. Premeditated (talk) 21:36, 8 July 2019 (UTC)

DiscussionEdit

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics

  •   Support David (talk) 07:01, 9 July 2019 (UTC)
  •   Strong support --Tinker Bell 22:14, 9 July 2019 (UTC)
  •   Support StudiesWorld (talk) 17:19, 15 July 2019 (UTC)
  •   Support MartinPoulter (talk) 14:36, 16 July 2019 (UTC)
  •   Support but why "typing discipline" and not "type system" which is the English label for Q865760? ArthurPSmith (talk) 20:45, 16 July 2019 (UTC)
  • @ArthurPSmith: Given that you added a new open question, why do you consider the property to be ready? Wouldn't it make more sense to wait till the concern is answered before marking it ready? ChristianKl❫ 08:09, 17 July 2019 (UTC)
    • @ChristianKl: The label in Spanish seems fine. I don't think properties need to wait to settle the exact label in one specific language. ArthurPSmith (talk) 13:35, 17 July 2019 (UTC)
      • @ArthurPSmith: Given that the English name gets used as basis for most translations I feels to me like having a consensus for a good English name is central before creating a property. ChristianKl❫ 14:00, 17 July 2019 (UTC)
    @Premeditated: Can you explain the choice of label here? ArthurPSmith (talk) 18:56, 17 July 2019 (UTC)
@ArthurPSmith, ChristianKl: The choice of label is the same as used in Infobox programming language. Typing discipline is kind of a nicer way to say typing system. I don't have any strong opinions on the name, other than it should be easy to understand for fellow contributors. - Premeditated (talk) 21:09, 17 July 2019 (UTC)
Makes sense - I hadn't looked at the infobox directly. Thanks. ArthurPSmith (talk) 14:29, 18 July 2019 (UTC)

video game mod ofEdit

   Ready Create
Descriptionmod for videogames
Representsvideo game (Q7889)
Data typeItem
Domainvideo game mod (Q865493)
Example 1KFMod (Q59398000) "Unreal Tournament 2004"
Example 2Grezzo 2 (Q55381964) "Doom"
Example 3True Patch (Q63035708) Vampire: The Masquerade – Bloodlines (unofficial patch)

MotivaciónEdit

Instead of always having to use based on (P144) i think it will make sense to give video game mods their own dedicated property. It's supposed to be like Wikidata:Property proposal/expansion but with video game mods instead of expansion packs or DLC. --Trade (talk) 23:12, 8 July 2019 (UTC)

DiscussionEdit

ΛΧΣ21 Vacation9 John F. Lewis (talk) Bene* talk #Reaper (talk) Josve05a (talk) Chris Mason (talk) FunPika Arthena (talk) Wangxuan8331800 (talk) Sjoerd de Bruin (talk) Zerabat (talk) Nicereddy (talk) Syum90 (talk) DrakeCaiman (talk) --George (Talk · Contribs · CentralAuth · Log) Andreasburmeister (talk) Danrok (talk) 18:20, 30 October 2015 (UTC) Macrike (talk) Dispenser (talk) 16:56, 7 July 2017 (UTC) --Zache (talk) 13:34, 12 July 2017 (UTC) Mohammed Adam (T) SharkD  Talk  06:41, 9 November 2017 (UTC) ZebaX2010 (talk) 00:49, 21 November 2017 (UTC) Sight Contamination (talk) Lewis Hulbert (talk) 20:26, 13 December 2017 (UTC) Jean-Fred (talk) 10:48, 28 February 2018 (UTC) Santer (talk) Cloaker416 (talk) 22:18, 12 June 2018 (UTC) Rampagingcarrot (talk) 19:57, 28 June 2018 (UTC) Diggr (talk) 08:07, 3 July 2018 (UTC) Harsh Rathod Poke me! 09:42, 7 July 2018 (UTC) Kirilloparma (talk) 00:30, 5 August 2018 (UTC) Sir Lothar (talk) 10:10, 10 August 2018 (UTC) Cwf97 (talk) 14:33, 22 October 2018 (UTC) Esteban16 (talk) 00:08, 27 October 2018 (UTC) Peterchanws Brasig Le Yota de Mars YotaMoteuchi (talk) 08:09, 22 May 2019 (UTC)   Notified participants of WikiProject Video games

  •   Support David (talk) 07:01, 9 July 2019 (UTC)
  •   Support Cwf97 (talk) 11:02, 13 July 2019 (EST)
  •   Comment Couldn't this potentially fall under modified version of (P5059)? Also, I think it would need a clearer name if added, e.g: "video game mod of", "video game modified", "mod/modification of video game", "modifies video game", "base video game", etc. NoInkling (talk) 02:42, 17 July 2019 (UTC)
  •   Comment I don't feel modified version of (P5059) is sufficient. It's not a different version or edition of the game, it's a modification that either changes certain aspects of the game or a full game that requires the original game in order to work. "Base video game" makes it sound like the mod were made by the original developer and would fit better with Wikidata:Property proposal/expansion. --Trade (talk) 02:53, 17 July 2019 (UTC)
  • Technically the mod's class (its instance of (P31) value), or the property's qualifiers, could disambiguate those cases, but of course that makes things a little less obvious and/or more difficult to query. By the way I think "Represents" should be video game (Q7889) and "Domain" should be video game mod (Q865493) in the template. NoInkling (talk) 03:22, 17 July 2019 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Ilya
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Pintoch
Daniel Mietchen
Jsamwrites
Tinker Bell
FabC
Jasc PL
putnik
Dhx1
Tris T7
Peb Aryan
lore.mazza004
Rc1959
Premeditated
  Notified participants of WikiProject Informatics ChristianKl❫ 13:49, 17 July 2019 (UTC)

Mac OS type codeEdit

   Ready Create
Descriptioncode used formerly by Mac OS to identify file types and programs
RepresentsType code (Q9090749)
Data typeString
Template parameterTemplate:Infobox file format (Q10986167)@es "type code"
Domainfile format (Q235557), software (Q7397)
Allowed valueshexadecimal (Q82828)
Example 1Photoshop File Format (Q2141903) → "38 42 49 4d" ("8BIM")
Example 2OpenType Font (Q260180) → "73 66 6e 74" ("sfnt")
Example 3AutoCAD (Q83570) → "41 43 41 44" ("ACAD")
Sourcehttps://www.macdisk.com/macsigen.php
Planned useUse it in infoboxes
Expected completenesseventually complete (Q21873974)
See alsomedia type (P1163)

MotivaciónEdit

(Indica tu motivación para solicitar esta propiedad aquí). --Tinker Bell 23:16, 11 July 2019 (UTC)

DiscussionEdit

  •   Support David (talk) 04:56, 12 July 2019 (UTC)
  •   Support --DannyS712 (talk) 12:30, 12 July 2019 (UTC)
  • could you add "Mac OS" or something similar to the label? Otherwise people are likely not to use it correctly. --- Jura 16:30, 12 July 2019 (UTC)
  •   Support - Premeditated (talk) 18:19, 13 July 2019 (UTC)

TikTok usernameEdit

MotivationEdit

Property for TikTok users. -- CptViraj (📧) 17:46, 12 July 2019 (UTC)

DiscussionEdit

eBay usernameEdit

   Under discussion
Descriptionitem's username on eBay
RepresentseBay (Q58024)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Grey DeLisle (Q13938)grey-delisle
Example 2Christian Frates (Q47691741)cwf12397
Example 3Media Markt (Q2381223)mediamarkt
Sourcehttps://www.ebay.com/
Formatter URLhttps://www.ebay.com/user/$1

MotivationEdit

Property for eBay users.

DiscussionEdit

image of bone or fossil recordEdit

   Under discussion
Descriptionimage of the fossil, bone or skeleton of this taxon
Data typeCommons media file
Domaintaxons
Allowed valuesFile:<foo>.<ext>
Example 1Vespersaurus (Q64836111)File:Vespersaurus foot.png
Example 2pig (Q787)File:Domestic pig skeleton at MAV-USP.jpg
Example 3MISSING

MotivationEdit

It's common for entries for taxa, especially extinct ones, to have at least two suitable images: a photo/illustration and the skeletal remains/fossil for it. It would be good to have both in their relevant entries. NMaia (talk) 06:08, 15 July 2019 (UTC)

DiscussionEdit

File:Domestic pig skeleton at MAV-USP.jpg / applies to part (P518) skeleton (Q7881) and Vespersaurus (Q64836111) image (P18)
File:Vespersaurus foot.png / applies to part (P518) fossil (Q40614)?--Tinker Bell 16:46, 15 July 2019 (UTC)
  •   Oppose Such as the explanation above, the existing property is sufficient David (talk) 06:44, 16 July 2019 (UTC)
  •   Comment In general, people prefer just one value in P18, so a selection with a distinct property could indeed be helpful. I'm not entirely convinced by the suggested wording, but I'm not really a specialist in the field. --- Jura 13:34, 20 July 2019 (UTC)

misas.org Catholic church IDEdit

   Under discussion
DescriptionIdentifier of a catholica church at misas.org
Data typeExternal identifier
Domainchurch building (Q16970), monastery (Q44613), chapel (Q108325)
Allowed valuesString containting alphabetic characters and -
Example 1Almudena Cathedral (Q849711)si-catedral-de-santa-maria-la-real-de-la-almudena-madrid
Example 2León Cathedral (Q175874)santa-iglesia-catedral-de-santa-maria-de-regla-leon
Example 3Tarazona Cathedral (Q2942832)catedral-de-santa-maria-de-la-huerta-tarazona
Format and edit filter validationIt seems it can be validated with the regex [a-z-]+
Sourcehttps://www.misas.org/
Planned useAdd it to churches I have recently created
Formatter URLhttps://www.misas.org/p/$1
See alsomesses.info Catholic church ID (P1644), GCatholic church ID (P2971)

MotivaciónEdit

I think it can be useful to link to the page at misas.org for churches in Spain to link to information like masses times, contact information. Jaimemf (talk) 15:01, 15 July 2019 (UTC)

DiscussionEdit

  •   Support David (talk) 06:47, 16 July 2019 (UTC)
  •   Support If it can help covering Spanish churches, why not. Nomen ad hoc (talk) 18:26, 16 July 2019 (UTC).

Zaragoza public art IDEdit

   Under discussion
DescriptionID of public art catalogued in zaragoza.es
Data typeExternal identifier
Domaininstances of monument (Q4989906) and instances of its subclasses, always using the statement located in the administrative territorial entity (P131) Zaragoza (Q10305) (recursively)
Allowed valuesinteger >= 1
Example 1Q2881966160
Example 2Goya memorial (Q6023031)1
Example 3Q602318612
Sourcehttps://www.zaragoza.es/sede/servicio/arte-publico/
Formatter URLhttps://www.zaragoza.es/sede/servicio/arte-publico/$1

MotivaciónEdit

It contains useful information for public pieces of art in Zaragoza (Q10305) provided by the official website of the city. Jaimemf (talk) 15:52, 15 July 2019 (UTC)

DiscussionEdit

Wayback IDEdit

   Under discussion
DescriptionID for web page archived in Internet Archive's service Wayback Machine
RepresentsWayback Machine (Q648266)
Data typeExternal identifier
Domainproperty
Allowed valuesyyyymmddhhmmss/URL
Allowed unitsnumbers and letter used usually in URL
Example 1Facebook (Q355) → 20190716020349/https://www.facebook.com/ (for qualifiers time stamp 20190716020349 and URL https://www.facebook.com/; please create option for these two qualifiers)
Example 2MISSING
Example 3MISSING
Sourcehttps://web.archive.org
Planned useadd manually to important websites, bot action required in future
Number of IDs in sourcemore than 371 billion web pages saved over time (possible values, only some will be added, as needed, by date)
Expected completenessalways incomplete
Formatter URLhttps://archive.org/web/$1 ''or'' https://web.archive.org/$1

MotivationEdit

Property needed to add archived version of many pages when they are down. Very bright future I suppose for this property as servers cannot be maintained forever so sites go down and can be linked through Wayback when needed. Obsuser (talk) 03:05, 16 July 2019 (UTC)

DiscussionEdit

  •   Oppose; archive URL (P1065) already exists, and full work available at (P953) could also be used. A copy of Facebook's home page is also not a sufficient substitute for the actual Facebook website, so I don't think the example would be an appropriate use of this hypothetical property. Jc86035 (talk) 10:24, 16 July 2019 (UTC)
archive URL (P1065) and full work available at (P953) can hypothetically be used to link Discogs too, for example, and we have separated properties however. It's not copy, it's page source of original with no alteration (it's arhived original). --Obsuser (talk) 10:44, 16 July 2019 (UTC)

WeChat Official AccountEdit

   Under discussion
Descriptionusername of the WeChat Official Account operated by this item
RepresentsWeChat (Q283233)
Data typeString
Domainhuman (Q5), organization (Q43229)
Allowed values[A-Za-z0-9_]+ (I am not very sure what special characters wechat accounts can take.)
Example 1Jiangsu Provincial People's Government (Q11134951) → weixunjiangsu ref.: https://weibo.com/weibojiangsu
Example 2Office of the Commissioner of the Ministry of Foreign Affairs of the People's Republic of China in the Hong Kong Special Administrative Region (Q10872036) → fmcoprc ref.: http://www.fmcoprc.gov.hk/chn/zydt/t1650543.htm
Example 3Huang Xiaoming (Q701194) → lovemingzone
Sourceitem's websites etc., wechat accounts themselves, yue:Template:Wechat

MotivationEdit

Although AFAIK wechat official accounts could not be accessed via a URL, their string names should still be quite a reasonable data set, just like Sina Weibo user ID (P3579). Estimates are >30million official accounts exist.--Roy17 (talk) 16:12, 16 July 2019 (UTC)

DiscussionEdit

  •   Comment unless it's not stable, this should have datatype external-id. If it's unstable, we probably shouldn't have it. --- Jura 13:23, 20 July 2019 (UTC)

AFCD PFKIDEdit

   Under discussion
Descriptionunique identifier for a food type in the Australian Food Composition Database
Data typeExternal identifier
Domainfood (Q2095)
Allowed valuesregex: F\d{6}
Example 1Cripps Pink (Q1140131)F000105
Example 2Banana bread (Q806097)F001374
Example 3watermelon (Q38645)F005520
Example 4lentil (Q61505177)F005177
Sourcehttps://www.foodstandards.gov.au/science/monitoringnutrients/afcd/Pages/default.aspx
Formatter URLhttps://www.foodstandards.gov.au/science/monitoringnutrients/afcd/Pages/fooddetails.aspx?PFKID=$1
See alsoNUTTAB food ID (P2760) AUSNUT food ID (P2759) AUSNUT 2011–13 Food Group ID (P4618)

MotivationEdit

New Australian government database and identifier scheme replacing NUTTAB food ID (P2760). This database captures nutrient information for foods. Dhx1 (talk) 13:51, 17 July 2019 (UTC)

DiscussionEdit

Thierry Caro 99of9 Canley Mattinbgn Kerry Raymond Samwilson JarrahTree ScottDavis Oronsay Pru.mitchell Bidgee Harryboyles Dhx1 SJK Nickw25 Danadl MargaretRDonald Wittylama

  Notified participants of WikiProject Australia --Dhx1 (talk) 13:53, 17 July 2019 (UTC)

Sebleouf
Teolemon
Vladimir Alexiev
Ash_Crow
AVRS
d1g
Dhx1
Tris T7 TT me

  Notified participants of WikiProject Food --Dhx1 (talk) 13:53, 17 July 2019 (UTC)

  Support Good to have a formatter URL for one of these food ones. It has good info on the web database too. --99of9 (talk) 14:28, 17 July 2019 (UTC)

  Support Important to keep up-to-date with changes, i.e. new database replacing NUTTAB. Oronsay (talk) 20:09, 17 July 2019 (UTC)

  Support MargaretRDonald (talk) 20:23, 17 July 2019 (UTC)

  •   Support David (talk) 06:29, 18 July 2019 (UTC)

  Support. Should have a format as a regular expression (P1793) like [Ff]\d{6}, if all of them start with an 'F'. - Premeditated (talk) 09:27, 18 July 2019 (UTC)

value group numberEdit

   Under discussion
Description(qualifier only) an higher level of series ordinal used to separate various lists already with series ordinal (P1545)
Data typeString
Domainany
Example 1(Q3595028) fanqie (P5523) (Q2391630) (series ordinal (P1545)=1, value group number=1), (Q55806623) (series ordinal (P1545)=2, value group number=1)
Example 2(Q3595028) fanqie (P5523) (Q2391630) (series ordinal (P1545)=1, value group number=2), (Q55806688) (series ordinal (P1545)=2, value group number=2)
Example 3MISSING
Planned useUse as a qualifier of fanqie (P5523) and ideographic description sequences (P5753)

MotivationEdit

See User_talk:Ivan_A._Krestinin#Bot_edits_on_P5523 as the background of the proposal. GZWDer (talk) 16:24, 18 July 2019 (UTC)

DiscussionEdit

Item Equivalence Fanqie (initial) Fanqie (final) References
A Guangyun (Q2189818)
A Jiyun (Q35792)
A Hongwu Zhengyun (Q10958946)
B Guangyun (Q2189818)
B Jiyun (Q35792), Hongwu Zhengyun (Q10958946)
C Guangyun (Q2189818)
C Jiyun (Q35792), Hongwu Zhengyun (Q10958946)
D Guangyun (Q2189818)
D Jiyun (Q35792)

There are 9 pairs of data, each consisting of an initial and final character, and these 9 pairs can be further grouped into four equivalent pairs of data (A,B,C,D). Are there any existing properties that can be used to handle this situation? KevinUp (talk) 21:00, 18 July 2019 (UTC)

Perhaps the value group number can be modified to "A1, A2, A3, B1, B2, C1, C2, D1, D2" or "1a, 1b, 1c, 2a, 2b, 3a, 3b, 4a, 4b" to mark the equivalence of certain data sets? KevinUp (talk) 21:12, 18 July 2019 (UTC)

Opensofias
Tobias1984
Micru
Arthur Rubin
Cuvwb
TomT0m
Tylas
Physikerwelt
Lymantria
Bigbossfarin
Infovarius
Helder
PhilMINT
Malore
Nomen ad hoc   Notified participants of WikiProject Mathematics for suggestions on how to handle this situation. The proposed property may also have other applications. KevinUp (talk) 19:35, 20 July 2019 (UTC)

orientationEdit

MotivationEdit

To migrate a large number of misuses of direction (P560), which is supposed to express a relative direction from the subject item toward the parent statement's value, where both items have a fixed location. This property will express how an item is aligned with respect to fixed axes, rather than the location of another item, and is thus not restricted to being a qualifier.

Also propose re-labeling direction (P560) to "relative direction" or "direction relative to subject" (and the equivalent in other languages) to mitigate its misuse. Swpb (talk) 18:40, 18 July 2019 (UTC)

DiscussionEdit

  •   Comment. This is mostly going to be used on items for buildings. What orientation is for them should thus be specified. Is that what's perpendicular to the main entrance? We have to let this be clear. Thierry Caro (talk) 17:04, 19 July 2019 (UTC)
    • Why do you think it will mostly be used for buildings? Only one of the examples is sort of a building; the biggest class of targets I know of are flags. Where it is used for a building and the intended face isn't clear, one can easily add a qualifier applies to part (P518) entrance (Q1137365) or similar. Swpb (talk) 18:38, 19 July 2019 (UTC)
  •   Support I think it would be useful for describing blazons. --Tinker Bell 18:49, 19 July 2019 (UTC)

Wikidata propertyEdit