Wikidata:Property proposal/Archive/42

From Wikidata
Jump to navigation Jump to search

This archive page is full. Use Archive/43 or subsequent ones.


Please restrict each archive page to 80 proposals, to avoid the Lua error: too many expensive function calls issue that messes up previous archive pages.




LACITO language ID

   Not done
Descriptionidentifier of a language at the web site of LACITO
Data typeString
Domainlanguoid (Q17376908)
Allowed valuesletters
ExampleWest Uvean (Q36837) => Fagauvea
Sourcehttp://lacito.vjf.cnrs.fr/ALC/listeparfamille.htm http://lacito.vjf.cnrs.fr/themes/oceanie/#ZonePrint http://lacito.vjf.cnrs.fr/themes/balkans/#ZonePrint etc.
Formatter URLhttp://lacito.vjf.cnrs.fr/ALC/Languages/$1_popup.htm
Discussion

Motivation The web site of the LACITO LACITO (Q3217451) publish some dozens pages about languages. Link the audio records of Pangloss Collection (Q6468667). This property could be usefull. Or not. Visite fortuitement prolongée (talk) 15:28, 19 April 2015 (UTC)

Proposé par: Visite fortuitement prolongée (talk)

You're not really sounding convincing. Do you intend to use this property in a project? --Pasleim (talk) 19:21, 26 April 2015 (UTC)
No. Visite fortuitement prolongée (talk) 19:36, 26 April 2015 (UTC)

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:41, 23 November 2015 (UTC)

establishing legislation

   Not done
DescriptionStatute or other legislative instrument that established a particular official activity
Data typeItem
Domainstatutory offices, organisations, publications, heritage registers, government programmes, etc
Allowed valuessources of law (Q846882)
ExampleNational Health Service (Q16251481)National Health Service Act 1946 (Q6973013),
Sourceexternal reference, Wikipedia list article, etc.
Motivation

Useful to be able to record what legislation established a particular official activity, and (by searching) what new activities particular legislation created. Jheald (talk) 11:42, 8 November 2015 (UTC)

Discussion
For this kind of data I prefer to use significant event (P793) with that structure:
National Health Service (Q16251481):
significant event (P793): inception
point in time (P585): xx.xx.xxxx (qualifier)
main regulatory text (P92): YYYYYY (qualifier)
or
National Health Service (Q16251481):
inception (P571): xx.xx.xxxx
main regulatory text (P92): YYYYYY (qualifier)
Snipre (talk) 22:12, 16 November 2015 (UTC)
@Snipre: I analyzed this property before giving my vote, I think it has a very different purpose: to inform on the basis of rules of an administrative region. e.g. . The idea of this proposal is another: report on the document that formalizes an organization. I believe that are sufficiently different things and therefore should have specific properties, so, I keep my  Support. --Almondega (talk) 00:33, 17 November 2015 (UTC)
Sorry but I don't see the differences you mentioned. In both cases we have a legal text which defines the goals and the general structure of an organization. Just change your scope and analyze the cases by using an organization point of view: the National Health Service in England and Brazil can be defined as social organizations which found their objectives and their means in a legal text depicted by main regulatory text (P92). Please provide objectives criteria to promote a new property which can't be replaced by main regulatory text (P92).
Again what do we want to have ? We want a link between an organization and a leagl text providing its goals and some basic information about its structure. That's it. main regulatory text (P92) can do that. Snipre (talk) 02:28, 17 November 2015 (UTC)
  •  Oppose per Snipre. --Casper Tinan (talk) 11:19, 17 November 2015 (UTC)
  •  Oppose. foundational text (P457) already exists. --Yair rand (talk) 14:13, 17 November 2015 (UTC)
  • Question Would anyone object if we changed the primary label of foundational text (P457) to "establishing legislation", which seems a more direct and concrete term to me. Looking at the current values for P457 (see "list of values" link at top-right of the property box at Property_talk:P457 to go to query), it seems to me that most of them could reasonably be described as "legislation" of one kind or another. "Foundational text" could remain as an alias. Jheald (talk) 14:37, 17 November 2015 (UTC)
    • What would be the benefit of that? All establishing legislation is also foundational text, but not all foundational text is legislation. However, all foundational texts that are legislation are establishing legislation. Replacing foundational text with establishing legislation limits the potential uses without adding any extra data clarity. --Yair rand (talk) 17:37, 17 November 2015 (UTC)
      • @Yair rand: because "foundational text" is such a vague term that people aren't adding it -- or even remembering that the property exists. "Establishing legislation" (in which I would include international treaties, and historical charters) is much more concrete -- it directly puts to people the question what established this in law, a more direct question which IMO is more likely to get a direct answer.
      Yes, you may be right, there may be some cases that don't fit, where "foundational text" would be the more appropriate term. I don't mean to exclude such cases -- I mean to include them, by accepting "foundational text" as an appropriate alias. But I do think that, as the primary label for the property, "establishing legislation" would be more likely to get people to add statements. Jheald (talk) 18:08, 17 November 2015 (UTC)
Before starting creation or modification of property we should understand which are the needs. What is the distinction between foundational text (P457) and main regulatory text (P92) ? Snipre (talk) 16:14, 18 November 2015 (UTC)

Not done - use the alternative method suggested. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:33, 19 November 2015 (UTC)

dis-establishing legislation

   Not done
DescriptionStatute or other legislative instrument that wound up, dissolved or otherwise brought to an end a particular official activity or body
Data typeItem
Domainstatutory offices, organisations, publications, heritage registers, government programmes, etc
Allowed valuessources of law (Q846882)
ExampleBritish Transport Commission (Q3246355)Transport Act 1962 (Q285716),
Sourceexternal reference, Wikipedia list article, etc.
Motivation

Useful to be able to record what legislation ended a particular official activity, and (by searching) what activities or bodies were wound up by a particular piece of legislation. Jheald (talk) 11:42, 8 November 2015 (UTC)

Discussion
National Health Service (Q16251481):
significant event (P793): dissolution
point in time (P585): xx.xx.xxxx (qualifier)
main regulatory text (P92): YYYYYY (qualifier)
or
National Health Service (Q16251481):
dissolved, abolished or demolished date (P576): xx.xx.xxxx
main regulatory text (P92): YYYYYY (qualifier)
Snipre (talk) 22:16, 16 November 2015 (UTC)
For one thing, a lot of searches, apps, and people using dumps only use the simplified "truthy" version of the database, which omits all qualifiers and all statements not of top rank. With searches there is also a particular limitation, that you can't use SPARQL's path operators, ie patterns including things like wdt:Pxxx/wdt:Pyyy*, if relationships are expressed using qualifiers.
Also there's a fundamental issue that if information is given in a qualifier, then it can't be separately referenced or qualified. (You can't have references specifically to a qualifier, nor a qualifier on a qualifier). So, as a broad strategy, it seems to me preferable, as far as possible, to put information on actual properties rather than qualifiers. The real purpose of a qualifier, it seems to me, is to indicate that information may not be generally true, or to distinguish context between different values of a main property, rather than as a packaging device for information.
I would prefer a standalone property, parallel to P457, rather than using a qualifier. And, as per Yair rand, it seems to me that there is a difference between the text that regulates something, and a text winding it up. (I also think there is a difference between the text regulating something and a text establishing it -- the difference between on the one hand the rule of a medieval monastery monastic rule (Q1397721), or the standing orders of a legislative assembly; compared with the charter giving the land for the monastery, or the legislative act setting up the legislature.) Jheald (talk) 14:58, 17 November 2015 (UTC)

Not done - use the alternative method suggested. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:31, 19 November 2015 (UTC)

time to altitude

Template parameter"time to altitude" in en:aircraft specs
Domainaircraft (Q11436)
Allowed valuesquantity with unit of time
Motivation

Widely cited aircraft specification. Josh Baumgartner (talk) 04:11, 30 September 2015 (UTC)

Discussion
  •  Comment how could we express this in more generic properties? I think we already have a wide range of aircraft related properties. --- Jura 04:31, 30 September 2015 (UTC)
    • What is the benefit in overloading generic properties? Thryduulf (talk: local | en.wp | en.wikt) 18:51, 30 September 2015 (UTC)
      • There is no such thing. Josh generally advocates the use of generic properties. So I think we should help him achieve this with aircraft as well. Given the field, I think it's particularly appropriate: aircraft have hundreds of technical characteristics and we can't make properties for each one. As they are not massively used, none of the usual advantages of having specific properties apply. --- Jura 09:03, 1 October 2015 (UTC)
        • @Jura1: I often see a more generic or a more specific approach as possible for a property, and when I do I provide an alternative solution to the discussion and let folks evaluate it. Simply saying be more generic or more specific is not terribly constructive. We are not limited to a certain number of properties for one field or the other, but likewise we shouldn't just go crazy making a million of them that nobody has a use for. If unnecessary duplication can be avoided, that is helpful as it keeps data structured better. If you feel this data can be better structured using existing properties, I am all ears on how you propose to do that. Josh Baumgartner (talk) 00:38, 20 October 2015 (UTC)
  •  Support. I have argued for more generic properties in lots of places but in this case I can't see where a generic property could do the job. This is a very specific aircraft related property and provides useful info that can't be provided otherwise. Joe Filceolaire (talk) 20:29, 25 October 2015 (UTC)
  •  Support per Joe Filceolaire. Thryduulf (talk: local | en.wp | en.wikt) 00:46, 26 October 2015 (UTC)
  •  Support Danrok (talk) 20:04, 23 November 2015 (UTC)

@Joshbaumgartner, Jura1, Thryduulf, Filceolaire, Danrok: ✓ Done time to altitude (P2362) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:52, 27 November 2015 (UTC)


Occurrences

   Not done
DescriptionNumber of times an event has occurred or been held
Data typeNumber (not available yet)
Template parameter"number" in en:Template:Infobox sports award; "Times_held" in en:Template:F1 race
Domainevents
Allowed valuesnon-negative numbers
ExampleGordon Bennett Cup in ballooning (Q1537962) → 59; United States presidential election (Q47566) → 57; Singapore Grand Prix (Q9137) → 16; Winter Olympic Games (Q82414) → 22
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsBots could harvest infobox data
Motivation

This is useful for all recurring events, whether scheduled or unscheduled (e.g. could be used for number of times a volcano has erupted) (Add your motivation for this property here.) Thryduulf (talk: local | en.wp | en.wikt) 19:34, 30 September 2015 (UTC)

Discussion

Not done, as quantity (P1114) already exists, That said, counting the number of instance of (P31) should suffice in most cases. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:40, 20 November 2015 (UTC)


ProCyclingStats ID (race)

DescriptionProCyclingStats ID (race)
Data typeString
Domaincycle sport (Q2215841)
Example2015 Grand Prix de Fourmies (Q20872499) → ...
Sourcehttp://www.procyclingstats.com/race/GP_de_Fourmies_La_Voix_du_nord_2015
Formatter URLhttp://www.procyclingstats.com/race/$1
Robot and gadget jobsyes
Motivation

For cyclists, I already have ProCyclingStats cyclist ID (P1663), Cycling Archives cyclist ID (P1409) and CQ Ranking male cyclist ID (P1541) that permits to have a link to database but only for cyclists. I need the same properties for races and for teams. As you can see on Tom Van Asbroeck, I use three templates to links with Wikidata, Modèle:ProCyclingStats, Modèle:Siteducyclisme and Modèle:Cqranking. Once I will obtain these six properties, I will adapt the templates, and when I will put them in the article, I will have links to these database.

You can see the code on Modèle:ProCyclingStats, PXXXX will be replaced by the new properties. The template ProCyclingStats is currently active with Wikidata in 16 different languages (see Template:ProCyclingStats (Q20742687)).

These properties are a part in a bigger project for entering all the datas from cycling on Wikidata to work together instead of doing the same work in different languages. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

Discussion
the url for the page for 2015 Grand Prix de Fourmies (Q20872499) on this web site is http://www.procyclingstats.com/race/GP_de_Fourmies_La_Voix_du_nord_2015. Are we saying the ID for this is "GP_de_Fourmies_La_Voix_du_nord_2015"? Joe Filceolaire (talk) 15:52, 12 November 2015 (UTC)
Yes and no, there is also a number like here http://www.procyclingstats.com/race.php?id=164097 . For cyclists, we can use the number or the text and it works. I don't know why it is sometimes a number and sometimes a text, and some contributors find the number when it is a text. Jérémy-Günther-Heinz Jähnick (talk) 15:52, 14 November 2015 (UTC)
✓ Done @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, Filceolaire, Joshbaumgartner, ComputerHotline: --Fralambert (talk) 14:16, 21 November 2015 (UTC)

ProCyclingStats ID (team)

Motivation

See above. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

Discussion
See comment on property above. Joe Filceolaire (talk) 15:55, 12 November 2015 (UTC)
✓ Done @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, Filceolaire, ComputerHotline: --Fralambert (talk) 14:36, 21 November 2015 (UTC)

Cycling Archives ID (race)

DescriptionCycling Archives ID (race)
Data typeString
Domaincycle sport (Q2215841)
Example2015 Grand Prix de Fourmies (Q20872499) → 255517
Sourcehttp://www.siteducyclisme.net/ritfiche.php?ritid=255517
Formatter URLhttp://www.siteducyclisme.net/ritfiche.php?ritid=$1
Robot and gadget jobsyes
Motivation

See above. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

Discussion
✓ Done @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, Filceolaire, ComputerHotline: --Fralambert (talk) 16:26, 21 November 2015 (UTC)

Cycling Archives ID (team)

DescriptionCycling Archives ID (team)
Data typeString
Domaincycle sport (Q2215841)
ExampleTopsport Vlaanderen-Baloise 2015 (Q18746658) → 22764
Sourcehttp://www.siteducyclisme.net/ploegfiche.php?id=22764
Formatter URLhttp://www.siteducyclisme.net/ploegfiche.php?id=$1
Robot and gadget jobsyes
Motivation

See above. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

Discussion
✓ Done @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, Filceolaire, ComputerHotline: --Fralambert (talk) 16:32, 21 November 2015 (UTC)

WikiProjects

   Not done
DescriptionWikiProjects on subject's scope
Data typeItem
Template parameteren:Template:WikiProjectBannerShell
DomainWikipedia articles
ExampleWikiProject Computing (Q15730590)
Robot and gadget jobsHarvest associated WikiProjects from en:Template:WikiProjectBannerShell template located on articles talk pages
Proposed byRezonansowy (talk)
Discussion

Motivation. See en:Wikipedia:Lua_requests#Module:AutoPortals, we need Wikidata for such cases. Rezonansowy (talk) 21:13, 26 February 2014 (UTC)

@Tobias1984, Emw, Bene*: You participate in WikiProjects on our Wikidata. What do you think about this proposal? --Rezonansowy (talk) 11:09, 5 March 2014 (UTC)
@Rezonansowy: Can you add an few more examples? I don't understand what this is about. --Tobias1984 (talk) 17:11, 7 March 2014 (UTC)
Tobias1984, If I understood correctly, what is meant is that each item should be connected with its related Wikiprojects as stated on the talk page. For instance, ampere (Q25272) according to the talk page belongs to the Wikiprojects WikiProject Physics (Q8487193), WikiProject Electrical engineering (Q14554993), etc. This, however, it is not feasible, since the scope of each wikiproject is different each language version of Wikipedia. Probably it can be done with badges, but we'll have to wait and see how Bugzilla40810 is implemented.--Micru (talk) 18:00, 7 March 2014 (UTC)
@Micru, Tobias1984: I think it can be done without any problems. See Wikipedia link on WikiProject Computing (Q15730590) and you see that on many wikis scope of this project is the same. In case of completely different scope which is proper to the article, we can just add a second item to this property. --Rezonansowy (talk) 10:52, 8 March 2014 (UTC)

@Micru, Tobias1984:?

@Rezonansowy:, as said I would prefer to wait and see how badges work, maybe they are a better approach. @Bene*: any info about when we could try the first version of badges? I saw that you were working on it and I was wondering how far you are.--Micru (talk) 15:31, 16 March 2014 (UTC)
Hi, although badges may be used for this task at some time, this is not the original usecase they are made for. Furthermore, there would be a huge amount of badges if we allow to add every WikiProject as a badge. While I understand that there might be cases where different Wikipedias treat topics in another way, I think there are much more cases where we can actually say that the topic belongs to the same WikiProject on all Wikipedia. You may prove me wrong but I do not see such a big problem in using statements for this purpose. -- Bene* talk 17:51, 16 March 2014 (UTC)
@Bene*: Badges were thought as a way of handling language- and project-specific tags, I do not understand why is a problem having a badge for each Wikiproject, maybe it will become clear later on, but now I just don't see how can that be a problem. A page doesn't belong to one Wikiproject in all Wikipedias, if you compare them you will see that sometimes they overlap but that's not the norm. IMHO, having language- and project-specific statements in Wikidata goes against one of the main fundaments of Wikidata, which is data reuse between projects.--Micru (talk) 15:47, 19 March 2014 (UTC)

I think this can only work if the biggest languages opt in and people will be fine with changing the article rating on Wikidata. We could create (subclass off)-items for the every language a project exists in. So actually we could solve the language problem. The biggest issue with this is that a majority of Wikipedians have not embraced Wikidata yet. en-wiki has 130 000 active contributors. Wikidata just 13000. Once the numbers are closer to each other we know that people know how to use Wikidata and then we could create a property like this one. --Tobias1984 (talk) 12:05, 19 March 2014 (UTC)

@Tobias1984: I posted this request because of this talk on Wikipedia. Wikidata could really help with managing associated WikiProjects and theirs portals, much more simply and like in my example multilingual. We can also develop a gadget similar to Edit links link in language toolbox. Centralization of WikiProjects is very important in whole article data centralization process. --Rezonansowy (talk) 14:36, 19 March 2014 (UTC)
@Rezonansowy: I do like the idea of centralizing this. I just don't know if a bot could do this right now. There are probably a few thousand changes of this every day. Plus the changes in quality assessment and importance to the project. The templates are often more complicated with field for task forces and other stuff. - But apart from the technical difficulties it would be interesting to see global article quality comparisons. --Tobias1984 (talk) 15:07, 19 March 2014 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────@Tobias1984: I think it can be done similar to en:Template:Authority control/VIAF, but with a little exception, we should create a separate template for it. Detailed process:

  • Register property WikiProjects, WikiProject class and WikiProject rating, see its structure on en:Talk:World Bank
  • Bot could find every template in head of the talk page starting from {{WikiProject...}} or just do the safer method by exploring the {{WikiProjectBannerShell}} contents
  • When every WikiProject along with its rating (some qualifiers) will be covered on Wikidata, bot could replace banner templates with a new automated template
  • Create a new template, with corresponding Lua module to import items from Wikidata, it should have note that every addition of WikiProject banner should be done through the Wikidata

What do you think? --Rezonansowy (talk) 13:23, 21 March 2014 (UTC)

@Rezonansowy:Sounds pretty good. Gathering the data and creating the properties is probably the first step. For the Wikipedias to opt in, it will probably take some convincing. --Tobias1984 (talk) 17:11, 21 March 2014 (UTC)

Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:44, 21 November 2015 (UTC)

Similar item

   Not done
Descriptionan item whose sitelink should be used if this item does not have a sitelink for a given language. Multiple values are allowed: The first item, which has the given sitelink, will be used. To specify the preferred item for a given language, use the Preferred for qualifier (optional). To specify the fragment of the target page, use the Fragment identifier qualifier (optional).
Data typeItem
Domainall items
Allowed valuesany item
Exampleschoolchild (Q48942)student (Q48282)
Proposed byPetr Matas
Discussion

See WD:Requests for comment/One vs. several sitelink-item correspondence#Use a property. Petr Matas 09:20, 28 November 2014 (UTC)

 Comment Isn't similarity a little too broad to be useful? The next question would be the reason for the similarity? --Tobias1984 (talk) 13:24, 20 December 2014 (UTC)
 Comment This might be a solution when Wikidata has separate items for an entity and things which are 'part of' it, but one or more Wikipedias has a single article for all of the parts together. Not sure what the best way to deal with this is. - PKM (talk) 00:44, 21 December 2014 (UTC)
 Comment I am not insisting on the name of the property. What is important, is its purpose for connecting Wikipedia (and maybe other sister projects) articles. Petr Matas 19:28, 21 December 2014 (UTC)
see said to be the same as (P460)--Oursana (talk) 01:33, 22 December 2014 (UTC)
Yes, there are a few properties (subclass of (P279), part of (P361), said to be the same as (P460)) with meaning similar to the one being proposed, but none of them is universally applicable and their use for this purpose would sometimes lead to unexpected results. Petr Matas 05:34, 22 December 2014 (UTC)
said to be the same as (P460)? See the descriptions: this item is said to be the same as that item, but the statement is disputed. But the example is not disputed, neither that both are not the same (de:Student/de:Schüler), nor that both are the same (en:Student). --Diwas (talk) 19:06, 28 December 2014 (UTC)
said to be the same as (P460) does not work for this concept, as it's purpose is to record when one source states that two items are separate and distinct while another states them as being the same, or where two different sources allude to a subject being the same as two different concepts which are known to be distinct. This proposal is about articles where in certain wikis, the subject is treated to separate articles while in others it is one article, especially when the language provides for different definition of what is covered by the concept. Josh Baumgartner (talk) 19:15, 20 October 2015 (UTC)
 Support: Wikidata is ... collaborative, multilingual, secondary database, collecting structured data to provide support for Wikipedia, Wikimedia Commons, the other Wikimedia projects, and well beyond that. Wikidata should serve the relations of similar concepts and articles about them. Wikidata should not say this relations have to be managed outside in several projects and language versions by redirects or atomised articles. In different languages, similar concepts are treated in one or several articles. --Diwas (talk) 20:21, 28 December 2014 (UTC)
 Comment The same property has been proposed also as Redirect to. Petr Matas 08:54, 26 April 2015 (UTC)
And has been not done. Visite fortuitement prolongée (talk) 19:03, 22 June 2015 (UTC)

Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:45, 21 November 2015 (UTC)

Preferred for

   Not done
Descriptiona qualifier of Similar item, indicating which Wikimedia project(s) prefer the given similarity
Data typeItem
Domainall items
Allowed valuesinstances of Wikimedia project (Q14827288)
Exampleschoolchild (Q48942) Similar to student (Q48282) with qualifier Preferred for English Wikipedia (Q328)
Proposed byPetr Matas
Discussion

See WD:Requests for comment/One vs. several sitelink-item correspondence#Use a property. Petr Matas 09:20, 28 November 2014 (UTC)

Make the following thought experiment to get the answer: You are reading a Wikipedia article on "red" in language A and you want to switch to language B, which is not linked to the corresponding data item. Is it appropriate to offer the B's article on "green" instead?
The relation is often (but not always) symmetric. Petr Matas 05:45, 22 December 2014 (UTC)
Thank you. That makes the intention much clearer. However, the proposal is still very unclear, and needs to be re-written to resolve that. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:42, 22 December 2014 (UTC)
You're welcome. Have you seen the proposal in the RfC? I believe that everything is explained there. Petr Matas 16:11, 22 December 2014 (UTC)
Thank you, but it needs to be clarified here. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:55, 25 April 2015 (UTC)

Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:41, 21 November 2015 (UTC)

Fragment identifier

   Not done
Descriptiona qualifier of Similar item, indicating the article fragment, which discusses the item's topic
Representsfragment identifier (Q1440450)
Data typeMultilingual text (not available yet)
Domainall items
Exampleschoolchild (Q48942) Similar to student (Q48282) with qualifier Fragment identifier en:"Pupil", fr:"Elève"
Format and edit filter validationit can be checked that the fragment exists in the target article
Proposed byPetr Matas
Discussion

This qualifier should serve as a replacement of the functionality proposed by RfC/Sitelinks with fragments. Petr Matas 18:12, 22 December 2014 (UTC)

 Support: Wikidata is ... collaborative, multilingual, secondary database, collecting structured data to provide support for Wikipedia, Wikimedia Commons, the other Wikimedia projects, and well beyond that. Wikidata should serve the relations to fragments. Wikidata should not say this relations have to be managed outside in several projects and language versions by redirects or atomised articles. Articles containing some fragments with clear relations to items, it is confusing to have no sitelinks to them. Since we have no sitelinks to fragments, this property will solve many problems, and it will be less critical and easier to create. --Diwas (talk) 20:21, 28 December 2014 (UTC)
 Oppose as currently proposed, but I am very sympathetic to the value of linking to headings. However, there are significant problems with such links that are not overcome by this proposal, such as how to stay in synch with changes to article headings. In the provided example, I'm not sure what it achieves, as "Pupil" is not a fragment in the enwiki article "student". Josh Baumgartner (talk) 20:12, 20 October 2015 (UTC)

Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:43, 21 November 2015 (UTC)


first attestation (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typePoint in time
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:14, 18 June 2013 (UTC)
Discussion

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:17, 22 November 2015 (UTC)

word's gender (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:18, 22 November 2015 (UTC)

word inflection (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 22 November 2015 (UTC)

declension of words (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion
  •  Oppose I think if we have word inflection we do not need a property declension. For example you can use de-noun-m as value for a masculine German noun.

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:35, 15 August 2015 (UTC)

conjugation (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:25, 18 June 2013 (UTC)
Discussion
  • In some form (link to article? type in Zaliznyak system?) it should be. Infovarius (talk) 13:59, 25 June 2013 (UTC)
  •  Oppose I think if we have word inflection we do not need a property conjugation. For example you can use de-verb-weak as value for a weak German verb.

 Not done. No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:32, 15 August 2015 (UTC)

homophone (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:46, 21 November 2015 (UTC)

variants (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:47, 21 November 2015 (UTC)

false friend (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:47, 21 November 2015 (UTC)

derivatives (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:48, 21 November 2015 (UTC)

international derivatives (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:49, 21 November 2015 (UTC)

synonyms (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wiktionary
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:49, 21 November 2015 (UTC)

Pronunciation

   Not done
DescriptionIPA pronunciation
Data typeMonolingual text (or item?)-invalid datatype (not in Module:i18n/datatype)
Template parameterWhile I don't know any infoboxes that use this, they might one day. This is also useful for querying.
DomainAll letters in all alphabets
Example<V> pronounced <"v">, <Yodh> pronounced <"j">
OR <V> pronounced <voiced labiodental fricative>, <Yodh> pronounced <palatal approximant>
Proposed byYpnypn (talk)

Note that qualifiers are very often needed. For example, z is pronounced "ts" in German but "z" in English.

While "item" might seem more logical, many languages use one letter for a vowel and a consonant, or for two vowels, so I think "String" makes more sense. Perhaps we could have two properties. – Ypnypn (talk) 23:47, 22 April 2013 (UTC)

Z is not always pronounced ts in German, that's the problem. Pronunciation differs depending on the surrounding letters and sometimes even without any hint. Note that not only letters have unique pronunciations but also di- and trigraphs. To really implement this, you would have to 1. specify the language, 2. specify under what conditions this particular pronunciation occurs (the rules can be quite complex), 3. either ignore all exceptions, i.e. losing this information, or list all exceptions, i.e. flooding the statement. —PοωερZtalk 12:02, 26 April 2013 (UTC)
See wikt:Wiktionary:IPA_pronunciation_key, these are just some languages and the list isn't even complete for them as far as I can tell. —PοωερZtalk 12:11, 26 April 2013 (UTC)
It doesn't make much sense, in my view, to add a "pronunciation" property to graphemes and glyphs. See "ghoti" for the classical example. Names and terms, perhaps, but even then pronunciation varies widely depending on dialect and language. Gabbe (talk) 09:44, 27 April 2013 (UTC)
Few languages have as crazy spelling as English. So even if it's hopeless to list every rule for Latin alphabets, it could still make sense for Hebrew, Russian, Arabic, etc. or other languages with simple pronunciation rules. – Ypnypn (talk) 19:11, 28 April 2013 (UTC)
Much enough do. In Russian, there are vowel reduction, consonant devoisation, consonat cluster melting… Even two words writing similary can be read different. Even if native Russian doesn't feel different between я reading in пять and тяпка, they are different IPA items… Ignatus (talk) 18:36, 6 June 2013 (UTC)

 Move --Tobias1984 (talk) 15:56, 5 August 2013 (UTC)

 Oppose This seems to be a duplicate of the 'IPA' property immediately above. The domain for this should be for words, not letters. The datatype should be 'string' since it does not have a language. We also need another Pronunciation property for a recording of a native speaker speaking the word. Filceolaire (talk) 21:37, 5 August 2013 (UTC)
 Oppose duplicate of IPA transcription (P898) --Pasleim (talk) 12:41, 15 May 2015 (UTC)

 Not done. No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:31, 15 August 2015 (UTC)

Sort key (en)

   Not done
Descriptionsee Wikidata:Wiktionary
Data typeString
Exampleespérer => esperer
Proposed byGZWDer (talk) 10:28, 18 June 2013 (UTC)
Discussion
Already exists, see P1964 (P1964) - Nikki (talk) 15:09, 2 September 2015 (UTC)

see also (en)

   Not done
Descriptionsee Wikidata:Wiktionary
Data typeItem
Examplemere => mère
Proposed byGZWDer (talk) 10:28, 18 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:07, 21 November 2015 (UTC)

refers to (en)

   Not done
DescriptionWikidata:Wiktionary
Data typeItem
Exampleapple => Q89
Proposed byGZWDer (talk) 09:47, 20 June 2013 (UTC)
Discussion
Weak oppose. There is no bijection between words and terms. Infovarius (talk) 06:57, 28 June 2013 (UTC)

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:31, 15 August 2015 (UTC)

example usage (en)

   Not done
DescriptionWikidata:Wiktionary
Data typeMonolingual text
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 09:47, 20 June 2013 (UTC)
Discussion

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:08, 21 November 2015 (UTC)

Female form/equivalent of

   Not done
Descriptionfemale form/equivalent of
Data typeItem
Template parameterput Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domainperson, term
Exampleprincess (Q863048) => prince (Q2747456))
Robot and gadget jobsCreate reverse value pair of "female form/equivalent of" for "male form/equivalent of" in target articles
Proposed byJared Zimmerman (talk)
Discussion

Motivation. Jared Zimmerman (talk) 07:14, 12 November 2013 (UTC)

@Jaredzimmerman (WMF): see Wikidata:Property_proposal/Unsorted#Female_form_of_label_.28string.29 for a proposal with monolingual string. --- Jura 12:31, 18 November 2014 (UTC)
 Oppose The example items are both instance of (P31)noble title (Q355567). Titles themselves have no gender, though they may be restricted to being held only by people of a certain gender. Princess is also subclass of (P279)woman (Q467), but this seems to be a conflation of two concepts: 'Princess' (the title/rank), and a 'princess' (person with title of Princess). For linking ranks of equivalent level, I would propose an 'equivalent rank' property. Then
⟨ princess (Q863048)  View with Reasonator View with SQID ⟩ equivalent rank Search ⟨ Q2747456 ⟩
would work just fine. For most things that do have gender specific concepts, simply define each of the gender-specific concepts as a subclass of the general concept and specify in each which gender they apply to. Josh Baumgartner (talk) 20:37, 20 October 2015 (UTC)

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:09, 21 November 2015 (UTC)

Male form/equivalent of

   Not done
Descriptionmale form/equivalent of
Data typeItem
Template parameterput Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domainperson, term
Exampleprince (Q2747456) => princess (Q863048))
Robot and gadget jobsCreate reverse value pair of "male form/equivalent of" for "female form/equivalent of" in target articles
Proposed byJared Zimmerman (talk)
Discussion

Motivation. Jared Zimmerman (talk) 07:16, 12 November 2013 (UTC)

Female and Male are not the only Genus. See Special:WhatLinksHere/Q162378, and I know at least two more... -- Lavallen (talk) 11:37, 2 March 2014 (UTC)
 Oppose as per female form above. Josh Baumgartner (talk) 20:37, 20 October 2015 (UTC)

Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:10, 21 November 2015 (UTC)

Personal Pronoun

   Not done
DescriptionPrefered personal pronoun for a person, usually tied closely with gender
Data typeitem, string-invalid datatype (not in Module:i18n/datatype)
Template parameterput Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domainperson
ExampleSample: Big Freedia (Q4905738)'s prefered pronoun is he (Q1196074)) or she (Q1270787))
Sourcehttps://en.wikipedia.org/wiki/Personal_pronoun
Proposed byJared Zimmerman (talk)
Discussion

Motivation. Jared Zimmerman (talk) 07:54, 12 November 2013 (UTC)

 Not done. No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:30, 15 August 2015 (UTC)

omission (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wikiquote
Data typeString
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:35, 18 June 2013 (UTC)
Discussion
  • I do not understand the meaning or intended use of this property, which has been "in progress" for more than a year. What sort of data items would have this property? What does it mean to be an "omission" of the thing to which the data item refers? A concrete example of a property value that would relate to a particular existing data item might help to clarify the intended meaning and use of the proposed property. ~ Ningauble (ping me at en.q) 13:09, 1 August 2014 (UTC)
 Oppose: I cannot imagine any use case for this property at Wikiquote. ~ Ningauble (ping me at en.q) 17:22, 1 September 2014 (UTC)

Not done. No Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:18, 15 August 2015 (UTC)

curators (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wikiquote
Data typeItem
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:35, 18 June 2013 (UTC)
Discussion
  • I do not understand the meaning or intended use of this property, which has been "in progress" for more than a year. What sort of data items would have this property? What does it mean to be "curators" of the thing to which the data item refers? A concrete example of a property value that would relate to a particular existing data item might help to clarify the intended meaning and use of the proposed property. ~ Ningauble (ping me at en.q) 13:10, 1 August 2014 (UTC)
 Oppose: I cannot imagine any use case for this property at Wikiquote. ~ Ningauble (ping me at en.q) 17:24, 1 September 2014 (UTC)

Not done. No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:18, 15 August 2015 (UTC)

curating time (en)

   Not done
Descriptionsee m:Wikidata/Notes/Future#Wikiquote
Data typePoint in time
Example 1MISSING
Example 2MISSING
Example 3MISSING
Proposed byGZWDer (talk) 10:35, 18 June 2013 (UTC)
Discussion
  • I do not understand the meaning or intended use of this property, which has been "in progress" for more than a year. What sort of data items would have this property? What is the meaning of "curating time" of the thing to which the data item refers? A concrete example of a property value that would relate to a particular existing data item might help to clarify the intended meaning and use of the proposed property. ~ Ningauble (ping me at en.q) 13:11, 1 August 2014 (UTC)
 Oppose: I cannot imagine any use case for this property at Wikiquote. ~ Ningauble (ping me at en.q) 17:26, 1 September 2014 (UTC)

Not done. No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:17, 15 August 2015 (UTC)


legislative enactment (en)

   Not done
DescriptionA tag marking that a document, act , edict , statute or proclomation is a document defining with authority what a law in a specified jurisdiction is.
Data typeUnsure- to be disscussed. (probably boolean or instance of type)-invalid datatype (not in Module:i18n/datatype)
DomainTo be defined for documents
Example 1MISSING
Example 2MISSING
Example 3MISSING
Robot and gadget jobsIntent is to create a list of enactements for table generation and searches.
Proposed bySfan00 IMG (talk) 14:26, 2 August 2013 (UTC)
Discussion
  • Suggested qualifers:
    • Year - year of enactment
    • Jurisdiction - Jurisdiction against which the enactment is applied.
    • Amended by - Other legislative enactments which modify this one from its original text
    • Repealed by - Other legislative enactments which modify this one by removing sections entirly.

This proposal is for a flag, that specfically allows a document identified at Wikipedia or Wiksource to be marked as a legislative enactment

It is intened that after this property is discussed others are implemented that enable further properties to be created which allow for details of enactments and repeals to be tracked, in the same way that sites like the UK SLD tracks UK primary and Secondary legislation for searches.

Sfan00 IMG (talk) 14:26, 2 August 2013 (UTC)

 Oppose Make 'legislative enactment' a 'Q' item and use property 'instance of (P31) to reference it. Filceolaire (talk) 20:03, 2 August 2013 (UTC)
Can you explain this in more depth?
Every work on wikisource will be tagged by the existing 'instance of (P31)' property as an 'instance of:novel' or 'instance of:history' or 'instance of:legislative enactment'. We don't need specific properties for each type of work. Filceolaire (talk) 07:35, 30 November 2013 (UTC)

 Not done per Filceolaire's solution. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:38, 15 August 2015 (UTC)

tomb_location_on_openstreetmap

   Not done
Descriptionjump to location of tomb in Openstreetmap project
Data typeoverpass query-invalid datatype (not in Module:i18n/datatype)
Template parameterput Wikipedia infobox parameters here. If existing, sample: "population" in en:template:infobox settlement
Domainperson
Examplehttp://overpass-turbo.eu/?Q=%28%0Anode[%22subject%3Awikidata%22%3D%22Q336977%22][%22historic%22%3D%22tomb%22]%3B%0Away[%22subject%3Awikidata%22%3D%22Q336977%22][%22historic%22%3D%22tomb%22]%3B%3E%3B%0Arel[%22subject%3Awikidata%22%3D%22Q336977%22][%22historic%22%3D%22tomb%22]%3B%3E%3B%0A%29%3B%0Aout%20meta%3B&C=51.1936;3.23812;18
Sourceopenstreetmap.org
Robot and gadget jobsdon't know yet
Proposed byPolyglot (talk)
Discussion

I'm a contributor to Openstreetmap.org. I'm experimenting a bit with adding wikidata tags to objects on OSM and trying to find out what the possibilities are.

To find them again, there is the possibility to use Overpass API as follows:

http://overpass-turbo.eu/?Q=node["subject:wikidata"="Q336977"]["historic"="tomb"];out;

I tried to add this query directly in an article on nl.wikipedia.org, but that's not acceptable. No external links inside the body text.

Does it make sense to create a property for this? If so, there may be other such queries coming along in the future. Also be aware that there may be several OSM objects as the result. For example Pater Damiaan is buried in Belgium, but his hand(s) were (re)buried as a shrine on Molokai.

Examples of other queries that I can think of: all statues representing a person or event all streets named after a poet or artist

Polyglot (talk) 23:29, 27 February 2014 (UTC)

We already have place of burial (P119) which links to a wikidata item e.g. a cemetery and burial plot reference (P965). The item for the cemetery should have the geo coordinates using the coordinate location (P625) property. These coordinates can be used on OSM.
Obviously OSM has its own coordinates for the tomb object. What I'm proposing is a way to show people where it is/go there on a live map.
We also have OpenStreetMap relation ID (P402) to link to OSM geoshapes. Filceolaire (talk) 02:29, 28 February 2014 (UTC)
I know about this one. It's a bad idea to use it, as osm object IDs are not guaranteed to be stable.
If an OSM user converts a node to a way (this can happen when the information starts as a node and later becomes more detailed as a building contour for example), or a way to a multipolygon relation, the OSM id changes. (nodes, ways and relations use separate sequences/primary keys.
This is the reason I've started my experiments. So I'm adding wikidata tags to objects on OSM. The next step is to establish a way for people to find them from the wikimedia projects. Overpass API can function as a bridge between Wikidata and Openstreetmap, but we need to figure out how to accomplish that.
I'm watching this page, but I didn't get notified that you replied to me. Polyglot (talk) 21:57, 28 February 2014 (UTC)
@Polyglot: Could you start a discussion over at OSM that changing the IDs is a bad idea from our point of view. Maybe old IDs could become redirects to new IDs. I also sometimes correct a few things at OSM and I think it would be good to make a field for Wikidata-ID in OSM. Do you know of any plans to implement that? --Tobias1984 (talk) 10:06, 1 March 2014 (UTC)
Hi Tobias
Unfortunately changing the ids is inevitable. We try to keep them as much as possible to preserve the history of the objects, but that doesn't always works out.
Also the ids are dependent on the kind of object. Nodes, ways and relations are numbered independently, but sometimes a real world object that was represented by a node becomes a way (outline for a building), or a building outline becomes a relation (building -> multipolygon). The other case is when a building gets split. One id is preserved, for the other part of the building a new id is created. In some cases it's the new id the Wikidata entry is/was pointing to and in other cases it should start point to both the old and the new OSM object.
This is what we mean when we say OSM ids are not stable and thus not suitable for use as foreign keys in other projects.
The problem is that this behaviour can't be changed anymore. The solution for it, is Overpass API, but now we need to figure out how to implement it as a bridge between both projects, either by creating templates on all of the Wikipedias or by doing something smarter with Wikidata properties.
This is what we are doing on the Openstreetmap side:
Wikidata tags described on Openstreetmap wiki
Polyglot (talk) 11:31, 1 March 2014 (UTC)
@Polyglot: I don't understand the technical details of all of this, but if you have the Wikidata-ID and we have the OSM-ID and both places filter out and correct duplicates then everything should work fine. In addition a bot could go back and forth and update IDs. Using the Wikidata-labels would boost the translation of OSM quite a bit I would think. Access to data would open up a whole new chapter of OSM where basically maps for anything could be generated. --Tobias1984 (talk) 11:48, 1 March 2014 (UTC)
@Tobias1984: In fact it suffices to realise that OSM IDs aren't stable and never will, but I'll try to explain it once more. An OSM user has some information about a forest and maps this on a node. He doesn't have aerial imagery at that point, maybe he's working on a mobile device. A node Nxxxxx is created.
Then a desktop OSM contributor passes by and draws the contour of the forest as a closed way. He transfers the data from the node to this way. He may or may not use the initial node as part of the new way. This doesn't matter. The object referring to the forest now continues life was way Wyyyyyy. Nodes and ways are kept in separate tables with unrelated primary keys.
Now a third user comes by several years later. By now the aerial imagery has improved tremendously and government geodata has become available under a free license. This user realises the forest has clearings and is actually split by a highway. To represent this we use multipolygon relations. So the forest is now represented by Rzzzzzz and all the tags are transfered to this relation.
It's not a problem for a wikidata=Qwwwwww tag to be transfered from node to way to relation. And an Overpass query will be able to find it. So the question now is how/where do we encode this Overpass Query so it becomes convenient to use them in Wikimedia projects? In the meantime I realised I defined the query a bit too simplistic. This one always works:
[http://overpass-turbo.eu/?Q=%28%0Anode%5B%22subject%3Awikidata%22%3D%22Q336977%22%5D%5B%22historic%22%3D%22tomb%22%5D%3B%0Away%5B%22subject%3Awikidata%22%3D%22Q336977%22%5D%5B%22historic%22%3D%22tomb%22%5D%3B%3E%3B%0Arel%5B%22subject%3Awikidata%22%3D%22Q336977%22%5D%5B%22historic%22%3D%22tomb%22%5D%3B%3E%3B%0A%29%3B%0Aout%20meta%3B&C=51.1936;3.23812;18 (

node["subject:wikidata"="Q336977"]["historic"="tomb"]; way["subject:wikidata"="Q336977"]["historic"="tomb"];>; rel["subject:wikidata"="Q336977"]["historic"="tomb"];>; ); out meta;]

It would be nice if it were possible if the Q-number gets inserted automatically depending on the Wikipedia page it's called from


--Polyglot (talk) 17:17, 1 March 2014 (UTC)
Ok I understand now. I think it is still manageable. If a user for example makes a point for a lake "Lake of Constance" then a bot could find the entry in Wikidata and assign the correct Wikidata-ID and add the OSM ID to Wikidata. When somebody draws a polygone of "Lake of Constance" the bot would do the same thing. A duplicate alert would be triggered on OSM and on Wikidata we would suddenly have 2 OSM IDs in one item. Then all we need is to delete the old dataset and a bot would delete the old ID from Wikidata. I think there are people capable of programming such a bot. On Wikidata it should probably be a dedicated bot that does a daily run. @Ladsgroup: What is your opinion about this? --Tobias1984 (talk) 17:32, 1 March 2014 (UTC)
@Tobias1984:I'm afraid we don't understand each other completely yet. I understand that bots could keep things in sync. But that's not really the issue. I would like to have a way to give a person who is looking at wikipedia the possibility to click a link and they are presented with a live map where they can zoom in and out and where the object(s) in question are highlighted. Behind the link there will probably be a template, which uses wikidata to know which Q-number to use. With the solution I'm proposing it's only needed to add Q-numbers on the Openstreetmap side. Overpass API will find them for you. Please try to click the link I corrected now, then press run in the Overpass window, so you can see what I mean.
When you click on that blue little circle, you get all the properties of the object, then you can click on the blue link and see the object on the main Openstreetmap website --Polyglot (talk) 18:00, 1 March 2014 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── @Polyglot: I tried out the tool and it look and works very well. I think if this is intended for Wikipedia, it probably has to be a template or a part of the Geohack-template. I don't think we should save query-strings on Wikidata. You could of course add that functionality to the Reasonator (Universe (Q1)  View with Reasonator View with SQID) or create your own fork of that? But I think more people should give their opinions about this. There might be some really interesting queries which would be easier to retrieve if they were stored here? --Tobias1984 (talk) 18:40, 1 March 2014 (UTC)

I haven't read this discussion very carefully but obviously it's not matter of creating new property, so please move this discussion to a more general place like WD:PC. about using bot for updating it, I think I can program something like that, specially based on dumps but as I said I haven't read it yet Amir (talk) 20:43, 1 March 2014 (UTC)

@Tobias1984:I'm sorry that I don't know what are the possibilities or procedures or the best way to achieve what I'm proposing. I do think there is value in storing those query strings here on wikidata, whether as a property or otherwise, so it becomes easier to create templates for them and such that when the query needs to be improved, it can be done in one central place.
I also think there are many more queries that make sense. I'm only discovering while I'm adding some wikidata tags on OSM. The last resting place of a person was just the first I stumbled upon.
  • All streets named after a person (although it would make sense to limit it to a geographic region)
  • All garages where a given brand is sold
  • All restaurants operated by the same operator
I had a look at some templates, but I don't feel confident to try and create one that works to demonstrate the possbilities. --Polyglot (talk) 23:28, 1 March 2014 (UTC)
@Polyglot: think about what Wikidata for a place needs from OSM. We need a link to the node/way/relation for that item on OSM. Wikidata doesn't need to know which it is. OSM can tell which it is because the first letter tells OSM if it is node/way or relation. I would suggest the way to achieve this is for a bot to add a 'wikidata=Q??????' to each item on OSM with coordinates on wikidata. Another bot then needs to ad 'OSM ID:n??????' statement to wikidata and keep it up to date as OSM gets changed. I hope you can see why this is pretty crucial for wikidata. Even if OSM nodes and ways are unstable I don't see why OSM relations have to be?
For nodes on OSM that don't relate to a wikidata item OSM can still reference a wikidata Qitem but this is an OSM issue, as a consumer of wikidata.
  • To identify all streets named after Q1234546 do a query on OSM for all streets with the tag 'named after:wikidata=Q123456'. Wikidata doesn't need to get involved. :There is no reason to store this query on wikidata item Q123456.
Then there are Qitems with coordinates which relate to aspects of that Qitem - place of birth, death, burial. All these link to items and those items should have the 'OSM ID' property. On OSM I suggest you use the reasonator or similar to attach an infobox to those items to show associated info from Wikidata, such as the names of the people identified as having been buried in that place. Remember that wikidata is likely to end up with lots more people than any one wikipedia.
If you want to search for the tomb of someone then do that query on wikidata. It will have a link to the place of burial which will link to the OSM map. Lets integrate the systems so you will even be able to do that search without leaving OSM. In practice most people will do the search on Google which will seamlessly integrate the search accross it's own info and it's copy of the wikidata and the OSM info and pop up a nice map.
Does that make sense? Filceolaire (talk) 19:51, 23 March 2014 (UTC)
 Oppose this property per discussion above. Filceolaire (talk) 20:00, 23 March 2014 (UTC)
 Oppose Just use coordinates. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:37, 12 July 2014 (UTC)

 Not done No consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:14, 15 August 2015 (UTC)

Category for pictures taken with camera

Descriptionlink a camera model to the Commons category for pictures taken with that model
Data typeItem
Domaincamera models
Allowed valuesitems for Commons categories
ExampleSony Alpha 550 (Q1041905) → Category:Taken with Sony DSLR-A550
SourceCommons

Link camera to category --- Jura 08:28, 19 July 2015 (UTC)

Do these categories exist outside of Commons? As I understand it, Commons categories aren't notable items by themselves, so if this is a property that's only useful for Commons categories, it might be better for it to work more like Commons category (P373). - Nikki (talk) 12:57, 19 July 2015 (UTC)
Items would need to be created. If you use a string, you can't have the category point back to the camera. --- Jura 13:11, 19 July 2015 (UTC)
@Jura1: I think this needs more discussion. Or an example that shows why this can't be done with existing properties. Are there cameras where there is a category for pictures of and one for pictures using the specific camera? --Tobias1984 (talk) 12:42, 14 August 2015 (UTC)
Commons:Category:Sony DSLR-A550 are pictures of the camera. It's subcategory Commons:Category:Taken with Sony DSLR-A550 are "pictures using". I think there are more subcategories for pictures using a given camera at Commons:Category:Photographs by camera manufacturer than actual pictures of cameras. Obviously, everything can always be done with a string-datatype property and a simulation of features that are otherwise included in more specific properties (items, media, number, monolingual string etc). --- Jura 13:00, 14 August 2015 (UTC)
@Jura1, Nikki: The property doesn't have a lot of discussion, but now is the chance to test the approach. Please try to get at least a few dozen statements into the system so we can look at the pros and cons. --Tobias1984 (talk) 13:33, 22 August 2015 (UTC)
@Tobias1984, Nikki: ✓ Done --- Jura 16:06, 22 August 2015 (UTC)


Natural abundance

Descriptionabundance of isotopes of a chemical element as naturally found on a planet
Representsnatural abundance (Q659662)
Data typeQuantity
Template parameter"abundance" in en:Modèle:Infobox isotope
Domainnuclear isotope
Examplecarbon-12 (Q1058364) → 98.93%
Motivation

Property needed for isotope infobox. Pamputt (talk) 09:31, 3 October 2015 (UTC)

Discussion
 Comment I would prefer 0.9893 as the format of the values. Also we need a good set of qualifiers for where the isotopic ratio was measured, and with which method. Especially for light element/isotopes the fractioning is quite large between the solid, liquid and gaseous state. --Tobias1984 (talk) 10:20, 3 October 2015 (UTC)
@Pamputt: can you respond on this? Is there a standard default context for "natural abundance" (e.g. Earth's crust) that could be assumed or should this property always come with qualifiers on location? ArthurPSmith (talk) 15:00, 2 December 2015 (UTC)
Indeed, Tobias is right. However, I think this property is usually used to describe the natural abundance in the Earth's crust. One has to check how it is used in the current infoboxes. Pamputt (talk) 23:08, 2 December 2015 (UTC)
 Support without units --Almondega (talk) 12:55, 19 October 2015 (UTC)

@Pamputt: Done ArthurPSmith (talk) 21:35, 4 December 2015 (UTC)

has superpartner

Descriptionpartner particle, in supersymmetry; inverse of "superpartner of"
Representssuperpartner (Q1051902)
Data typeItem
Domainparticles
Examplegluon (Q3299)gluino (Q250974), electron (Q2225)selectron (Q1087203)

superpartner of

Descriptionpartner particle, in supersymmetry; inverse of "has superpartner"
Representssuperpartner (Q1051902)
Data typeItem
Domainparticles
Examplegluino (Q250974)gluon (Q3299), selectron (Q1087203)electron (Q2225)
Motivation

These paired relations between particles and theorized particles are well-defined, and currently absent. Swpb (talk) 19:29, 5 October 2015 (UTC)

Discussion

statement describes

Descriptiona formalization of the statement contains a bound variable in this class
Data typeItem
Domainstatement (Q2684591), conjecture (Q319141)
Allowed valuesmostly mathematical objects
ExamplePythagorean theorem (Q11518) => right triangle (Q158688), abc conjecture (Q306393) => natural number (Q21199)
Proposed byDanneks (talk)
Discussion

Notable property for theorems; could be used in substitution templates, in preambles of Wikipedia articles. Danneks (talk) 13:08, 1 October 2014 (UTC)


I want to add that I don't think this is an ideal way to organize the data about theorems, but it will be needed (at least) during the initial period to make the data more discoverable. At the moment, Wikidata knows about circa 1800 theorems and 200 conjectures, and the only search option are labels (which is not very good, because the name of a theorem usually does not describe its content). Danneks (talk) 20:22, 12 October 2014 (UTC)

 Support good compromise beetween expressivity and modelisation of the formula. TomT0m (talk) 18:55, 10 March 2015 (UTC)

  •  Support. I think this property could usefully be used for similar theorems and 'laws' outside the scope of mathematical objects. For example "Parkinson's Law:statement describes:project management"? Filceolaire (talk) 17:24, 18 June 2015 (UTC)
If there is a source which states that Parkinson's Law is something like "In most cases of project management...", then I don't see a reason why this property cannot be applied. Anyway the property's description doesn't specify a formal language etc. Danneks (talk) 01:30, 24 June 2015 (UTC)

@Danneks, Filceolaire: ✓ Done ArthurPSmith (talk) 18:59, 9 December 2015 (UTC)


MGI gene symbol

DescriptionThe official gene symbol for a mouse gene
Data typeString
DomainMouse genes
Allowed valuesA gene symbol should: normally 3-5 characters, and not more than 10 characters, use only Roman letters and Arabic numbers. Begin with an uppercase letter (not a number), followed by all lowercase letters / numbers (exceptions are possible) (For more details see ...)
ExampleProp1 (Q18253252) → "Prop1"
SourceMGI
Formatter URLhttp://www.ncbi.nlm.nih.gov/gene/?term=($1%5BSYM%5D)+AND+Mus+musculus%5BOrganism%5D
Robot and gadget jobsThe User:ProteinBoxBot is enriching Wikidata items on mouse genes.
Motivation

Currently gene symbols for mouse genes can not be covered in Wikidata. There exists a property gene symbol (P353), however this is specific for human genes. Gene symbols for the mouse genome are issued by MGI. I would like to propose a Wikidata property called MGI gene symbol, to be able to store gene symbols issues by MGI on a Wikidata item on mouse genes. Andrawaag (talk) 21:26, 20 October 2015 (UTC)

 Support This is quite important to help in distinguishing between human and mouse genes and proteins while preserving common nomenclature. But perhaps make the formatter URL point to MGI http://www.informatics.jax.org/marker/summary?nomen=($1%5BSYM%5D) ? --I9606 (talk)

@I9606: I have considered the MGI as source for the formatter URL. However, that URL points to a landing page, which can contain multiple entries. It is not an exact match, nor is it limited to the symbol only. (e.g. TP53. The link provided by the ncbi does exact matches and limits to symbol only. Of course a link to http://www.informatics.jax.org with an exact match on symbol would be preferable. Andrawaag (talk) 22:30, 20 October 2015 (UTC)

 Support Very important to make the distinction between mouse and human gene symbols Putmantime (talk) 22:19, 20 October 2015 (UTC)

 Support Seems to be required to link out to the appropriate gene entry in jax.org, Also prevents mixing of mouse and human gene symbol data in the same property. Sebotic (talk) 20:54, 21 October 2015 (UTC)

  •  Support. I am assuming the geneticists will sort out a unified system for identifying genes before we get hundreds of species on here. In the meantime this seems to be the least worst option. Joe Filceolaire (talk) 00:12, 4 November 2015 (UTC)

WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

✓ Done - @Andrawaag: ArthurPSmith (talk) 19:51, 11 December 2015 (UTC)

NCBI Locus tag

   Done: NCBI locus tag (P2393) (Talk and documentation)
Descriptionunique gene identifier that can be used for any species of organism
Data typeString
Domaingenes
Allowed valuessingle value string
Exampletryptophan synthase subunit beta CT_170 (Q21279562) → "CT_170"
SourceNational Center for Biotechnology Information (NCBI)
Formatter URLhttp://www.ncbi.nlm.nih.gov/gene/?term=$1
Robot and gadget jobsUser:ProteinBoxBot and the proposed Microbot will include this on all gene items.
Motivation

While gene symbol is a unique identifier for human genes, this is not the case for other species, especially microbes. NCBI issues a unique locus tag prefix for every genome assembly submitted, systematically applying a unique identifier to each gene in the genome, independent of it function or pathway involvement. Locus prefixes are at least three characters, the first required to be a letter and no special characters, followed by an underscore (i.e. A2C_00001, A2C_00002, etc...). This will provide a unique identifier for genes that can be used in any species of organism. Putmantime (talk) 23:23, 11 November 2015 (UTC)

 Support--I9606 (talk) 23
10, 16 November 2015 (UTC)

 Support Important and useful identifier from the NCBI universe Sebotic (talk) 05:56, 17 November 2015 (UTC)

WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Discussion
Considering this was proposed on November 11th, and has nothing but support, could we move forward with its creation? It is needed in my data model. Thanks Putmantime (talk) 22:51, 3 December 2015 (UTC)

✓ Done - @Putmantime: ArthurPSmith (talk) 19:42, 11 December 2015 (UTC)


has substituent

   Not done
Descriptionnotable substituents of a molecule
Representssubstituent group (Q898422)
Data typeItem
Template parameter(none that i know of)
Domainchemical substance (Q79529)
Allowed valueschemical substance (Q79529)
Example
Sourcewikipedia categories and lists about substituted substances, ChemSpider (?)
Robot and gadget jobsgathering data, checking consistency based on SMILES (?)
Motivation

i think this property would help alot with organizing substances according to their structure, it's also more precise than the potentially misleading has part(s) (P527). -- 85.239.100.58 10:01, 15 October 2015 (UTC)

Saehrimnir
Leyo
Snipre
Dcirovic
Walkerma
Egon Willighagen
Denise Slenter
Daniel Mietchen
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Benjaminabel
99of9
Kubaello
Fractaler
Sebotic
Netha
Hugo
Samuel Clark
Tris T7
Leiem
Christianhauck
SCIdude
Binter
Photocyte
Robert Giessmann
Cord Wiljes
Adriano Rutz
Jonathan Bisson
GrndStt
Ameisenigel
Charles Tapley Hoyt
ChemHobby
Peter Murray-Rust
Erfurth
TiagoLubiana
NadirSH
Matthias M.
S8321414

Notified participants of WikiProject Chemistry

Discussion
  •  Oppose unless a much more specific definition of "substituent" is used.--Jasper Deng (talk) 16:40, 15 October 2015 (UTC)
  •  Comment I would better use functional group. But the problem is not the term but the list of substituents or functional group. here we need a better system than just wp categories. Snipre (talk) 17:13, 15 October 2015 (UTC)
    • what i (i wrote it at school, therefore anonymous) had in mind is this: any molecule that has a wikidata entry, that can be seen as a part of the molecule in question when ignoring hydrogen atoms. also, since this is a transitive property, substituents of substituents should probably not be listed. so, Q7250331 would list acetic acid (Q47512) and propane (Q131189) but not ethane (Q52858) or formic acid (Q161233). i'm not a chemist, maybe there is a better term or approach for this. -- opensofias (talk) 17:50, 15 October 2015 (UTC)
      • With that definition you will never have the support of the chemists. Better have a look at en:Functional group or the different systems used in the group contribution approach. Snipre (talk) 18:11, 15 October 2015 (UTC)
        • i'm sorry, for answering very late. i feel like functional group wouldn't describe the relation i mean, as it seems to refer to things that are radicals and connect at a specific point. however the relation seems to be of relevance in much of chemistry, usually in phrases like "is a (substituted) tryptamine", "has a purine structure/group" etc. perhaps it could be called "has molecular group", "has subgroup" or perhaps "substituted from"? --opensofias (talk) 17:52, 3 November 2015 (UTC)
          • If I understand what you mean I will say that you speak about chemical families but this is not a well defined property. Again the only good way to split a molecule into parts is the functional groups and to work on the groups definition to see if we can create groups with the size of the serotonin. Snipre (talk) 12:51, 4 November 2015 (UTC)
  •  Oppose per Jasper Deng. --Leyo 10:27, 4 November 2015 (UTC)
  •  Oppose Without any more information about this proposal I reject this proposal. Snipre (talk) 10:35, 5 December 2015 (UTC)

 Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:02, 5 December 2015 (UTC)


image of a function

Descriptionthe set of values that a function actually has
Representsrange of a function (Q1806121)
Data typeItem
Domaininstances of mapping (Q370502), function (Q11348), morphism (Q1948412), binary relation (Q130901)
Allowed valuesinstances of set (Q36161), class (Q217594)
Examplesquare function (Q3075175)non-negative real number (Q18729403)
Proposed byPetr Matas
Discussion

A function must produce all values specified by this property, but it does not need to produce all values specified by codomain (P1571). Therefore the former provides more information, whereas the latter is simpler. Petr Matas 15:05, 8 January 2015 (UTC)

Opensofias
Tobias1984
Arthur Rubin
Cuvwb
TomT0m
Physikerwelt
Lymantria
Bigbossfarin
Infovarius
Helder
PhilMINT
Malore
Lore.mazza51
Wikisaurus
The Anome
The-erinaceous-one
Daniel Mietchen
Haansn08
Xenmorpha
John Samuel
Jeremy Dover
Toni 001
Bocardodarapti
Duckmather
HTinC23
fgnievinski
Paul-Olivier Dehaye
uni
Dexxor
慈居

Notified participants of WikiProject Mathematics

 Support --Tobias1984 (talk) 15:19, 8 January 2015 (UTC)
@Petr Matas: Can you still create the target-item in the example. We could put a list of number-sets on the property talk-page and make a "one-of" constraint for that list. --Tobias1984 (talk) 15:19, 8 January 2015 (UTC)
I could not find the right item, probably we will have to create it. We should also discuss, whether item is the right data type for this property and for definition domain (P1568). Petr Matas 15:35, 8 January 2015 (UTC)
@Petr Matas: Items seems right to me. It makes translation easier in this case and I think that number-sets could hold statements of their own. In the case of non-negative real numbers could have statments like: smallest value = 0, largest value = infinity, ... - I also don't think that there is an item for "non-negative real numbers". If we ever find one in minor language, we can just merge the items. --Tobias1984 (talk) 16:14, 8 January 2015 (UTC)
Ok, non-negative real number (Q18729403) created. Petr Matas 17:10, 8 January 2015 (UTC)
@Tobias1984, Petr Matas: count nonzero real number (Q19546578)  View with Reasonator View with SQID in :) TomT0m (talk) 18:40, 10 March 2015 (UTC)
 Support. TomT0m (talk) 18:40, 10 March 2015 (UTC)
@Petr Matas: The value of the sudgested property depend on definitional domain (definition domain (P1568)), e.g. square function (Q3075175) of a complex number is a complex number. How to handle with such cases? -- Sergey kudryavtsev (talk) 10:32, 24 April 2015 (UTC)
May be better use definition domain (P1568) as qualifier? -- Sergey kudryavtsev (talk) 10:39, 24 April 2015 (UTC)
@Sergey kudryavtsev: I say we can totally have several items linked somehow, as functions with different domains are mathematically speaking different function. We could have
⟨ complex number square function ⟩ generalization of (P7719) View with SQID ⟨ real number square function ⟩
, maybe with
⟨ complex number square function ⟩ instance of (P31) View with SQID ⟨ function that computes a square ⟩
and
⟨ real number square function ⟩ instance of (P31) View with SQID ⟨ function that computes a square ⟩
. TomT0m (talk) 10:47, 24 April 2015 (UTC)
Therefore you gets a incorrect (ambiguous item) example for this property. If square function (Q3075175) means "square function of a real number", we should rename it correctly, even if in English.
However my suggestion of definition domain (P1568) as qualifier looks reasonable and make it possible to handle with both ambiguous and definitely defined items. Even mathematical statement f(x): R → R shows a function domain and image together. -- Sergey kudryavtsev (talk) 12:13, 24 April 2015 (UTC)
I don't know, this seems later harder to use the item in a statement, requires also a qualifier, a default value ... On the other hand making two items is easy and makes the use of the items non ambiguous. Labels in Wikidata can be the same, it's the description that is used to disambiguate, so there is no problem of keeping the square function label for the function on real numbers. Creating a class item of function that have the usual properties of a square function also makes sense conceptually, it could be associated with those properties that makes us say this function is a square function, for example. This is way more advanced stuff than students could encounter when they first hear of the square function, and usually the Wikipedia article about square function is about the function on real numbers. So it is a model that leaves the room for several articles on Wikipedias that are for different kind of readers. TomT0m (talk) 13:19, 24 April 2015 (UTC)
Wikipedia usually discusses the real function in the first place, so the article should be linked to the real function item, which will be used to populate the main infobox. The complex function is usually only discussed in a section of the same article, and a second infobox linked to the complex function item can be added to that section. Therefore the class item is not going to be used by Wikipedias and the domain/codomain/input set/image statements can be left out from it. Petr Matas 12:11, 25 April 2015 (UTC)
 Comment There are four sets related to function input and output. Properties for three of them have already been created and this proposal is for the last one missing:
input set (P1851) real number (Q12916) codomain (P1571) real number (Q12916)
definition domain (P1568) nonzero real number (Q19546578) image of a function positive real number (Q3176558)
Petr Matas 14:02, 26 April 2015 (UTC)
✓ Done @Petr Matas, Tobias1984, TomT0m: this seemed to be generally well supported. I removed the articles from the English names. ArthurPSmith (talk) 20:19, 11 December 2015 (UTC)


MLSSoccer.com ID

   Done: MLS player ID (P2398) (Talk and documentation)
DescriptionIdentifier for a soccer player profile on MLSSoccer.com. MLSSoccer.com is the official Website of Major League Soccer. There is a profile with most up-to-date data for each soccer player playing or having ever played in the MLS. It is usually linked from the Wikipedia player profile.
RepresentsJack McInerney (Q3805624)
Data typeString
Domaindie Art von Objekten, die diese Eigenschaft haben können
Allowed values[-a-z]+[0-9]*
ExampleWorldFootball.net person ID (P2020) is very similar. // Jack McInerney (Q3805624)jack-mcinerney
SourceMLSSoccer.com
Formatter URLhttp://www.mlssoccer.com/players/$1
Motivation

The identificator can be used in various Wikipedia articles of MLS players. Escpecially, it would be a help for creating new articles and check correctness of the linked MLSSoccer.com profiles. Yellowcard (talk) 15:02, 16 September 2015 (UTC)

Discussion

Where is the struggle that this property has not been created yet? Anything that has to be made clear? Yellowcard (talk) 15:13, 5 October 2015 (UTC)

British Council artist ID

DescriptionIdentifier for an artist, in the catalogue of the British Council
Data typeString
Domainartists
ExampleF Gregory Brown (Q18389785)brown-f-gregory-1887
Sourcehttp://visualarts.britishcouncil.org/collection
Formatter URLhttp://visualarts.britishcouncil.org/collection/artists/$1
Robot and gadget jobsMix'n'Match ?
Motivation

The British Council has a collection of more than 8,500 artworks by modern British artists, displayed in over 100 countries. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:11, 26 October 2015 (UTC)

Discussion

Elonet ID for an actor

Template parameterWikipedia infobox parameters, "Elonet" parameter in the actor template

Elonet is a web version of The Finnish National Filmography. Useful. Elonet movie ID (P2346) was already created. --Stryn (talk) 19:08, 24 November 2015 (UTC)

Discussion

@Stryn, Filceolaire: ✓ Done Elonet person ID (P2387) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:36, 11 December 2015 (UTC)

Six Degrees of Francis Bacon ID

DescriptionIdentifier in the Six Degrees of Francis Bacon database
Data typeString
DomainPeople
Allowed values8-digit number
ExampleJan Łaski (Q339351)10000001
Formatter URLhttp://sixdegreesoffrancisbacon.com/people/$1
Robot and gadget jobsCurrently in mix-and-match (~3000 identified)
Motivation

A major scholarly database studying the social networks (eg correspondence, acquaintance, patronage) between ~15,000 figures of the sixteenth, seventeenth, and eighteenth century. This is data we do not currently capture in Wikidata very well and the two databases could complement each other wonderfully. This would be a very useful complement to Oxford Dictionary of National Biography ID (P1415) (the seed for 6Degrees was the ODNB) and to Early Modern Letters Online person ID (P1802), among others. Andrew Gray (talk) 19:26, 24 November 2015 (UTC)

Discussion

French Sculpture Census ID

DescriptionIdentifier in the French Sculpture Census (English)
Data typeString
DomainPeople
ExampleNicolas-Sébastien Adam (Q2403645)adam-the-younger-nicolas-sebastien-called
Formatter URLhttp://frenchsculpture.org/en/artist/$1
Robot and gadget jobsCurrently in mix-and-match (~650 of 700 identified)
Motivation

Small but detailed database of French sculptors, including biographical summaries and - unusually - copyright statements. The matching done so far uses the English text; there is a parallel French text with a distinct URL (compare [1] and [2]. This would probably need a seperate identifier. Andrew Gray (talk) 19:44, 24 November 2015 (UTC)

Discussion

@Andrew Gray, Filceolaire, Ayack, Runner1928, Jane023: ✓ Done --Kolja21 (talk) 20:45, 8 December 2015 (UTC)

Academic Tree ID

DescriptionIdentifier for a person in the Academic Tree database
RepresentsThe Academic Family Tree (Q21585670)
Data typeString
Template parametermultiple for scientists & scholars: doctoral_advisor, academic_advisors, doctoral_students, notable_students
Domainperson
Allowed valuesnumeric value
ExampleJohn Keith Moffat (Q21575049)72187
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
SourceThe Academic Family Tree
Formatter URLhttp://academictree.org/chemistry/peopleinfo.php?pid=$1
Robot and gadget jobsBots should be tasked matching Wikipedia bios to academictree.org and creating authority control parameters to the Academic Tree profile, as well as populating infobox parameters (or the equivalent Wikidata parameters) from and to academictree.org. If there is a missing URL or bio on academictree.org, the Wikipedia URL can be linked in either field (as seems currently the practice sometimes).
Motivation

Academictree.org, which is creative commons licensed, seems useful as both an authority control profile/bio and for populating missing infobox parameters related to doctoral advisor, academic advisors, doctoral students, notable students. It should be possible to do this automatically, although the exact rule is complicated as multiple different infobox parameters need to be pulled from academictree.org and vice-versa. (Academictree keeps track of whether someone is a doctoral student/advisor or some other kind of academic advisor/student, so the correct infobox parameter should be inferable, but it is not always a 1:1 relationship. It should be possible to pull from academictree.org into wikipedia infobox since that is always many:1, but the reverse, transferring from Wikipedia infobox to academictree.org may be harder. The names in Wikipedia do not always correspond to the exact names in academictree.org, hence is useful to do this as an authority control parameter.

John Keith Moffat entry, which appears as Keith Moffat on academictree.org which is matches the Library of Congress authority control name, although some long recent bios by e.g., Edinburgh University use "John Moffat" instead; both John Moffat and Keith Moffat are ambiguous with other similarly-named bios appearing in Wikipedia. Then finding the academictree.org profile for Prof. Moffat providing information on both his notable postdoc advisor --- not mentioned in most of his other bios --- who already had both a Wikipedia bio and unlinked academictree entry to his own notable students not listed already listed in Wikipedia/Wikidata. Finally, the academictree.org database says it is under Creative Commons license. Thus, it would seem useful to link and cross-populate the relevant Wikidata fields against the academictree fields to resolve name ambiguities (authority control) as well as providing missing data/links between existing Wikipedia/Wikidata bios G8239823 (talk) 21:28, 27 November 2015 (UTC)

Discussion

@G8239823, Pigsonthewing, Kolja21, Runner1928: ✓ Done. — Ayack (talk) 12:34, 9 December 2015 (UTC)

  •  Comment There seems to be a problem with the validation filter for non-chemistry entries. So the URL I gave for the filter above works correctly for non-chemistry folks. Consider the following mathematician: http://academictree.org/chemistry/peopleinfo.php?pid=66786 . If you set the AcademicTreeId to 66786 (as I did, see https://www.wikidata.org/wiki/Q57554) no link appears in Wikidata. However, if you actually go to the URL in the filter above, http://academictree.org/chemistry/peopleinfo.php?pid=66786 redirects to http://academictree.org/math/peopleinfo.php?pid=66786 . If you try to do this for someone in the ChemistryTree, then there is no problem. So I think the Wikidata filter is thrown off by the redirect it is getting back from AcademicTree for non-chemistry folks. You could have two properties to specify both the tree and the ID, but this seems unnecessary since the ID also specifies the tree. The Tree could be auto populated into wikidata to avoid the redirect, although this seems overkill. I suggest instead the filter be modified to be aware of the redirect issue. Thanks for implementing this; I think this will be incredibly cool, and helpful for well-known historical PhDs still lacking ISNI or other good authority control.

@Ayack, Pigsonthewing, Kolja21, Runner1928: See issue in comment above. G8239823 (talk) 05:34, 11 December 2015 (UTC)

A general URL (without "chemistry", "math" etc.) would be better but AFAIK Wikidata should work with all numeric values. I have no idea why some items are showing the links and other not. This might be a case for the Wikidata:Administrators' noticeboard. (BTW: The tree a person is listed in can be switched. Only the ids are stable.) --Kolja21 (talk) 07:20, 11 December 2015 (UTC)
Example: Robin Lovell-Badge (Q20706796) is part of the GenetiTree. Nevertheless the chemistry URL works. --Kolja21 (talk) 07:29, 11 December 2015 (UTC)

Chemins de mémoire ID

Descriptionidentifier of a place on www.cheminsdememoire.gouv.fr
Data typeString
Domainplace
ExampleKemmelberg Ossuary (Q2073286)le-mont-kemmel
Sourcehttp://www.cheminsdememoire.gouv.fr
Formatter URLhttp://www.cheminsdememoire.gouv.fr/fr/$1
Robot and gadget jobsalready on mix'n'match ([3])
Motivation

Website by the French Ministry of Defence which presents information about more than 700 "places of memory" — Ayack (talk) 20:29, 28 November 2015 (UTC)

Discussion

@Runner1928: ✓ Done. — Ayack (talk) 12:46, 9 December 2015 (UTC)

French diocesan architects ID

Domainperson
Robot and gadget jobsmix'n'match
Motivation

Interesting database of French diocesan architects which is already on mix'n'match. — Ayack (talk) 11:16, 1 December 2015 (UTC)

Discussion

@Ayack, Runner1928, Magnus_Manske: ✓ Done French diocesan architects ID (P2385). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:38, 11 December 2015 (UTC)

CTHS person ID

   Done: CTHS person ID (P2383) (Talk and documentation)
Descriptionidentifier for a person in the directory of French learned societies
RepresentsComité des travaux historiques et scientifiques (Q2985434)
Data typeString
Domainperson
ExampleCharles Maurras (Q3048)101743
Sourcehttp://cths.fr/an/selec.php?sc=pr
Formatter URLhttp://cths.fr/an/prosopo.php?id=$1
Robot and gadget jobsmix'n'match
Motivation

Directory of members of French learned societies (scientists, writers, etc.) since the 17th century. It has more than 20.000 entries. — Ayack (talk) 11:17, 2 December 2015 (UTC)

Discussion

@Multichill: ✓ Done. — Ayack (talk) 12:53, 9 December 2015 (UTC)


h-node entry

   Not done
DescriptionLinks to the relevant entry on the h-node hardware database
Data typeString
Domainhardware, vendors, architectures, individual products
ExampleAcer (Q481778)notebooks/catalogue/en/1/1/Acer/
Sourcehttps://www.h-node.org/
Formatter URLhttps://h-node.org/$1
Motivation

This would be useful to check how free software friendly the hardware model/vendor/architecture is. Pikolas (talk) 11:52, 23 June 2015 (UTC)

Discussion
I am not sure about this. 2 issues come to mind: 1st: Is it guaranteed that the h-node.org URLs will be stable and reliable? This needs to be the case. 2nd: This property would conflate vendors, compabilities, hardware classes and concrete hardware models, possilby much more. This does not sound good for a database. --Wiki-Wuzzy (talk) 13:38, 28 June 2015 (UTC)
@Pikolas: Your example and formatter URL do not match, Which value would you have us store? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:15, 7 July 2015 (UTC)
@Pigsonthewing: Thanks, corrected. Pikolas (talk) 12:04, 7 July 2015 (UTC)
Thank you. However, it now seems that the content returned by, for example, https://h-node.org/notebooks/catalogue/en/1/1/Acer/ and https://h-node.org/notebooks/catalogue/en/1/1/Dell/ is identical. I therefore see little purpose in using such an identifier. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:47, 7 July 2015 (UTC)
No response, so  Oppose. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:37, 20 November 2015 (UTC)
Marked as Not Done: Don't see any support, I see a mix of brands on the page which is the result of the link, so not really useful. Mbch331 (talk) 19:16, 3 December 2015 (UTC)

Film format

   Not done
Description...
Data typeItem
Template parameterfilmformat in w:Template:Infobox_camera, etc.
Domaincameras, films
Allowed valuesitems for specific formats
ExampleUniverse (Q1)Earth (Q2)
Sourceinfobox
Motivation
Can you give an example? I'm not sure where you would use this. Most movies have been recorded on multiple film formats. Joe Filceolaire (talk) 18:10, 31 August 2015 (UTC)
Discussion

MediaWiki hooks used

DescriptionMediaWiki hooks used by this extension
RepresentsMediaWiki hook (Q21674818)
Data typeItem
Template parametermw:Template:Extension#hook
Domaininstanceof MediaWiki extension (Q6805426)
Allowed valuesinstanceof MediaWiki hook (Q21674818)
ExampleMassMessage (Q21651675)ParserFirstCallInit (Q21675537)
SourceMediaWiki git repositories
Robot and gadget jobsLegobot is going to add this
Motivation

This is part of importing mw:Template:Extension into Wikidata. I'm going to create this property now as to facilitate quick usage of the data. Legoktm (talk) 03:18, 7 December 2015 (UTC)

Discussion

✓ Done MediaWiki hooks used (P2377) Legoktm (talk) 03:20, 7 December 2015 (UTC)

deprecated in version

DescriptionSoftware version it was deprecated in
Data typeItem
Template parameterdeprecated parameter of mw:Template:MediaWikiHook
DomainAny software feature
Allowed valuesAny item relating to a software version
ExampleAPIGetDescription (Q21675074)MediaWiki 1.25 (Q21683649)
Sourceexternal reference
Robot and gadget jobsLegobot will add it.
Motivation

I'm going to create this immediately to facilitate the import of mediawiki.org data. Legoktm (talk) 01:28, 8 December 2015 (UTC)

Discussion

✓ Done deprecated in version (P2379) Legoktm (talk) 01:38, 8 December 2015 (UTC)


substrate of

   Done: substrate of (P2414) (Talk and documentation)
Descriptionthe substrate that an enzyme acts upon to create a product
Data typeItem
Domainmolecules
Allowed valuesWikidata item(s)
Example1H-indole (Q319541)tryptophan synthase (Q21397124)
SourcePrimary literature PubMed (Q180686), UniProt (Q905695), BRENDA (Q569357), etc...
Motivation

There are currently no means of linking enzymes to the substrates they act upon. This would provide that useful link. Putmantime (talk) 23:39, 11 November 2015 (UTC)

This is needed, but want input from chemistry people to make there is no overlap with what they are doing WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --I9606 (talk) 23:13, 16 November 2015 (UTC)

Discussion
Notified participants of WikiProject Chemistry
✓ Done --Tobias1984 (talk) 16:46, 21 December 2015 (UTC)

personal best

   Done: personal best (P2415) (Talk and documentation)
Descriptionan individual's best performance in a given discipline
Representspersonal record (Q21142177)
Data typeNumber (not available yet)
Template parameter"pb" in en:template:infobox sportsperson
Domainperson
Allowed valuestimes or distances (up to two decimal places)
ExampleUsain Bolt (Q1189)field of work (P101)100 metres (Q164761) → personal best = 9.58 seconds
Format and edit filter validationnumber
Sourceexternal reference (e.g. IAAF website) or Wikipedia infobox
Robot and gadget jobsPotential to have bot tasks to fetch external data from certain sports body websites
See alsorecord held (P1000)
Motivation

The addition of this property will allow the inclusion of one of the key statistics of a person involved in sports such as athletics, cycling, swimming, weightlifting, etc. This information is almost always documented in Wikipedia articles for the person. Unifying it through WikiData is highly desirable as this piece of data does not need qualification and works across languages. Ide'ally this property should be able to be qualified by the corresponding sport/event, point in time, and location. This is my first time proposing so any advice on how best to technically achieve that would be much appreciated.

Looking to the future, as a personal best is the base unit for sport records, queries on the data could establish higher level records (world, continental, etc.) through this property and produce rankings. Sillyfolkboy (talk) 18:05, 18 October 2015 (UTC)

Discussion
⟨ Usain Bolt (Q1189)  View with Reasonator View with SQID ⟩ personal best Search ⟨  9.58 seconds ⟩
sport (P641) View with SQID ⟨ running (Q105674)  View with Reasonator View with SQID ⟩
position played on team / speciality (P413) View with SQID ⟨ 100 metres (Q164761)  View with Reasonator View with SQID ⟩
point in time (P585) View with SQID ⟨ 2009 August 16 ⟩
location (P276) View with SQID ⟨ Berlin (Q64)  View with Reasonator View with SQID ⟩
I disagree with this modelling.
⟨ competes in sport / discipline ⟩ 100 meters Search ⟨ personal best ⟩
9.58 seconds Search ⟨ {{{5}}} ⟩
seems way better. A rule of thumb : the "main snak"
⟨ competes in sport / discipline ⟩ 100 meters Search ⟨ object or value ⟩
or
⟨ Usain Bolt (Q1189)  View with Reasonator View with SQID ⟩ personal best Search ⟨  9.58 seconds ⟩
should be meaningful by itself. Which is the case when "competes in sport" is the main property, but not for "personal best" which is useless without qualifiers. author  TomT0m / talk page 10:30, 15 November 2015 (UTC)
 Support Either way, I support creation of this property; how it gets used can be developed by those actually applying it. Josh Baumgartner (talk) 20:45, 22 October 2015 (UTC)
@Joshbaumgartner: I agree that there are benefits to separating "personal best" from "field of work" at the top level. This allows us to separately document a speciality and keep data on personal bests more broadly in non-specialities. Decathletes for example shouldn't have all ten events as their speciality, but rather decathlon as their speciality, and their bests for each event separately.
I'm not sure if the "position played" property is a better choice for specific variations of a discipline – the idea of competing in an event is quite different from a specialised team position. The former is much more changeable. Certainly, in terms of the track and field example I feel that "position played on team / speciality" would be better characterised as "sprinter" in this case, rather than a specific sprint event (e.g. 100 metres). Do you know of any other better options than the more generalised "field of work" one? Sillyfolkboy (talk) 17:26, 25 October 2015 (UTC)
@Sillyfolkboy: I do not know another property off hand. Field of work (with which we can say that a scientist works in the field of nuclear physics) certainly seems more of a stretch than position played (where the only question is whether it should be limited to position within a team or not, but at least it is clearly sport-focused). Personally, I see no reason why position played on team / speciality (P413) should be limited to team sports, and would be happy with correcting its description accordingly. Josh Baumgartner (talk) 19:19, 26 October 2015 (UTC)
@Joshbaumgartner: I think the high level idea for this property gets really problematic for runners, cyclists, swimmers and gymnasts, as their speciality covers a range of events. It would seem counter intuitive to have many events listed as a specialism. It works fine for sports where athletes are limited in their abilities to fulfil a role (e.g. very rarely is a ski jumper also a skier, or a goalkeeper also a forward). Maybe "participant of" (P1344) is a better fit for listing various non-speciality sporting events? Sillyfolkboy (talk) 20:09, 26 October 2015 (UTC)

Sports disciplines competed in

Description... Disciplines or events an athlete competes in within a sport
Data typeItem
DomainPerson
ExampleHaile Gebrselassie (Q171500)sport (P641)/field of work (P101)/position played on team / speciality (P413) → Sports disciplines competed in → marathon (Q40244), 5000 metres (Q240500), 10,000 metres (Q163892), half marathon (Q215677)
Motivation

Following on from the above request on personal bests, I believe there is a desire to have a property on the specific sports discipline or events that athletes take part in. Josh Baumgartner above recommended position played on team / speciality (P413) to indicate this, but I think there is a difference here. For a number of sports, the competitor will compete in a variety of distinct events. P413 deals with a specialism, which correlates relatively well to sports where people specialise (e.g. football defender, quarterback, shot putter).

However it works poorly for people where it would be useful to list the many events they compete in, e.g. Haile Gebrselassie (Q171500), Bradley Wiggins (Q193876), Simone Biles (Q7520267). The specialism of P143 is better defined as the higher-level occupation (distance runner, cyclist, artistic gymnast). The more general field of work (P101) and sport (P641) work better at the higher level too, as events within a sport aren't really sports themselves. Effectively this property would allow us to specify, for example that Haile Gebrselassie competes in the sport of athletics (P641), in which he specialises as a long-distance runner (P413), and competes in the events of A, B and C (this new property). Sillyfolkboy (talk) 23:03, 2 November 2015 (UTC)

Discussion
  •  Support but the datatype should be item I think. Thryduulf (talk: local | en.wp | en.wikt) 22:08, 3 November 2015 (UTC)
  •  Support a needed clarification. Antrocent (talk) 15:12, 4 November 2015 (UTC)
  •  Question do we good definitions of what is a sport and what is a discipline ? author  TomT0m / talk page 17:41, 8 November 2015 (UTC)
    • @TomT0m: I think it's any event that a sportsperson can enter in a tournament that represents just one aspect of a sport (i.e. not the sport itself). So yes for gymnastics rings, mixed doubles tennis, and 400 metres. No to gymnastics, tennis or sprinting. On a related note, weight-classes and sailboat-classes could be defined as special instances of the sports disciplines concept. Sillyfolkboy (talk) 22:09, 13 November 2015 (UTC)
      • @Sillyfolkboy: That does not answer on the definition of a "sport", this is just examples :) If I quote the frwiki definition of "sport" : "Le sport est un ensemble d'exercices physiques se pratiquant sous forme de jeux individuels ou collectifs pouvant donner lieu à des compétitions." => "Sport is a set of physical exercises that are played as individual or collective games and that can occur as competitions". Then "400 metres" is one of that exercises, and "athletics" is just a subclass of sport. author  TomT0m / talk page 11:36, 14 November 2015 (UTC)
        • @TomT0m: One could take the sports governing body approach, in that the sport is the whole thing organised by that body, while the athletes specialise in the disciplines/events within that sport (the Olympics makes this same distinction). The events are aspects of the same sport, not distinct sports in themselves. By comparison, while 100 metres and 200 metres are aspects of track and field (thus events, not sports), skiing and football are not aspects of the same sport (thus not events but sports). Sillyfolkboy (talk) 15:01, 14 November 2015 (UTC)
          • @Sillyfolkboy: Good point. But I think we should be consistent and take into account the token/type distinction as a foundation for Wikidata's ontology, see Help:Classification for an introduction, and use Olympics definitions as one of the alternative and use their item as "Olymic sport" and "Olympic disciple" (as metaclasses probably). There is always events involved anyway in a sport, there is no sport without people playing it at one time or another, informally or in competition :) author  TomT0m / talk page 15:09, 14 November 2015 (UTC)
            • @TomT0m: This concept is common in other sports ontologies (e.g. BBC's sport:subDiscipline). I believe the sub-sport idea needs to be free from competition hierarchy, chiefly to reflect general definitions on biographies. Not doing so effectively means that for sportspeople we would remove a connection with the sport under which they are commonly defined, in favour of the subdiscipline they compete in. This is unhelpful both in team sports, where the "sport" would, for example, become "11-a-side football", rather than the parent "association football", and also for sports with classes, "light welterweight" instead of "boxing". Alternatively, if we continue to list the main sport with the events as the person's "sport" then we have a conceptual hierarchy within that group which is not reflected data-wise on that item. The lack of an adequate property is the reason why sportspeople's events, classes, and subdivisions are largely absent from Wikidata, even though they are commonplace in biographical infoboxes of many sports. Sillyfolkboy (talk) 19:34, 14 November 2015 (UTC)
              • @Sillyfolkboy: That make sense, BUT : I think Wikidata should be confortable dealing with alternative ontologies to be able to represent different POV and deal with cultural differences. The solution I propose is totally compatible with your approach. It's just a minor disagreement in definitions that is actually dealable with the "metaclass" concept alone and a few competing but coexisting peacefully properties if really needed. Let's try to classify sport game using the principles used in Help:Classification
                The "tokens" or "instances" are games or actual competition, like 1998 FIFA World Cup Final (Q585295). Some are formalized using a set of rules governing the kind of people allowed to play or how to score, who is the winner, what are the components of the game ... . Let's take the class of all game that follows the same rules than 1998 FIFA World Cup Final (Q585295). It's association football match (Q16466010). It's a subclass of "sport game", as all instances of association football games are also sport game. We can imho assimilate all the classes of this kind to what you call a "discipline", or sometime a "sport". We can model this by a "metaclass" called (in english) "sport discipline", or whatever each locutors of each language wants, what's important is how we define it : a class of games following the same rule. What's define a discipline item is then clearly the rules of the game. Let's take another class of games : boxing games. It's also obviously a subclass of "sport game", as all instances of boxing games are also sport game. But there is "classes" of players, and the rule furthers refine the classification of the games with properties of the players, heavy one are not allowed to compete with finer ones, males and female can't compete together in the same game. There is then several subclasses of "boxing game" like "female boxing game" as one of them. For athletics : this is a sport that regroups games of very different kind. We can class the game by "100 meters", "marathons". They both are subclasses of "running games". For some historical reasons or whatever other, running games are classified as "athletic games" together with "pole vault" and others. I'd say "athletic games" is an instance of what you call a "sport" : it's a metaclass as it's an instance of a class of games. By putting an "instance of" : "Olympic sport" to the "athletics game" item and all the item of the like ("association football", ...) we can reflect pretty easily different classifications of game like the one you are suggesting, or other classifications based on practical federations organizations, or more "theorical" ones. Those "metaclasses" can be used to define more or less precise properties. author  TomT0m / talk page 11:09, 15 November 2015 (UTC)
                • @TomT0m: Am I reading it right that your alternative to having this property is to have all the sports disciplines listed as sports on a biography, with each discipline being a sub-class of the parent sport on its own item? I think the "Olympic sport" idea is a distraction because 99.9% of a sub-discipline's existence is non-Olympic in nature. For example, if we are listing Usain Bolt's personal best in the sub-sportsdiscipline of 100 metres, then it should have no relation to the Olympics at all because there is no real world connection between that performance and the Olympics (it was set at the World Championships). Sillyfolkboy (talk) 15:03, 15 November 2015 (UTC)
                  • @Sillyfolkboy: That would work indeed. As 100 meters or 200 meters are subclasses of athletics, we know he is an athlete, so "Sport: athletism" would be nothing but redundant. The "Olympic sport" was just an illustration of the flexibility of such an approach. author  TomT0m / talk page 15:36, 15 November 2015 (UTC)
  •  Support. I think we need this a lot so we can distinguish, for instance, between 'tennis' and 'mixed doubles tennis'. This is a flexible approach that allows us to reflect different definitions, and not beeing ambiguous about what we mean. author  TomT0m / talk page 15:09, 14 November 2015 (UTC)
  •  Support There is going to be a lot of hashing over what constitutes a 'sport' and what is merely a 'discipline' and I know that the label, description, etc. will be sorted out as we go through this, but I the basis is sound, so let's get the property in place and exactly how it is used can be developed as a result. Josh Baumgartner (talk) 21:12, 13 November 2015 (UTC)
  •  Support} in accordance with the extensive discussion above. Joe Filceolaire (talk) 01:26, 9 December 2015 (UTC)


Crystallography Open Database ID (COD ID)

   Not done
DescriptionID in Crystallography Open Database
Data typeNumber (not available yet)
Domainchemical substance (Q79529)
Allowed valuesnumber
Examplelithium niobate (Q424481) → 1007081
SourceCrystallography Open Database (Q1142422)
Formatter URLhttp://www.crystallography.net/cod/$1.html
Motivation

This property must be very useful for people making images of crystal structures, etc. -- Ktns (talk) 22:23, 2 October 2015 (UTC)

Discussion
  • Mind you, this is not always a one-to-one relation: COD works at an experiment level: one experiment, one CIF file, one identifier. So, there are two reasons why one chemical composition can have multiple COD identifiers is that one chemical can have different crystal structures (polymorphism) and each can be measured more than one time. Another thought is that many "substances", like lithium niobate (Q424481), can occur in different sizes. For example, lithium niobate (Q424481) also exists as nanomaterials. Different size, typically means different chemistry (e.g. due to different size/surface ratio, etc, etc). So, that would constitute a third reason why this property would be a 1-to-n relation. And, because substances are not well-established in Wikipedia, and neither in Wikidata, it actually leaves room for seeing this relation n-to-n. But none of this is for me a reason to not like this addition! Egon Willighagen (talk) 14:47, 4 October 2015 (UTC)
  • The comment above by Egon is a good point. We don't want dataset-ids. If the database wants to be included they need to build an ontology of their own, i.e. they should have identifiers for materials, minerals, and any other concept they want to distinguish. --Tobias1984 (talk) 14:55, 4 October 2015 (UTC)
@Ktns: I do think that it would be nice to link to this database, but I think we should inquire if they can put their IDs on the website (e.g. the ID for quartz which links all the quartz-measurements together). That would be a much more structured information to store. If we just store the IDs of measurements, then we can have less useful links, and loose the ability to use the identifiers more similar to primary keys. - I do think it would be easy for them to create identifiers for their data and expose them for us to link to. For example they have their data sorted for individual spacegroups: http://www.crystallography.net/cod/result.php?spacegroup=I%20a%20-3%20d - They probably have the same for minerals and it might just be an email and some waiting away. - Just to comment on PDB structure ID (P638): I think it is mostly on Wikidata because it is in an infobox. I don't know if the same is true for this website. --Tobias1984 (talk) 23:36, 7 October 2015 (UTC)
+1 with Tobias1984. We have to avoid to transform WD items into link directories. We should focus on one identifier per database. Snipre (talk) 15:20, 23 October 2015 (UTC)
@Ktns: Without any new proposition, I classify this property proposal as not done. Snipre (talk) 11:01, 22 December 2015 (UTC)

Chemical exposure limits

Pocket guide to Chemical Hazards

  •  Support all of these. Translating safety information into wikidata is the first step to localising them into all the languages and appifying them and whatever else people smarter than me can come up with. Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
Snipre: The United States and the European Union set different levels for legally permissible exposure to chemical hazards. Since this property pertains to exposure limits defined in law, it's reasonable to specify which country is responsible for which law. For the property proposals pertaining to recommended (i.e. non binding) limits, recommendations are published by government agencies (including the one I work for) and by non-government organizations such as the American Industrial Hygiene Association. Please let me know if you need any additional information. James Hare (NIOSH) (talk) 17:33, 5 November 2015 (UTC)
James Hare (NIOSH) I don't have a problem with the difference between countries or to specify in which country the limit is applied but I am wondering about the utility of having permissible and recommended time-weighted average exposure limit difference. From my experience as European most of the agencies providing exposure limits are the agencies which are in charge by the law to define that kind of limit. So in that case there is no sense to distinguish between the legal limit and the recommended limit. So my question was to know if outside US the distinction is pertinent. Snipre (talk) 22:38, 5 November 2015 (UTC)
Snipre, according to the International Labour Organization, the one other country to publish non-binding recommendations is Japan, through an organization called the Japan Society for Occupational Health. Other than Japan and the US, it does seem the vast majority of countries have a streamlined system where the recommendation is the law. Even then, I am not sure that consolidating the recommended values and legally binding values into one property is the best option, considering that we would need qualifiers to distinguish between binding and non-binding. (And I will be posting recommended and permissible limits for over 600 items.) James Hare (NIOSH) (talk) 16:21, 6 November 2015 (UTC)
James Hare (NIOSH) I agree with you about the fact that will implies some precise queries to extract the desired values. But the reference data can be used as filtering criteria if it is well documented. I am just afraid with a misuse of the properties if the definition difference between them is too small for people who are not aware about the distinction. For European persons the distinction permissble or recommended is not clear so I think people will definitively use the reference data to filter the values they want to use. The best will be to get feedback of other persons in order to have an international point of view on that question. Snipre (talk) 17:24, 10 November 2015 (UTC)
@Filceolaire, Tobias1984, Almondega, Thryduulf, Jasper Deng, Leyo: Can you give your feedback about a distinction between a recommended and a permissible properties for exposure limits. Thanks. Snipre (talk) 17:28, 10 November 2015 (UTC)
In my opinion permissible/recommended sound more like something that should go into the qualifier. Maybe User:James Hare (NIOSH) can create an item on test.wikidata that uses all of these properties for several countries. Then if it looks workable, we create the properties on Wikidata-proper too. --Tobias1984 (talk) 22:01, 10 November 2015 (UTC)
This further complicated by the fact that in some countries the law is that people should follow the current recommendations of standards bodies so that recommendations are effectively legal limits (if someone is injured then there must have been negligence somewhere. The fact that you followed recommendations is the easiest way to show you weren't negligent. If you don't follow the latest recommendations then it is very hard to show you were negligent). Joe Filceolaire (talk) 02:14, 11 November 2015 (UTC)
Filceolaire, I have made a test item for gypsum. The three standard qualifiers to be used are applies to jurisdiction, publisher, and duration (of work day considered for the time weighted average, usually 10 hours but can be different). For non-binding recommendations, applies to jurisdiction is explicitly set to no value. Route of evaluation is additionally used as a qualifier for such substances where there is a lower limit for respirable particles than for the particle in general. James Hare (NIOSH) (talk) 15:33, 18 November 2015 (UTC)
James Hare (NIOSH) Thank your for the time you spent on filling these examples. I prefer that way but I would move the publisher property in the reference section. Snipre (talk) 16:33, 18 November 2015 (UTC)
That makes sense, Snipre. James Hare (NIOSH) (talk) 16:35, 18 November 2015 (UTC)
Euh wait, this will be a problem if in the same document you provide both values. Is it possible ? Snipre (talk) 16:36, 18 November 2015 (UTC)
Snipre, I am not sure where the problem would be? James Hare (NIOSH) (talk) 14:43, 24 November 2015 (UTC)
James Hare (NIOSH) Better avoid the risk to have twice publisher property in the reference section in case someone wants to provide all the data about the reference document: one publisher for the data and one publisher for the document. So your examples are perfect and we can go with it. Really sorry for the long discussion. Snipre (talk) 15:31, 24 November 2015 (UTC)
Snipre, I have now updated the proposals to reflect the outcome of this discussion. James Hare (NIOSH) (talk) 15:09, 1 December 2015 (UTC)
@Snipre: Info Sorry for the delay. Here in Brazil (Q155), that is regulated by a Ministry of Labour and Employment (Q10330434) Q10337393 (regulated standard) (available here, in Portuguese (Q5146)). In it are set limites de tolerância (en: tolerance limits) for different risks: physical, chemical, biological, ergonomic and accidents. But from what I saw, does not define otherwise limit (as a recommended limit). I'm not sure how to declare this information, then I prefer not vote. (My English is terrible, so I'm sorry for this.)--Almondega (talk) 16:26, 18 November 2015 (UTC)
@James Hare (NIOSH), Almondega, Filceolaire: I think we spend quite enough time on that proposals and this is ok from my side. Snipre (talk) 16:18, 1 December 2015 (UTC)

@Snipre: Where is the Property documentation of this proposal? --Almondega (talk) 19:55, 1 December 2015 (UTC)

@Almondega: this discussion header refers to the four proposals below: time-weighted average exposure limit, ceiling exposure limit, maximum peak exposure limit, and short-term exposure limit. James Hare (NIOSH) (talk) 20:35, 1 December 2015 (UTC)
@James Hare (NIOSH): Ah, ok! How often the discussion is after the proposal, I just searched on text above :P Thanks. --Almondega (talk) 22:19, 1 December 2015 (UTC)
Notified participants of WikiProject Chemistry Please vote in favor of the next 4 proposals. And by the way please have a look at the the 6 other proposals about toxicological data below. These are the last batch of properties to complete the initial set of properties selected to described chemical in WD (see Wikidata: WikiProject Chemistry/Properties). Thank you. Snipre (talk) 17:16, 1 December 2015 (UTC)

time-weighted average exposure limit

Descriptionrecommended or required concentration limit for chemical exposure in a workplace in a given work day
Representstime-weighted average concentration (Q21010836)
Data typeNumber (not available yet)
Domainchemicals
Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); duration (i.e. length of workday used in measurement) applies to jurisdiction (P1001) as qualifier for legally defined limits (explicitly set to "none" for recommendations known to be non-binding)
Exampleacetone (Q49546) → 0.0024 gram per litre (Q834105); applies to jurisdiction (P1001)United States of America (Q30); duration → 10 hour (Q25235)
SourceNIOSH pocket guide to chemical hazards (superseded) (Q20022913) for U.S. values; potentially other sources as well
Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
Proposed byJames Hare (NIOSH) (talk) 18:55, 21 October 2015 (UTC)
Motivation

James Hare (NIOSH) (talk) 18:55, 21 October 2015 (UTC)

Addendum: This proposal was originally listed under "permissible time-weighted average exposure limit". As a result of the discussion below I have re-scoped the proposal to include both legal limits and non-binding limits. James Hare (NIOSH) (talk) 15:00, 1 December 2015 (UTC)
Discussion
See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
@Filceolaire: Can you again give your approval for the 4 properties ? As many changes occured since your first comment it will be more clear if you can confirm yourposition. Thanks Snipre (talk) 10:41, 5 December 2015 (UTC)
 Support Snipre (talk) 16:18, 1 December 2015 (UTC)
 Question @James Hare (NIOSH): Is this example real? I searched for it here, but I didn't find 10-hours limits... --Almondega (talk) 22:38, 1 December 2015 (UTC)
Yes Almondega, it's in the Pocket Guide (not RTECS). James Hare (NIOSH) (talk) 22:41, 1 December 2015 (UTC)
@James Hare (NIOSH): but there I don't found more details, just it:

Exposure Limits:

  • NIOSH REL: TWA 250 ppm (590 mg/m3)
  • OSHA PEL: TWA 1000 ppm (2400 mg/m3)

Where is the information about the duration → 10 hour (Q25235)? --Almondega (talk) 23:10, 1 December 2015 (UTC)

@Almondega: What do you mean ? The qualifier duration is the propertie duration (P2047). But we are discussing about the change of the label. Snipre (talk) 10:41, 5 December 2015 (UTC)
@Snipre, James Hare (NIOSH): I'm just a little worried about the source of information, 'cause I didn't find the information about the qualifier duration (P2047) on the page... --Almondega (talk) 17:18, 5 December 2015 (UTC)
Almondega, the time-weighted average is based on a given length of a workday, which by default is ten hours (see [4]: "For NIOSH RELs, "TWA" indicates a time-weighted average concentration for up to a 10-hour workday during a 40-hour workweek"). I specify it here because other organizations may publish time weighted average exposure limits assuming a different workday length. James Hare (NIOSH) (talk) 15:08, 15 December 2015 (UTC)

@Snipre, James Hare (NIOSH): ✓ Done time-weighted average exposure limit (P2404) --Almondega (talk) 18:38, 15 December 2015 (UTC)

ceiling exposure limit

Descriptionrecommended or required maximum concentration for chemical exposure in a given work day
Representsceiling concentration (Q21010844)
Data typeNumber (not available yet)
Domainchemicals
Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); applies to jurisdiction (P1001) as qualifier; duration and route of administration (P636) as optional qualifiers for legally defined limits (explicitly set to "none" for recommendations known to be non-binding)
Example1,2-dichloroethane (Q161480) → 0.000405 gram per litre (Q834105); applies to jurisdiction (P1001)United States of America (Q30)
SourceNIOSH pocket guide to chemical hazards (superseded) (Q20022913) for U.S. values; potentially other sources as well
Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
Motivation

James Hare (NIOSH) (talk) 18:55, 21 October 2015 (UTC)

Addendum: This proposal was originally listed under "permissible ceiling exposure limit". As a result of the discussion above I have re-scoped the proposal to include both legal limits and non-binding limits. James Hare (NIOSH) (talk) 15:01, 1 December 2015 (UTC)
Discussion
See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
 Support Snipre (talk) 16:18, 1 December 2015 (UTC)

@Snipre, James Hare (NIOSH): ✓ Done ceiling exposure limit (P2405) --Almondega (talk) 19:23, 15 December 2015 (UTC)


maximum peak exposure limit

Descriptionrecommended or required maximum concentration for chemical exposure during a five-minute excursion within a certain period of hours
Representsfive-minute maximum peak (Q21129503)
Data typeNumber (not available yet)
Domainchemicals
Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); applies to jurisdiction (P1001) as qualifier for legally defined limits (explicitly set to "none" for recommendations known to be non-binding); duration as qualifier
Examplecarbon tetrachloride (Q225045) → 0.0002 gram per litre (Q834105); applies to jurisdiction (P1001)United States of America (Q30); duration → 4 hour (Q25235)
SourceNIOSH pocket guide to chemical hazards (superseded) (Q20022913) for U.S. values; potentially other sources as well
Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
Motivation

James Hare (NIOSH) (talk) 18:55, 21 October 2015 (UTC)

Addendum: This proposal was originally listed under "permissible maximum peak exposure". As a result of the discussion above I have re-scoped the proposal to include both legal limits and non-binding limits. James Hare (NIOSH) (talk) 15:02, 1 December 2015 (UTC)
Discussion
See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
 Support Snipre (talk) 16:18, 1 December 2015 (UTC)

@Snipre, James Hare (NIOSH): ✓ Done maximum peak exposure limit (P2406) --Almondega (talk) 19:23, 15 December 2015 (UTC)

short-term exposure limit

Descriptionrecommended or required concentration limit for chemical exposure during a brief time window
Representsshort-term exposure limit (Q7501690)
Data typeNumber (not available yet)
Domainchemicals
Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); applies to jurisdiction (P1001) as qualifier for legally defined limits (explicitly set to "none" for recommendations known to be non-binding); duration as qualifier
Exampledichloromethane (Q421748) → 0.00043375 gram per litre (Q834105); applies to jurisdiction (P1001)United States of America (Q30); duration → 15 minute (Q7727)
SourceNIOSH pocket guide to chemical hazards (superseded) (Q20022913) for U.S. values; potentially other sources as well
Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
Motivation

James Hare (NIOSH) (talk) 18:55, 21 October 2015 (UTC)

Addendum: This proposal was originally listed under "permissible short-term exposure limit". As a result of the discussion above I have re-scoped the proposal to include both legal limits and non-binding limits. James Hare (NIOSH) (talk) 15:03, 1 December 2015 (UTC)
Discussion
See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
 Support Snipre (talk) 16:18, 1 December 2015 (UTC)

@Snipre, James Hare (NIOSH): ✓ Done short-term exposure limit (P2407) --Almondega (talk) 19:23, 15 December 2015 (UTC)

WikiPathways ID

Domaingene (Q7187), protein (Q8054), chemical substance (Q79529)
SourceWikiPathways (Q7999828)
Robot and gadget jobsthe idea is to keep bots keep this information updated
Motivation

Increasingly, database projects about genes, proteins, and metabolites are asking about which pathways from WikiPathways (Q7999828) apply to their biological entity. However, in WikiPathways itself, there is no single gene database identifier (Entrez Gene ID (P351), Ensembl gene ID (P594), etc) used to identify genes in these pathways. By providing this entity-pathway information in Wikidata (Q2013), all these databases (Metabolights, PubChem (Q278487), ChEBI (Q902623), etc) can use Wikidata as source of continuously updated list of this links. Egon Willighagen (talk) 17:33, 10 December 2015 (UTC)

Discussion
 Support Wikipathways is valuable resource on biological interactions. Having the ability to include meta data of these pathways, would be nice.--Andrawaag (talk) 09:53, 14 December 2015 (UTC)

@Egon Willighagen, Andrawaag: ✓ Done WikiPathways ID (P2410) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:38, 20 December 2015 (UTC)


number of awards

   Done: no label (P2422) (Talk and documentation)
Descriptionquantity of people who have been awarded or granted the subject item
Data typeQuantity
Template parameterw:ru:Шаблон:Карточка награды: Количество награждений
Domainaward (Q618779)
Allowed valuesnon-negative
Example
Motivation

Полезное свойство для карточек, а также для дедубликации данных в нескольких статьях по теме "Праведники мира" по просьбе User:Pessimist2006 и User:Amire80.
Another usefull property for infoboxes. Vlsergey (talk) 10:00, 1 September 2015 (UTC)

Discussion


list

   Not done
Descriptionlist of items of this type; inverse of is a list of (P360)
Data typeItem
Domaintypes whose members are identified in a list item
Examplenon-narrative film (Q17093751)list of feature films described as non-narrative (Q21009884)
orbit (Q4130)list of orbits (Q1467586)
Motivation

Allows navigation from the generic (type) to the specific (list of examples of that type, where such list has a wikidata item). Swpb (talk) 19:21, 24 September 2015 (UTC)

Discussion

 Not done has list (P2354) was created through a different proposal. Andreasm háblame / just talk to me 06:22, 28 December 2015 (UTC)

standard unit for this quantity

   Not done
DescriptionStandard unit used to express this quantity (e.g. in International System of Units (Q12457))
Data typeItem
Domainphysical quantity (Q107715)
Allowed valuesunit of measurement (Q47574)
Examplelength (Q36253)metre (Q11573)
Motivation

As mentioned in the discussion about "standard unit" proposal above, it may be a good idea to assign "standard" units of measurement to specific quantities. It is related to measured physical quantity (P111), however the quantity may have many units related to it via measured physical quantity (P111) but usually would have only one standard unit. Laboramus (talk) 08:25, 12 October 2015 (UTC)

Discussion
 Oppose We already have P2237 (P2237); @Laboramus: If you agree with this property, please withdraw your proposal. Snipre (talk) 13:58, 28 October 2015 (UTC)
 Not done Laboramus hasn't reacted anymore to the oppose, no support. Mbch331 (talk) 10:10, 21 December 2015 (UTC)

issued by

   Done: issued by (P2378) (Talk and documentation)
Descriptionorganisation that issues or allocates an indentifier
Data typeItem
Template parameter?
Domain(unique) identifiers
Allowed valuesorganisations
Example
Sourceexternal reference, Wikipedia list article, etc.
Motivation

Particularly for national identifiers, the issuing body would seem to be an important aspect of the item. I can't find a way to represent this currently. Thryduulf (talk: local | en.wp | en.wikt) 23:42, 12 November 2015 (UTC)

Discussion

diameter

   Done: diameter (P2386) (Talk and documentation)
Descriptionthe diameter of a circular or spherical objects
Representsdiameter (Q37221)
Data typeNumber (not available yet)
Template parameter"leadingdiameter", "drivingdiameter" and "trailingdiameter" in en:Template:Infobox locomotive; "diameter" in en:Template:Infobox building; etc
Domaincircular or spherical objects
Allowed valuespositive numbers with units of length
ExampleLNER Class A4 4468 “Mallard” (Q1070761) has part(s) (P527) leading wheel (Q2043007) (this property as a qualifier) → 0.965 metre (Q11573); London Eye (Q160659) → 120 metre (Q11573)
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsimport from infoboxes
Motivation

We have radius (P2120) but not the diameter, and while one is calculable from the other many things are more properly specified as a diameter than as a radius. Thryduulf (talk: local | en.wp | en.wikt) 16:26, 17 November 2015 (UTC)

Discussion

service ribbon

Template parametergeneric in any biographic infobox in plwiki
Domainorder (Q193622), medallion (Q131647), maybe breast badge (Q799000)
Allowed valuesimage file
Sourceexternal reference, Wikipedia list article, etc.
Motivation

I do not know if it was ever proposed but there is very often seen parameter {{{odznaczenia}}} (that means plural form of decoration (Q11796413)) in plwiki filled with a lot of small images linking to such awards. Paweł Ziemian (talk) 23:50, 20 December 2015 (UTC)

Discussion
 Support I had the same idea, very useful for grade of honor, and stop confusion Olivier LPB (talk) 14:05, 21 December 2015 (UTC)

@Paweł Ziemian, Olivier LPB: ✓ Done service ribbon image (P2425) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:42, 28 December 2015 (UTC)

YouTube channel id

DescriptionID of the YouTube channel of a person, or organisation
Data typeString
Domainhuman (Q5), organization (Q43229)
Allowed valuesUC([a-zA-Z-_0-9]){22}
ExampleJordan Jansen (Q16240161) => UCDLPyCCDRSxQd1OtBkup-Bw
SourceYouTube
Formatter URLhttps://www.youtube.com/channel/$1
Motivation

Proposing with the aim of splitting website account on (P553) (see Wikidata:Project chat#Website_user_names). Per this, YouTube is the third-most used value for P553, after Twitter & Facebook. The YouTube account can either be a username or a channel id. A channel id needs to be a separate item, because it's different from a user link. Channel id is always 24 characters long and always starts with UC. Mbch331 (talk) 16:31, 23 July 2015 (UTC)

Discussion

voltage

   Done: voltage (P2436) (Talk and documentation)
Representsvoltage (Q25428)
Data typeQuantity
Domainelectrified stuff
Example3000 V DC (as qualifier of Florence–Rome railway (Q1158780)type of electrification (P930)overhead contact line (Q110701))
Motivation

Useful unit to have, for things like the example above. Sjoerd de Bruin (talk) 20:17, 25 October 2015 (UTC)

Discussion
Would it be possible to allow for units like the width property? Antrocent (talk) 00:59, 23 November 2015 (UTC)
... but then you will need this property on the target item of P930. Jheald (talk) 16:59, 28 October 2015 (UTC)
@Raminagrobis: Is this under the right headline? --Tobias1984 (talk) 12:07, 28 October 2015 (UTC)

Prosopographia Attica (it) – (Please translate this into English.)

Descriptionidentifier for a person in Prosopographia Attica (Q2113277) by Johannes Kirchner (Q1697841)
RepresentsProsopographia Attica (Q2113277)
Data typeNumber (not available yet)
DomainQ5
Allowed valuesNatural numbers between 1 and 15588
ExampleHypereides (Q314447) → 13912
Format and edit filter validation1-digit to 5-digit numbers
SourceBand 1 and Band 2
Motivation

PA (Prosopographia Attica) is, along with the wider PAA (A Prosopography of Ancient Athens), the most important catalog of ancient Athenian citizens; it's used by many modern sources like Davies' Athenian propertied families; moreover, it's available online gratis, unlike PAA, so users can read it easily. Epìdosis 16:38, 24 November 2015 (UTC)

Discussion

✓ Done, @Epìdosis: --ValterVB (talk) 09:03, 25 December 2015 (UTC)