Wikidata:Property proposal/Archive/35
ZINC ID
[edit]Domain | chemical compound |
---|---|
Allowed values | number |
Source | PubChem etc |
- Motivation
Database with 22,724,825 compounds. GZWDer (talk) 09:51, 1 September 2015 (UTC)
- Discussion
@GZWDer: Done ZINC ID (P2084) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:51, 20 September 2015 (UTC)
Nikkaji
[edit]Domain | chemical compound |
---|---|
Allowed values | Jx.xxx.xxxA |
Source | KEGG, ChEMBL |
- Motivation
Database with 3,419,170 compounds. GZWDer (talk) 07:42, 2 September 2015 (UTC)
- Discussion
- Support. Joe Filceolaire (talk) 22:13, 12 September 2015 (UTC)
@GZWDer, Filceolaire: Done Nikkaji ID (P2085) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:02, 20 September 2015 (UTC)
Leadscope ID
[edit]Domain | chemical compound |
---|---|
Allowed values | LS-#### |
Source | ZINC, ChemSpider, PubChem |
- Motivation
Database with 150,331 compounds. GZWDer (talk) 09:31, 2 September 2015 (UTC)
- Discussion
@GZWDer: Done Leadscope ID (P2083). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:32, 20 September 2015 (UTC)
CDD Public ID
[edit]Domain | chemical compound |
---|---|
Allowed values | number |
Source | ZINC |
- Motivation
Database with 1,412,817 compounds. GZWDer (talk) 11:42, 2 September 2015 (UTC)
- Discussion
- Support. Joe Filceolaire (talk) 22:14, 12 September 2015 (UTC)
@GZWDer, GZWDer: Done P2086 (P2086) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:14, 20 September 2015 (UTC)
Melting point
[edit]Description | melting point of a substance at standard temperature and pressure (Q102145) |
---|---|
Data type | quantity (units = temperature)-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en and fr infoboxes about chemicals |
Domain | term |
Example | see Wikidata:Chemistry_task_force/Properties. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Question I assume this needs a pressure qualifier? —★PοωερZtalk 13:49, 7 June 2013 (UTC)
- The pressure dependency of melting point is less critical than for boiling point and the pessure qualifier has to be reserved only for measurement done at very high pressure like at several MPa. I think for a difference of 1-2 bar the effect is in the range of the measurement uncertainty. For melting point the heating rate during the measurement is more critical than the pressure. Fore example if you double the pressure you reduced the melting point of water by 0.007°C. Most of melting points have an uncertainty of 0.1°C so we can forget this influence. Snipre (talk) 14:38, 7 June 2013 (UTC)
- Maybe a qualifier could point to standard temperature and pressure (Q102145) for most measurements. For different laboratory conditions we would probably need a couple of qualifiers. Eutectic and azetropic points will be a challenge. I'm still hoping for a datatype that can handle multi-variate data sets. Especially for the pressure and temperature ranges of natural processes that would be interesting (E.g. A query for the melting point of water ice in the center of Jupiter). We have to start solid and simple ;). --Tobias1984 (talk) 19:18, 7 June 2013 (UTC)
- Instead of requiring each claim involving this property to be qualified with fields for assumed information like standard temperature and pressure, I think it would make more sense to update the property documentation to note that those standards conditions are default parameters that qualify the claim. That is: don't specify the default qualifiers in each claim, specify them in the property documentation. This would drastically cut boilerplate-bloat. Qualifiers should be reserved for claims that vary the standard conditions. Emw (talk) 03:24, 8 June 2013 (UTC)
- Making STP the default, sounds good. --Tobias1984 (talk) 07:57, 8 June 2013 (UTC)
- Support --Tobias1984 (talk) 14:17, 7 June 2013 (UTC)
- Support Emw (talk) 03:24, 8 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Support --Cvf-ps (talk) 10:58, 26 June 2013 (UTC)
- Support. Joe Filceolaire (talk) 21:44, 12 September 2015 (UTC)
- Support though is there a way to also refer to this as "freezing point"? Same figure, just depends whether you're starting as a liquid or as a solid. James Hare (NIOSH) (talk) 15:37, 24 September 2015 (UTC)
- Done --Tobias1984 (talk) 11:18, 25 September 2015 (UTC)
Boiling point
[edit]Description | boiling point of a substance with pressure as qualifer |
---|---|
Data type | quantity (units = temperature)-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | term |
Example | see Wikidata:Chemistry_task_force/Properties. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support --Joe Filceolaire (talk) 21:45, 12 September 2015 (UTC)
- Support James Hare (NIOSH) (talk) 15:40, 24 September 2015 (UTC)
- Done --Tobias1984 (talk) 20:50, 25 September 2015 (UTC)
size of team at start/size of team at finish
[edit]Description | number of players/sled dogs/etc. in a team at the start of a match or race |
---|---|
Data type | Number (not available yet) |
Domain | Used as properties for races items. It could also be used as a qualifier for mushers in races to indicate with how many dogs they started with and for teams of cyclists. Also as a general item for types of sports teams. |
Allowed values | number |
Example | Iditarod Trail Sled Dog Race (Q1415139): 16 qualifier instance of (P31) maximum (Q10578722) applies to part, aspect, or form (P518) sled dog (Q28997) |
Proposed by | Harmonia Amanda (talk) |
Description | number of players/sled dogs/etc. in a team at the end of the race or match |
---|---|
Data type | Number (not available yet) |
Domain | Used as properties for races items. It could also be used as a qualifier for mushers in races to indicate with how many dogs they finished and for football and other teams for how many players they finished with. |
Allowed values | number |
Example | Iditarod Trail Sled Dog Race (Q1415139): 8 qualifier instance of (P31) minimum (Q10585806) applies to part, aspect, or form (P518) sled dog (Q28997) |
Proposed by | Harmonia Amanda (talk) |
- Discussion
rewritten Joe Filceolaire (talk) 17:06, 22 August 2015 (UTC)
I work on sled dog races and this is a very important information. We could use it three times for all races: number of dogs at the start pf the race, minimal number of dogs to be allowed to finish without disqualification, and as a qualifier the number of dogs with each participants had at the end of the race or when they scratched/withdrawn. Harmonia Amanda (talk) 06:57, 5 February 2015 (UTC)
- Support -Ash Crow (talk) 12:05, 7 February 2015 (UTC)
- Perhaps make a more generic "number per team"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:40, 21 February 2015 (UTC)
- @Ash Crow: Any comment? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:37, 6 March 2015 (UTC)
- You mean for all types of animals you can attach to a sled/charriot/etc? If so, I agree. -Ash Crow (talk) 20:20, 6 March 2015 (UTC)
- @Ash Crow: I mean for all sports; 11 for association football, 15 for rugby union, etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:36, 6 March 2015 (UTC)
- Seems weird to mix humans and animals on this.... -Ash Crow (talk) 22:03, 6 March 2015 (UTC)
- Ash Crow it doesn't seem weird to me to use the same property for humans and animals but it does raise the question as to whether or not to count the human driver. There is of course the precedent of Rowing where the "mens 8" means 8 rowers plus a coxswain. I agree with Andy that it needs to be made more general for me to support it. Filceolaire (talk) 23:13, 20 March 2015 (UTC)
- Seems weird to mix humans and animals on this.... -Ash Crow (talk) 22:03, 6 March 2015 (UTC)
- @Ash Crow: I mean for all sports; 11 for association football, 15 for rugby union, etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:36, 6 March 2015 (UTC)
- You mean for all types of animals you can attach to a sled/charriot/etc? If so, I agree. -Ash Crow (talk) 20:20, 6 March 2015 (UTC)
- @Ash Crow: Any comment? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:37, 6 March 2015 (UTC)
- Weak oppose I would suggest things like . TomT0m (talk) 11:15, 8 May 2015 (UTC)
- Actually I didn't came back to this because I then thought we would need two properties, one for the start and one for the end, which could be used with qualifiers for ranking (P1352) in the items of the races (see 2015 Iditarod (Q19455277) for example). We could then just add this information as qualifiers for each participant on races items and as qualifiers for races on participants items and use the two properties for general statements on races items with qualifiers for minimum and maximum values.
- But I don't understand @TomT0m: proposal at all: that would mean creating an item for each dog team? But teams change between races, mushers never use always the same dogs. It's not the same running the Iditarod with 16 dogs and the FL500 with 8... should we create an item for each team in each race?
- As for mixing humans and dogs, I don't see how we could do that at all. For sled dog races, you have always a minimal number of dogs to have at the finish line or you are disqualified. It's a central information, included on most reports. I agree we should aim for generic properties but I don't know many sports were you can drop a member of your team (and when this dropping is a sufficiently important information to be included on Wikidata). I fail to see how the alternative solutions would solve my current problem.
- What do you think @Ash Crow:, @Pigsonthewing:, @Filceolaire:, @TomT0m:? Any other idea? --Harmonia Amanda (talk) 14:47, 18 May 2015 (UTC)
- How about if we rename this property as "size of team". I think that in dog racing "team" is well understood as referring to the number of dogs.
- If a race has a starting team size of 10 and a minimum size of 5 then the race would have statements
- <size of team:10 (applies to part:starting team)>,
- <size of team:5 (applies to part:minimum size of dog team)>
- <participant:Caribou Barbie (size of team:6)(time:5 days 6 hours 5 minutes)(ranking:4)>
- Would that work Harmonia? Filceolaire (talk) 21:48, 23 May 2015 (UTC)
- That would probably work @Filceolaire:. We won't be able to indicate if a team started with less dogs than authorized (it happen) but it's not so frequent. I think it could work for Jérémy-Günther-Heinz Jähnick (with cycling) as well. --Harmonia Amanda (talk) 17:20, 24 May 2015 (UTC)
- property name ammended as discussion above. OK @Ash Crow:, @Pigsonthewing:, @Harmonia Amanda:, @TomT0m:? Support Joe Filceolaire (talk) 00:04, 21 August 2015 (UTC)
- Thank you. However, I now wonder why we couldn't just just "has part=dog" with a qualifying quantity? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:40, 21 August 2015 (UTC)
- property name ammended as discussion above. OK @Ash Crow:, @Pigsonthewing:, @Harmonia Amanda:, @TomT0m:? Support Joe Filceolaire (talk) 00:04, 21 August 2015 (UTC)
- That would probably work @Filceolaire:. We won't be able to indicate if a team started with less dogs than authorized (it happen) but it's not so frequent. I think it could work for Jérémy-Günther-Heinz Jähnick (with cycling) as well. --Harmonia Amanda (talk) 17:20, 24 May 2015 (UTC)
- How about if we rename this property as "size of team". I think that in dog racing "team" is well understood as referring to the number of dogs.
Ok, so, as I understand, I can, on the item of a race, add P:size of the team:8, qualifier:instance of:sled dog, qualifier:???:number minimum and P:size of the team:16, qualifier:instance of:sled dog, qualifier:???:number maximum. I still can't indicate the most interesting information: with how many dogs each musher started and finished. Seems still more easy for me to create to properties "size of team at start" and "size of team at end", which offer us the possibility to enter all the data. Otherwise we are obligated to create horrible items like "minimum size of dog team" (what??), "8 dogs at the starting point" (which ok, would be a method to have the information with only this property but ><) and the same. We can't use qualifiers for qualifiers so, sorry we need either two more precise properties or many horrible items giving two/three information at the same time. @Ash Crow:, @Pigsonthewing:, @Filceolaire:, @TomT0m:. --Harmonia Amanda (talk) 13:02, 21 August 2015 (UTC)
- I agree with Andy above, I think we totally can live with a patterns. To indicate a min and max numbers we should create the min and max numbers qualifiers. To indicate the starting number and ending number we should add several statements with some key event or valid in period-like qualifier. possible examples, modelling for a team:
- ⟨ The team ⟩ has part Search ⟨ sled dogs ⟩
quantity (P1114) ⟨ 10 ⟩
valid in period (P1264) ⟨ start of the race ⟩ - ⟨ The team ⟩ has part Search ⟨ sled dogs ⟩
quantity (P1114) ⟨ 10 ⟩
valid in period (P1264) ⟨ end of the race ⟩
- ... That would work on the team item though. author TomT0m / talk page 13:23, 21 August 2015 (UTC)
- But we don't have team items and we won't ever have them. Each dog team change for every race for every musher. It's totally absurd. We won't create "team of Dallas Seavy in the 2014 Iditarod", "team of Dallas Seavey in the 2015 Iditarod" and the same! It's absurd, we don't have the data (the name of the dogs, for instance, we usually just have the name of the leading(s) dog(s) of the winning team. I said that months ago @TomT0m: and it's still true. These items don't exist and will probably never exist so it's not the solution. --Harmonia Amanda (talk) 13:56, 21 August 2015 (UTC)
- @Harmonia Amanda: Let's call the team lead by one participant <The participant team'>. And you must have an item for each participants, and it's not a problem to have one for each participant's team, it's like any sportsteam. Let's say this team is not constant in dogs composition from race to race. Then you have this solution. This items would fulfils structural need, so we totally can have them. As you said, we can't put everything on a qualifier, so to express complex relations we have to use auxiliary items, and team items are commons in sport. author TomT0m / talk page 14:21, 21 August 2015 (UTC)
- That's even more absurd "each possible combination of dogs Dallas Seavey ever leaded in a race" item with you can't even add relevant data (like, the first teams Dallas Seavey leaded belonged to his father, then, they were his own dogs, many mushers work sometimes for a kennel and sometimes for another and sometimes on their own, and sometimes fabricates teams with dogs rented by several different kennels, a specific team may have received a prize (yes there is prizes for the dogs, which doesn't apply, of course, for any other dogs the same musher leaded in another race)), just to avoid creating a specific property! You actually prefer to create several thousands absurd items with no significant data associated than to create two properties? I don't understand you at all. @TomT0m: --Harmonia Amanda (talk) 14:29, 21 August 2015 (UTC)
- @Harmonia Amanda: An item is just an identifier, it's not really important. If a racer can lead several team, then you can store the history of the teams he lead that way. I'm just trying to think a little bit generic because if we can find generic solutions, they will apply on other kind of races as well, so it can be worth thinking of what is really specific to this sport and what is not and can be factorized. This make the whole model more manageable and can allow infobox code reuse, for example. author TomT0m / talk page 14:50, 21 August 2015 (UTC)
- @TomT0m: Yes, one solution of two properties usable in any type of races, usable in infoboxes and when you need only to translate two properties in all languages. One other solution necessitating creating several thousands of absurd items with no interesting data, which we can't use in infoboxes because how can you use that in infoboxes, I wonder, and which means several thousands of translations to work in the case where these items could be used in infoboxes. Sorry if I think my proposition is much more generic and necessitating less work overall! --Harmonia Amanda (talk) 15:00, 21 August 2015 (UTC)
- @Harmonia Amanda: Jeremy just drafted a proposal for Wikidata:Cycling, can you have a look ? Your pov is appreciated and we will be able to discuss all this with a little more higher view, I hate these discussions property by property who are way too focused on a detail to think well. author TomT0m / talk page 15:15, 21 August 2015 (UTC)
- @TomT0m: I don't see anywhere on the page the discussion about the number of people in the team. But my proposal should also work for @Jérémy-Günther-Heinz Jähnick:. For cycling, "p:size of the team at start" should be used in the races items, with the value (and two values if, like for sled dogs, you have a minimal and maximal number of people/dogs/others in the team). And for each participating teams (and for each musher in the case of sled dogs races) you can use "p:size of the team at the end" because I think that in cycling too, a team can "lose" members during a race, with injuries or disqualifications (and "p:size at start" if they didn't begin with the "standard" number or if there isn't a standard number). So my proposal of two properties should be generic enough to work also on cycling (Jeremy, is that right?). --Harmonia Amanda (talk) 15:28, 21 August 2015 (UTC)
- @Harmonia Amanda: For size at start you would need an item for the team ... And also, you'll have to say that the team is made either of dogs or humans, which lead us again to has part(s) (P527). So although I get your point on creating new properties, which I do not oppose, I'm still not sure that this new one actually are the best way to do ... author TomT0m / talk page 15:37, 21 August 2015 (UTC)
- Bonjour à tous, je m'exprime exceptionnellement en français parce que je suis crevé, si bien que ça ne risque pas d'être clair. En ce qui me concerne, je n'ai pas besoin de cette propriété, parce que le nombre de coureurs max et min dans une équipe est détaillé dans la section règlement de l'article, quand nous en avons le temps. Je suis donc incompétent pour répondre à cette demande, et comme je ne m'y connais pas dans les courses de chiens de traineaux, je n'ai pas d'avis bien tranché. Jérémy-Günther-Heinz Jähnick (talk) 17:43, 21 August 2015 (UTC)
- @Harmonia Amanda: For size at start you would need an item for the team ... And also, you'll have to say that the team is made either of dogs or humans, which lead us again to has part(s) (P527). So although I get your point on creating new properties, which I do not oppose, I'm still not sure that this new one actually are the best way to do ... author TomT0m / talk page 15:37, 21 August 2015 (UTC)
- @TomT0m: I don't see anywhere on the page the discussion about the number of people in the team. But my proposal should also work for @Jérémy-Günther-Heinz Jähnick:. For cycling, "p:size of the team at start" should be used in the races items, with the value (and two values if, like for sled dogs, you have a minimal and maximal number of people/dogs/others in the team). And for each participating teams (and for each musher in the case of sled dogs races) you can use "p:size of the team at the end" because I think that in cycling too, a team can "lose" members during a race, with injuries or disqualifications (and "p:size at start" if they didn't begin with the "standard" number or if there isn't a standard number). So my proposal of two properties should be generic enough to work also on cycling (Jeremy, is that right?). --Harmonia Amanda (talk) 15:28, 21 August 2015 (UTC)
- @Harmonia Amanda: Jeremy just drafted a proposal for Wikidata:Cycling, can you have a look ? Your pov is appreciated and we will be able to discuss all this with a little more higher view, I hate these discussions property by property who are way too focused on a detail to think well. author TomT0m / talk page 15:15, 21 August 2015 (UTC)
- @TomT0m: Yes, one solution of two properties usable in any type of races, usable in infoboxes and when you need only to translate two properties in all languages. One other solution necessitating creating several thousands of absurd items with no interesting data, which we can't use in infoboxes because how can you use that in infoboxes, I wonder, and which means several thousands of translations to work in the case where these items could be used in infoboxes. Sorry if I think my proposition is much more generic and necessitating less work overall! --Harmonia Amanda (talk) 15:00, 21 August 2015 (UTC)
- @Harmonia Amanda: An item is just an identifier, it's not really important. If a racer can lead several team, then you can store the history of the teams he lead that way. I'm just trying to think a little bit generic because if we can find generic solutions, they will apply on other kind of races as well, so it can be worth thinking of what is really specific to this sport and what is not and can be factorized. This make the whole model more manageable and can allow infobox code reuse, for example. author TomT0m / talk page 14:50, 21 August 2015 (UTC)
- Harmonia Amanda I see your problem. the answer is that you have items for mushers and that has to substitute for teams. Each participant/musher has a bunch of qualifiers, one corresponding to each column in the results table. Now the results table for en:2005 Idatarod only has columns for ranking (P1352), time and prize money (which will need datatype 'number with units' before we can create them) and lead dogs. I guess you want to add two columns for the team size at the start and finish. We can't have qualifiers on qualifiers so this has to be separate properties These are actually useful for other sports besides mushing. Players can get sent off in soccer and then the team has to play with 10 players or less. so I Support the creation of two properties - size of team at start and size of team at finish. Can we go ahead and amend the proposal? If you want a lead dogs property then that will have to be a separate discussion. Joe Filceolaire (talk) 16:53, 21 August 2015 (UTC)
- @TomT0m: « For size at start you would need an item for the team » uh? Sorry? "size at start" necessitate a number in value. So I won't need an item, no. I'll need to add '8' or '9' or whatever number it is... but certainly not to create a dummy item to answer. On the item of the race I'll use as properties : "size at start" with value "10" and qualifier "apply to: sled dogs" and "instance of: minimum", and "size at start:16" with qualifiers apply to:sled dogs, instance of:maximum. I'll add as properties "size at end" with two values too, 8 and 16 (for example), with qualifiers instance of minimum/maximum, apply to: sled dogs. Then, I'll use p:participant with the name of the mushers as value, and "size of team at start: 14" "size of team at end:9" as qualifiers of the musher. And I have all my information without creating absurd and void items. These two properties could be used for several sports, because even soccer, or rugby, or volley, etc. can have teams without the number maximum of players and this number can change through the match. Seems to me like the easiest solution. What do you think @Ash Crow:, @Pigsonthewing:, @Filceolaire:? (and I don't want right now a "lead dog" property, the data is much to scarce but I agree it's another discussion). --Harmonia Amanda (talk) 22:35, 21 August 2015 (UTC)
- I Support this. I'm going to go ahead and rewrite the proposal - see above. Tweak if I got anything wrong. Joe Filceolaire (talk) 17:06, 22 August 2015 (UTC)
- I Support the new proposition for two properties --Harmonia Amanda (talk) 21:55, 22 August 2015 (UTC)
- Support too. -Ash Crow (talk) 21:04, 23 August 2015 (UTC)
- @TomT0m: « For size at start you would need an item for the team » uh? Sorry? "size at start" necessitate a number in value. So I won't need an item, no. I'll need to add '8' or '9' or whatever number it is... but certainly not to create a dummy item to answer. On the item of the race I'll use as properties : "size at start" with value "10" and qualifier "apply to: sled dogs" and "instance of: minimum", and "size at start:16" with qualifiers apply to:sled dogs, instance of:maximum. I'll add as properties "size at end" with two values too, 8 and 16 (for example), with qualifiers instance of minimum/maximum, apply to: sled dogs. Then, I'll use p:participant with the name of the mushers as value, and "size of team at start: 14" "size of team at end:9" as qualifiers of the musher. And I have all my information without creating absurd and void items. These two properties could be used for several sports, because even soccer, or rugby, or volley, etc. can have teams without the number maximum of players and this number can change through the match. Seems to me like the easiest solution. What do you think @Ash Crow:, @Pigsonthewing:, @Filceolaire:? (and I don't want right now a "lead dog" property, the data is much to scarce but I agree it's another discussion). --Harmonia Amanda (talk) 22:35, 21 August 2015 (UTC)
- That's even more absurd "each possible combination of dogs Dallas Seavey ever leaded in a race" item with you can't even add relevant data (like, the first teams Dallas Seavey leaded belonged to his father, then, they were his own dogs, many mushers work sometimes for a kennel and sometimes for another and sometimes on their own, and sometimes fabricates teams with dogs rented by several different kennels, a specific team may have received a prize (yes there is prizes for the dogs, which doesn't apply, of course, for any other dogs the same musher leaded in another race)), just to avoid creating a specific property! You actually prefer to create several thousands absurd items with no significant data associated than to create two properties? I don't understand you at all. @TomT0m: --Harmonia Amanda (talk) 14:29, 21 August 2015 (UTC)
- @Harmonia Amanda: Let's call the team lead by one participant <The participant team'>. And you must have an item for each participants, and it's not a problem to have one for each participant's team, it's like any sportsteam. Let's say this team is not constant in dogs composition from race to race. Then you have this solution. This items would fulfils structural need, so we totally can have them. As you said, we can't put everything on a qualifier, so to express complex relations we have to use auxiliary items, and team items are commons in sport. author TomT0m / talk page 14:21, 21 August 2015 (UTC)
- But we don't have team items and we won't ever have them. Each dog team change for every race for every musher. It's totally absurd. We won't create "team of Dallas Seavy in the 2014 Iditarod", "team of Dallas Seavey in the 2015 Iditarod" and the same! It's absurd, we don't have the data (the name of the dogs, for instance, we usually just have the name of the leading(s) dog(s) of the winning team. I said that months ago @TomT0m: and it's still true. These items don't exist and will probably never exist so it's not the solution. --Harmonia Amanda (talk) 13:56, 21 August 2015 (UTC)
- I just noticed this proposal is similar to Wikidata:Property_proposal/Event#number_of_starters except (as I understand it) that is more for the number of 'participants'. minimum number of players (P1872) and maximum number of players (P1873) seem similar too except that I think those are for the total including all the teams, or something. Joe Filceolaire (talk) 22:46, 23 August 2015 (UTC)
- From what I understand "number of starters" would be "25" for the 2015 Yukon Quest, and "99" for the Iditarod... so not the same (and I plan to use this too). --Harmonia Amanda (talk) 00:37, 24 August 2015 (UTC)
- Support After explication, it seem different of other "players" property. --Fralambert (talk) 00:53, 24 August 2015 (UTC)
- Harmonia Amanda: I noticed a change in the "number" datatype. Now you can attach any item as unit for any property with this datatype. This means we can use a "sled dog" item as the unit for this property so we can say <size of team at start:21; unit = sled dog>. Joe Filceolaire (talk) 22:26, 25 September 2015 (UTC)
@Ash Crow:, @Pigsonthewing:, @Filceolaire:, @TomT0m: @Jérémy-Günther-Heinz Jähnick: @Fralambert: both properties are created! --Harmonia Amanda (talk) 00:29, 26 September 2015 (UTC)
specific gravity
[edit]Description | relative density compared to water |
---|---|
Represents | relative density (Q10972285) |
Data type | Number (not available yet) |
Domain | chemicals |
Allowed values | any number (dimensionless figure) with optional qualifiers for temperature of the substance (default is 68 degree Fahrenheit (Q42289)) and temperature of water (default is 4 degree Celsius (Q25267)) |
Example | starch (Q41534) → 1.45 |
Source | Pocket Guide to Chemical Hazards, published by National Institute for Occupational Safety and Health (Q60346) |
Robot and gadget jobs | Future mass importation of the Pocket Guide to Chemical Hazards into Wikidata. |
- Motivation
This property is part of a planned mass importation of the Pocket Guide to Chemical Hazards into Wikidata. James Hare (NIOSH) (talk) 18:04, 24 September 2015 (UTC)
- Discussion
Notified participants of WikiProject Chemistry
- I would somehow lean more towards expressing this like this: https://www.wikidata.org/w/index.php?title=Q41534&type=revision&diff=253477049&oldid=252851608 (this also avoid a dimensionless measurement). --Tobias1984 (talk) 18:20, 24 September 2015 (UTC)
- That should work. James Hare (NIOSH) (talk) 22:48, 24 September 2015 (UTC)
- Not done --Tobias1984 (talk) 10:46, 26 September 2015 (UTC)
RXNO Ontology
[edit]Description | RSC ontology for organic reactions |
---|---|
Represents | Name Reaction Ontology (Q20991891) |
Domain | eponymous chemical reaction (Q1049494) |
Allowed values | string |
Example | Wolff rearrangement (Q255452) → RXNO:0000051 [1] |
Source | https://github.com/rsc-ontologies/rxno/ |
Formatter URL | http://www.rsc.org/publishing/journals/prospect/ontology.asp?id=$1 |
- Motivation
File:Rsc-ont.svg--Kopiersperre (talk) 14:25, 21 September 2015 (UTC)
- Discussion
- Support. Are you proposing to import the instance of and subclass of relations (as shown on the .svg file) from this ontology too? Is the license compatible? Joe Filceolaire (talk) 22:35, 21 September 2015 (UTC)
- Support. Almondega (talk) 18:54, 24 September 2015 (UTC)
- Done --Tobias1984 (talk) 10:51, 26 September 2015 (UTC)
Decomposition point
[edit]Description | decomposition point of a substance |
---|---|
Data type | value with units-invalid datatype (not in Module:i18n/datatype) |
Template parameter | pl:Szablon:Związek chemiczny infobox, ru:Шаблон:Вещество |
Domain | chemical substance (Q79529) |
Example | copper(II) acetylide (Q9138794) → 100 °C (with remark explosively) [from: CRC Handbook of Chemistry and Physics (Q904273), 90th]
gold trichloride (Q174129) → >160 °C [from: CRC Handbook of Chemistry and Physics (Q904273), 90th] possible remarks to indicate pressure and like explosively, violently |
Source | scientific literature (eg. CRC Handbook of Chemistry and Physics (Q904273)) |
Notified participants of WikiProject Chemistry
- Motivation
Annotation from Wikidata:WikiProject Chemistry/Properties made by user:Michał Sobkowski: "Decomposition is usually indicated in m.p. or b.p. records (as is proposed here, see above). However, it is not necessarily coincided with these values. Decomposition may take place without phase transition, e.g. in gas phase; an observed "boiling point" may be just decomposition into volatile product(s) without reaching the real b.p. of a substance; the phase of a decomposing substance may not be known. Thus, instead of adding unprecise remarks to the m.p./b.p.'s (which are reasonable only in printed material, to save place), an additional field assigned exclusively for this value would be advantageous." ∼Wostr (talk) 18:20, 12 June 2015 (UTC)
- Discussion
- Support But we have to be able to specify an interval. Snipre (talk) 19:35, 12 June 2015 (UTC)
- Support Of course this will have to have constraints; preferably I would like to see the temperature in kelvins and this cannot be applied to elements (compounds only).--Jasper Deng (talk) 01:06, 13 June 2015 (UTC)
- Support Almondega (talk) 02:59, 14 August 2015 (UTC)
- Support. I changed the datatype to "value with units" as this should specify if it is celcius or kelvin. Joe Filceolaire (talk) 22:46, 2 September 2015 (UTC)
- Done --Tobias1984 (talk) 10:58, 26 September 2015 (UTC)
Sublimation point
[edit]Description | sublimation point of a substance with pressure as qualifer |
---|---|
Data type | quantity (units = temperature)-invalid datatype (not in Module:i18n/datatype) |
Domain | term |
Example | see Wikidata:Chemistry_task_force/Properties. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Support. Joe Filceolaire (talk) 21:46, 12 September 2015 (UTC)
- Done --Tobias1984 (talk) 10:57, 27 September 2015 (UTC)
Half-Life
[edit]Description | Amount of time required for the amount of something to fall to half its initial value. |
---|---|
Represents | half-life (Q47270) |
Data type | Quantity |
Template parameter | en:Template:Infobox isotope halflife |
Domain | subatomic particles, radioactive isotopes |
Example | neutron (Q2348) → 880,3 ± 1,1 s |
- Motivation
Propety needed for infoboxes Pamputt (talk) 11:13, 19 September 2015 (UTC)
- Discussion
- Support. Joe Filceolaire (talk) 11:20, 19 September 2015 (UTC)
- Support added "radioactive isotopes" to domain. --Tobias1984 (talk) 08:35, 20 September 2015 (UTC)
- Support Aryamanarora (talk) 19:49, 22 September 2015 (UTC)
- Done --Tobias1984 (talk) 11:12, 27 September 2015 (UTC)
Weight of person
[edit]Description | weight of tennis player |
---|---|
Data type | Number (not available yet) |
Template parameter | "weight" in en:template:Infobox tennis biography |
Domain | person |
Allowed values | n/a |
Example 1 | MISSING |
Example 2 | MISSING |
Example 3 | MISSING |
Source | ATP/WTA/ITF websites |
Proposed by | --Stryn (talk) 16:23, 1 May 2013 (UTC) |
- Discussion
- Comment Remember about units. That English template supports both kilograms and pounds. --AVRS (talk) 14:55, 4 May 2013 (UTC)
- Support No need to store two numbers, because one can be calculated from the other. Vinkje83 (talk) 10:02, 7 May 2013 (UTC)
- Oppose redundant with the pending mass property. 'Mass' is clearly applicable to both astronomical objects and people, and any other matter. Emw (talk) 03:01, 8 May 2013 (UTC)
- Comment strictly speaking, mass is not equal to weight. For measuring people on Earth, it is moot, but if we want to make it a broad generic property, which is the right way to go, then we have to remember that in scientific disciplines (especially astronomy), weight and mass are two different (albeit related) properties. Joshbaumgartner (talk) 10:06, 9 May 2013 (UTC)
- Can you give a specific example of where this property would be used and where it would also not be trivially deducible from the subject's mass and its location (e.g. Earth)? I of course agree that W = mg, but I think it's also important to realize that when one refers to at least a person's weight, the subject's mass is virtually always the more relevant and intended property. Emw (talk) 02:37, 15 May 2013 (UTC)
- Strictly speaking, mass and weight are two completely different concepts of course, and given that they are measured using different units, there is no way we can mix them. But the "weight" of a person really means his mass, have you ever seen the weight of a person measured in newtons ? --Zolo (talk) 07:22, 15 May 2013 (UTC)
- Comment strictly speaking, mass is not equal to weight. For measuring people on Earth, it is moot, but if we want to make it a broad generic property, which is the right way to go, then we have to remember that in scientific disciplines (especially astronomy), weight and mass are two different (albeit related) properties. Joshbaumgartner (talk) 10:06, 9 May 2013 (UTC)
Support as a generic 'weight' property applicable to all items, not just tennis players or even just people. Joshbaumgartner (talk) 10:06, 9 May 2013 (UTC)Josh Baumgartner (talk) 18:11, 15 September 2015 (UTC)- Comment How does this work exactly? A person's weight does not stay the same. Danrok (talk) 21:20, 21 May 2013 (UTC)
Support. We should wait until there are date qualifiers, so we could have "measured on YYYY-MM-DD" or "reported on YYYY-MM-DD". Superm401 - Talk 07:29, 22 May 2013 (UTC)- Actually, I'm not sure if we should have both this and mass. If it is approved, it should not be limited to tennis players, but probably be available to any object. Superm401 - Talk 07:34, 22 May 2013 (UTC)
- I'm not sure about "reported on YYYY-MM-DD", e.g. on Rafael Nadal's ATP World Tour profile page is only "188 lbs (85 kg)", not any dates. But on en-Wikipedia has "Last updated on" text on the tennis player infobox. --Stryn (talk) 07:51, 22 May 2013 (UTC)
- Actually, I'm not sure if we should have both this and mass. If it is approved, it should not be limited to tennis players, but probably be available to any object. Superm401 - Talk 07:34, 22 May 2013 (UTC)
- Support a general "mass" property, as all these things are mass not wieght in the physical sense (sure enough, the word weight is commonly used, but I think the Wikidata label should have the technically accurate label to avoid confusions). For qualifiers, I would think that it is enough to use the general "as of" qualifier, possibly supplementted by others like determination method or standard (P459) . --Zolo (talk) 08:19, 22 May 2013 (UTC)
- Comment The weight of it is not just for people. Is there a way to let the weight create a general? --Crazy1880 (talk) 09:46, 23 June 2015 (UTC)
- After going back and forth on this, I eventually decided on Oppose, because I don't think a separate property is justified. It's true that we use "weight" to talk about people when we're referring to the mass, but that usage is not restricted to humans, we use "weight" when referring to the mass of pretty much anything, e.g. en:Template:Infobox banknote, en:Template:Infobox automobile, en:Template:Infobox animal breed, en:Template:Infobox cheese, en:Template:Infobox computer hardware, en:Template:Infobox building and en:Template:Infobox artwork is just a small selection of non-person infoboxes which have a weight parameter referring to the mass. I think it would be better to handle this via the label, description and aliases of the generic property (I would probably use something like "weight (mass)" as the English label but that's a discussion for elsewhere. :)). - Nikki (talk) 12:13, 13 September 2015 (UTC)
- Oppose. No need for a separate property just for people. Also, due to contradictory interpretations of "weight" and that it is rarely (if ever) necessary in wikidata to express the force of gravity on an object, the term "weight" should not be used. Jc3s5h (talk) 13:10, 13 September 2015 (UTC)
- Support In a general property "mass" property we can't do range checks (0kg -- 100kg, plus exceptions). For other purposes, the property page for this could still hold a "subproperty of" statement. --- Jura 13:21, 13 September 2015 (UTC)
- @Jura1: Seems pretty easy to write some query combining your range check with intance of human or a subclass of it. author TomT0m / talk page 13:35, 13 September 2015 (UTC)
- If you will, of course, but you'd have to notify the contributors as well. If you wont help us, we would have to create a separate property and rely on the existing Special:ConstraintReport and its currently implemented features. --- Jura 13:46, 13 September 2015 (UTC)
- @Jura1: Seems pretty easy to write some query combining your range check with intance of human or a subclass of it. author TomT0m / talk page 13:35, 13 September 2015 (UTC)
- Oppose not convinced that this property is worth doing since you can tell it's a human from the <instance of:human> claim. Joe Filceolaire (talk) 14:24, 14 September 2015 (UTC)
- Oppose mass property is sufficient, since weight is a derivative of mass (W=mg). Mass is equal to 'weight at 1g' which is what the assumed use of weight for most things would be (a person's weight for example). Josh Baumgartner (talk) 18:11, 15 September 2015 (UTC)
- Oppose, per above. --Yair rand (talk) 23:15, 16 September 2015 (UTC)
- Oppose, per above. --Casper Tinan (talk) 13:57, 17 September 2015 (UTC)
- Not done --Tobias1984 (talk) 13:45, 27 September 2015 (UTC)
NDF-RT ID
[edit]Description | The identifier for the National Drug File Reference Terminology |
---|---|
Represents | NDF-RT (Q21008030) |
Data type | String |
Domain | drugs, diseases |
Allowed values | N0000000000 Prefix 'N' with 10 digits |
Example | vemurafenib (Q423111) → N0000183250 |
Source | https://rxnav.nlm.nih.gov/ |
Formatter URL | https://rxnav.nlm.nih.gov/REST/Ndfrt/allconcepts?nui=$1 |
Robot and gadget jobs | Will be added and maintained by User:ProteinBoxBot/Drug_items |
- Motivation
This property allows for linking the NDF-RT data to Wikidata items. NDF-RT is a authoritative resource on drug and disease concepts and also an important access point for drug-drug, drug-disease interactions and the MeSH terminology. This will give Wikidata one more important identifier in the biomedical sciences and enable unprecedented identifier mappings. Sebotic (talk) 10:00, 24 September 2015 (UTC)
- Discussion
- Support Is useful. lv_ra (talk) 15:40, 24 September 2015 (UTC)
- Done --Tobias1984 (talk) 13:48, 27 September 2015 (UTC)
Vaporization enthalpy
[edit]See Wikidata:Property_proposal/Pending/2#Vaporization enthalpy (en)
Description | vaporization enthalpy of a substance with temperature as qualifier |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | chemistry, physics |
Example | Vaporization enthalpy of methanol: 37400.00 J/mol at 298.15 K |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Done --Tobias1984 (talk) 14:01, 27 September 2015 (UTC)
Combustion enthalpy
[edit]See Wikidata:Property_proposal/Pending/2#Combustion enthalpy (en)
Description | combustion enthalpy |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | chemistry, physics |
Example | see Wikidata:Chemistry_task_force/Properties. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Done --Tobias1984 (talk) 14:12, 27 September 2015 (UTC)
Kinematic viscosity
[edit]Description | viscosity of a substance with phase of matter and temperature as qualifiers |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | chemistry, physics |
Example | see Wikidata:Chemistry_task_force/Properties. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Done --Tobias1984 (talk) 14:37, 27 September 2015 (UTC)
Vapor pressure
[edit]See Wikidata:Property_proposal/Pending/2#Vapor_pressure_.28en.29
Description | vapor pessure of a substance with temperature as qualifier |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | chemistry, physics |
Example | Vapor pressure of methanol: 12,3 kPa at 20°C |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Support --Cvf-ps (talk) 11:04, 26 June 2013 (UTC)
- Support James Hare (NIOSH) (talk) 16:08, 24 September 2015 (UTC)
- Done --Tobias1984 (talk) 15:05, 27 September 2015 (UTC)
Radius
[edit]Description | The radius of an astronomical object (and other spherical stuff). |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en:template:Infobox planet equatorial_radius, polar_radius, mean_radius |
Domain | Any spherical object (obvious case: planets) |
Proposed by | MER-C (talk) 12:57, 9 February 2013 (UTC) |
- Support. I suggest to use qualifiers to distinguish polar or equatorial radius. --Paperoastro (talk) 14:14, 9 February 2013 (UTC)
- Support Danrok (talk) 19:31, 24 February 2013 (UTC)
- Support it is necessary for infobox. Sunpriat (talk) 19:34, 6 October 2014 (UTC)
- Done --Tobias1984 (talk) 15:21, 27 September 2015 (UTC)
Women wing
[edit]Description | subsidiary for women in a political party or organization |
---|---|
Data type | Item |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | National Coalition Party (Q304191) → National Coalition Party's Women's Association (Q5405349) |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
- Seems overly specific, since has part(s) (P527) or has subsidiary (P355) with a qualifier (applies to part, aspect, or form (P518)) to indicate scope seems to cover it: ⟨ National Coalition Party (Q304191) ⟩ has part(s) (P527) ⟨ National Coalition Party's Women's Association (Q5405349) ⟩Josh Baumgartner (talk) 03:32, 16 September 2015 (UTC)
applies to part, aspect, or form (P518) ⟨ woman (Q467) ⟩- @Joshbaumgartner: you're right. I withdraw my proposal. --★ → Airon 90 15:26, 17 September 2015 (UTC)
Youth wing
[edit]Description | subsidiary for young people in a political party or organization |
---|---|
Data type | Item |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | National Coalition Party (Q304191) → Youth of the National Coalition Party (Q5137919) |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
- Seems overly specific, since has part(s) (P527) or has subsidiary (P355) with a qualifier (applies to part, aspect, or form (P518)) to indicate scope seems to cover it: ⟨ National Coalition Party (Q304191) ⟩ has part(s) (P527) ⟨ Youth of the National Coalition Party (Q5137919) ⟩Josh Baumgartner (talk) 03:32, 16 September 2015 (UTC)
applies to part, aspect, or form (P518) ⟨ youth (Q190007) ⟩- @Joshbaumgartner: you're right. I withdraw my proposal. --★ → Airon 90 15:26, 17 September 2015 (UTC)
children's organization
[edit]Description | subsidiary for children in a political party or organization |
---|---|
Data type | Item |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | National Coalition Party (Q304191) → National Children's Association (Q17185079) |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
- Seems overly specific, since has part(s) (P527) or has subsidiary (P355) with a qualifier (applies to part, aspect, or form (P518)) to indicate scope seems to cover it: ⟨ National Coalition Party (Q304191) ⟩ has part(s) (P527) ⟨ National Children's Association (Q17185079) ⟩Josh Baumgartner (talk) 03:32, 16 September 2015 (UTC)
applies to part, aspect, or form (P518) ⟨ child (Q7569) ⟩- @Joshbaumgartner: you're right. I withdraw my proposal. --★ → Airon 90 15:26, 17 September 2015 (UTC)
student political organization
[edit]Description | subsidiary for teacher in a political party or organization |
---|---|
Data type | Item |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | National Coalition Party (Q304191) → Student Union of National Coalition Party (Q10660958) |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
@Airon90: Can you translate both example items into English. We have to make sure that the most people possible, understand the example in order to use the property. --Tobias1984 (talk) 19:57, 15 September 2015 (UTC)
- I'm not sure for the translations (Italian is my mother tongue and I can't translate that word) so I commented it. You can find it between <!-- and -->. I'll translate the item names tomorrow ASAP --★ → Airon 90 21:41, 15 September 2015 (UTC)
- Seems overly specific, since has part(s) (P527) or has subsidiary (P355) with a qualifier (applies to part, aspect, or form (P518)) to indicate scope seems to cover it: ⟨ National Coalition Party (Q304191) ⟩ has part(s) (P527) ⟨ Student Union of National Coalition Party (Q10660958) ⟩Josh Baumgartner (talk) 03:32, 16 September 2015 (UTC)
applies to part, aspect, or form (P518) ⟨ student (Q48282) ⟩- @Joshbaumgartner: you're right. I withdraw my proposal. --★ → Airon 90 15:26, 17 September 2015 (UTC)
Associated newspaper
[edit]Description | official newspaper of a political party or organization |
---|---|
Data type | Item |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | National Coalition Party (Q304191) → Nykypäivä (Q18661033) |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
- Support @Airon90: I think "associated newspaper" would be clearer. --Tobias1984 (talk) 20:02, 15 September 2015 (UTC)
- @Tobias1984: Ok. I don't care about the name but about the concept :P --★ → Airon 90 21:41, 15 September 2015 (UTC)
- @Airon90: It is mostly to make sure that the properties are well defined before they are created. Further examples for this property might be German Bundestag (Q154797) = Das Parlament (Q1170039). --Tobias1984 (talk) 22:07, 15 September 2015 (UTC)
- Oppose Overly specific, since has part(s) (P527) or has subsidiary (P355) seems to cover it as ⟨ National Coalition Party (Q304191) ⟩ has subsidiary (P355) ⟨ Nykypäivä (Q18661033) ⟩or if the newspaper is not actually owned by the organization, but merely affiliated with it the claim should be on the newspaper's item as Josh Baumgartner (talk) 04:04, 16 September 2015 (UTC)
has use (P366) ⟨ newspaper (Q11032) ⟩- @Joshbaumgartner: you're right. I withdraw my proposal. --★ → Airon 90 15:26, 17 September 2015 (UTC)
Membership
[edit]Description | number of people who joined an organization |
---|---|
Data type | Number (not available yet) |
Template parameter | fi:Malline:Puolue (Template:Infobox political party (Q5622823)) |
Allowed values | organizations |
Example | Arcigay (Q637369) → 228,563 Old example: National Coalition Party (Q304191) → 41,000 |
- Motivation
Important property to describe the element in its wholeness ★ → Airon 90 16:13, 14 September 2015 (UTC)
- Discussion
- Oppose @Airon90: I think the example should work with number of seats (P1342) --Tobias1984 (talk) 19:58, 15 September 2015 (UTC)
- @Tobias1984: Not at all: P1342 is for members of an institution. This one is for quantify the member of a party. Things are very different. --★ → Airon 90 21:41, 15 September 2015 (UTC)
Oppose number of seats (P1342) will work fine, there is no need for it to be so specific.Josh Baumgartner (talk) 04:04, 16 September 2015 (UTC)
- @Joshbaumgartner: Did you read what I wrote above? Read the English description of the property number of seats (P1342): «number of seats/members in an assembly (legislative house or similar)». It can't be used to describe the member of an organization. What about non-political organizations? I changed the example to avoid confusion. --★ → Airon 90 08:26, 16 September 2015 (UTC)
- @Airon90: We are constantly redifining properties on Wikidata. Just go to the talk page of number of seats (P1342) and announce that you will change the label or add aliases to fit your use-case. If nobody diasagrees with you, then you can make the changes, ping a few translators and then you can go ahead and add the new statements. --Tobias1984 (talk) 09:47, 16 September 2015 (UTC)
- @Airon90: Let me clarify: there is no need for number of seats (P1342) to be so specific. As Tobias states, you can simply broaden it to allow for your use case here without needing to create a new property. Josh Baumgartner (talk) 18:41, 16 September 2015 (UTC)
- @Tobias1984, Joshbaumgartner: I Oppose to a redefinition of the property 1342 because - if so - it will be used in the same item with different meaning (member in institution (Parliament, EU, ...) and member of the party: in the old example there will be number of seats (P1342) → [37 (Eduskunta), 5 (EU), 41000 (membership)] ) and IMHO it is an incorrect use of a property. I don't think that this property is too specific or more specific tham P1342 simply because they covers two different areas. IMHO. :) --★ → Airon 90 18:48, 16 September 2015 (UTC)
- @Airon90: I can see your point on that, but I am not sure that is such a problem:
- @Tobias1984, Joshbaumgartner: I Oppose to a redefinition of the property 1342 because - if so - it will be used in the same item with different meaning (member in institution (Parliament, EU, ...) and member of the party: in the old example there will be number of seats (P1342) → [37 (Eduskunta), 5 (EU), 41000 (membership)] ) and IMHO it is an incorrect use of a property. I don't think that this property is too specific or more specific tham P1342 simply because they covers two different areas. IMHO. :) --★ → Airon 90 18:48, 16 September 2015 (UTC)
- @Joshbaumgartner: Did you read what I wrote above? Read the English description of the property number of seats (P1342): «number of seats/members in an assembly (legislative house or similar)». It can't be used to describe the member of an organization. What about non-political organizations? I changed the example to avoid confusion. --★ → Airon 90 08:26, 16 September 2015 (UTC)
- Support. Don't use number of seats (P1342). That has a specific meaning related to numbers elected to a council or parliament and should not be confused with general membership. That is why we have specific "member of" properties like member of sports team (P54) and member of political party (P102). Once this new proposal is accepted add a "subproperty of" statement to all the other "member of" properties. We should probably change the name of P1342 too to make it clearer what it refers to. Joe Filceolaire (talk) 12:12, 19 September 2015 (UTC)
- Comment it seems to the confusion in this discussion is due to the fact that someone changed the label (and implicitly the scope) of P1342 without any prior consultation. --- Jura 22:46, 28 September 2015 (UTC)
- @Tobias1984, Joshbaumgartner: Just a ping to know if you changed your mind now because of the label change. --★ → Airon 90 07:39, 29 September 2015 (UTC)
- Support Seems alright. number of seats (P1342) need not be so specific, but that shouldn't hold up this property at this point since fixing it doesn't seem to be in the cards. Josh Baumgartner (talk) 07:46, 29 September 2015 (UTC)
- Done Time to try this out and see if it works. --Tobias1984 (talk) 11:41, 29 September 2015 (UTC)
frame of reference for opposition
[edit]Description | qualifier for the property "opposite of" (P461) to define the context of the opposition |
---|---|
Data type | Item |
Domain | qualifier only on opposite of (P461) only |
Allowed values | items explaining the frame of reference/context for the opposition |
Example | female (Q6581072): opposite of (P461) → male (Q6581097): frame of reference for opposition: gender binary (Q5530970) |
- Comment This proposal is based on a suggestion by @AVRS: here. --- Jura 07:28, 28 August 2015 (UTC)
- Support Some of the opposites can't be understood without the context, or should be understood as oppositions within that context. --- Jura 07:45, 28 August 2015 (UTC)
- Comment The discussion on deleting opposite of (P461) is not closed. Please do not conclude this discussion before it is. author TomT0m / talk page
- Comment I proposed a solution using another property and the partion notion : humans are either men, women or transgender, which is well defined and more precise than this one. author TomT0m / talk page 09:28, 28 August 2015 (UTC)
- I suggest you use Wikipedia's talk page to comment on their POV. --- Jura 09:33, 28 August 2015 (UTC)
- What ? author TomT0m / talk page 12:05, 28 August 2015 (UTC)
- I suggest you use Wikipedia's talk page to comment on their POV. --- Jura 09:33, 28 August 2015 (UTC)
- Support Lymantria (talk) 12:29, 30 August 2015 (UTC)
- Hmm. I could support this as a general qualifier to give more info about properties ("Frame of reference" or "specifically" or something similar) but it probably won't be enough to convince me that opposite of (P461) as currently used is worth keeping. I just don't see women as the opposite of men when the en:intersex article list five different things that can define biological sex (not to mention the types of gender identity - have we figured out how to classify drag queens yet?). Joe Filceolaire (talk) 18:17, 31 August 2015 (UTC)
- The property has over 500 uses currently — certainly not mostly gender-related, although very many of them are "Films shot in …" vs "Films set in …" (?!). --AVRS (talk) 21:19, 6 September 2015 (UTC)
- Hey; you picked that as you example. Joe Filceolaire (talk) 22:25, 6 September 2015 (UTC)
- Not really. All I started was the creation of the property opposite of (P461) at Wikidata:Property_proposal/Archive/6#P461. I haven't even added it to "man" and "woman", but someone criticized it based on what others have done later, so I suggested a solution based on what is used for other properties, and Jura made this proposal based on it. --AVRS (talk) 10:09, 7 September 2015 (UTC)
- Hey; you picked that as you example. Joe Filceolaire (talk) 22:25, 6 September 2015 (UTC)
- The property has over 500 uses currently — certainly not mostly gender-related, although very many of them are "Films shot in …" vs "Films set in …" (?!). --AVRS (talk) 21:19, 6 September 2015 (UTC)
- Comment See also: P794 (P794) (an alternative to instance of (P31) for antipodes?), criterion used (P1013), present in work (P1441), from narrative universe (P1080), part of (P361). --AVRS (talk) 10:27, 7 September 2015 (UTC)
- Note that criterion used (P1013) currently has an incompatible definition at Property talk:P1013. For gender, determination method or standard (P459) seems better (if gender binary can be called a method; the English Wikipedia article calls it a classification). For antipodes, either P794 (P794) (still no better than instance of (P31)?) or criterion used (P1013). Also, IIRC, the list I presented is from searching for properties containing "as" or related to fiction. --AVRS (talk) 11:02, 13 September 2015 (UTC)
- Property:P1013 in English "criterion used" might be sufficient. --- Jura 10:45, 7 September 2015 (UTC)
- Oppose, use criterion used (P1013) Popcorndude (talk) 00:46, 8 September 2015 (UTC)
- Oppose. criterion used (P1013) sound better to me. Joe Filceolaire (talk) 20:55, 12 September 2015 (UTC)
- withdrawn using criterion used (P1013) instead. --- Jura 06:43, 26 September 2015 (UTC)
BC Geographical Names ID
[edit]Description | Unique ID of the BC Geographical Names (Q795716)} |
---|---|
Data type | String |
Template parameter | en:Template:BCGNIS: id = |
Domain | geographic location (Q2221906) |
Allowed values | d+ |
Example | Mount Fairweather (Q1544340) → 38638 |
Source | http://geobc.gov.bc.ca/base-mapping/atlas/bcnames/ |
Formatter URL | http://apps.gov.bc.ca/pub/bcgnws/names/$1.html |
- Motivation
This proprety is used on enwiki for as a sources for the coordinate and the origin of geographical names in British Columbia (Q1974) Fralambert (talk) 00:29, 24 August 2015 (UTC)
- Discussion
- Support --Pasleim (talk) 16:03, 25 August 2015 (UTC)
- Support Jonathan Groß (talk) 21:00, 17 September 2015 (UTC)
Banque de noms de lieux du Québec id
[edit]Description | the unique identifier for geographical names in Quebec |
---|---|
Data type | String |
Domain | geographic location (Q2221906) |
Allowed values | \d+ |
Example | Montreal (Q340) → 42164 |
Source | http://www.toponymie.gouv.qc.ca/ct/ToposWeb/recherche.aspx?avancer=oui |
Formatter URL | http://www.toponymie.gouv.qc.ca/ct/ToposWeb/fiche.aspx?no_seq=$1 |
- Motivation
Give the id of every place (event street) in Quebec (Q176). Fralambert (talk) 00:46, 24 August 2015 (UTC)
- Discussion
- Support --Pasleim (talk) 16:03, 25 August 2015 (UTC)
- Support Jonathan Groß (talk) 21:00, 17 September 2015 (UTC)
International Nuclear Event Scale
[edit]Description | INES level of this event |
---|---|
Represents | International Nuclear Event Scale (Q185657) |
Data type | Item |
Domain | nuclear incident (Q19960719), nuclear accident (Q1620824) |
Allowed values | level of INES scale (Q21012976) |
Example | Three Mile Island accident (Q840847) => INES level 5 event (Q21013003) ; Chernobyl disaster (Q486) => INES level 7 event (Q21013001) ; Roissy nuclear incident (Q3149899) => INES level 3 event (Q21013005) ; |
- Motivation
INES is an international reference for nuclear accident level measurement. Visite fortuitement prolongée (talk) 20:27, 21 May 2015 (UTC)
- Discussion
- Support --AmaryllisGardener talk 20:51, 21 May 2015 (UTC)
- Support Thryduulf (talk: local | en.wp | en.wikt) 22:52, 21 May 2015 (UTC)
- Support --- Jura 10:03, 24 May 2015 (UTC)
- I suggest changing the data-type to "item" and creating an item for each of the seven (?) possible values. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:08, 31 May 2015 (UTC)
- Reading the en.wp article, there are 8 (or possibly 9) values. The scale runs from 0-7 (least to most significant) and there is also an "out of scale" level that sits below 0 for events of "no safety relevance". As this seems to be used for events at or near nuclear facilities that do not involve anything radioactive I'm not sure we'd need an item for it. As the example events used by en.wp do not include any specific articles for events at levels 0 or 1, the need for an "out of scale" item seems limited. Although thinking about it, as one of the events at "Out of scale" was a "tornado sighting within the protected area of the nuclear power plant.", it is possible that a notable tornado event could have an "out of scale" impact on a nuclear facility. Thryduulf (talk: local | en.wp | en.wikt) 15:36, 2 June 2015 (UTC)
- Support --ComputerHotline (talk) 14:03, 5 June 2015 (UTC)
- Support -- NavinoEvans (talk) 11:35, 13 June 2015 (UTC)
- I agree with Andy that the datatype should be item rather than number. Filceolaire (talk) 17:37, 18 June 2015 (UTC)
- Item-datatype would indeed be better. @Visite fortuitement prolongée, AmaryllisGardener, Thryduulf, ComputerHotline, NavinoEvans: ok to change? --- Jura 12:20, 7 September 2015 (UTC)
- Definite yes from me, using items would be much better. NavinoEvans (talk) 16:05, 7 September 2015 (UTC)
- I am ok to that change. Visite fortuitement prolongée (talk) 20:48, 7 September 2015 (UTC)
- Yes. Need to decide whether to have an "Out of scale" event though. Thryduulf (talk: local | en.wp | en.wikt) 13:59, 9 September 2015 (UTC)
- You could use "novalue" for that, but you are probably better served with a dedicated item. In any case, I don't think that needs to be decided before creation. I updated the proposal to enable creation. --- Jura 07:48, 26 September 2015 (UTC)
- Done --Tobias1984 (talk) 12:05, 1 October 2015 (UTC)
Flash point
[edit]Description | lowest temperature at which it can vaporize to form an ignitable mixture in air. Add qualifier for measurement method: open cup or closed cup. Not equal to fire point. |
---|---|
Data type | quantity (units = Temperature)-invalid datatype (not in Module:i18n/datatype) |
Template parameter | fr:infobox chimie, en:chembox |
Domain | chemistry, physic |
Allowed values | number |
Proposed by | Snipre (talk) 12:12, 8 July 2013 (UTC) |
- Discussion
-
- Support --Tobias1984 (talk) 08:45, 19 July 2013 (UTC)
- Support --Jakob (Scream about the things I've broken) 15:26, 15 August 2013 (UTC)
- Support. datatype changed Joe Filceolaire (talk) 21:42, 12 September 2015 (UTC)
- Support necessary for chemical safety data. James Hare (NIOSH) (talk) 15:32, 24 September 2015 (UTC)
@Danrok, Kolja21, Pamputt, Pigsonthewing, Tobias1984: Is there a property creator for the creation of this property ? Thank you Snipre (talk) 21:04, 1 October 2015 (UTC)
- Done Sorry, The back-log is huge :) --Tobias1984 (talk) 21:37, 1 October 2015 (UTC)
focal length
[edit]Description | focal length of lens, generally in millimeters |
---|---|
Data type | number with units (when available)-invalid datatype (not in Module:i18n/datatype) |
Domain | lenses, cameras with built-in lenses, etc. |
Allowed values | items for specific formats |
Example | Universe (Q1) → Earth (Q2) |
Source | infobox, Freebase: https://www.freebase.com/digicams/digital_camera/wide_focal_length https://www.freebase.com/digicams/digital_camera/tele_focal_length |
- Support to import data from FB. --- Jura 13:18, 2 September 2015 (UTC)
- Support. Should be for large telescopes as well (most of these don't have lenses - they have parabolic mirrors. Joe Filceolaire (talk)
- Done --Tobias1984 (talk) 13:01, 4 October 2015 (UTC)
antiparticle
[edit]Description | elementary particle with the same mass and opposite charges |
---|---|
Data type | Item |
Domain | items which are subclass of elementary particle (Q43116) |
Example | electron (Q2225) → positron (Q3229) |
- Motivation
More specific than the vague opposite of (P461). Swpb (talk) 21:32, 24 September 2015 (UTC)
- Discussion
- Support clearly defined. author TomT0m / talk page 09:33, 28 September 2015 (UTC)
- Support Why not. Pamputt (talk) 09:14, 3 October 2015 (UTC)
- Done --Tobias1984 (talk) 13:12, 4 October 2015 (UTC)
Astronomical distance
[edit]Description | The distance to a (nearby) astronomical object. |
---|---|
Data type | Quantity |
Domain | astronomical objects with a negligible cosmological redshift |
Example | electron (Q2225) → positron (Q3229) |
MER-C (talk) 13:32, 8 February 2013 (UTC)
- Support --Paperoastro (talk) 14:58, 8 February 2013 (UTC)
Support -- MichaelSchoenitzer (talk) 01:19, 9 February 2013 (UTC)- Support - but it should it not be "distance from the Earth"? Njardarlogar (talk) 11:56, 21 February 2013 (UTC)
- Support it is necessary for infobox. Sunpriat (talk) 19:24, 6 October 2014 (UTC)
- Review voting
Do we really need a separate property for astronomical distance? Any distance property can take astronomical units. --Tobias1984 (talk) 10:46, 13 September 2015 (UTC)
- We have astronomical unit (Q1811) as a unit. That should be enough. But have we a generic distance property? --Succu (talk) 21:57, 25 September 2015 (UTC)
- Not done Not enough support in review process in my opinion. --Tobias1984 (talk) 13:18, 4 October 2015 (UTC)
IDLH
[edit]Description | the level of chemical exposure that can cause death or permanent adverse health effects |
---|---|
Represents | Immediately dangerous to life or health (Q682341) |
Data type | Number (not available yet) |
Template parameter | en:Template:Chembox Hazards parameter IDLH |
Domain | chemicals |
Allowed values | numbers with a unit of measurement such as gram per litre (Q834105) |
Example | methyl bromide (Q421758) → 0.0009725 gram per litre (Q834105) |
Source | Pocket Guide to Chemical Hazards, published by National Institute for Occupational Safety and Health (Q60346) |
Robot and gadget jobs | Part of future mass importation of the Pocket Guide to Chemical Hazards into Wikidata. |
- Motivation
This is part of a mass importation of data from the Pocket Guide to Chemical Hazards into Wikidata. James Hare (NIOSH) (talk) 23:51, 24 September 2015 (UTC)
- Discussion
- Already proposed and accepted. The proposal is pending. We just have to ask a property creator to do it. Snipre (talk) 23:17, 27 September 2015 (UTC)
- Done Property created now. Will archive the 2 proposals together. --Tobias1984 (talk) 21:46, 1 October 2015 (UTC)
molecular mass
[edit]Description | the mass of a molecule measured relative to the mass of carbon-12 |
---|---|
Represents | molecular mass (Q182854) |
Data type | Number (not available yet) |
Domain | types of items that may bear this property |
Allowed values | any integer or floating point number |
Example | methyl bromide (Q421758) has a molecular mass of 95.0 |
Source | Many chemical references, including the Pocket Guide to Chemical Hazards published by National Institute for Occupational Safety and Health (Q60346) |
Robot and gadget jobs | Future mass importation of the Pocket Guide to Chemical Hazards into Wikidata |
- Motivation
This property is part of a planned mass importation of data from the Pocket Guide to Chemical Hazards. Note that molecular mass is a dimensionless value measured relative to the molecular mass of Carbon-12 which is exactly 12. James Hare (NIOSH) (talk) 16:59, 24 September 2015 (UTC)
- Discussion
Notified participants of WikiProject Chemistry
- Comment Did you consider using this: diff ? --Tobias1984 (talk) 13:55, 27 September 2015 (UTC)
- Weak oppose I prefer to use the property mass. Snipre (talk) 11:19, 28 September 2015 (UTC)
- If the mass property can be used to represent molecular mass in AMUs (which appears to be the case), then that will work. James Hare (NIOSH) (talk) 13:33, 1 October 2015 (UTC)
- Not done Using generic mass property seems to work. --Tobias1984 (talk) 13:21, 4 October 2015 (UTC)
PubChem Substance ID (SID)
[edit]Description | Substance identifier in the PubChem database. |
---|---|
Domain | chemical substance (Q79529) |
Allowed values | number |
Example | zeolite Y (Q191326) → 135307179 |
Source | PubChem (Q278487) |
Formatter URL | https://pubchem.ncbi.nlm.nih.gov/substance/$1 |
- Motivation
The PubChem CID (P662) already exists and I would like to see the ability to tag substances in Wikidata with their PubChem SID. An example where it can be used is zeolite Y (Q191326) which is found in PubChem as SID 135307179. Nanomaterials are other examples, and I may wish to add a few of those too. Egon Willighagen (talk) 15:08, 20 September 2015 (UTC)
- Discussion
- Support --Tobias1984 (talk) 10:07, 24 September 2015 (UTC)
- Oppose Isn't PubChem CID (P662) sufficient? SID is hardly ever linked to in Wikipedias AFAIK. --Leyo 22:15, 24 September 2015 (UTC)
- @leyo: The difference between compound and substance is that the former represents a defined unique entity of covalently bound atoms, whereas the latter is a defined mixture of 2 or more chemical compounds in a certain ratio. They exclude each other which makes it hard to link to Pubchem from WD chemicals substance items, as there is no property ID for them. Sebotic (talk) 05:57, 30 September 2015 (UTC)
- @Sebotic: : please note that some definitions, a compound is a substance. For example in the definition of the UIPAC for chemical elements, an elements is defined as a type of substances (see http://goldbook.iupac.org/C01022.html ). So we must sort out the mess created one way or another. The ways I see : either involves making enwiki change its definition a little bit (difficult, I tried), or define clearly each items and link all articles to the right one. I plan to do this but I feel a little alone at this time for such a task atm. :) author TomT0m / talk page 09:05, 30 September 2015 (UTC)
- @leyo: The difference between compound and substance is that the former represents a defined unique entity of covalently bound atoms, whereas the latter is a defined mixture of 2 or more chemical compounds in a certain ratio. They exclude each other which makes it hard to link to Pubchem from WD chemicals substance items, as there is no property ID for them. Sebotic (talk) 05:57, 30 September 2015 (UTC)
- Support Sebotic (talk) 05:57, 30 September 2015 (UTC)
- Support lv_ra (talk) 14:23, 30 September 2015 (UTC)
- Done --Tobias1984 (talk) 13:24, 4 October 2015 (UTC)
Binding energy
[edit]Description | energy required to disassemble a whole system into separate parts |
---|---|
Represents | binding energy (Q420754) |
Data type | Quantity |
Template parameter | "binding_energy" in en:Modèle:Infobox isotope |
Domain | nuclear isotope |
Example | carbon-12 (Q1058364) → 92161.753± 0.014 keV |
- Motivation
Property needed for isotope infobox. Pamputt (talk) 09:31, 3 October 2015 (UTC)
- Discussion
- Done Fasttracking: Straightforward and included in many inforboxes. --Tobias1984 (talk) 13:32, 4 October 2015 (UTC)
Solid solution series with
[edit]Description | the mineral forms a continous or discontinous "solid solution series" with another mineral |
---|---|
Represents | solid solution (Q787619) |
Data type | Item |
Template parameter | put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement |
Domain | Q templates |
Allowed values | valid minerals |
Example | chrysoberyl-mariinskite series; chrysoberyl forms a series with mariinskite and vice-e-versa; hedenbergite-petedunnite; hedenbergite forms a series with petedunnite and vice-e-versa |
Format and edit filter validation | (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17) |
Source | mindat.org (Q15221937) - [2] |
Robot and gadget jobs | no |
Proposed by | Chris.urs-o (talk) |
- Discussion
(Add your motivation for this property here.) Chris.urs-o (talk) 06:47, 4 January 2015 (UTC)
- @Snipre: --Tobias1984 (talk) 08:13, 7 January 2015 (UTC)
- Sorry too specific for me. I have only knowledge in chemistry and engineering stuff. Snipre (talk) 12:40, 7 January 2015 (UTC)
- Support Looks useful. --Tobias1984 (talk) 08:13, 7 January 2015 (UTC)
- Support. Joe Filceolaire (talk) 18:14, 4 August 2015 (UTC)
- Done --Tobias1984 (talk) 13:59, 4 October 2015 (UTC)
Pseudo crystal habit
[edit]Description | the chemical compound may seem to have a higher symmetry |
---|---|
Data type | Item |
Template parameter | put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement |
Domain | Q templates |
Allowed values | pseudomonoclinic, pseudoorthorhombic, pseudotetragonal, pseudotrigonal, pseudohexagonal, pseudocubic |
Example | Leucite and CdCl2 have a orthorhombic crystal symmetry, but they show a pseudo cubic crystal habit |
Format and edit filter validation | (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17) |
Source | mineralienatlas.de, mindat.org, Athena |
Robot and gadget jobs | no |
Proposed by | Chris.urs-o (talk) |
- Discussion
(@Sbisolo:, @Tobias1984:, @John Mortimore:; it could be a subproperty of habitus; it is important to know that a mineral appears to have a higher symmetry although it is not perfect) Chris.urs-o (talk) 07:23, 4 January 2015 (UTC)
- Comment I am wondering if it is also possible to query this. A mineral has a crystal structure that links to a symmetry. The habit of a mineral also has a symmetry. If the symmetries don't match, then the habit is called e.g. pseudocubic. But maybe this explicit approach would be good too. --Tobias1984 (talk) 08:16, 7 January 2015 (UTC)
- @Chris.urs-o: Please show how you example would work; i.e. what value would be entered? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:49, 9 March 2015 (UTC)
- Ok, let's try. The crystal system is a physical characteristic determined in the laboratory. The habit is a visual appearance of the species sample. I suppose that the pseudocrystal habit would be a subproperty of habit.
- Halit (NaCl) has a cubic symmetry, with following cell parameters: a =5.6404(1) Å =b =c and α=90° =β =γ
- Analcime (Na2(Al2Si4O12) · 2H2O) has a triclinic symmetry, but it always looks pseudocubic. Cell parameters: a =13.723 to 13.733 Å =b =c
- Boracite (Mg3(B7O13)Cl) has a orthorhombic symmetry, but often a pseudocubic morphology. Cell parameters: a = 8.577(6) Å, b = 8.553(8) Å, c = 12.09(1) Å
- Perovskite (CaTiO3) has a orthorhombic symmetry, but often a pseudocubic morphology. Cell parameters: a = 5.447(1) Å, b = 7.654(1) Å, c = 5.388(1) Å
- Bernalite (Fe(OH)3 · nH2O (n = 0.0 to 0.25)) has a orthorhombic symmetry. Morphology: flattened pyramidal crystals, pseudo-octahedral to pseudo-cubic. Cell parameters: a = 7.544 Å, b = 7.56 Å, c = 7.558 Å
- Pertlikite (K2(Fe2+,Mg)2Mg4Fe23+Al(SO4)12 · 18H2O) has a tetragonal symmetry, but often a pseudocubic morphology. Cell parameters: a = 19.2080 Å, c = 27.2158 Å
- Regards --Chris.urs-o (talk) 05:57, 10 March 2015 (UTC)
- Chris.urs-o have you discussed with collaboration with mindat.org? Their web site says their info is copyright but it is sponsored by an academic institution and says its info is provided by thousands of volunteers so it may be willing to let us have their info. Either way if any of our properties are meant to duplicate theirs (do they publish an ontology?) we should note this. Joe Filceolaire (talk) 18:04, 2 August 2015 (UTC)
- We are not duplicating, identifiers are not a problem yet. It is easier to cite MinDat. Nickel-Strunz 9 ed (updated 2009) is based on a very old PDF file of 2009. It can not be copied & pasted, but Nickel-Strunz 10 ed (MinDat) is very similar. Strunz 8 ed (MinDat/ Athena/ Lapis) is based on Strunz 8 ed (printed). I did not know, that it is a modified version, I assumed it is the same. Karl H. Strunz (1910–2006) allowed the use of Strunz 8 ed (printed) on Athena. Nickel-Strunz 9 ed (updated 2009) is a courtesy of Ernest H. Nickel (1925–2009) & Monte C. Nichols (1938–2014), Minerals Data, Inc.. Nickel-Strunz 10 ed (webmineral.com) is an update of Nickel-Strunz 9 ed (updated 2009), it is a courtesy of James A. Ferraiolo. Nickel-Strunz 10 ed (MinDat) is a minor modification of Nickel-Strunz 10 ed (webmineral.com), it excludes discredited minerals for example. English Wikipedia uses this identifier. IMA-CNMNC Newsletter (Wikidata:WikiProject Mineralogy/IMA number references#CNMNC/ CNMMN site) publishes mineral group, type locality, crystal system and space group of a new mineral many times, original literatur is available on: [3]. The main task right now is finding valid minerals on Wikidata but "lost in space", and listing and administrating them on Wikidata:WikiProject Mineralogy/Mineral list#Sortable lists of Nickel-Strunz identifiers. I'm using MinDat to administrate property named after, but there is webmineral.com and a PDF file available, as well. I was thinking of editing very notable minerals, but I do not have editing capacity. Regards --Chris.urs-o (talk) 02:37, 3 August 2015 (UTC)
- Notes:
- Strunz 8 ed (printed) > Strunz 8 ed (Athena)/Strunz 8 ed (Lapis) > Strunz 8 ed (MinDat)
- Nickel-Strunz 9 ed (printed) > Nickel-Strunz 9 ed (updated 2009) > Nickel-Strunz 10 ed (James A. Ferraiolo) > Nickel-Strunz 10 ed (MinDat)
- I have not these books at home:
- Strunz, Hugo; Nickel, Ernest H. (2001). Strunz Mineralogical Tables (9 ed.). Stuttgart: Schweizerbart. p. 870. ISBN 978-3-510-65188-7
- Strunz, Hugo (1982). Mineralogische Tabellen (in German) (8 ed.). Leipzig: Akademische Verlagsgesellschaft Geest. u. Portig. p. 621
- Weiß, Stefan (2008). Das Große Lapis-Mineralienverzeichnis
- Regards --Chris.urs-o (talk) 07:41, 4 August 2015 (UTC)
- Support. Joe Filceolaire (talk) 18:14, 4 August 2015 (UTC)
- Done I think this is something that needs to tried out. --Tobias1984 (talk) 14:10, 4 October 2015 (UTC)
Kernel version
[edit]Description | put English description for property here, e.g. same as in the infobox documentation |
---|---|
Represents | Linux kernel (Q14579) |
Data type | String |
Domain | Linux and BSD distributions |
Allowed values | Valid version numbers |
Example | Debian (Q7593): software version identifier (P348) => 7 with qualifier "kernel version" => 3.2.41 |
Source | Distribution mailing lists |
Proposed by | --Tobias1984 (talk) 21:53, 1 December 2014 (UTC) |
- Discussion
WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --Tobias1984 (talk) 21:53, 1 December 2014 (UTC)
- This seems like an overly specific property. Wouldn't it be better to create a more general property that lists the packages supplied by a distribution, with the version number as a qualifier? (This would also imply making an item for each major version of a distribution. Also, some distributions ship multiple kernel versions over their lifetime, which I think would be difficult to express if kernel version already is a qualifier.) —Ruud 16:51, 19 December 2014 (UTC)
- Oppose @Tobias1984:I would rather see the use of the has part(s) (P527) property with a qualifier "version", or directly a "linux 3.2.41" item, subclass of "linux" or something, with a "version" statement.
- Comment You can’t put qualifiers on qualifiers, so in the above example, this would require a separate item for Debian 7. —DSGalaktos (talk) 12:32, 28 March 2015 (UTC)
- @DSGalaktos, Tobias1984: WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. : I think it would be better to use items for software versions, Python2.6 is an edition of python, for example, and that would make us aligned with Wikidata:WikiProject Books. TomT0m (talk) 12:11, 6 June 2015 (UTC)
- Comment You can’t put qualifiers on qualifiers, so in the above example, this would require a separate item for Debian 7. —DSGalaktos (talk) 12:32, 28 March 2015 (UTC)
- Items for software versions would mean we create a new item for notepad++ 6.8.7.2 and InternetExplorer 11.0.9600.17801? --Pasleim (talk) 22:44, 6 June 2015 (UTC)
- @Pasleim: I guess that when there is a lot of releases it's way overkill to go up to minor patch versions. But I guess not all of them are published anyway, even in that case there would not be 17801 items for 11.0.9600 :) If we would not maintain a history of versions with version Search, nobody would create all the items anyway, except if this is done automatically. So I don't think we really have to worry about that. What we would gain is that when several distros includes Linux 4.2.1, we just have to say and not and , that we will be able to put statements about Linux 4.2.1, for example added feature, and regularity of the model, so less special cases in query or in infobox templates. TomT0m (talk) 11:33, 7 June 2015 (UTC)
- @TomT0m, Pasleim: Notability for software releases is a really difficult topic. If we make items for versions will also mean that we run 2 approaches parallel. In any case we can only gather data about programs that have some kind of written release information. But we also need to ignore the bugfix releases if we want to keep the whole system manageable. Wikidata is also really bad for inputting long lists of data into a single property, which makes version history editing difficult. --Tobias1984 (talk) 15:44, 7 June 2015 (UTC)
- @Tobias1984: Why would that be difficult ? We can make it very simple if we want. Like I said, it's not because we create items that the history on software that we will store be longer than if we do not. It's a separate question. It's because (hypothetically) we chose the create items solution that this will modify the number of statements per page. TomT0m (talk) 16:42, 7 June 2015 (UTC)
- @TomT0m, Pasleim: Notability for software releases is a really difficult topic. If we make items for versions will also mean that we run 2 approaches parallel. In any case we can only gather data about programs that have some kind of written release information. But we also need to ignore the bugfix releases if we want to keep the whole system manageable. Wikidata is also really bad for inputting long lists of data into a single property, which makes version history editing difficult. --Tobias1984 (talk) 15:44, 7 June 2015 (UTC)
- @Pasleim: I guess that when there is a lot of releases it's way overkill to go up to minor patch versions. But I guess not all of them are published anyway, even in that case there would not be 17801 items for 11.0.9600 :) If we would not maintain a history of versions with version Search, nobody would create all the items anyway, except if this is done automatically. So I don't think we really have to worry about that. What we would gain is that when several distros includes Linux 4.2.1, we just have to say and not and , that we will be able to put statements about Linux 4.2.1, for example added feature, and regularity of the model, so less special cases in query or in infobox templates. TomT0m (talk) 11:33, 7 June 2015 (UTC)
- Not done Not enough support. --Tobias1984 (talk) 14:11, 4 October 2015 (UTC)
Lithography
[edit]Description | lithography in nanometers |
---|---|
Data type | Item |
Domain | central processing unit (Q5300) / electronic circuit (Q1815901) |
Allowed values | 22, 32, 45, 65, 90, 130, 180, 250. |
Example | Xeon 3040 (Q15229424) : 65 nm |
Source | Intel website, for Intel processors |
Robot and gadget jobs | Robots can gather info on the Intel website and fill the property with it. |
Proposed by | MisterSanderson (talk) |
- Discussion
I want to add information to the CPU items, but there aren't enough properties to that. MisterSanderson (talk) 00:48, 25 November 2013 (UTC)
- changed datatype. Filceolaire (talk) 22:44, 25 November 2013 (UTC)
- Why "number with dimension" instead of simply "number"?--MisterSanderson (talk) 00:48, 26 November 2013 (UTC)
- Because this is a measurement of length. Remember that while current processors are measured in nanometers past processors were measured in micrometers and future processors will be measured in picometers. Filceolaire (talk) 07:46, 30 November 2013 (UTC)
- Given the diameter of a silicon atom (over 0.2 nm), I think it will be fairly unlikely that we will ever need the measure lithographic processes in picometers ;) —Ruud 17:29, 19 December 2014 (UTC)
- Because this is a measurement of length. Remember that while current processors are measured in nanometers past processors were measured in micrometers and future processors will be measured in picometers. Filceolaire (talk) 07:46, 30 November 2013 (UTC)
- Why "number with dimension" instead of simply "number"?--MisterSanderson (talk) 00:48, 26 November 2013 (UTC)
- Support the dimension would be the physical unit "meter". I think everybody uses simply number because the other thing doesn't seem to work with the template. --Tobias1984 (talk) 16:04, 27 November 2013 (UTC)
- What about AMD?--Kopiersperre (talk) 13:38, 11 November 2014 (UTC)
- @Kopiersperre: I am not an expert where else this measurement is used, but I think the domain "semiconductors" would probably sum it up? --Tobias1984 (talk) 22:02, 21 November 2014 (UTC)
- @Tobias1984: I must point out, that a 22 nm processor does not have any element, which is 22 nm long. (See Keine 14-Nanometer-Struktur in Broadwell) --Kopiersperre (talk) 14:10, 23 November 2014 (UTC)
- @Kopiersperre: That certainly makes things more complicated. In that case we should rely on independent measurements and not the marketing words. Maybe even require a qualifier that states how the measurement was made (e.g. with an ion probe). --Tobias1984 (talk) 15:02, 23 November 2014 (UTC)
- I think what Kopiersperre means is that the term "22 nm" is the name of a particular lithographic process (sometimes it's qualified by the name of the semiconductor foundry), and should not be directly interpreted as a physical quantity (nor should we try to make it into one by relying on "independent measurements"). We can be pragmatic and make it into a number with dimension as the names of lithographic processes have always followed the convention of being a number followed by "micrometer" or "nanometer". —Ruud 17:00, 19 December 2014 (UTC)
- Actually, Wikipedia already has articles on the various processes and Wikidata thus has items on them: 22 nm lithography process (Q1059061), 1.5 µm lithography process (Q1135912), Category:International Technology Roadmap for Semiconductors lithography nodes (Q7003854), ... We should probably link them to those instead. —Ruud 17:22, 19 December 2014 (UTC)
- @Ruud Koot: - It might be a good idea to make this an item-datatype instead. That way we can avoid the situation described by User:Kopiersperre. --Tobias1984 (talk) 20:35, 19 December 2014 (UTC)
- @Kopiersperre: That certainly makes things more complicated. In that case we should rely on independent measurements and not the marketing words. Maybe even require a qualifier that states how the measurement was made (e.g. with an ion probe). --Tobias1984 (talk) 15:02, 23 November 2014 (UTC)
- @Tobias1984: I must point out, that a 22 nm processor does not have any element, which is 22 nm long. (See Keine 14-Nanometer-Struktur in Broadwell) --Kopiersperre (talk) 14:10, 23 November 2014 (UTC)
- @Kopiersperre: I am not an expert where else this measurement is used, but I think the domain "semiconductors" would probably sum it up? --Tobias1984 (talk) 22:02, 21 November 2014 (UTC)
- What about AMD?--Kopiersperre (talk) 13:38, 11 November 2014 (UTC)
- Support with datatype 'item'. Joe Filceolaire (talk) 15:47, 2 August 2015 (UTC)
- Done --Tobias1984 (talk) 14:17, 4 October 2015 (UTC)
Listed in PackageIndex
[edit]Description | Many programs available for Linux have public listings of their packages. Connecting to these indexes would allow to check up on version numbers using bots. |
---|---|
Data type | URL |
Template parameter | ? |
Domain | software |
Allowed values | Valid package indexes or repositories |
Example | Inkscape (Q8041) → "https://apps.fedoraproject.org/packages/inkscape" (+Qualifier: Fedora), "https://launchpad.net/ubuntu/+source/inkscape" (+Qualifier Ubuntu) |
- Motivation
As usual this should improve Wikidatas interlinking between relevant software pages. Bots can use these pages to check if a newer version of a program exists. --Tobias1984 (talk) 21:35, 12 June 2015 (UTC)
- Discussion
- Comment @Tobias1984: I think it's a good idea, I would however prefer a different model, for example a more generic property. Either part of (P361) qualified with a package index reference qualifier, or something like a packaged in/by property instead of has part. What do you think ? TomT0m (talk) 10:48, 9 July 2015 (UTC)
WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
- @TomT0m: - I think using part of (P361) in this case would dilute the meaning of the property too much. Maybe something like "is listed in" would be better for this case. --Tobias1984 (talk) 21:01, 9 July 2015 (UTC)
- @Tobias1984: I don't think so, a software is a part of a distribution. As a consequence it has a package and a package url in the distribution website. This is the semantics of part of, nothing more, nothing less ... author TomT0m / talk page 08:36, 3 August 2015 (UTC)
@Tobias1984: I suggest separate properties for every distro. For ArchLinux a qualifier wouldn't be enough, because it has normal packages (e.g. https://www.archlinux.org/packages/extra/x86_64/inkscape/) and the Arch User Repository (Q17521339) (e.g. https://aur.archlinux.org/packages/atom-editor-git/).--Kopiersperre (talk) 12:24, 14 September 2015 (UTC)
- @Kopiersperre: I don't think this is a good idea, this is not a flexible solution. I would suggest, if the part of solution is not accepted, to use with qualifiers such as package url or catalog url. author TomT0m / talk page 12:38, 14 September 2015 (UTC)
I would Support a packaged in with a distribution range and a software domain, with the qualifiers package url and cataog url. ( WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. because this must be settled at some point). author TomT0m / talk page 12:38, 14 September 2015 (UTC)
- Not done Not enough support. --Tobias1984 (talk) 14:19, 4 October 2015 (UTC)
Cell line ontology ID
[edit]Description | Identifier for an ontology which describes anatomic origin and nature of eukaryotic cell lines. |
---|---|
Represents | Cell line Ontology (Q21039006) |
Data type | String |
Domain | biology and medicine |
Allowed values | CLO_0000000 - CLO_9999999 |
Example | Jurkat (Q1632589) → CLO_0007043 |
Format and edit filter validation | 'CLO_' as prefix followed by seven digits |
Source | http://www.clo-ontology.org/ |
Formatter URL | http://purl.obolibrary.org/obo/$1 |
Robot and gadget jobs | ProteinBoxBot will add these IDs |
- Motivation
Cell lines are an essential tool for biology and medicine. CLO is currently the only ontology which systematically orders and issues IDs to cell lines. Having the CLO IDs in Wikidata would help representing cell lines in WD and to link them with other ontologies like UBERON and MeSH. Sebotic (talk) 09:49, 2 October 2015 (UTC)
- Discussion
- Support --Tobias1984 (talk) 10:17, 2 October 2015 (UTC)
- Support Andrew Su (talk) 15:19, 2 October 2015 (UTC)
- Support lv_ra (talk) 16:06, 2 October 2015 (UTC)
- Support Could be a very useful. Has value for in vitro drug studies, or antibody production. Gtsulab (talk) 17:46, 2 October 2015 (UTC)
- Support --I9606 (talk) 18:15, 2 October 2015 (UTC)
- Done --Tobias1984 (talk) 14:23, 4 October 2015 (UTC)
solves
[edit]Description | the subject is an algorithm or a method to solve a type of problem |
---|---|
Represents | problem solving (Q730920) |
Data type | Item |
Domain | algorithm (Q8366) , maybe other heuristic or non mathematical problem solving methods |
Allowed values | computational problem (Q3435924) , others ? |
Example | DPLL algorithm (Q2030088) → boolean satisfiability problem (Q875276), , ... |
- Motivation
A defining property of algorithms. TomT0m (talk) 15:41, 1 July 2015 (UTC)
- Discussion
- WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. (fixed). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:41, 10 July 2015 (UTC)
Support I am not very familiar with wikidata, so this shouldn't be considered as an important support. Nevertheless, I am very familiar with algorithms (you can check my edits on the wikipedia in French), and I think this relation makes a lot of sense.--Roll-Morton (talk) 13:06, 28 September 2015 (UTC)
Support This seems like a useful property. The infoxbox Template:Infobox algorithm (Q5910871) in various languages has the parameter class which seems to correspond to this property although sometimes that seems to be just the class of algorithm (as in search algorithm), rather than the problem solved. Silverfish (talk) 21:47, 30 September 2015 (UTC)
- Done --Tobias1984 (talk) 14:28, 4 October 2015 (UTC)
Mass excess
[edit]Description | difference between its actual mass and its mass number in atomic mass units. |
---|---|
Represents | mass excess (Q1571163) |
Data type | Quantity |
Template parameter | "excess_energy" in en:Modèle:Infobox isotope |
Domain | nuclear isotope |
Example | deuterium (Q102296) → 13135.720 ± 0.001 |
- Motivation
Property needed for isotope infobox. Pamputt (talk) 09:31, 3 October 2015 (UTC)
- Discussion
- Done Fasttracking. Included in many infoboxes and well defined. --Tobias1984 (talk) 14:37, 4 October 2015 (UTC)
YerelNet village ID
[edit]Template parameter | Now ID is in references links. After transferring all IDs to WD, I will add a YerelNet link in tr:w:Türkiye köy bilgi kutusu(Turkey village infobox) with arbitrary access. |
---|---|
Allowed values | 6 digit number bigger than 200000 |
Source | external reference, Wikipedia list article, etc. |
Robot and gadget jobs | A bot created all village article in TRwiki from YerelNet. Now I will use it for updating and adding new infos. |
- Motivation
YerelNet is a government(Republic of Turkey Ministry of Development) funded portal contains informations about all 18.335 village. We used YerelNet for creating village articles in 2007. It is our main source of information about villages. Now there is YerelNet links in References/External links section contains IDs but some of them deleted by users. I wanna store all IDs in WD so we can keep it secure. Mavrikant (talk) 13:02, 18 September 2015 (UTC)
- Discussion
- Support --Elmacenderesi (talk) 14:21, 24 September 2015 (UTC)
- Support Please confirm urgently. McAang (talk) 09:27, 26 September 2015 (UTC)
- Support--HakanIST (talk) 20:05, 26 September 2015 (UTC)
- SupportZaitsév (talk) 20:16, 26 September 2015 (UTC)
- Support Uğurkent (talk) 15:21, 27 September 2015 (UTC)
@Mavrikant, Elmacenderesi, McAang, HakanIST, Zaitsév, Uğurkent: Done YerelNet village ID (P2123). Datatype is "sting", as is standard. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:13, 28 September 2015 (UTC)
CrunchBase person ID
[edit]Domain | people |
---|---|
Allowed values | Valid CrunchBase URL slugs |
Source | Wikipedia external links |
- Motivation
Useful and widely-used database. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:03, 17 August 2015 (UTC)
- Discussion
What about organizations? Would it make sense to format the values like this?:
--Floscher (talk) 11:43, 21 August 2015 (UTC)
- Support but rename to Crunchbase person ID then we can make a Crunchbase organisation ID too. Joe Filceolaire (talk) 17:52, 21 August 2015 (UTC)
- Agreed; see below. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:25, 26 August 2015 (UTC)
- Support --Vladimir Alexiev (talk) 09:26, 18 September 2015 (UTC)
@Floscher, Filceolaire, Vladimir Alexiev: Done Crunchbase person ID (P2087) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:37, 20 September 2015 (UTC)
CrunchBase organisation ID
[edit]Domain | organisations |
---|---|
Allowed values | Valid CrunchBase URL slugs |
Source | Wikipedia external links |
- Motivation
Useful and widely-used database. Per above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:30, 26 August 2015 (UTC)
- Support. Joe Filceolaire (talk) 22:15, 26 August 2015 (UTC)
- Support --Vladimir Alexiev (talk) 09:26, 18 September 2015 (UTC)
@Filceolaire, Vladimir Alexiev: Done Crunchbase organization ID (P2088) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:47, 20 September 2015 (UTC)
Library of Congress JukeBox ID
[edit]Description | Library of Congress JukeBox ID |
---|---|
Domain | people |
Allowed values | numerical |
Robot and gadget jobs | A bot would have to be written to match the entries |
- Motivation
The Library of Congress JukeBox ID contains a list of available recordings by early singers. The list has over 10,000 recordings and is expanding. Sadly the Jukebox ID is not currently linked to the LCCN. Richard Arthur Norton (1958- ) (talk) 02:01, 28 August 2015 (UTC)
- Discussion
@Richard Arthur Norton (1958- ): Done Library of Congress JukeBox ID (former scheme) (P2089). DAta type is string, as is standard for identifiers. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:02, 20 September 2015 (UTC)
Power of 10 athlete ID
[edit]- Motivation
Power of 10 (Q20892680) is the reference database for athletes from the United Kingdom. It is used by Template:Power of 10 (Q20892684) and its profiles for specific athletes are already called 280 times on the English Wikipedia, 201 times on the German Wikipedia, 22 times on the French Wikipedia, etc. Thierry Caro (talk) 23:36, 30 August 2015 (UTC)
- Discussion
- Support. Joe Filceolaire (talk) 21:43, 6 September 2015 (UTC)
@Thierry Caro, Filceolaire: Done Power of 10 athlete ID (P2090) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:12, 20 September 2015 (UTC)
FISA ID
[edit]Template parameter | used in local templates of Template:World Rowing (Q14334032) |
---|---|
Domain | people |
Allowed values | FISA uses numerical values (1 to 5 digits at the moment, might be 6 at some point in the future); string datatype because it’s an identifier rather than a quantifier |
Format and edit filter validation | ^[\d]{1,6}$ — unique value (each ID must not be used for more than one item) — single statement with exceptions (typically there is only one ID per person, but there are some rare exceptions from this rule) |
Source | IDs are going to be imported from local templates (Template:World Rowing (Q14334032)) and the database itself |
- Motivation
For the sports of rowing, FISA’s database at www.worldrowing.com/athletes/ is one of the most important sources for biographies (personal data and competition results). It currently contains ~45.000 entries of rowers that competed at the Summer Olympics, World Rowing Championships, Continental Championships, World Rowing Cup, and some other competitions that are not important here.
Until now, the rower ID is saved and used in local templates (Template:World Rowing (Q14334032)), but not on Wikidata. Wikidata has items for more than 4000 rowers, mostly competitors of the Olympics, World Champs or European Champs, and most of them could easily be equipped with their FISA ID in this property. I already have a large list that I could import to Wikidata using Quick Statements, once this property is created. Similar properties are listed in Template:Sports properties. —MisterSynergy (talk) 19:03, 4 September 2015 (UTC)
- Discussion
- The URL format should be http://www.worldrowing.com/athletes/athlete/$1, and then Support. Thierry Caro (talk) 14:58, 5 September 2015 (UTC)
- Thanks for your support. For which reason do you want to change the URL format? —MisterSynergy (talk) 15:48, 5 September 2015 (UTC)
- It is the landpage. Thierry Caro (talk) 08:11, 6 September 2015 (UTC)
- Ok, I understand. The proposed URL contains much more useful information about competition results, thus I tought it would be better to use it rather than the landig page. However, I wouldn’t mind changing it (and did so in the proposal box above). —MisterSynergy (talk) 08:29, 6 September 2015 (UTC)
- It is the landpage. Thierry Caro (talk) 08:11, 6 September 2015 (UTC)
- Thanks for your support. For which reason do you want to change the URL format? —MisterSynergy (talk) 15:48, 5 September 2015 (UTC)
- Being an identifier, I'd suggest a string datatype. That's the only thing I'd change, generally you have my Support. Sannita - not just another it.wiki sysop 10:21, 6 September 2015 (UTC)
- Thanks for advice and support. I’ve changed the proposed datatype to “string”. —MisterSynergy (talk) 10:46, 6 September 2015 (UTC)
- Support. Joe Filceolaire (talk) 21:45, 6 September 2015 (UTC)
- Thanks for your support. —MisterSynergy (talk) 13:42, 7 September 2015 (UTC)
- Question: Would it be necessary to link a “subject item” (not yet proposed)? If so, which would be the advantages? Can we use World Rowing (Q684885) or shall I create a new item “Worldrowing database” (or similar)? —MisterSynergy (talk) 13:42, 7 September 2015 (UTC)
I tried to add this and some other things to the proposal, but that failed. See [4], —MisterSynergy (talk) 14:18, 7 September 2015 (UTC)Works now. —MisterSynergy (talk) 06:38, 8 September 2015 (UTC)
- Okay, no answer for quite some time… There is World Rowing (Q684885) given as “subject item” at the moment, and this seems to be okay if compared to other similar properties. What else do we have to do for property creation? —MisterSynergy (talk) 18:55, 17 September 2015 (UTC)
@MisterSynergy, Thierry Caro, Sannita, Filceolaire: Done World Rowing ID (P2091) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:30, 20 September 2015 (UTC)
Guthrie code
[edit]Description | Guthrie code of a Bantu language |
---|---|
Represents | Guthrie classification of Bantu languages (Q5621787) |
Data type | String |
Template parameter | « guthrie » in en:Template:Infobox language |
Domain | language |
Allowed values | [A-S][0-1000][A-Z] |
Example | Ngoni (Q7022547) → N12 |
Source | http://goto.glocalnet.net/mahopapers/nuglonline.pdf |
- Motivation
Guthrie code is a parameter of language infobox and is rather common in Bantu languages work. Pamputt (talk) 22:58, 14 July 2015 (UTC)
- Discussion
Support. Joe Filceolaire (talk) 17:32, 21 August 2015 (UTC)
Deutsche Ultramarathon-Vereinigung ID
[edit]Description | Identifier for individual runners inside Deutsche Ultramarathon-Vereinigung (Q1204310)'s database. |
---|---|
Represents | Deutsche Ultramarathon-Vereinigung (Q1204310) |
Data type | String |
Domain | people |
Example | Kathy D'Onofrio-Wood (Q20745593) → 27314 |
Source | http://statistik.d-u-v.org |
Formatter URL | http://statistik.d-u-v.org/getresultperson.php?runner=$1 |
- Motivation
Deutsche Ultramarathon-Vereinigung (Q1204310)'s database is the best one about ultramarathon (Q26303). As I write this message, it includes 693433 runners that each have their own ID there and most of the time don't have a World Athletics athlete ID (P1146). Thierry Caro (talk) 12:01, 3 August 2015 (UTC)
- Discussion
- Support Très bonne idée, ça pourrait nous permettre de faire également un modèle de lien externe généré uniquement par Wikidata comme ProCyclingStats. Jérémy-Günther-Heinz Jähnick (talk) 12:44, 3 August 2015 (UTC)
Comment Please, this is already quite used on frwiki, where we have fr:Modèle:DUV to generate such links. Thierry Caro (talk) 19:58, 23 August 2015 (UTC)
FAST-ID
[edit]Description | authority control identifier in WorldCat's “FAST Linked Data” authority file |
---|---|
Represents | Faceted Application of Subject Terminology (Q3294867) |
Data type | String |
Domain | people, corporations, events, topics, geographic entities, … |
Allowed values | [1-9][0-9]* |
Example | |
Source | e.g. VIAF adds FAST-IDs to their clusters |
Formatter URL | http://id.worldcat.org/fast/$1 |
- Motivation
I saw that this ID is present in VIAF clusters but not here in Wikidata. It could be used to differentiate between similar items. For importing statements, I guess the license (Open Data Commons Attribution) is not compatible. But I'd still find it useful to at least have another authority control ID to add to Wikidata items.
The FAST authority file is derived from the Library of Congress Subject Headings (Q1823134), so it should be possible to automatically add FAST-IDs to Wikidata-items which already have Library of Congress authority ID (P244) set. --Floscher (talk) 12:05, 13 August 2015 (UTC)
- Discussion
- This seems premature as the urls redirect to http://experimental.worldcat.org/fast/1204829/ I suspect that if it is an "authority" that we wish for it to come out of an experimental phase. — billinghurst sDrewth 01:38, 17 August 2015 (UTC)
- As far as I understand it, the linked data viewer is in experimental phase, not the complete authority file. The FAST authority file is developed since 1998 and when they published it as linked data last year, the authority file got this new interface (see [5] for details). That's probably the reason why it is hosted on http://experimental.worldcat.org . --Floscher (talk) 11:51, 17 August 2015 (UTC)
- Support. Remember that the reason we have a formatter url and a reference string instead of just a url for each item is so that we can easily manage changes such as might happen if this gets moved to a different server. Joe Filceolaire (talk) 17:39, 21 August 2015 (UTC)
- Support I thought this is derived from (different rendition of) LoC (LCSH+LCNAF). But that's not so, eg Edward Snowden is http://id.loc.gov/authorities/names/no2013111241.html, which is a different id from FAST. --Vladimir Alexiev (talk) 09:36, 18 September 2015 (UTC)
treats
[edit]Description | Links a pharmaceutical drug and the disease(s) it is used for treating. |
---|---|
Data type | Item |
Template parameter | Use (Therapeutic use) en:Template:Infobox_drug_mechanism |
Domain | pharmaceutical drugs, chemical compounds, proteins, nucleic acids |
Allowed values | Wikidata items |
Example | dabrafenib (Q3011604) → skin melanoma (Q18558032) |
Source | National Drug File (https://rxnav.nlm.nih.gov) |
Robot and gadget jobs | Will be added and maintained by User:ProteinBoxBot/Drug_items |
- Motivation
The information of which drug can be used for treating a certain disease is not represented in Wikidata yet. This property shall be used to link a drug to the diseases it can be used for treating. Sebotic (talk) 10:00, 24 September 2015 (UTC)
- Discussion
- Support Makes sense Andrawaag (talk) 12:21, 24 September 2015 (UTC)
- Support Is needed. lv_ra (talk) 15:39, 24 September 2015 (UTC)
- Support --I9606 (talk) 17:00, 24 September 2015 (UTC)
- Notified participants of WikiProject Medicine
- Support --Tobias1984 (talk) 08:58, 25 September 2015 (UTC)
- Support Egon Willighagen (talk) 14:52, 4 October 2015 (UTC)
- Done --Tobias1984 (talk) 12:16, 5 October 2015 (UTC)
treated by
[edit]Description | Lists drugs which can be used to treat a certain disease. |
---|---|
Data type | Item |
Domain | diseases |
Allowed values | Wikidata items |
Example | skin melanoma (Q18558032) → dabrafenib (Q3011604) |
Source | National Drug File (https://rxnav.nlm.nih.gov) |
Robot and gadget jobs | Will be added and maintained by User:ProteinBoxBot/Drug_items |
- Motivation
The reverse of the 'treats' property proposal Sebotic (talk) 10:00, 24 September 2015 (UTC)
- Discussion
- Notified participants of WikiProject Medicine
- @Sebotic: Maybe this just needs to be an alias for possible treatment (P924). --Tobias1984 (talk) 10:05, 24 September 2015 (UTC)
- @Tobias1984: I disagree. I would use 'treated by' as a title, since it is designed to be an inverse property of 'treats'. Also 'medical treatment' is often used when talking about mental health treatments or surgical procedures, not so much drugs. Even in Wikipedia, when searching for 'medical treatment' you get redirected to an article about 'Therapy' or 'Major Trauma'. I am not saying if this is right or not, but 'treated by' is used when talking about drugs. 'Medical treatment' could be an alias to 'treated by'. lv_ra (talk) 16:46, 24 September 2015 (UTC)
- @Sebotic: @Tobias1984: My initial thoughts was also around the use of 'treat'... it implies perhaps "more", though at least one dictionary described 'treatment' as 'relief or cure' a disease; combined with your arguments, I decided to write down my thoughts... what about having the property reflect what actually happens: a drug gets prescribed to a patient... it's not always a disease the drug works against, but sometimes a disorder (see this interesting paper). Anyway, perhaps confusion would reduce if the property would be linked to the fact that "the drug is accepted a prescription treatment for"? The provenance would then be, for example, the FDA report, or they European equivalent. Egon Willighagen (talk) 15:11, 4 October 2015 (UTC)
- @Emitraka: That makes sense. But I wonder if we also need the inverse property. The query system is getting pretty good and adding inverse statements double the workload. Or is there another reason for the proposal above this one? --Tobias1984 (talk) 17:41, 24 September 2015 (UTC)
- @Tobias1984: As far as I know, properties like are proposed "pair-wise". Also from an ontological point of view it is standard practice. lv_ra (talk) 19:01, 24 September 2015 (UTC)
- @Tobias1984:@Emitraka: I agree that on first sight it seems plausible to use 'Medical treatment' also for drugs. But the disease items in WD carrying this property are medical procedures and drug classes, not single drugs. Adding single drugs to 'Medical treatment' will intermingle completely different things. Regarding the reverse property: The capabilities of the WD SPARQL endpoint are already remarkable. But for direct use in infoboxes with lua-script, the reverse property will be required (at least to my knowledge and at least for now). Also, drug-disease relations are often 1:n in both directions, one drug can be used for treatment of several diseases (even off label use) and for most diseases there exist several drugs/drug combinations which are used for treatment. Having those in a WD item will make it easier for users accessing the WD disease item web pages directly to make use of the drug disease link data. From a bot writing point of view, adding the reverse links is simple. Also in regard of lv_ras' point of ontological bidirectionality, I would therefore be in favor of adding this property. Sebotic (talk) 06:59, 25 September 2015 (UTC)
- @Tobias1984: As far as I know, properties like are proposed "pair-wise". Also from an ontological point of view it is standard practice. lv_ra (talk) 19:01, 24 September 2015 (UTC)
- @Tobias1984: I disagree. I would use 'treated by' as a title, since it is designed to be an inverse property of 'treats'. Also 'medical treatment' is often used when talking about mental health treatments or surgical procedures, not so much drugs. Even in Wikipedia, when searching for 'medical treatment' you get redirected to an article about 'Therapy' or 'Major Trauma'. I am not saying if this is right or not, but 'treated by' is used when talking about drugs. 'Medical treatment' could be an alias to 'treated by'. lv_ra (talk) 16:46, 24 September 2015 (UTC)
- Support --Tobias1984 (talk) 08:59, 25 September 2015 (UTC)
- Done --Tobias1984 (talk) 12:16, 5 October 2015 (UTC)
solvent
[edit]Description | Substance which will dissolve this item |
---|---|
Data type | Item |
Domain | Solvents |
Example | erythrityl tetranitrate (Q417174) → acetone (Q49546) |
Source | Freebase |
Robot and gadget jobs | Freebase import |
- Motivation
Needed to import https://www.freebase.com/chemistry/solubility_relationship/solvent Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:09, 18 June 2015 (UTC)
- Discussion
- Needs a qualifier (very soluble / freely soluble / soluble / sparingly soluble / slightly soluble / very slightly soluble)--Kopiersperre (talk) 07:05, 19 June 2015 (UTC)
- @Kopiersperre: No, I think we have to go out of this non scientific way to classify solubility. I agree with the property solvent but not as main property but as qualfifier of the property solubility. Snipre (talk) 12:54, 22 June 2015 (UTC)
- Support As qualifier of solubility. Snipre (talk) 12:55, 22 June 2015 (UTC)
- My classification is not non-scientific, it's from European Pharmacopoeia (5.11):
Label | g·l−1 |
---|---|
very soluble | > 1000 |
freely soluble | 100-1000 |
soluble | 33-100 |
sparingly soluble | 10-33 |
slightly soluble | 1-10 |
very slightly soluble | 0,1-1 |
not soluble | < 0,1 |
Isn't this an option?--Kopiersperre (talk) 19:05, 22 June 2015 (UTC)
- @Kopiersperre: This is not scientific because this is the result of an evaluation: you have to provide the reference of the table in order to be able to understand what soluble is. Solubility in g/l or mg/l is an absolute value and not a relative like the ones you proposed. Then this table doesn't allow to classify components having the same class of solubility: between 100 and 1000 g/l there is a huge gap. Better use absolute values and let later the data user filter or translate these data into relative index. Snipre (talk) 13:31, 23 June 2015 (UTC)
- @Snipre: This convinces me.--Kopiersperre (talk) 13:58, 23 June 2015 (UTC)
- Oppose The solubility (Q170731) is a function (Q3075154) of temperature (Q11466) and pressure (Q39552). I think it's better use a solubility equilibrium (Q863829) constant as property (Q937228). Almondega (talk) 18:48, 15 August 2015 (UTC)
- @Almondega: pressure affects solubility of gazes but not of solids and liquids. For gazes you should add the pressure too as qualifier. Snipre (talk) 16:35, 11 September 2015 (UTC)
- @James Hare (NIOSH), GZWDer: Please provide your comment about this proposal. Snipre (talk) 13:09, 5 October 2015 (UTC)
- Done --Tobias1984 (talk) 13:22, 5 October 2015 (UTC)
Solubility (en)
[edit]See Wikidata:Property_proposal/Pending/2#Solubility (en)
Description | solubility of a substance with solvent and temperature as qualifiers |
---|---|
Data type | quantity with unit-invalid datatype (not in Module:i18n/datatype) |
Template parameter | en, fr and de infoboxes about chemicals |
Domain | chemistry, physics |
Example | sodium chloride (Q2314): 360 g/kg of solvent, solvent:water (Q283), temperature (P2076): 25°C. |
Proposed by | GZWDer (talk) 03:07, 7 June 2013 (UTC) |
- Discussion
- Support Snipre (talk) 12:09, 7 June 2013 (UTC)
- Support --Kaligula (talk) 07:06, 19 June 2013 (UTC)
- Support--Saehrimnir (talk) 15:46, 24 June 2013 (UTC)
- Support --Cvf-ps (talk) 11:09, 26 June 2013 (UTC)
- Question: solubility in what, exactly? Will the assumption be solubility in water or will each item have to specify the solvent? James Hare (NIOSH) (talk) 15:40, 24 September 2015 (UTC)
- @James Hare (NIOSH): Please have a look at the description of the property proposal: solubility of a substance with solvent and temperature as qualifiers. The solvent should be specified as qualifier. There is currently a property proposal for this qualifier just above this one. Snipre (talk) 13:02, 5 October 2015 (UTC)
- @GZWDer: An open question is still blocking this property. And this property and "dipole moment" are missing examples. --Tobias1984 (talk) 12:58, 5 October 2015 (UTC)
- @Tobias1984: This proposal has to be created with the above one. Snipre (talk) 13:10, 5 October 2015 (UTC)
- Done --Tobias1984 (talk) 13:22, 5 October 2015 (UTC)