Shortcut: WD:PP/SCI

Wikidata:Property proposal/Natural science

From Wikidata
Jump to: navigation, search
Property proposal: Generic Authority control Person Organization
Event Creative work Term Space
Place Sister projects
Economics Transportation Natural science Property metadata

See also[edit]


This page is for the proposal of new properties.

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

Creating the property

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


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

Contents

Physics and astronomy[edit]

average yearly temperature[edit]

   Under discussion
Description temperature calculated by averaging the minimum and maximum daily temperatures over 30 years in a certain place
Data type Number
Domain instances of geographic region (Q82794) and instances of, recursively, its subclasses
Allowed values from -400 (minimum using degree Fahrenheit (Q42289), near to the absolute zero (Q81182)) to 350 (maximum using kelvin (Q11579), perhaps could be reached inside a volcano)
Allowed units the same as temperature (P2076), that is, degrees Celsius (Q25267), kelvin (Q11579) and degree Fahrenheit (Q42289)
Example Zaragoza (Q10305) → 15.5 °C (according to aemet.es, the Agencia Estatal de Meteorología (Q2826727))
Planned use firstly, importing data for some Spanish municipalities from the Agencia Estatal de Meteorología (Q2826727)
Robot and gadget jobs creating and regularly updating a world map (Q653848) that represents how these values are distributed across the planet
See also temperature (P2076), Köppen climate classification (P2564)
Motivation

Wikidata is lacking in climate data, and the average yearly temperature is a particularly relevant measurement. abián 15:57, 28 August 2016 (UTC)

Discussion
I think that we have a problem.
  1. If we only create a property for the average monthly temperature, we won't be able to get the average yearly temperature if we don't have well-defined data of all months. In some cases, we know the average yearly temperature but not the average monthly one.
  2. If we only create a property for the average yearly temperature, we'll never be able to know the average monthly temperature.
  3. If we create both properties, we should never use both for the same Wikidata item. This situation could be controlled using a {{Constraint:Conflicts with}}.
There isn't a perfect solution. If we usually know the average monthly temperature, I would say 1. If we usually know the average yearly temperature but hardly ever the average monthly one, I would say 2. And, if there's no a "usual" situation, I would say 3. If I would have to choose right now, without being able to talk or to find out about this, I would choose 3. --abián 20:37, 28 August 2016 (UTC)
  • Average monthly temperatures are way more informative than plain yearly average. Whether we create a specific property for this or not, we should think about how bring here monthly averages too, creating a coherent model including the later ones too.
1) Having a specific property for yearly averages and using generic temperature (P2076) 'qualified' with determination method (P459) for the monthly ones would be pretty awkward.
2) Having "average yearly temperature" and "average monthly temperature" using somehow the month as qualifier would make a little more sense. I don't know.
3) Having "average yearly temperature", "average january temperature", and "average february temperature" and... -> no.
Regardless all that, qualifiers as start time (P580) or end time (P582) should be added too. Strakhov (talk) 20:09, 28 August 2016 (UTC)
Option 2 makes much sense. :-) --abián 20:49, 28 August 2016 (UTC)
month of the year (P2922) would work as the qualifier in this scenario. Thryduulf (talk) 22:11, 28 August 2016 (UTC)
We'd need "average maximum temp." and "average minimum temp." too. Recently we approved precipitation height (P3036), but it seems pretty weird, as it represents a point in time, not an average. How about "average montly precipitation height" and "average yearly precipitation height"? Seriously, I think we need to apply here a more holistic view, not proposing one by one. Strakhov (talk) 17:09, 30 August 2016 (UTC)
  • Pictogram voting comment.svg Comment would it be possible to consider instead a property that provides a database of temperatures for the location so that whatever monthly or yearly averages are wanted can be computed from it? It might have to be a URL to a dataset...? ArthurPSmith (talk) 19:19, 30 August 2016 (UTC)
    The average yearly temperatures in a certain decade are fixed values, they won't change. However, external links will probably do, sooner or later. And, as only linking an external database wouldn't be enough to retrieve data from the Wikimedia projects, I think that it's better to directly save these data in Wikidata. --abián 09:16, 2 September 2016 (UTC)
  • Well, sometimes old values do change thanks to reanalyses - or at least in certain datasets they wouldn't be perfectly fixed. In any case, what I think would be best here would be to be able to store the full dataset, say as a CSV file, in Wikimedia Commons. However, Commons doesn't allow CSV or other dataset files at the moment. If we store monthly averages directly in wikidata, then you have 12 statements per year - for some locations there are 150 years or so of data (perhaps more in England?) so you could have 1800 temperature statements on a location item in wikidata under this approach. That doesn't seem like a good idea to me. ArthurPSmith (talk) 15:41, 21 September 2016 (UTC)
  • Per Phabricator:T120452, tabular data storage is coming to Commons at some point. I'm not familiar with what the current state of work on it is. Thryduulf (talk) 20:11, 21 September 2016 (UTC)
  • They wouldn't be 1800 temperature statements in any case. These values are average ones, usually, in a 30-years period, not in a year. --abián 18:11, 22 September 2016 (UTC)

If I'm not wrong, these are the possible Wikidata properties concerning average temperatures and their dependencies.

Deriving average temperatures.svg

These dependencies can be applied, mutatis mutandis, to any kind of average climate data (average rainfall, average relative humidity, average number of frosty days, etc.).

Having read all comments, having done some research, and knowing that these data:

  • have an absolutely different availability depending on the relevance of the place, on the country and on the antiquity;
  • should always be used with qualifiers start time (P580) and end time (P582);
  • should always have a direct reference;
  • are historical and should never change since they are added to Wikidata;

... I propose that we exceptionally assume some degree of duplication with them and that we allow to store multiple declarations using these properties even for the cases that some of them could be derived from others.

For the case of monthly data, declarations should also necessarily have the qualifier month of the year (P2922).

In conclusion, concerning this property, "average yearly temperature", I still think that creating it would be a good idea. --abián 12:25, 2 September 2016 (UTC)

  • Given that it makes sense to fill for almost any place with a location, I think having a specific property for it is warranted. Symbol support vote.svg Support ChristianKl (talk) 18:20, 25 September 2016 (UTC)
  • Pictogram voting comment.svg Comment I think it would be good to have the monthly series of min/max/avg, but I don't think current quantity type and GUI is quite ready for this.
    --- Jura 23:53, 29 September 2016 (UTC)
  • Pictogram voting comment.svg Comment Please see Phabricator:T147049.
    --- Jura 09:03, 30 September 2016 (UTC)
    • +1 Climate data is needed on Wikidata. The RedBurn (ϕ) 11:53, 15 February 2017 (UTC)
  • @Abián, Thryduulf, ChristianKl, Jura1: Commons now has tabular data; I strongly suggest that instead of this proposal we propose a "temperature dataset" property with datatype "Commons media" to allow for whatever temperature data is available to be linked to a location. ArthurPSmith (talk) 16:15, 10 January 2017 (UTC)
    • Pictogram voting comment.svg Comment Obviously, this is only marginally related to average yearly temperature, but I don't quite see the difference between gifs at Commons and Commons datasets. Neither allow us currently to do comparisons with other locations. Given that quantity datatype has gotten more efficient in terms of resources, we might try a single property for temperatures.
      --- Jura 16:42, 10 January 2017 (UTC)
  • Symbol oppose vote.svg Oppose use tabular data on Commons. Average yearly temperature is only single quantity out of many relevant ones for climate data. Average/min/max yearly/monthly/daily temperature/precipitation are others. We should find a solution which works for all these quantities. Here it should become clear that Wikidata is not the right place for it. Climate data are tabular data and the developers decided to store tabular data on Commons and not on Wikidata, so let's use Commons. A demo is already online: en:User:Yurik/WeatherDemo using the data stored on commons:Data:Ncei.noaa.gov/weather/New York City.tab. --Pasleim (talk) 16:54, 11 January 2017 (UTC)
Pictogram voting comment.svg Comment How many dimensions data should have when we call it "tabular"? Geographic dimension represented using items.
Census data have 3 dimensions right now: location, point in time, sex.
It is possible to get 50+ dimensions from census information, we need only selection of dimensions on Wikidata, not complete 1-to-1 dumps.
Pictogram voting comment.svg Comment If we use .csv / .tabs on commons, then I would like to have a property about "tabular data available on commons"; and with qualifier about topic ("Climate data"). d1g (talk) 03:19, 14 January 2017 (UTC)
That is far too generic. It would be like having a property called "string" that we use for all strings. - Nikki (talk) 18:19, 31 January 2017 (UTC)
  • Pictogram voting comment.svg Comment this is my first time at the property proposals page, so I'm going to keep things to a comment for now. I was just editing Q21726404, and I was looking for a property for annual temperature. There are tons of bot-generated pages on the Swedish Wikipedia, for example the bot generated page for the item I just mentioned. The bot found structured data to make that page, so I feel that Wikidata could have a viable property for this. Icebob99 (talk) 14:53, 16 February 2017 (UTC)

dimension[edit]

   Under discussion
Description wymiar wielkości fizycznej
Represents Dimension of physical quantity (Q19110)
Data type Mathematical expression
Domain physical quantity
Allowed values L^aM^bT^cI^dΘ^eN^fJ^G
Example torque (Q48103) → L2MT−2
Motivation

(Add your motivation for this property here.) GZWDer (talk) 17:09, 16 January 2017 (UTC)

Discussion
  • I would like a more descriptive description. ChristianKl (talk) 07:54, 17 January 2017 (UTC)
    "dimension" is a concept described in physics and engineering texts--basically it's a way to indicate the mathematical power a particular unit has. The example above given is torque, which has the dimension length ^ 2 * mass * time ^ -2. en:Dimensional_analysis#Concrete_numbers_and_base_units probably covers this the best on Wikipedia. --Izno (talk) 18:35, 17 January 2017 (UTC)
@Izno:I know what it is. I criticize that the current description of the property is not necessarily enough to let a user discover the meaning of the property. Especially a user without math background. ChristianKl (talk) 12:16, 6 February 2017 (UTC)
  • This should probably be derived from some addition to the bases mass, temperature and etc, and then using an item linkage we should link torque and etc to those basic dimensions. So, probably a support but only for mass, temperature, and etc while we use some other properties to link torque to its dimensional items. --Izno (talk) 18:35, 17 January 2017 (UTC)
  • Symbol support vote.svg Support I don't have any problem with the proposal as is. Looks like a good use for our mathematical expression data type. (note, pinging Wikiproject Physics participations) ArthurPSmith (talk) 19:44, 17 January 2017 (UTC)
  • Is this a property corresponding to the item Dimension of physical quantity (Q19110) ? For example see energy (Q11379) which has quality (P1552) Dimension of physical quantity (Q19110) with qualifier defining formula (P2534) "L^2MT^{-2}" . Will the proposed property serve a similar purpose but directly without having to use "has quality (P1552)"? DavRosen (talk) 19:56, 13 February 2017 (UTC)
  • @DavRosen: yes, I think you've captured exactly the idea. I've added the relationship to Q19110 in the template. ArthurPSmith (talk) 18:27, 14 February 2017 (UTC)

Tobias1984 Snipre Physikerwelt Pamputt Petermahlzahn Jibe-b Restu20 Daniel Mietchen TomT0m ArthurPSmith Mu301 Sarilho1 SR5 DavRosen Pictogram voting comment.svg Notified participants of WikiProject Physics

  • Is this a "typical" pattern? First we have an <item> that is widely used in "has quality" (p1552) <item> [<qualifier>] and we turn that into <propertyCorrespToItem> [<qualifierOrSubPropertyOfIt>]? If so, then shouldn't this become part of the formal process? I.e. don't propose a new property until it's corresponding item is repeatedly being used as the subject of "has quality"(p1552) (or perhaps some other properties similar to "has quality")? That way we can "try it out" and show that it makes sense, and how it is being used, before creating the corresponding new property? Maybe there could even be a way to automatically replace those original "prototype" usages with the direct usage of the new property. DavRosen (talk) 19:05, 14 February 2017 (UTC)
  • Also, should the proposed property be a subproperty of "defining formula" (P2534), since this is simply a formula that defines a dimension? Maybe I'm misunderstanding how subproperties work, though DavRosen (talk) 19:10, 14 February 2017 (UTC)

minimum wavelength of electromagnetic sensitivity / maximum wavelength of electromagnetic sensitivity[edit]

   Ready <create>
Description maximum electromagnetic wavelength that the item can detect
Represents wavelength (Q41364)
Data type Number
Template parameter "wavelength" in en:template:infobox telescope
"telescope_wavelength" in en:template:infobox spaceflight
Domain instances of organism (Q7239) or measuring instrument (Q2041172)
Allowed units meters, kilo-, centi-, milli-, micro-, nano-, pico-, femto-, attometers
Example Arecibo Observatory (Q44547)maximum wavelength of electromagnetic sensitivity  1 m
human eye (Q430024)maximum wavelength of electromagnetic sensitivity  700 nm
Compton Gamma Ray Observatory (Q41519)maximum wavelength of electromagnetic sensitivity  40 pm
Planned use Add statements about the electromagnetic sensitivity ranges of organisms and measuring instruments
See also minimum frequency of audible sound (P3387)
   Ready <create>
Description minimum electromagnetic wavelength that the item can detect
Represents wavelength (Q41364)
Data type Number
Template parameter "wavelength" in en:template:infobox telescope
"telescope_wavelength" in en:template:infobox spaceflight
Domain instances of organism (Q7239) or measuring instrument (Q2041172)
Allowed units meters, kilo-, centi-, milli-, micro-, nano-, pico-, femto-, attometers
Example Arecibo Observatory (Q44547)minimum wavelength of electromagnetic sensitivity  3 cm
human eye (Q430024)minimum wavelength of electromagnetic sensitivity  400 nm
Compton Gamma Ray Observatory (Q41519)minimum wavelength of electromagnetic sensitivity  60 am
Planned use Add statements about the electromagnetic sensitivity ranges of organisms and measuring instruments
See also maximum frequency of audible sound (P3465)
Motivation

By analogy with minimum frequency of audible sound (P3387) / maximum frequency of audible sound (P3465), but for sensitivity to the electromagnetic spectrum, which is more often expressed in terms of wavelength than frequency.

Tobias1984 Snipre Physikerwelt Pamputt Petermahlzahn Jibe-b Restu20 Daniel Mietchen TomT0m ArthurPSmith Mu301 Sarilho1 SR5 DavRosen Pictogram voting comment.svg Notified participants of WikiProject Physics --Swpb (talk) 14:34, 16 February 2017 (UTC)

Discussion
Symbol support vote.svg Support looks reasonable to me (2 properties). ArthurPSmith (talk) 17:02, 16 February 2017 (UTC)

Biology[edit]

Please visit Wikidata:WikiProject Taxonomy for more information. To notify participants use {{Ping project|Taxonomy}}
Please visit Wikidata:WikiProject Biology for more information.

eMonocot taxon ID[edit]

   Under discussion
Description ID for taxon in eMonocot
Represents eMonocot (Q23580063)
Data type External identifier
Template parameter |emonocot= and |emonocotfamily= in en:Template:Taxonbar (both without prefix)
Domain taxon
Allowed values urn:kew.org:wcs:(taxon%7Cfamily):\d+
Example Hippeastrum (Q757257)urn:kew.org:wcs:taxon:278065
Orchidaceae (Q25308)urn:kew.org:wcs:family:32
Vanilleae (Q147795) - urn:kew.org:wcs:family:440
Formatter URL http://e-monocot.org/taxon/$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 16:29, 17 January 2017 (UTC)

Discussion

Abbe98
Achim Raschka (talk)
Brya (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
Delusion23 (talk)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
Michael Goodyear
MPF
PhiLiP
Andy Mabbett (talk)
Prot D
pvmoutside
Rod Page
Soulkeeper (talk)
Tinm
Tommy Kronkvist (talk)
TomT0m
Pictogram voting comment.svg Notified participants of WikiProject Taxonomy

  • Comment: If the string urn:kew.org:wcs: is required, it should be part of the formatter URL. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:58, 17 January 2017 (UTC)
  • Pictogram voting comment.svg Comment :This is just a copy of WCSPF. Also, why pick an example that is wrong? - Brya (talk) 05:38, 18 January 2017 (UTC)
    • "WCSPF"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:04, 18 January 2017 (UTC)
      • = World Checklist of Selected Plant Families. BTW: the ID is an URN and hence urn:kew.org:wcs: is part of the ID and not of the formatter URL. --Succu (talk) 14:00, 18 January 2017 (UTC)
  • I changed the name to eMonocot taxon ID ChristianKl (talk) 12:39, 5 February 2017 (UTC)
To make what more understandable, ChristianKl? --Succu (talk) 20:07, 7 February 2017 (UTC)
When reading a list of properties I want to make it easy for the reader to understand what the property is about. Even a person who doesn't know what eMonocot happens to be get's an impression with this name. ChristianKl (talk) 11:28, 8 February 2017 (UTC)

only valid for subset[edit]

   Under discussion
Description This should only be used as a qualifier. It denotes that the statement isn't true for all instances but only for a subset.
Data type Item
Example Rectus abdominis muscle (Q275150) innervated by (P3189) Sixth intercostal nerve (Q27058097) → this property → Unknown value
Motivation

I take information about innervation from Anatomy and Human Movement Structure and Function SIXTH EDITION (Q27050364). It tells me that in sometimes Rectus abdominis muscle (Q275150) is innervated by Sixth intercostal nerve (Q27058097) while in other cases it isn't.

I want this property to be able to enter this kind of knowledge in Wikidata. I'm personally unsure whether this is the best way to model this domain. If someone has other suggestions I'm happy. ChristianKl (talk) 14:03, 24 January 2017 (UTC)

Discussion
  • Maybe use applies to part (P518)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:38, 24 January 2017 (UTC)
    • No, I'm pretty sure that's a different meaning than ChristianKl intends, but maybe also indicates the name is confusing. I think the meaning wanted here is effectively the difference between "sometimes" and "always". How to model that in wikidata? ArthurPSmith (talk) 18:27, 24 January 2017 (UTC)
      • I also think that applies to part (P518) has a slightly different meaning. I think it's worthwhile to have properties that can make precise statements about issues like this and it's not good to overload applies to part (P518) with slightly different meanings. A human might understand what's meant when he reads the data but an automated system might not. ChristianKl (talk) 09:56, 25 January 2017 (UTC)
  • Well, you need an item for the subset anyway ? So, why not just put the statement in that item and left what is valid in every case in the upper one ? author  TomT0m / talk page 21:49, 25 January 2017 (UTC)
It might be that we have a source that says that this is true for 50% of the population. This information could be filled in. ChristianKl (talk) 09:09, 27 January 2017 (UTC)
How do you express "50% of the population" ? The set is not identified. Isn't this the notion of incidence (Q217690) View with Reasonator See with SQID or something similar you're looking for ? Or you're looking for something similar to disjoint union of (P2738) See with SQID or subclass of (P279) qualified with a numerical value representing this ? author  TomT0m / talk page 11:30, 27 January 2017 (UTC)
@TomT0m:I think it's worth having a specific property for this to allow for automated interaction with the data. If you think there's a specific way this data can already be presented I invite you to edit the example of Rectus abdominis muscle (Q275150) accordingly. ChristianKl (talk) 07:44, 2 February 2017 (UTC)
@TomT0m, ChristianKl: You can use proportion (P1107) to express this. --Swpb (talk) 17:19, 15 February 2017 (UTC)
@Swpb: If you think this property can be used here, could you edit the linked example accordingly? ChristianKl (talk) 17:52, 15 February 2017 (UTC)

seed dispersal[edit]

   Ready <create>
Description mode used by the item to disperse his seeds
Represents seed dispersal (Q943313)
Data type Item
Domain seed plants (Q25814)
Allowed values subclass of (P279)  seed dispersal (Q943313) (tree)
Example Arabidopsis thaliana (Q158695)anemochory (Q427893)
Motivation

Tobias1984 (talk) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits TypingAway (talk) Daniel Mietchen (talk) Tinm (talk) Tubezlob Bamyers99 (talk) Vincnet41

Pictogram voting comment.svg Notified participants of WikiProject Biology

I think this property should be just for plant, but maybe I'm wrong. What do you think? Tubezlob (🙋) 13:15, 14 February 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Thierry Caro (talk) 16:35, 14 February 2017 (UTC)
  • Symbol support vote.svg Support - I suggested this a year ago, but did not follow through. It does not need to be called "seed dispersal mode"; just "seed dispersal" is clear enough. - Brya (talk) 17:26, 14 February 2017 (UTC)
    • Thank you @Brya:, I changed. Tubezlob (🙋) 18:35, 14 February 2017 (UTC)
      • Thank you. - Brya (talk) 18:45, 14 February 2017 (UTC)
  • Symbol support vote.svg Support --Succu (talk) 18:25, 18 February 2017 (UTC)

inflorescence[edit]

   Ready <create>
Description placement of flowers on the stem of a flower plant
Represents inflorescence (Q156428)
Data type Item
Domain angiosperms (Q25314)
Allowed values subclass of (P279)  inflorescence (Q156428)
Example water forget-me-not (Q147165)scorpioid cyme (Q28771657)
Motivation

Tobias1984 (talk) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits TypingAway (talk) Daniel Mietchen (talk) Tinm (talk) Tubezlob Bamyers99 (talk) Vincnet41

Pictogram voting comment.svg Notified participants of WikiProject Biology

Useful to describe angiosperms. Tubezlob (🙋) 09:52, 15 February 2017 (UTC)

Discussion
  • Symbol support vote.svg Support - cool, I hadn't heard of these terms before, but it does sound useful for describing flowers. ArthurPSmith (talk) 18:34, 15 February 2017 (UTC)
  • Symbol support vote.svg Support --Tobias1984 (talk) 21:12, 15 February 2017 (UTC)
  • Symbol support vote.svg Support - Brya (talk) 06:27, 17 February 2017 (UTC)
  • Symbol support vote.svg Support --Succu (talk) 18:26, 22 February 2017 (UTC)

has fruit type[edit]

   Under discussion
Description morphology of the fruit of this taxon, as defined in botany
Represents type of fruit (Q28149961)
Data type Item
Domain angiosperms (Q25314) (or Spermatophytes?)
Allowed values subclasses of type of fruit (Q28149961)
Example 1. Rubus subg. Rubus (Q13180)compound drupe (Q163233); 2. Magnolia (Q157017)follicetum (Q145167) 3. Pyrus (Q434)pome (Q41274)
Source Template:Fruits (Q6792069) - note that this template varies per language
Motivation

I have to agree that subclass relations are not the best to show such relations. d1g (talk) 16:08, 16 February 2017 (UTC)

Discussion
  • This seems to be expressed via subclass of (P279). If you need a more specific relationship because of your template use a qualifier like as (P794) type of fruit (Q28149961). ChristianKl (talk) 16:22, 16 February 2017 (UTC)
    • I added an example with Magnolia after this comment. Maybe @Brya: has a better explanation.
    • My understanding that there is no strict criterion how "classes" relate between each other, they are used as labels along descriptive text. d1g (talk) 16:38, 16 February 2017 (UTC)

As I understand it, the intent is for a property "this taxon has this type of fruit" or "this plant taxon has type of fruit". The "double examples" are confusing: Magnolia (Q157017): aggregate fruit (Q4692249), is clearer. - Brya (talk) 17:29, 16 February 2017 (UTC)

... not Q4692249 but subclass of 4692249, i.e. no label (Q28790541); see w:Follicle (fruit) for description. d1g (talk) 17:43, 16 February 2017 (UTC)
OK. - Brya (talk) 18:16, 16 February 2017 (UTC)
Can't you get that information simply by chaining this taxon is source of (P1672) and subclass of (P279)? If the fruit item doesn't yet exist you could create it with a bot and call it "SPECIES NAME fruit". ChristianKl (talk) 19:24, 16 February 2017 (UTC)
No, this taxon is source of (P1672) is intended for things that are tradeable products. The "fruits" intended here are much wider in scope, and need not be edible. - Brya (talk) 20:07, 16 February 2017 (UTC)
Okay, I see that it might be useful to have a new property. But why shouldn't the new property directly link to the fruit in question? There might be other information besides the type of the fruit that's valuable. ChristianKl (talk) 20:51, 16 February 2017 (UTC)
What's the fruit in question of Opuntia stenopetala (Q2027719)? A general trait of Opuntia (Q158991) is that all species develop a fruit (Q1364) that can be characterised as indehiscent fruit (Q160034). --Succu (talk) 21:34, 16 February 2017 (UTC)

Classification was updated: Identification Of Major Fruit Types d1g (talk) 05:00, 17 February 2017 (UTC)

What is botanically a fruit, as intended here, may well be what in popular language is called a "seed", a "pod", or a "husk". The vast majority of fruits don't have an individual name (you are talking about creating upwards of three hundred thousand items on not-notable concepts). - Brya (talk) 05:18, 17 February 2017 (UTC)
It would be notable via our notability guidelines given that it's a structural need. It would be quite useful to have an image of the fruit. We might also be interested in storing information like the average weight of the fruit or the amount of seeds per fruit.  – The preceding unsigned comment was added by ChristianKl (talk • contribs).
We could, and also an item for the flowers, an item for the chemistry, an item for the wood (if present), etc. But it would be a lot simpler to just have new properties. There is no need, at most there is a desire. - Brya (talk) 11:53, 20 February 2017 (UTC)
I'm not sure how well defined the term "wood" happens to be but having an item for the wood of a pine tree allows us later to specify that a chair is made out of the wood of a pine tree, so there might be practical use of such a property.
We use the term structural need when creating the item of a spouse for a person where we just know the name of the spouse. Given our desire for structured data we don't store the name as a string but actually, create a new item for it.
When it comes to writing Wikipedia article there's a desire to combine multiple small topics into a single Wikipedia article. Given that our target at Wikidata is to build a structured database our goals are different.
When we have an item for the fruit it's a lot easier to add various information to the fruit. Any items on commons that contains the fruit can be tagged with the item once commons reaches the required phase. An African hunter-gatherer name might have names for a lot of fruits that don't have English names. If we already have items for the names a researcher who uploads the names of such a language can easily link the information. It's valuable to structure our knowledge in a way that makes it easy to add new knowledge.
I created a new proposal for https://www.wikidata.org/wiki/Wikidata:Property_proposal/Natural_science#has_fruit and Symbol oppose vote.svg Oppose this proposal. ChristianKl (talk) 13:12, 20 February 2017 (UTC)
I think you misunderstood the intention of this proposal. I think the intention is to give information about a general morphological trait (that of the fruit produced by individuals belonging to a certain taxon). Probably the name should be something like "has Fruit type". The most comprehensive classification of fruit types I know was published as A Systematic Treatment of Fruit Types (Q28807032) in 1994. It defines 95 fruit types. A draft is User:Succu/Fruit Types. --Succu (talk) 17:01, 20 February 2017 (UTC)
@Succu: "has fruit type" or "has fruit of type" would work here. I think I remember A Systematic Treatment of Fruit Types (Q28807032). AFAIR this is mostly regarded as overdoing things. The User:D1gggg/Identification Of Major Fruit Types is more generally used. - Brya (talk) 18:06, 20 February 2017 (UTC)
see also here, or here. - Brya (talk) 04:49, 21 February 2017 (UTC)
I changed the label to "has fruit type". I think we can use both classifications alongside. Generally Symbol support vote.svg Support. --Succu (talk) 14:41, 21 February 2017 (UTC)
Oh sure, anything that is referenced can be included. Just keep in mind that most use the less detailed approach. - Brya (talk) 18:05, 21 February 2017 (UTC)
@ChristianKl: Actually we have long had pine (pine (Q1503211)), a notable topic. In theory we could have items for flowers, item for wood, etc of each taxon (lots of possible properties for each flower or bit of wood). The overwhelming majority is not notable. - Brya (talk) 18:06, 20 February 2017 (UTC)
Pictogram voting question.svg Question On which scientific source is this classification based? --Succu (talk) 20:23, 17 February 2017 (UTC)
  • If we use a separate item for this, it would result in 2 relations taxon-fruit, fruit-metafruit: no label (Q28791696).
  • Symbol support vote.svg Support Single property in single item Paeonia (Q147105) and single value could be easier to enter. I have no opinion how to name such property. d1g (talk) 06:11, 17 February 2017 (UTC)
  • Symbol support vote.svg Support - Brya (talk) 18:05, 21 February 2017 (UTC)

haplogroup[edit]

   Ready <create>
Description mtDNA or Y-DNA haplogroup of somebody. This is very sensitive information, only used with a reliable source.
Represents Haplogroup (Q80686)
Data type Item
Domain people
Example Benjamin Franklin (Q34969)Haplogroup V (Q1458022)
Source en:List of haplogroups of historic people
Robot and gadget jobs No
Motivation

(Add your motivation for this property here.) GZWDer (talk) 18:39, 16 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support Dhx1 (talk) 15:15, 8 February 2017 (UTC)
  • Symbol support vote.svg Support Once the information is there.--Arbnos (talk) 16:23, 20 February 2017 (UTC)

has fruit[edit]

   Under discussion
Description the fruit of the plant
Represents fruit (Q1364)
Data type Item
Domain plants
Example Rubus subg. Rubus (Q13180)blackberry (Q19842373)
Motivation

In https://www.wikidata.org/wiki/Wikidata:Property_proposal/type_of_fruit_Q28149961 there the desire for having a property to store the type of a fruit. It became apparent that we currently don't have a way to specifically say that blackberry (Q19842373) is the fruit of Rubus subg. Rubus (Q13180). Given that there's a lot of information we could reasonable store about the fruit like the average weight, the image or the subclass it's makes sense to store that information in the item of the fruit. ChristianKl (talk) 13:10, 20 February 2017 (UTC)

Discussion
What about natural product of taxon (P1582)? --Pasleim (talk) 13:33, 20 February 2017 (UTC)
It's used for more than just fruits and thus doesn't allow automatic querying of the fruits. Given that very many plants have fruits I think it's worthwhile to have a specialized property instead of trying to solve it with a qualifier for natural product of taxon (P1582). It's also not clear that all fruits are "products". ChristianKl (talk) 13:39, 20 February 2017 (UTC)
For querying just add the condition that the entities should be subclasses of fruit (Q1364) (example query). --Pasleim (talk) 14:07, 20 February 2017 (UTC)
Yes, this is so. In this respect the property is superfluous. - Brya (talk) 18:33, 20 February 2017 (UTC)
I think this is sufficient. --Succu (talk) 14:32, 21 February 2017 (UTC)
Pictogram voting question.svg Question Is this proprty intended to provide the common names of a fruit like in this list? --Succu (talk) 15:08, 20 February 2017 (UTC)
Having the information about names like this is one way this property is valuble but I don't think it's the only one. ChristianKl (talk) 15:52, 20 February 2017 (UTC)
Pictogram voting comment.svg Comment It seems to me that the vast majority of fruits are not notable, and would not have an item of their own, so this would have very limited use. - Brya (talk) 18:31, 20 February 2017 (UTC)
Our criteria for notability under (2) is that it's a clearly identifiable conceptual or material entity where there are serious public sources that describe an item. It's my understanding that most species of plants get described by biologists in a way that thhere serious public information about traits of the fruit. Do you think that isn't true and there are fruits of plants over which there's no published information at all?
If I find academic sources that say that the fruit is a compound drupe (Q163233) than I have described the clearly identifiable identity with serious public sources. ChristianKl (talk) 22:10, 20 February 2017 (UTC)
That is only so in a limited sense. It should be easy enough to find a book devoted to tomatoes or to apples, so these are clearly notable. But the average fruit will get a line in a description of the taxon. To me that is not notability. By the way, there are plenty of flowers that have books devoted to them. - Brya (talk) 05:05, 21 February 2017 (UTC)
The key question is whether the information we use in Wikidata to describe a item can be source from serious and public sources. That's what (2) is about. It doesn't really matter if there's only a little information available as long as the information we have in the item corresponds to the available and trustworthy information. As far as the flower goes it's an anatomical feature. I would model it the same we as human leg (Q6027402)'s relationship to human (Q5). ChristianKl (talk) 09:05, 21 February 2017 (UTC)
You will note that we do not have an item for the leg of every animal (only for humans), although the legs of most animals can be described from serious and public sources. -Brya (talk) 11:43, 21 February 2017 (UTC)
We don't have an item for every leg currently but we currently don't want to store any information about the legs. If we take the weight of the brain of a giraffe that's well stored in giraffe brain (Q25685967). That's better than having a "weight of the brain" property. If someone made a list with the weight of legs of different species the way to store that information would be to create new items. ChristianKl (talk) 14:06, 21 February 2017 (UTC)
It is possible to make items for each of the brains of all the animals in the world (like giraffe brain (Q25685967)), but I think that would be weird, unless it is possible to put some dozen properties in such an item. It would make more sense to have items for all the well-known mushrooms, that is, apart from the items for species of fungi. - Brya (talk) 17:40, 21 February 2017 (UTC)
Our notability criteria don't use a minimum amount of statements that can be made. In computer programming convention wisdom holds that a single function should be as short as possible. System generally get designed with principles like "seperation of concern" in mind. Managing information this way might feel weird if you are used to manage information the way it's managed books or in Wikipedia articles but it's the more appropriate way for managing a linked data system. ChristianKl (talk) 18:14, 21 February 2017 (UTC)
Your coding analogy is a little bit flawed. Ontology design follows his own rules. KISS (Q131560) is something they have in common. Maybe some day we have a manual of style how to do it at Wikidata. As long as you don't give a better definition of this property: Symbol oppose vote.svg Oppose. --Succu (talk) 21:02, 21 February 2017 (UTC)

Biochemistry and molecular biology[edit]

Please visit Wikidata:WikiProject Molecular biology for more information. To notify participants use {{Ping project|Molecular biology}}

PROSITE ID[edit]

   Under discussion
Description identifier for a protein family, domain or functional site, in the PROSITE database
Data type External identifier
Template parameter |PROSITE= in en:Template:Pfam box
Domain protein families, domains and functional sites
Allowed values PDOC\d{5}
Example Bromodomain (Q1829843)http://www.expasy.org/cgi-bin/prosite-search-ac?PDOC00550 PDOC00550]
Formatter URL http://www.expasy.org/cgi-bin/prosite-search-ac?$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 08:09, 17 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:35, 17 January 2017 (UTC)
  • Symbol support vote.svg Support While I support this proposal, there are two issues. The first one is a conceptual problem in its current form. What is proposed here is to create a PROSITE documentation ID, not a PROSITE ID. PROSITE, which I created, has entries for the "methods" (pattern, profile, rule) to detect a family or domain, these have accessions of the type "PS[0-9][0-9][0-9][0-9][0-9]", one or more method entries are then linked to a documentation entry (PDOC). So maybe two properties need to be created or if the PDOC property is only one which will be used in Wikidata, the property name should be changed. The second problem is the proposed URL which is not adequate, the proposal uses the "search" URL while it should use the "entry" URL. For the example in the proposal it should be: http://prosite.expasy.org/PDOC00550 Amb sib (talk) 07:27, 25 January 2017 (UTC)
  • Symbol neutral vote.svg Neutral until the issues raised by Amb sib are resolved. -Emitraka (talk) 20:05, 16 February 2017 (UTC)

MEROPS enzyme ID[edit]

Description ID for a proteolytic enzyme in MEROPS database
Represents MEROPS (Q25712)
Data type External identifier
Template parameter MEROPS at en:Template:Infobox protein family
Domain protein
Allowed values S##
Example S4 protein domain (Q17142858) → S41
Formatter URL http://merops.sanger.ac.uk/cgi-bin/merops.cgi?id=$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 08:15, 17 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support But with a proposition for a change in the description to "ID for a proteolytic enzyme or inhibitor" as MEROPS not only include peptidases but also their inhibitors. The "allowed values" is also incorrect as inhibitors use I## identifiers.--Amb sib (talk) 07:36, 25 January 2017 (UTC)
  • I changed the name to "MEROPS enzyme ID". ChristianKl (talk) 21:43, 10 February 2017 (UTC)
  • Symbol support vote.svg Support -Emitraka (talk) 20:04, 16 February 2017 (UTC)
  • @GZWDer, Emitraka: ✓ Done ChristianKl (talk) 21:40, 25 February 2017 (UTC)

Structural Classification of Proteins ID[edit]

   Under discussion
Description ID for protein domains in SCOP database, and also Superfamily database
Represents Structural Classification of Proteins database (Q4832556)
Data type External identifier
Template parameter SCOP at en:Template:Pfam box
Domain protein domain
Allowed values (please clarify)
Example Bromodomain (Q1829843) → 1b91
Formatter URL http://scop.mrc-lmb.cam.ac.uk/scop/search.cgi?tlev=fa;&pdb=$1 or http://supfam.org/SUPERFAMILY/cgi-bin/search.cgi?search_field=$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 08:19, 17 January 2017 (UTC)

Discussion

I support this proposal, however several things need to be changed. The example "1b91" is a PDB ID for a particular protein with a bromodomain, not the SCOP ID for bromodomains. It looks like the SCOP for the bromodomain superfamily is a.29.2. The formatter URL should be changed to this. Furthermore, the superfamily database has a separate ID for bromodomain SSF47370, and so should be a separate property. What will be the source for these? I'd suggest the xrefs from interpro. Gstupp (talk) 19:55, 29 January 2017 (UTC)

Conserved Domain Database ID[edit]

   Under discussion
Description identifier for a protein domain in the Conserved Domain Database
Represents CDD (Q5163159)
Data type External identifier
Template parameter |CDD= in en:Template:Pfam box
Domain protein domain
Allowed values cd\d{5}
Example Bromodomain (Q1829843)cd04369
Formatter URL http://www.ncbi.nlm.nih.gov/Structure/cdd/cddsrv.cgi?uid=$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 08:23, 17 January 2017 (UTC)

Discussion

Sequence Ontology ID[edit]

   Under discussion
Description ID in Sequence Ontology
Data type External identifier
Template parameter |1= in en:Template:SO
Domain several?
Allowed values number
Example Coronavirus frameshifting stimulation element (Q5172252)0000233
Source Open Biomedical Ontologies (Q4117183)
Formatter URL http://www.sequenceontology.org/miso/current_release/term/SO:$1
Robot and gadget jobs Yes
Motivation

(Add your motivation for this property here.) GZWDer (talk) 08:29, 17 January 2017 (UTC)

Discussion

BA candidate.svg Weak oppose The formatter URL and example point to a Sequence Ontology (Q7452458) identifier, which is just one of the many ontologies within the OBO Foundry. Is this property proposal meant to be specifically for sequence ontology IDs or any biomedical ontology URI? If the former, the ID should contain the prefix/namespace/scheme "SO:" (CURIE). If the latter, we have exact match (P2888) which is meant for holding URIs for equivalent identifiers in other ontologies. Gstupp (talk) 22:42, 23 January 2017 (UTC)

Symbol oppose vote.svg Oppose I agree with Gstupp. Each ontology should have its own property, as we already have for e.g. Gene Ontology ID (P686), ChEBI ID (P683), Disease Ontology ID (P699), UBERON ID (P1554), which are all from the OBO space of ontologies. Sebotic (talk) 00:48, 24 January 2017 (UTC)

Symbol oppose vote.svg Oppose The way the proposal is written does not correspond with it's label. @GZWDer did you want to propose just the SO ID maybe? Emitraka (talk) 14:35, 24 January 2017 (UTC)

@Gstupp, Sebotic, Emitraka: What I want to propose is ID in Sequence Ontology, corresponding to en:Template:SO. I didn't know Sequence Ontology is only a part of Open Biomedical Ontologies. If there's already a property for this I'm going to withdraw the request. I have updated the proposal.--GZWDer (talk) 15:35, 24 January 2017 (UTC)
@GZWDer: I think it would be great to have links to sequence ontology in wikidata! However, two things. 1) The ID needs to have the namespace "SO:" as part of the ID, and 2) Your example is linking Coronavirus frameshifting stimulation element (Q5172252) with the sequence ontology item for "mature_transcript", which is not correct. I think what you mean (and I'm not a geneticist...) is that Coronavirus frameshifting stimulation element (Q5172252) is subclass of (P279) of Mature messenger RNA (Q6792003), where Mature messenger RNA (Q6792003) has the SO ID: SO:0000233. So the example should be that Mature messenger RNA (Q6792003)SO:0000233 Gstupp (talk) 17:59, 25 January 2017 (UTC)
@GZWDer: if you implement all the changes suggested by Gstupp above, I am all for the proposal. The SO terms will be very useful for multiple projects. Emitraka (talk) 16:01, 26 January 2017 (UTC)
I agree with Emitraka. I would also welcome that property! --Andrawaag (talk) 16:06, 26 January 2017 (UTC)

activator of (biochemistry)[edit]

   Ready <create>
Description protein for which this chemical acts as an activator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example XNT [PMID: 18391097] (Q27089254)Angiotensin I converting enzyme 2 (Q301630)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Symbol support vote.svg Support ArthurPSmith (talk) 19:07, 16 February 2017 (UTC)
  • Symbol support vote.svg Support This property - and all the others proposed for this project - will be tremendously helpful in creating the edges between biochemical compounds. -Emitraka (talk) 19:59, 16 February 2017 (UTC)
  • Symbol support vote.svg Support NuriaQueralt (talk) 04:59, 26 February 2017 (UTC)

agonist of (biochemistry)[edit]

   Ready <create>
Description protein for which this chemical acts as an agonist
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example mibolerone (Q6827784)Androgen receptor (Q416601)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

positive allosteric modulator of[edit]

   Ready <create>
Description protein for which this chemical acts as a positive allosteric modulator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example VPC171 (Q27089155)Adenosine A1 receptor (Q3062781)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

antisense inhibitor of[edit]

   Ready <create>
Description protein/gene for which this chemical (e.g. a miRNA/siRNA) acts as an antisense inhibitor
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example Eteplirsen (Q5402585)Dystrophin (Q412285)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

inhibitor of (Biochemistry)[edit]

   Ready <create>
Description protein for which this chemical compound acts as an inhibitor
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example vemurafenib (Q423111)B-Raf proto-oncogene, serine/threonine kinase (Q21109218)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Given the way we currently name properties I would prefer "Biochemical Inhabitor" over "Inhibitor (Biochemistry)". Otherwise Symbol support vote.svg Support ChristianKl (talk) 11:58, 8 February 2017 (UTC)
  • I welcome this proposal, so I certainly Symbol support vote.svg Support this proposal. However, I am wondering if we could rename it into "inhibits" (similar to encodes/encoded by) to have the directionality of the relationship explicit. --Andrawaag (talk) 19:39, 8 February 2017 (UTC)
  • Symbol support vote.svg Support ArthurPSmith (talk) 19:07, 16 February 2017 (UTC)
  • Symbol support vote.svg Support -Emitraka (talk) 20:02, 16 February 2017 (UTC)

antagonist of (Biochemistry)[edit]

   Ready <create>
Description protein for which this chemical compound acts as an antagonist
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example tretinoin (Q29417)Nuclear receptor ROR-beta (Q21117235)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

negative allosteric modulator of[edit]

   Ready <create>
Description protein for which this chemical compound acts as a negative allosteric modulator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example MK-2206 (Q25100065)AKT serine/threonine kinase 1 (Q21114990)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

disrupting agent for (Biochemistry)[edit]

   Ready <create>
Description protein/protein complex for which this chemical compound acts as a disrupting agent
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example MDM2 proto-oncogene (Q2639180)Tumor protein p53 (Q283350)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

blocker of (Biochemistry)[edit]

   Ready <create>
Description protein (e.g. channel/pore protein) for which this chemical compound acts as a blocker
Data type Item
Domain chemical compound (Q11173)
Allowed values protein (Q8054)
Example 9-anthroic acid (Q27074044)Anoctamin 1 (Q21105176)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Pictogram voting comment.svg Comment in principle this sounds good. However, these are unidirectional relationships and it's not clear to me which direction these properties are intended for - at the least the descriptions are very unclear. Is the property intended to be in a statement on the protein, so that a protein would have a list of chemical compounds that are "blockers" for it? Or the other way around - a statement on the chemical compound that it is a blocker for a particular protein? ArthurPSmith (talk) 20:56, 7 February 2017 (UTC)
The reason not to propose 2 properties is mainly to keep the number of properties low. I agree that the label might need to be adjusted to make it clearer (e.g. to "blocker of", "blocks (molecular biology)"). But overall, it should be sufficient if theses statements reside on the ligands (ligands can also be proteins/peptides). From a query (SPARQL) perspective, unidirectional relations should be fine. If, for some reason, bi-directional relations should be required, a new property could be proposed (or the one in discussion here could be used on the target, in combination with a qualifier). Sebotic (talk) 08:19, 8 February 2017 (UTC)
  • Symbol support vote.svg Support. I agree with the above. I also would prefer a property name dictating the directionality (e.g. block) --Andrawaag (talk) 19:45, 8 February 2017 (UTC)
  • -- oppose-- (no more see below) on this and related ones until label and descriptions are fixed. @Sebotic: I was not asking that there be both direct and inverse properties - one direction is fine. But it needs to be extremely clear which direction the property is acting or it will be used incorrectly and you will have protein channels that blockade chemicals etc. rather than the reverse. Please fix these labels and descriptions to make directionality clear. ArthurPSmith (talk) 18:21, 14 February 2017 (UTC)
@ArthurPSmith: I adjusted all primary labels and descriptions so they should be unambiguous now. Let me know if you'd like any further changes. Best, Sebotic (talk) 19:30, 15 February 2017 (UTC)
@Sebotic: well you don't have to be quite so detailed - I adjusted this one from your last version to something that I think is clear enough without all the verbiage. I also lower-cased the label as that's the usual standard here. See Help:Properties for some guidelines on writing property labels and descriptions. Does this seem ok to you? ArthurPSmith (talk) 20:12, 15 February 2017 (UTC)
@ArthurPSmith: Thanks, I adjusted label and description for all others. Sebotic (talk) 18:46, 16 February 2017 (UTC)
  • Symbol support vote.svg Support Ok this looks good to me now then too, thanks! ArthurPSmith (talk) 19:02, 16 February 2017 (UTC)
  • Symbol support vote.svg Support -Emitraka (talk) 20:02, 16 February 2017 (UTC)

recognition sequence / cutting site of restriction enzyme / isoschizomer / neoschizomer / isocaudomer[edit]

   Under discussion
Description DNA sequence recognized by a restriction enzyme, DNA binding domain, etc.
Represents Recognition sequence (Q7302658)
Data type String
Domain restriction enzyme (Q219715), DNA-binding domain (Q13479514), etc.
Allowed values /^(5'-[ACGTRMWSYKHBDVN]+-3'|3'-[ACGTRMWSYKHBDVN]+-5')$/
Example EcoRI (Q417754) → "5'-GAATTC-3'"
Source w:List_of_restriction_enzyme_cutting_sites
   Under discussion
Description DNA cutting site of restriction enzyme
Data type String
Domain restriction enzyme (Q219715)
Allowed values /^(5'-[ACGTRMWSYKHBDVN]+↓[ACGTRMWSYKHBDVN]+-3'|3'-[ACGTRMWSYKHBDVN]+↑[ACGTRMWSYKHBDVN]+-5')$/
Example EcoRI (Q417754) → "5'-G↓AATTC-3'", "3'-CTTAA↑G-5'"
Source w:List_of_restriction_enzyme_cutting_sites
   Under discussion
Description isoschizomers of the restriction restriction enzyme, which have the same recognition sequence and the cutting site.
Represents Isoschizomer (Q644180)
Data type Item
Domain restriction enzyme (Q219715)
Allowed values restriction enzyme (Q219715)
Example MspI→HpaII, HpaII→MspI (both enzymes recognize and cut "5'-C↓CGG-3'").
Source w:List_of_restriction_enzyme_cutting_sites
   Under discussion
Description neoschizomers of the restriction restriction enzyme, which have the same recognition sequence but a different cutting site.
Represents Neoschizomer (Q16945915)
Data type Item
Domain restriction enzyme (Q219715)
Allowed values restriction enzyme (Q219715)
Example SmaI (Q6130415) → XmaI, XmaI → SmaI (Q6130415) (both recognize "5'-CCCGGG-3'", but the cutting site of SmaI is "5'-CCC↓GGG-3'" and that of XmaI is "5'-C↓CCGGG-3'").
   Under discussion
Description isocaudomer of the restriction restriction enzyme, which have the different recognition sequence but produces the same termini
Represents Isocaudomer (Q17000139)
Data type Item
Domain restriction enzyme (Q219715)
Allowed values restriction enzyme (Q219715)
Example MboI → BamHI, BamHI → MboI (cutting site of MboI is "5'-N↓GATCN-3'" and that of BamHI is "5'-G↓GATCC-3'", so both enzymes produce the same cohesive end "GATC".)
Motivation

There are many restriction enzymes, which have specific recognition sequences and cutting sites (see w:List_of_restriction_enzyme_cutting_sites), and some enzymes have isoschizomers, neoschizomers or isocaudomer. To introduce these data into Wikidata, new properties are needed.

Expression method for DNA sequence and cutting site is open to some debate. --Okkn (talk) 02:02, 19 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Discussion

Chemistry[edit]

Please visit Wikidata:WikiProject Chemistry for more information. To notify participants use {{Ping project|Chemistry}}


IECIC 2015[edit]

   Under discussion
Description Inventory of Existing Cosmetic Ingredients in China (2015)
Data type External identifier
Domain cosmetic ingredients
Allowed values numbers
Example 2,6-pyridinedicarboxylic acid (Q417164) → 3926
Format and edit filter validation number
Source http://cirs-reach.com/news-and-articles/new-inventory-of-existing-cosmetic-ingredients-in-china-launched-(iecic-2015,-final-version).html
Planned use import the whole Inventory in Mix n'Match
Robot and gadget jobs no
Motivation

Having chinese labels on cosmetic ingredients, linking it with the European and American systems. Teolemon (talk) 18:56, 17 October 2016 (UTC)

Putting it here to show the advantages:

2,6-pyridinedicarboxylic acid (Q417164) → 3926 (2,6-二羧基吡啶) (2,6-DICARBOXYPYRIDINE)

Discussion
  • @Teolemon: Seems reasonable, but the example given, "3926 (2,6-二羧基吡啶) (2,6-DICARBOXYPYRIDINE)", does not match the allowed values ("numbers") in the proposal. Please resolve this discrepancy. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:13, 20 October 2016 (UTC)
  • I would like the long name as the label to make it easier to understand for the viewer what the property is about. ChristianKl (talk) 11:01, 29 October 2016 (UTC)
    • Then I think you probably want item datatype, with an item for the different ingredients. Thryduulf (talk) 01:03, 31 October 2016 (UTC)

Carbon dioxide equivalent[edit]

Carbon dioxide equivalent

   Under discussion
Description Equivalent amount of carbon dioxide to measure product's carbon footprint, which represents a product’s contribution to global warming through the emission of greenhouse gases during product's life-cycle
Represents Carbon dioxide equivalent (Q1933140)
Data type Number
Domain manufactured products
Allowed units kg CO2e
Example Iphone 7 -> 56 kg CO₂e
Source
Planned use Add this information to manufactured products
Motivation

Promote sustainable products and manufacturing https://en.wikipedia.org/wiki/Sustainable_products. Qupro (talk) 02:29, 5 January 2017 (UTC)

Maybe It could be use by http://wikifootprints.org/

  • @Qupro: Please give en example using an existing Wikidata item and a value, like in other property proposals. Ping me if you need help. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:37, 5 January 2017 (UTC)
  • @pigsonthewing: Thanks, I have update it. Qupro (talk) 15:33, 15 January 2017 (UTC)
Discussion
Pictogram voting comment.svg Comment the description and allowed units do NOT match the planned use. Is this intended to be for greenhouse gases other than CO2 (per the description), or is it intended to describe the carbon footprint of commercial products (the example link and "planned use" statements)? Assuming it is for commercial products, the units should be grams (of CO2 equivalent) or grams per 100 grams of product or something along those lines ArthurPSmith (talk) 18:47, 5 January 2017 (UTC)
  • @ArthurPSmith, You are right, I have change the description, It's for commercial products. After more reading and find http://wikifootprints.org/ , not sure if value could be given per product, Kg or by a given custom quantity. Qupro (talk) 15:33, 15 January 2017 (UTC)
Pictogram voting comment.svg Comment @Qupro: Please be coherent: you mentioned the application domain as "greenhouse gas", so chemicals, and after you set in domain "companies, manufactured products". Please fix this if you want we support your proposal. Snipre (talk) 09:06, 14 January 2017 (UTC)
  • @Snipre , Thanks, I have changed as I have commented before. Qupro (talk) 15:33, 15 January 2017 (UTC)
Symbol oppose vote.svg Oppose We have already global-warming potential (P2565) so I am currently opposed to this proposal. Snipre (talk) 09:08, 14 January 2017 (UTC)
  • I didnt know about global-warming potential property, so, now that the description has been clarified, Are these 2 properties equivalent?. If yes, I will start using global-warming potential (P2565). Qupro (talk) 15:33, 15 January 2017 (UTC)
    • @ArthurPSmith: I Knew but as the initial proposal was not clear and was mentioning greenhouse gases I prefered to oppose.
    • @Qupro: I suppose you don't know the subject because your proposal can't be interesting for specialists and can even lead to wrong conclusions: there are several methods to calculate the carbon equivalent of the production of 1 kg of substance/one good or the use of one service. Methods can differ according to their boundaries (cradle-to-gate, cradle-to-grave,...) or by their methodology (focus on pollution, energy,...). So they is no unique value but different values according to the method used. Instead of a general property using qualifier to describe the method better create one property for each method. Snipre (talk) 22:59, 17 January 2017 (UTC)
      • @Snipre: So, what about using Qualifiers ? Here an example of this Help:About data#/media/File:Statement with reference and qualifier - Earth.png Maybe "determination method" (Property:P459) could be use for methodology and "of (scope)" (Property:P642) could be used for boundaries. Would this be enough to define value in order to be useful? Qupro (talk) 21:08, 18 January 2017 (UTC)
        • @Qupro: You can do a lot things but you have to show in your proposal the way to model the data you want to see imported. You want to use qualifiers, ok, but which qualifiers, which values to use ? this should be indicated in the proposa. Provide a full example with a reference and if possible provide good sources. My concern is about the limited definition of your property and the uncovered domain of a lot of other environmental indicators which are used in LCIA (life cycle impact assement). There are 2 levels in environmental indicators, the combined indicators like Eco-Indicator 99, CML 2002, Impact 2002+, ReCiPe or Ecological scarcity and the single indicators like ozone depletion, acidification, eutrophication, land use or climate change. My advice is try to read something about LCIA (perhaps this can help) and try to redefine the proposal. If you are not clear enough at the level of the proposal, your property will become a mix of different data with different data modeling and finally will be useless. Snipre (talk) 07:07, 22 January 2017 (UTC)
Symbol support vote.svg Support @Snipre: global-warming potential (P2565) is for greenhouse gases, this property proposal is for commercial products, these are two very different things (which was what my earlier comment was based on). Now that Qupro has clarified this property is meant for commercial products, I support it. ArthurPSmith (talk) 14:02, 17 January 2017 (UTC)
  • Symbol support vote.svg Support per ArthurPSmith. ChristianKl (talk) 22:28, 20 February 2017 (UTC)

activator of (biochemistry)[edit]

   Ready <create>
Description protein for which this chemical acts as an activator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example XNT [PMID: 18391097] (Q27089254)Angiotensin I converting enzyme 2 (Q301630)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Symbol support vote.svg Support ArthurPSmith (talk) 19:07, 16 February 2017 (UTC)
  • Symbol support vote.svg Support This property - and all the others proposed for this project - will be tremendously helpful in creating the edges between biochemical compounds. -Emitraka (talk) 19:59, 16 February 2017 (UTC)
  • Symbol support vote.svg Support NuriaQueralt (talk) 04:59, 26 February 2017 (UTC)

agonist of (biochemistry)[edit]

   Ready <create>
Description protein for which this chemical acts as an agonist
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example mibolerone (Q6827784)Androgen receptor (Q416601)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

positive allosteric modulator of[edit]

   Ready <create>
Description protein for which this chemical acts as a positive allosteric modulator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example VPC171 (Q27089155)Adenosine A1 receptor (Q3062781)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

antisense inhibitor of[edit]

   Ready <create>
Description protein/gene for which this chemical (e.g. a miRNA/siRNA) acts as an antisense inhibitor
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example Eteplirsen (Q5402585)Dystrophin (Q412285)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

inhibitor of (Biochemistry)[edit]

   Ready <create>
Description protein for which this chemical compound acts as an inhibitor
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example vemurafenib (Q423111)B-Raf proto-oncogene, serine/threonine kinase (Q21109218)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Given the way we currently name properties I would prefer "Biochemical Inhabitor" over "Inhibitor (Biochemistry)". Otherwise Symbol support vote.svg Support ChristianKl (talk) 11:58, 8 February 2017 (UTC)
  • I welcome this proposal, so I certainly Symbol support vote.svg Support this proposal. However, I am wondering if we could rename it into "inhibits" (similar to encodes/encoded by) to have the directionality of the relationship explicit. --Andrawaag (talk) 19:39, 8 February 2017 (UTC)
  • Symbol support vote.svg Support ArthurPSmith (talk) 19:07, 16 February 2017 (UTC)
  • Symbol support vote.svg Support -Emitraka (talk) 20:02, 16 February 2017 (UTC)

antagonist of (Biochemistry)[edit]

   Ready <create>
Description protein for which this chemical compound acts as an antagonist
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example tretinoin (Q29417)Nuclear receptor ROR-beta (Q21117235)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

negative allosteric modulator of[edit]

   Ready <create>
Description protein for which this chemical compound acts as a negative allosteric modulator
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example MK-2206 (Q25100065)AKT serine/threonine kinase 1 (Q21114990)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

disrupting agent for (Biochemistry)[edit]

   Ready <create>
Description protein/protein complex for which this chemical compound acts as a disrupting agent
Data type Item
Domain biology, chemistry
Allowed values Wikidata items of instance of (P31)/subclass of (P279): chemical compound (Q11173) or protein (Q8054)
Example MDM2 proto-oncogene (Q2639180)Tumor protein p53 (Q283350)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion

blocker of (Biochemistry)[edit]

   Ready <create>
Description protein (e.g. channel/pore protein) for which this chemical compound acts as a blocker
Data type Item
Domain chemical compound (Q11173)
Allowed values protein (Q8054)
Example 9-anthroic acid (Q27074044)Anoctamin 1 (Q21105176)
Source Guide to Pharmacology, ChEMBL, BindingDB, PDB
Planned use Several thousand chemical compound to protein relations should be imported
Motivation

We have been importing proteins, chemical compounds and the relations between those and have modeled the relation by using physically interacts with (P129) and qualifiers to indicate the type of relation (e.g. Activator, Inhibitor). This approach is not very convenient. It makes adding data by users more difficult, as well as querying the data with SPARQL and it also makes it impossible to properly map these relations to external resources/ontologies. Therefore, we talked to the folks from ChEMBL and they kindly provided us with their list of chemical compound - protein mechanistic relations. We are currently also getting these relations established in the Relation Ontology which allows for interoperability and direct integration of these relations Wikidata with the OBO world. This is a big advantage, as data contributions to Wikidata can easily disseminate into the OBO world, making community curation in WD even more valuable. In total, there are 29 relations, I will now just propose the 10 most important as properties. Sebotic (talk) 19:05, 6 February 2017 (UTC)

Andrew Su
Marc Robinson-Rechavi
Pierre Lindenbaum
Michael Kuhn
Boghog
Emw
Chandres
Dan Bolser
Pradyumna
Chinmay
Timo Willemsen
Salvatore Loguercio
Tobias1984
Daniel Mietchen
Optimale
Mcnabber091
Ben Moore
Alex Bateman
Klortho
Hypothalamus
Vojtěch Dostál
Gtsulab
Andra Waagmeester
Sebotic
Mvolz
Toniher
Elvira Mitraka
David Bikard
Dan Lawson
Francesco Sirocco
Konrad U. Förstner (talk)
Chris Mungall (talk)
Kristina Hettne
Hardwigg
i9606
Putmantime
Tinm
Karima Rafes
Finn Årup Nielsen
Jasper Koehorst
Till Sauerwein
Crowegian
Nothingserious
Okkn
AlexanderPico
Amos Bairoch
Gstupp
DePiep
Pictogram voting comment.svg Notified participants of WikiProject Molecular biology

Saehrimnir
Leyo
Snipre
Jasper Deng
Dcirovic
Walkerma
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
Nothingserious
Antony Williams (EPA)
TomT0m
Wostr
Devon Fyson
User:DePiep
User:DavRosen
Pictogram voting comment.svg Notified participants of WikiProject Chemistry


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • Pictogram voting comment.svg Comment in principle this sounds good. However, these are unidirectional relationships and it's not clear to me which direction these properties are intended for - at the least the descriptions are very unclear. Is the property intended to be in a statement on the protein, so that a protein would have a list of chemical compounds that are "blockers" for it? Or the other way around - a statement on the chemical compound that it is a blocker for a particular protein? ArthurPSmith (talk) 20:56, 7 February 2017 (UTC)
The reason not to propose 2 properties is mainly to keep the number of properties low. I agree that the label might need to be adjusted to make it clearer (e.g. to "blocker of", "blocks (molecular biology)"). But overall, it should be sufficient if theses statements reside on the ligands (ligands can also be proteins/peptides). From a query (SPARQL) perspective, unidirectional relations should be fine. If, for some reason, bi-directional relations should be required, a new property could be proposed (or the one in discussion here could be used on the target, in combination with a qualifier). Sebotic (talk) 08:19, 8 February 2017 (UTC)
  • Symbol support vote.svg Support. I agree with the above. I also would prefer a property name dictating the directionality (e.g. block) --Andrawaag (talk) 19:45, 8 February 2017 (UTC)
  • -- oppose-- (no more see below) on this and related ones until label and descriptions are fixed. @Sebotic: I was not asking that there be both direct and inverse properties - one direction is fine. But it needs to be extremely clear which direction the property is acting or it will be used incorrectly and you will have protein channels that blockade chemicals etc. rather than the reverse. Please fix these labels and descriptions to make directionality clear. ArthurPSmith (talk) 18:21, 14 February 2017 (UTC)
@ArthurPSmith: I adjusted all primary labels and descriptions so they should be unambiguous now. Let me know if you'd like any further changes. Best, Sebotic (talk) 19:30, 15 February 2017 (UTC)
@Sebotic: well you don't have to be quite so detailed - I adjusted this one from your last version to something that I think is clear enough without all the verbiage. I also lower-cased the label as that's the usual standard here. See Help:Properties for some guidelines on writing property labels and descriptions. Does this seem ok to you? ArthurPSmith (talk) 20:12, 15 February 2017 (UTC)
@ArthurPSmith: Thanks, I adjusted label and description for all others. Sebotic (talk) 18:46, 16 February 2017 (UTC)
  • Symbol support vote.svg Support Ok this looks good to me now then too, thanks! ArthurPSmith (talk) 19:02, 16 February 2017 (UTC)
  • Symbol support vote.svg Support -Emitraka (talk) 20:02, 16 February 2017 (UTC)

Medicine[edit]

Please visit Wikidata:WikiProject Medicine for more information. To notify participants use {{Ping project|Medicine}}

TA98 Latin term[edit]

   Under discussion
Description Latin name for anatomical subject as described in Terminologia Anatomica 98
Represents Terminologia Anatomica (Q286567)
Data type External identifier
Template parameter en:template:Infobox artery -->
Example hepatic artery proper (Q542166)arteria hepatica propria

Continuation of former proposal. In this proposal it is not just a Latin name, but a controlled vocabulary, as specified on TA98.


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine @Adert:@Pigsonthewing, Snipre, ChristianKl, Jura1, Pasleim:--Micru (talk) 21:12, 19 January 2017 (UTC)

  • Pictogram voting question.svg Question Terminologia Anatomica (Q286567) might be classical Latin language which cannot be copyrighted. Alternatively, it might be a copyrightable identification system owned by International Federation of Associations of Anatomists (Q2896474), especially if they are making odd arbitrary decisions to give new nonstandard names in Latin language to anything. I am not familiar enough with this system to confirm that it should not be copyrightable. Can anyone give an opinion about whether any part of Terminologia Anatomica might be copyrighted, or whether the organization publishing the system claims a copyright over it? Blue Rasberry (talk) 21:42, 19 January 2017 (UTC)
    • I'm no legal expert but in general names are usually not protected by copyright. I can call an iPhone an iPhone without violating copyright. Suis genesis database rights last 15 years, so the TA98 should be out of it.

Given that Wikipedia didn't get real problems with CAS numbers and there the authoring organisation cares about asserting copyright, I don't see why the Terminologia Anatomica would be different. ChristianKl (talk) 07:06, 22 January 2017 (UTC)

I don't think that's what native is supposed to be. A native name is of a different nature than a name from a controlled vocabulary. ChristianKl (talk) 15:47, 22 January 2017 (UTC)
  • Symbol support vote.svg Support The function of this property isn't served by the usual Label name in the Latin language. Therefore it's different then "Wikidata:Property proposal/Latin name". I would prefer if the property to exist as "external id" and changed it accordingly. ChristianKl (talk) 07:06, 22 January 2017 (UTC)

only valid for subset[edit]

   Under discussion
Description This should only be used as a qualifier. It denotes that the statement isn't true for all instances but only for a subset.
Data type Item
Example Rectus abdominis muscle (Q275150) innervated by (P3189) Sixth intercostal nerve (Q27058097) → this property → Unknown value
Motivation

I take information about innervation from Anatomy and Human Movement Structure and Function SIXTH EDITION (Q27050364). It tells me that in sometimes Rectus abdominis muscle (Q275150) is innervated by Sixth intercostal nerve (Q27058097) while in other cases it isn't.

I want this property to be able to enter this kind of knowledge in Wikidata. I'm personally unsure whether this is the best way to model this domain. If someone has other suggestions I'm happy. ChristianKl (talk) 14:03, 24 January 2017 (UTC)

Discussion
  • Maybe use applies to part (P518)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:38, 24 January 2017 (UTC)
    • No, I'm pretty sure that's a different meaning than ChristianKl intends, but maybe also indicates the name is confusing. I think the meaning wanted here is effectively the difference between "sometimes" and "always". How to model that in wikidata? ArthurPSmith (talk) 18:27, 24 January 2017 (UTC)
      • I also think that applies to part (P518) has a slightly different meaning. I think it's worthwhile to have properties that can make precise statements about issues like this and it's not good to overload applies to part (P518) with slightly different meanings. A human might understand what's meant when he reads the data but an automated system might not. ChristianKl (talk) 09:56, 25 January 2017 (UTC)
  • Well, you need an item for the subset anyway ? So, why not just put the statement in that item and left what is valid in every case in the upper one ? author  TomT0m / talk page 21:49, 25 January 2017 (UTC)
It might be that we have a source that says that this is true for 50% of the population. This information could be filled in. ChristianKl (talk) 09:09, 27 January 2017 (UTC)
How do you express "50% of the population" ? The set is not identified. Isn't this the notion of incidence (Q217690) View with Reasonator See with SQID or something similar you're looking for ? Or you're looking for something similar to disjoint union of (P2738) See with SQID or subclass of (P279) qualified with a numerical value representing this ? author  TomT0m / talk page 11:30, 27 January 2017 (UTC)
@TomT0m:I think it's worth having a specific property for this to allow for automated interaction with the data. If you think there's a specific way this data can already be presented I invite you to edit the example of Rectus abdominis muscle (Q275150) accordingly. ChristianKl (talk) 07:44, 2 February 2017 (UTC)
@TomT0m, ChristianKl: You can use proportion (P1107) to express this. --Swpb (talk) 17:19, 15 February 2017 (UTC)
@Swpb: If you think this property can be used here, could you edit the linked example accordingly? ChristianKl (talk) 17:52, 15 February 2017 (UTC)

may prevent[edit]

   Under discussion
Description a disease which may be prevented by a certain drug
Data type Item
Domain Medicine
Allowed values Wikidata items of instance of (P31) or subclass of (P279) disease (Q12136)
Example aspirin (Q18216)myocardial infarction (Q12152) -->
Source http://www.fda.gov/, http://ema.europa.eu/, https://www.nlm.nih.gov/research/umls/sourcereleasedocs/current/NDFRT/
Planned use several hundred preventative drug usages should be added to Wikidata
See also drug used for treatment (P2176), medical condition treated (P2175), cause of (P1542), significant drug interaction (P769)
Motivation

As listed above, Wikdata has several properties to describe drug-disease interactions (drug used for treatment (P2176), medical condition treated (P2175)), drug side effects (cause of (P1542)) and drug-drug interactions (significant drug interaction (P769)). What is still missing is a way to describe that a certain medication can prevent a disease from even occuring. This property proposal should cover these cases. Sebotic (talk) 19:00, 8 February 2017 (UTC)


Tobias1984
Doc James
User:Bluerasberry
Wouterstomp
Gambo7
Daniel Mietchen
Andrew Su
Peter.C
Klortho
Remember
Matthiassamwald
Projekt ANA
Andrux
Pavel Dušek
Was a bee
Alepfu
FloNight
Genewiki123
Emw
emitraka
Lschriml
Mvolz
Franciaio
User:CFCF
User:Lucas559
User:Jtuom
Chris Mungall
ChristianKl
Pictogram voting comment.svg Notified participants of WikiProject Medicine

Discussion
  • What exactly is meant by "may"? I think the property should likely to be worded to be more clear about the meaning. ChristianKl (talk) 22:09, 8 February 2017 (UTC)
I followed the wording of NDF-RT and it makes sense, because medications in many cases do not have a 100% success rate. But certainly, I can rename it to 'used for prevention of', if you prefer that. Sebotic (talk) 09:54, 9 February 2017 (UTC)
Many substances that are labeled with drug used for treatment (P2176) aren't better than placebo's. They are used by doctors to treat but there's no evidence that they are effective for that purpose. When it comes to this property it's important to be clear about whether this property indicates that there's evidence that supports this claim. I don't think it has to be made clear in the property name so "may prevent" is okay. But it should be made clear in the property description. We don't want people to make bad decisions because they think the property indicates proof for the capability of preventing a disease when it doesn't. ChristianKl (talk) 14:50, 10 February 2017 (UTC)

Mineralogy[edit]

Please visit Wikidata:WikiProject Mineralogy for more information. To notify participants use {{Ping project|Mineralogy}}

Informatics[edit]

Please visit Wikidata:WikiProject Informatics for more information. To notify participants use {{Ping project|Informatics}}

File format magic numbers[edit]

   Under discussion
Description magic numbers used to incorporate file format metadata in form of a string coded hexadecimal number (usual encoding, "0" = 0 and "F" = 15, space ignored). Qualifiers can specify an offset and a padding value for this number.
Data type String
Template parameter Template:Infobox file format (Q10986167) magic number parameter
Domain file format (Q235557)
Example Graphics Interchange Format (Q2192) -> 47 49 46 38 39 61
Source Gary Kessler's File Signatures Table
Planned use I plan to add magic numbers to Wikidata items for the corresponding file formats.
Motivation

Magic numbers are constant numerical or text values used to identify file formats. Having this data in Wikidata will help make file format information more complete. Magic numbers are part of how we verify file signatures and are used in forensic computing. This is also a parameter of the Infobox:File format. It will be possible to transfer all of the magic numbers stored in infoboxes to Wikidata if we create this property. There is also this list [List of file signatures] that we could transfer to Wikidata. YULdigitalpreservation (talk) 15:43, 17 October 2016 (UTC)

Qualifier[edit]

(Additions to the proposal by TomT0m)

Offset[edit]
   Under discussion
Description qualifier of "magic number" for the number of bytes before the magic number to be searched in a file
Data type Number
Example Modelling the format "RVT" "
[512 (0x200) byte offset]
00 00 00 00 00 00 00 00 	  	[512 (0x200) byte offset]
........
RVT 	  	Revit Project File subheader
gives
< RVF > magic number search < 00 00 00 00 00 00 00 00 >
offset search <  512 >
.
Source Gary Kessler's File Signatures Table
Planned use qualifier for the property above

Talk[edit]

  • Symbol support vote.svg Support Symbol wait.svg Wait. author  TomT0m / talk page 17:31, 17 October 2016 (UTC)
  • Symbol support vote.svg Support but there are several other kinds of "magic numbers" so I think the name needs to be more descriptive - maybe "file format magic numbers"? Also, with string value isn't there some room for ambiguity in how the numbers are to be represented here? ArthurPSmith (talk) 18:18, 17 October 2016 (UTC)
    • Good point. If the numbers are string coded hexadecimal, this should be made explicit. The spaces seems also totally irrelevant and adds burden to parse. I can also see in the files that spec also specifies offsets : [11 byte offset] and [512 (0x200) byte offset]. This could be handled better than with an unspecified string format in a structured data projects. Also see if the string can't encode the non-hex version such as directly the string, for example in
    46 41 58 43 4F 56 45 52 FAXCOVER
    2D 56 45 52 	        -VER
    
    it should be possible to store more efficiently directly "FAXCOVER-VER", maybe an offset with a qualifier, and maybe a "padding value" also with a qualifier, something like
    < format > magic string search < FAXCOVER-VER >
    offset search < 0 byte >
    padding search < 0 >
    . author  TomT0m / talk page 18:32, 17 October 2016 (UTC)
    • Pictogram voting comment.svg Comment Thanks for this feedback. I revised the label for the property proposal. It looks like we will need a hexadecimal option as well as an ascii option. I welcome suggestions of how to further refine the proposal. YULdigitalpreservation (talk) 13:45, 18 October 2016 (UTC)
  • Symbol support vote.svg Support It will be very useful for data regarding file type identification. CC0 (talk) 11:45, 28 October 2016 (UTC)
  • Pictogram voting comment.svg Comment Could this property be specified to contain values which are Perl Compatible Regular Expressions (PCRE), allowing for more advanced signatures to be specified if desired? For example, "\x89PNG\x0D\x0A\x1A\x0A" for the PNG family, "\x00\x01\x00\x00Standard Jet DB" for Microsoft Access MDB, "GIF8[79]a" for the GIF family, etc. The advantages are: for ASCII-only-signatures (GIF), it's human-readable. For signatures containing binary/non-ASCII data (PNG), it's in a readily usable format (C/C++ strings for example) and for optionally complex signatures, it's in a format ready to use with a PCRE compliant parser. Pixeldomain (talk) 02:44, 17 November 2016 (UTC)
    Pictogram voting comment.svg Comment The offset could be identified in the PCRE expression, as an example: "(?s)^\x00\x01\x02.{38}ANSWERTOEVERYTHING" would look from the start of the file for \x00\x01\x02 then skip 38 bytes to offset 42 in the file where it would look for "ANSWERTOEVERYTHING". More advanced expressions could look at bytes from the end of the file (ZIP archives have a central directory tacked on the end of the file), perform negative look-aheads, etc. Whilst there is extra complexity with PCRE, it does not have to be used, and the fall-back is a simple C/C++ string representing binary data. Pixeldomain (talk) 03:09, 17 November 2016 (UTC)
  • Pictogram voting comment.svg Comment Also worth taking a look at is how the magic file of the "file" command stores file type signatures: https://github.com/file/file/tree/master/magic/Magdir Pixeldomain (talk) 03:32, 17 November 2016 (UTC)
    Pictogram voting comment.svg Comment Also take a look at the FIDO PRONOM database at https://raw.githubusercontent.com/openpreserve/fido/af3fc47791855ad7b955eb4272411113bfcff54d/fido/conf/formats-v88.xml which uses PCRE to define signatures for each file type. Pixeldomain (talk) 04:04, 17 November 2016 (UTC)

programming paradigm[edit]

   Under discussion
Description the programming paradigm in which a programming language is classified
Represents programming paradigm (Q188267)
Data type Item
Template parameter "paradigm" in en:Template:Infobox programming language
Domain programming language (Q9143)
Example
Motivation

This property is important for the classification of programming languages and to be compatible with the mentioned infobox. The Wikipedia article en:Programming paradigm has a box with a list of items that can be used within this property. It could be simplified to "paradigm" if the property could be useful in other areas. Luk3 (talk) 02:20, 21 November 2016 (UTC)

Discussion

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics Does this seem right? ChristianKl (talk) 21:03, 10 December 2016 (UTC)

  • Symbol oppose vote.svg Oppose This is a classification property, I prefer a classification using classes per Help:Classification. What would be more interesting would be properties to describe the types of programming languages (something to describe that functional programming fundamental obects/bases are function. author  TomT0m / talk page 11:32, 11 December 2016 (UTC)
    As a second thought, I think we should get before taking such a decision be straight on what a paradigm is : for enwiki : Programming paradigms are a way to classify programming languages and for frwiki : Un paradigme de programmation est un style fondamental de programmation informatique qui traite de la manière dont les solutions aux problèmes doivent être formulées dans un langage de programmation (A programming paradigm is a fundamental style of computer programming who deals with the way the solutions of the problems must be expressed in a programming language.) But the frwiki article is noted as needing sources. This way of saying things implies that this is not a direct classification of programming languages, and that we could define the "multi paradigm programming language" class as something like "there is several values of allowed paradigms for this language".
    In the first, clearly this is a way of classifying programming languages, and in the second, it is not directly (this reflects the ArthurPSmith search and my interrogation about this property).
    A quicly made bibliography about an ontology of programming languages : http://www.scienpress.com/Upload/JCM/Vol%202_4_4.pdf ; https://www.researchgate.net/publication/242381616_Towards_a_Programming_Language_Ontology (a language theorist perspective) , another page on classification of programming languages : https://www.info.ucl.ac.be/~pvr/paradigms.html and they indeed use the definition of the frwiki article : A programming paradigm is a style of programming a computer that is defined by a specific set of programming concepts and techniques, as embodied by its kernel language author  TomT0m / talk page 12:21, 11 December 2016 (UTC)
    Just a quick line about classification of languages in the "low/high" level scale : http://er.yuvayana.org/definition-classification-of-computer-programming-languages/ (a sample, there is many of such pages in google results)
    A highly narrower perspective : classification of massively parallel languages : http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.39.2856&rep=rep1&type=pdf author  TomT0m / talk page 12:28, 11 December 2016 (UTC)
    Symbol oppose vote.svg Oppose @TomT0m, Luk3: another perspective on classification of languages is their ancestry - en:Generational_list_of_programming_languages for example, and one could imagine classes for "C-based", "Fortran-based", "LISP-based" etc. groupings of languages. But that's not what we've actually done - looking at the SQID view for programming language (Q9143) we actually already have a good collection of subclasses along the "paradigm" axis, so I think I agree with TomT0m, we should do this via instance of (P31) relationships to eg. functional programming language (Q3839507), object-oriented programming language (Q899523) etc. I'm withdrawing my supporting note above, and I think we do not actually need this property here now. ArthurPSmith (talk) 13:54, 12 December 2016 (UTC)
  • Symbol oppose vote.svg Oppose per TomT0m/APS. --Izno (talk) 15:56, 14 December 2016 (UTC)
  • Symbol support vote.svg Support ~nmaia d 13:47, 20 December 2016 (UTC)

emulates platform[edit]

   Under discussion
Description computing platform which this emulator emulates
Data type Item
Domain instances of emulator (Q202871) (including subclasses)
Allowed values instances of computing platform (Q241317), operating system (Q9135), central processing unit (Q5300) (subclasses included)
Example VICE (Q647098)Commodore 64 (Q99775), DOSBox (Q479783)DOS (Q170434)
Source en:List of computer system emulators
See also platform (P400)
Motivation

This is related to but distinct from platform (P400). P400 means that a given program runs on that platform. Whereas, this would say that the program emulates the platform. If we consider a Commodore 64 emulator running on Microsoft Windows, there are two distinct platforms involved, the native platform (Microsoft Windows) and the emulated platform (Commodore 64). The former platform would be indicated by P400, the latter platform by this property. (Possibly, we could also create emulation versions of operating system (P306) and CPU (P880), although I am unsure if that is necessary or not.) SJK (talk) 13:41, 10 January 2017 (UTC)

Discussion
  • @SJK: Thank you for proposing this important property. I proposed a similar property in the "Natural Science" category (filed under "informatics"). Perhaps we could combine them? What is your opinion of using "emulated by" vs "emulates platform"? YULdigitalpreservation (talk) 18:23, 10 January 2017 (UTC)
    • @YULdigitalpreservation: Sorry I didn't notice your proposal before I made this one. I didn't realise "Informatics" was filed under "Natural sciences"–since I don't think of this stuff as natural science–but anyway, that aside–I actually think emulation is more a property of the emulator than the thing being emulated. Potentially, a popular platform could end up with dozens of emulators, and it would be neater to mark each of those emulators with "emulates" than marking the emulated platform with dozens of "emulated by" properties. (The reverse case is less common – a single emulator may emulate dozens of platforms, e.g. MAME, but the vast majority of emulators only emulate a single platform.) From an essentialist viewpoint–putting aside philosophical debates about whether essentialism is right or not–for A to emulate B is part of the essence of A rather than the essence of B–if I write a Commodore 64 emulator, I am not really changing the Commodore 64 platform, I am creating a new and separate thing which happens to emulate that platform. So rather than adding a property to "Commodore 64" pointing to my emulator, I should add a property to my emulator pointing to "Commodore 64". SJK (talk) 20:05, 10 January 2017 (UTC)
      • You just have to include the subpage on "informatics" as well. I agree that this is the right way to model this. author  TomT0m / talk page 08:26, 11 January 2017 (UTC)
  • @SJK: What would be the difference beetween "implements platform" and "emulates platforms" ? This is a very similar relation conceptually. A software implementing a Java version and a software implementing a gaming device are essentially the same. Would you oppose a generalization and a rename to "implements platform" ? Maybe a problem we would have to face is the quality of the implementation, complete spec versus reversed engineered and imperfect one. author  TomT0m / talk page 08:26, 11 January 2017 (UTC)
    • @TomT0m: Hmm. Not completely opposed. Although, I wonder how broadly we define "platform". For example, an application server (e.g. WebSphere, WebLogic, JBoss) may implement a certain version of J2EE. But is J2EE a platform? Or is it a standard? Suppose we want a way to say some software implements some standard (ISO, ECMA, etc.) – would we consider those standards to be "platforms" which are implemented? I don't think so in every case – while some ISO standards define things broad enough to be called "platforms" (e.g. ISO 23271 which standardises a big chunk of .Net), other ISO standards define things too narrow to be called a "platform", e.g. ISO 9660 (CD-ROM format). Maybe we need an "implements standard" or "implements specification" property? Well then, "WebSphere implements spec J2EE" would make sense since J2EE is a formal specification which WebSphere implements. Whereas, "VICE implements specification Commodore 64" doesn't make sense since "Commodore 64" was never a formally documented specification intended for implementation by multiple vendors. So, given all of this, I'm a little hesitant about generalising "emulates platform" to "implements platform" – it might make more sense to have a different property like "implements specification" instead? On the other hand, it could be useful as a way of saying multiple computer models all constitute the same platform, e.g. "Mac Classic implements platform 68K Macintosh", "Mac II implements platform 68K Macintosh", "Quadra 840AV implements platform 68K Macintosh". So I don't know. SJK (talk) 03:04, 15 January 2017 (UTC)
      • @SJK: The naming of the property is not especially important. I think overall whatever is impemented - a platform, a spec, a gaming device - we know what it is by checking the instance of (P31) statement of the object of the claim. So a generic property to capture all those ideas is enough for us. author  TomT0m / talk page 08:36, 15 January 2017 (UTC)
  • @SJK: I'm concerned about the use of 'platform'. Is IBM207 a platform? If we look at how P400 is used [1] it seems like we would need to expand our understanding of platform to accommodate this proposed property. YULdigitalpreservation (talk) 19:09, 17 January 2017 (UTC)
    • @YULdigitalpreservation: – I'm confused, what do you mean by "IBM207". I've never heard of any IBM product by that name. SJK (talk) 19:53, 17 January 2017 (UTC)
      • @SJK: Thanks for catching that. I got the name wrong. I was attempting to talk about IBM System/370 (Q1586139). YULdigitalpreservation (talk) 19:57, 17 January 2017 (UTC)
        • @YULdigitalpreservation: I don't see why IBM System/370 (Q1586139) could not be considered a platform. "Platform" is a bit of a nebulous term which refers to some combination of hardware, CPU architecture, operating system. (It doesn't refer to an individual model of computer, or an individual OS version, but rather a family of similar computer models–and a new OS version containing incremental changes is probably not enough to constitute a new platform, yet Windows 3.1 and Windows 10 are arguably so far apart as to constitute a different platform.) For example, when we say "Commodore 64" is a platform, we are referring to the 6502 CPU, the various Commodore interface chips and peripherals, and the KERNAL ROM software–"Apple II" is a quite different platform despite having the same CPU, since the interface chips, peripherals, and software (whether in ROM or on disk) are quite different. System/370 is a series of IBM mainframe models, including the CPU and peripherals – since 370s never used off-the-shelf CPUs, we don't have the same possibility we have for C64 and Apple II of two distinct platforms both using the same CPU type. But, System/370 is was not a purely IBM platform since there were also clone manufacturers (e.g. Amdahl) which manufactured machines compatible at the hardware layer. Now, System/370 had different operating systems belonging to different OS families – OS/360 descendants such as MFT (which became OS/VS1) and MVT (which became OS/VS2 then SVS then MVS), DOS/360 (which became DOS/VSE), VM/CMS, etc. Does that make each of those operating systems a separate platform? Well, if so, then "Apple II" isn't a single platform either, because it also had multiple operating systems (Apple DOS, ProDOS). Now, the other factor is that IBM 370 is part of a succession of generations: 360, 370, 370/XA, ESA/370, ESA/390, z/Architecture–are each of these generations a distinct platform, or are they successive versions of a single platform? Well, that's a bit like asking if an Apple I and an Apple IIgs are the one platform, or if a 2016 model PC with a 64-bit CPU running Windows 10 is the same platform as the original IBM PC running PC-DOS 1.0–whether you want to consider them as different versions of one platform or as distinct platforms is a bit arbitrary. But, an IBM 360 or 370 is about as far apart from a contemporary z/Architecture mainframe as a contemporary 64-bit PC compatible is from the original IBM PC. SJK (talk) 02:16, 18 January 2017 (UTC)
          • @SJK: Thanks for sharing your thoughts on how to model this. I want to be sure that we can talk about cases of the same hardware environment on which different software is running as well as cases of the same software environments running on physical hardware as well as running on emulated hardware. I described some of this at WikiProject_Informatics/Configured_environments. YULdigitalpreservation (talk) 19:11, 20 January 2017 (UTC)

emulated by[edit]

   Under discussion
Description This property will indicate hardware that can be emulated by a piece of emulation software
Data type Item
Domain informatics
Example
Source List of computer system emulators
Planned use I would like to add information about what emulators are available for different hardware configurations.
Motivation

We need a way to connect these applications with the hardware that they emulate. YULdigitalpreservation (talk) 19:31, 16 December 2016 (UTC)


Discussion

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics.

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics Does the property work the way it is? ChristianKl (talk) 20:57, 16 February 2017 (UTC)

supports programming language[edit]

   Under discussion
Description programming language which is supported by this programming tool
Data type Item
Domain instances of programming tool (Q1077784) (including subclasses)
Allowed values instances of programming language (Q9143) (including subclasses)
Example
See also programming language (P277)
Motivation

programming language (P277) means the programming language a program is developed in. However, for programming tools, the programming languages supported by the tool can be different from the programming language in which the tool itself is written. For example, GnuCOBOL (Q7095747) is a compiler for the programming language COBOL (Q131140), but it is not itself written in COBOL, it is actually written in C (Q15777). So, in that case, P277 would point to the C programming language and this property would point to COBOL. The domain of this property is any tool which takes some specific programming language(s) as input or subject, whether that be a compiler, interpreter, debugger, IDE, profiler, code coverage tool, testing framework, static analysis tool, etc. SJK (talk) 13:56, 10 January 2017 (UTC)

Discussion
  • I think something like this is good, but I think I would prefer to see more specific properties e.g. "compiles", "syntax colors", and etc., unless there's a reasonable belief that every program is going to support the same features for every language it supports. --Izno (talk) 21:35, 10 January 2017 (UTC)
    • @Izno: Not in principle opposed to more specific properties, although it is unclear to me how many are actually needed, so I thought proposing just one was a good start. Also, do we need more specific properties or can that be expressed via qualifiers? For example, what if we qualified this property with use (P366) syntax highlighting (Q747907) to say it supported the programming language for syntax colouring, or use (P366) scripting language (Q187432) to say it supported it as a scripting language? In many cases, it should be obvious what this property means by the class the item belongs to, e.g. on an instance of compiler (Q47506) we can assume it means the compiler supports this programming language as input to be compiled, unless a qualifier indicates something else. SJK (talk) 07:07, 11 January 2017 (UTC)

autonomous system number[edit]

   Under discussion
Description A unique ASN is allocated to each AS for use in BGP routing.
Data type External identifier
Template parameter asn at en:template:Infobox NSP
Domain ISPs
Allowed values number
Example Cogent Communications (Q1106938) → 174
Source unclear, any user have some?
Robot and gadget jobs probably
Motivation

See en:Autonomous system (Internet) GZWDer (talk) 16:10, 16 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support with sources of IANA, AFRINIC, APNIC, ARIN, LACNIC and RIPE NCC for data, and constraints that the number is a 32-bit unsigned integer between the range 0 and 4294967296 inclusive. If possible, reserved ASNs should also be added as constraints to prevent their use. Pixeldomain (talk) 07:02, 17 January 2017 (UTC)
  • Symbol support vote.svg Support - however, the domain statement is wrong, any organization can have an ASN, it's required for a network to be multi-homed under the BGP protocol, I believe. So many universities for instance have them. ArthurPSmith (talk) 13:54, 17 January 2017 (UTC)

algorithm complexity[edit]

This is a proposal of six related properties.

worst-case performance[edit]

   Under discussion
Description time complexity of an algorithm at most
Data type Mathematical expression
Template parameter time at en:Template:Infobox algorithm
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(n^2)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No

best-case performance[edit]

   Under discussion
Description time complexity of an algorithm at least
Data type Mathematical expression
Template parameter time at en:Template:Infobox algorithm
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(n log n)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No

average performance[edit]

   Under discussion
Description time complexity of an algorithm on average
Data type Mathematical expression
Template parameter average-time at en:Template:Infobox algorithm
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(n log n)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No

worst-case space complexity[edit]

   Under discussion
Description space complexity of an algorithm at most
Data type Mathematical expression
Template parameter space at en:Template:Infobox algorithm
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(n)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No

best-case space complexity[edit]

   Under discussion
Description space complexity of an algorithm at least
Data type Mathematical expression
Template parameter N/A
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(log n)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No

average space complexity[edit]

   Under discussion
Description space complexity of an algorithm on average
Data type Mathematical expression
Template parameter N/A
Domain algorithm
Allowed values math expression
Example quicksort (Q486598) → O(log n)
Source e.g. en:Sorting algorithm
Robot and gadget jobs No
Motivation

(Add your motivation for this property here.) GZWDer (talk) 18:53, 16 January 2017 (UTC)

Discussion
  • Symbol support vote.svg Support best-case and worst-case property proposals. Pixeldomain (talk) 07:17, 17 January 2017 (UTC)
  • Pictogram voting comment.svg Comment How is "average" defined? Sum of the time taken to execute each permutation of the algorithm, divided by the total number of permutations? Is "average" defined by a probability distribution of a limited number of samples? I see a comment at English Wikipedia which indicates "average" is ambiguous, whereas "expected time complexity" is allegedly better defined. Pixeldomain (talk) 07:17, 17 January 2017 (UTC)
  • Symbol support vote.svg Support --Andrawaag (talk) 09:55, 27 January 2017 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics ChristianKl (talk) 11:16, 27 January 2017 (UTC)

  • Pictogram voting comment.svg Comment Agreed with the previous comment. Please add the relate item to the exact complexity notion associated.
  • Pictogram voting comment.svg Comment Datatype should be item, and the formula put in this item. It's less error prone as there is no ambiguity on the kind of "O" used in the formula and there is no risk of bad parsing later. Something like a "linear" item, or maybe "linear space". It's even possible to create items like "linear time algorithm". author  TomT0m / talk page 11:43, 27 January 2017 (UTC)
  • Symbol oppose vote.svg Oppose per TomT0m unless the data type is changed. Also do we really need 6 properties for this, isn't there another way to handle it (e.g with a qualifier?) ArthurPSmith (talk) 16:35, 27 January 2017 (UTC)
  • Pictogram voting comment.svg Comment en:w:Shellsort has some examples of non-simple complexities, for example:

. If this was an individual item, what would it be labelled? And how many items would need to be created to support the definition of all algorithm complexities? At the moment, I don't see how it would be practical to create an item for each complexity. Pixeldomain (talk) 01:30, 6 February 2017 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics Are there additonal comments about how this property should be created? Item or formula? ChristianKl (talk) 15:52, 16 February 2017 (UTC)

  • Pictogram voting comment.svg Comment Items would clearly make querying for algorithms with similar complexity easier (identifier instead of looking for a similar string). --Tobias1984 (talk) 19:55, 16 February 2017 (UTC)
  • Pictogram voting comment.svg Comment @Tobias1984: Agreed that items have theoretical benefits over formulas, but the practical outcome will be many items without meaningful labels (see my example above). How many complexity formulas will have meaningful labels in different languages? On this basis, I still think formulas may be better suited for these properties. Pixeldomain (talk) 03:12, 17 February 2017 (UTC)

data storage device[edit]

   Under discussion
Description data storage device supported by a machine (e.g. camera or mobile phone)
Represents data storage device (Q193395)
Data type Item
Template parameter |storage= at en:Template:Infobox camera
Domain machine
Allowed values data storage device
Example Canon EOS 300D (Q64039)CompactFlash (Q678615)
Source Freebase
Robot and gadget jobs Probably
Motivation

Note: First proposed at Wikidata:Property_proposal/Archive/38#storage medium. GZWDer (talk) 13:03, 18 January 2017 (UTC)

Discussion

public key fingerprint[edit]

   Under discussion
Description short sequence of bytes to identify a longer cryptographic public key
Represents public key fingerprint (Q6578920)
Data type String
Allowed values alphanumeric
Example Tim Berners-Lee (Q80) → 4D4B 9D1D C032 0710 3CDC DE0B 344D 9666 1177 9EE7
Glenn Greenwald (Q5568842) → 734A 3680 A438 DD45 AF6F 5B99 A4A9 28C7 69CD 6E44
Motivation

The exact system (PGP, SSH, Groove etc) can be defined with a qualifier. ~nmaia d 17:36, 25 January 2017 (UTC)

Discussion
Having a property makes sense but there should be a notion that it always has to be sourced. ChristianKl (talk) 09:21, 27 January 2017 (UTC)
Symbol support vote.svg Support but wonder whether determination method (P459) should be a mandatory qualifier to describe how the fingerprint was generated. I also suggest creating a regular expression for "allowed values" which captures common syntaxes for public key fingerprints (covering PGP, X.509 certificates, etc). Dhx1 (talk) 14:28, 1 February 2017 (UTC)
@Dhx1: Thanks for the suggestion. I also thought of this but since I don't know how to create a regular expression, I'll leave that open to anyone who would like to do it. ~nmaia d 15:46, 1 February 2017 (UTC)
For OpenPGP the regexe should be: '([0-9A-F]{4} ){9}[0-9A-F]{4}' or more flexible but harder to read: '([0-9A-F]{4} ?){10}' -- MichaelSchoenitzer (talk) 19:30, 4 February 2017 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pictogram voting comment.svg Notified participants of WikiProject Informatics ChristianKl (talk) 17:58, 4 February 2017 (UTC)

  • Pictogram voting comment.svg Comment Isn't this fairly dynamic information? --Swpb (talk) 17:08, 15 February 2017 (UTC)
    Pictogram voting comment.svg Comment @Swpb: Keys are generally changed very infrequently (2 years or more). Additionally, historical key information is just as important as current key information. Dhx1 (talk) 13:49, 19 February 2017 (UTC)

ITU/ISO/IEC object identifier[edit]

   Under discussion
Description unique global identifier standardized by the ITU and ISO/IEC for naming any object, concept, or thing
Represents object identifier (Q1781028)
Data type External identifier
Domain any item
Allowed values regular expression: [012](\.\d+)*
Example Intel (Q248) → 1.3.6.1.4.1.343
Source various registries
Planned use apply OIDs to Wikidata items such as organisations/companies, networking equipment, encryption algorithms, etc
Motivation

Object identifiers (OIDs) are widely used in the telecommunications and computing sectors to uniquely identify objects, concepts and things. Typically this includes encryption algorithms, attributes and fields within computer network protocols, hardware equipment operating on networks and some objects/concepts in the health sector. These identifiers are standardized at the top level by the ITU and ISO/IEC, with registered authorities responsible for standardizing and maintaining sub-elements of the tree of identifiers. See en:Object identifier for more detailed information and examples of usage. Pixeldomain (talk) 04:36, 24 February 2017 (UTC)

Discussion
  • Symbol support vote.svg Support. Though this needs a more specific name, perhaps "ICU/ISO/IEC object identifier"? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:01, 24 February 2017 (UTC)

Geology[edit]

Please visit Wikidata:WikiProject Geology for more information.

Geography[edit]

tributary orientation[edit]

   Under discussion
Description Specify if the stream confluence is a left bank or right bank tributary
Represents watercourse (Q355304)
Data type Item
Domain Hydrography
Allowed values left bank (Q27834806) and right bank (Q27834918)
Example Shenandoah River (Q777907) → right bank of (mouth of the watercourse (P403)) Potomac River (Q179444)
Motivation
  • It is useful to know if a stream confluence is of left bank or right bank. --YanikB (talk) 12:55, 14 February 2017 (UTC)
Discussion
  • @YanikB: When you create a new property proposal please don't delete the motivation part but fill it and sign the proposal, so it's easy to see who created it. Don't label a proposal as ready the moment it get's created.
When it comes to the examples, tell us which items should be associated with which other items.
Currently, I don't think that the description is informative enough for a person who doesn't already know what the term "Hydrographic orientation" means. ChristianKl (talk) 11:20, 14 February 2017 (UTC)
✓ Done --YanikB (talk) 12:58, 14 February 2017 (UTC)
  • @YanikB: thanks for updating but this makes no sense to me - and I can find no ready definition online of "hydrographic orientation". Do you have a source or explanation for what Shenandoah River (Q777907) → right bank means? ArthurPSmith (talk) 17:08, 14 February 2017 (UTC)
@ArthurPSmith: The idea is to determine if a stream is of left bank or right bank. I found a name for this property from the article of WP bank (Q2897058). As I am French-speaking the English name may not make sense. Someone could translate ? --YanikB (talk) 14:34, 15 February 2017 (UTC)
@YanikB: the enwiki article for bank (Q2897058) shows a diagram with "left bank" and "right bank", but every river has both sides, I don't understand what your criterion is for choosing one side or the other here. I also looked at the article in French wikipedia which doesn't have that diagram and doesn't seem to mention "left" and "right" ("gauche" or "droit") at all (the first image shows a river with its two banks). Neither article mentions "hydrographic orientation" or "Orientation hydrographique" respectively, nor are there other articles anywhere in those wikipedias with that label or anything like it that I can find. Please point to a URL with a real reference here if this is really something you have source information for, because as you have explained it to this point I don't believe this makes any sense as a property at all. ArthurPSmith (talk) 14:45, 15 February 2017 (UTC)
@ArthurPSmith: I should have mentioned that it is about the confluence with a main stream. So the Shenandoah(mouth of the watercourse (P403)) is a right bank tributary of the Potomac.--YanikB (talk) 15:06, 15 February 2017 (UTC)
Ah, ok, I suppose that makes this well-defined. I see you've updated the definition. I wonder if the label could be better too. I'll look around if there's another term for this. ArthurPSmith (talk) 18:46, 15 February 2017 (UTC)
  • Symbol support vote.svg Support ok I've modified the name to "tributary orientation" which seems to be the closest I can find to an English name for this. I think it's a good idea to have this property. However, it could also be done via instance of (P31)... ArthurPSmith (talk) 17:09, 16 February 2017 (UTC)
The name could also be "tributary bank confluence". --YanikB (talk) 13:14, 19 February 2017 (UTC)
  • The definition is a bit more clear but I would expect that most readers still don't know what it is about. Additionally I'm not sure whether left (Q13196750) and right (Q14565199) are the right items. How about items titled "left bank" and "right bank"? ChristianKl (talk) 21:00, 16 February 2017 (UTC)
Why not left bank (Q27834806) and right bank (Q27834918). --YanikB (talk) 13:14, 19 February 2017 (UTC)
  • Given the example, is this property supposed to be used as a qualifier? ChristianKl (talk) 21:15, 16 February 2017 (UTC)
@ChristianKl: Ideally, but tools have some difficulty working with qualifiers. :( --YanikB (talk) 13:14, 19 February 2017 (UTC)
@ArthurPSmith, ChristianKl: I have made a request to allow the use left bank (Q27834806) or right bank (Q27834918) as qualifier for mouth of the watercourse (P403) (Add qualifiers). --YanikB (talk) 12:53, 22 February 2017 (UTC)

Maths[edit]

Please visit Wikidata:WikiProject Mathematics for more information. To notify participants use {{Ping project|Mathematics}}

probability distribution related properties[edit]

This is a proposal of several probability distribution related properties

support of a function[edit]

   Under discussion
Description the subset of the domain containing those elements which are not mapped to zero
Represents support (Q1136376)
Data type Mathematical expression
Template parameter support at en:Template:Probability distribution
Domain functions
Example normal distribution (Q133871)R
Source Many
Robot and gadget jobs Probably no

probability density function[edit]

   Under discussion
Description a function whose value at any given sample (or point) in the sample space can be interpreted as providing a relative likelihood that the value of the random variable would equal that sample
Represents probability density function (Q207522)
Data type Mathematical expression
Template parameter pdf at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

probability mass function[edit]

   Under discussion
Description a function that gives the probability that a discrete random variable is exactly equal to some value
Represents probability mass function (Q869887)
Data type Mathematical expression
Template parameter pdf at en:Template:Probability distribution
Domain probability distribution
Example Poisson distribution (Q205692)
Source Many
Robot and gadget jobs Probably no

cumulative distribution function[edit]

   Under discussion
Description the probability that X will take a value less than or equal to x
Represents cumulative distribution function (Q386228)
Data type Mathematical expression
Template parameter cdf at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

quantile function[edit]

   Under discussion
Description the value at which the probability of the random variable is less than or equal to the given probability
Represents quantile function (Q3489473)
Data type Mathematical expression
Template parameter quantile at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

mean of a probability distribution[edit]

   Under discussion
Description the long-run average value of repetitions of the experiment it represents
Represents expected value (Q200125)
Data type Mathematical expression
Template parameter mean at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)μ
Source Many
Robot and gadget jobs Probably no

median of a probability distribution[edit]

   Under discussion
Description the value separating the higher half of a data sample, a population, or a probability distribution, from the lower half
Represents median (Q226995)
Data type Mathematical expression
Template parameter median at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)μ
Source Many
Robot and gadget jobs Probably no

mode of a probability distribution[edit]

   Under discussion
Description the value that appears most often in a set of data
Represents mode (Q188224)
Data type Mathematical expression
Template parameter mode at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)μ
Source Many
Robot and gadget jobs Probably no

variance of a probability distribution[edit]

   Under discussion
Description the expectation of the squared deviation of a random variable from its mean
Represents variance (Q175199)
Data type Mathematical expression
Template parameter mode at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)μ
Source Many
Robot and gadget jobs Probably no

skewness of a probability distribution[edit]

   Under discussion
Description a measure of the asymmetry of the probability distribution of a real-valued random variable about its mean
Represents skewness (Q330828)
Data type Mathematical expression
Template parameter skewness at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871) → 0
Source Many
Robot and gadget jobs Probably no

excess kurtosis[edit]

   Under discussion
Description a measure of the "tailedness" of the probability distribution of a real-valued random variable
Represents Kurtosis (Q287251)
Data type Mathematical expression
Template parameter kurtosis at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871) → 0
Source Many
Robot and gadget jobs Probably no

information entropy[edit]

   Under discussion
Description the expected value (average) of the information contained in each message
Represents Information entropy (Q204570)
Data type Mathematical expression
Template parameter entropy at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

moment-generating function[edit]

   Under discussion
Description an alternative specification of its probability distribution
Represents Moment-generating function (Q535587)
Data type Mathematical expression
Template parameter mgf at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

characteristic function[edit]

   Under discussion
Description the Fourier transform of the probability density function
Represents characteristic function (Q822139)
Data type Mathematical expression
Template parameter chat at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

Fisher information[edit]

   Under discussion
Description a way of measuring the amount of information that an observable random variable X carries about an unknown parameter θ of a distribution that models X
Represents Fisher information (Q1420659)
Data type Mathematical expression
Template parameter fisher at en:Template:Probability distribution
Domain probability distribution
Example normal distribution (Q133871)
Source Many
Robot and gadget jobs Probably no

probability generating function[edit]

   Under discussion
Description a power series representation (the generating function) of the probability mass function of the random variable
Represents Probability-generating function (Q372071)
Data type Mathematical expression
Template parameter pgf at en:Template:Probability distribution
Domain probability distribution
Example Poisson distribution (Q205692)
Source Many
Robot and gadget jobs Probably no
Motivation

These properties may provide some useful information about probability distributions. GZWDer (talk) 21:15, 17 February 2017 (UTC)

Discussion
  • Currently many of those properties have quite general names and are therefore likely to be used outside of the stated domain. Please use more narrow names if you want to focus on this domain. ChristianKl (talk) 22:38, 17 February 2017 (UTC)
    • Changed.--GZWDer (talk) 05:27, 18 February 2017 (UTC)
  • Okay the names now look reasonable to me. GA candidate.svg Weak support.

Opensofias (talk) Tobias1984 (talk) Micru (talk) Arthur Rubin (talk) Cuvwb (talk) Danneks (talk) TomT0m (talk) Tylas (talk) Physikerwelt (talk) Lymantria (talk) Pictogram voting comment.svg Notified participants of WikiProject Mathematics ChristianKl (talk) 16:33, 18 February 2017 (UTC)

All sciences[edit]

models[edit]

   Under discussion
Description this item models some aspect of this real thing
Represents Model (Q234018)
Data type Item
Domain equation (Q11345) to start
Allowed values natural science (Q7991) to start
Example Navier–Stokes equations (Q201321)fluid dynamics (Q216320)
Planned use connecting equations to fields of use
Motivation

This is a little rough of a proposal, so I'm throwing some spaghetti at the wall here.

I need a way to connect e.g. Navier–Stokes equations (Q201321) to e.g. fluid dynamics (Q216320). I asked at Wikidata:Project chat#Domain of an equation and it seems this is a hole of some sort. I could hack around this ostensibly by saying that there are certain terms in the equation (such as energy), but that doesn't actually get me to the "domain" of the system modeled by these equations.

I could maybe use used by (P1535)? This doesn't carry the full semantics desired, however. I could go the other direction and say the field "uses" the equations, but I think that leads to a very cluttered field item.

There's a related problem at e.g. numerical methods in continuum mechanics (Q18327519) which splits the notion of a numerical method by orthogonal fields such as continuum mechanics (which I only noticed by chance). Since we have no Wiki* pages which are concerned with those specific Wikidata items, I don't think the way that's been done is ideal. That may need another property though--I'll invite discussion here for that subtopic. Izno (talk) 23:33, 3 January 2017 (UTC)

Discussion
any possibility of "modeled by" instead of "Model"? MechQuester (talk) 05:48, 30 January 2017 (UTC)

Tobias1984 Snipre Physikerwelt Pamputt Petermahlzahn Jibe-b Restu20 Daniel Mietchen TomT0m ArthurPSmith Mu301 Sarilho1 SR5 DavRosen Pictogram voting comment.svg Notified participants of WikiProject Physics ChristianKl (talk) 12:11, 6 February 2017 (UTC)

WIGOS identifier[edit]

   Under discussion
Description identifier of a meteorological station, in the WIGOS database
Represents WIGOS identifier (Q28686426)
Data type External identifier
Domain weather station (Q190107)
Allowed values int\.wmo\.wigos-([0-9]|1[0-4])-(([0-9]|[1-9][0-9]{1,3}|[1-5][0-9]{4}|6[0-4][0-9]{3}|65[0-4][0-9]{2}|655[0-2][0-9]|6553[0-4])-){2}-[0-9A-Z]{1,16}(-[0-9A-Z]+)?
(refer to Manual on the WMO Integrated Global Observing System (Q28686657) page 106 for further information)
Example Blue Hill Meteorological Observatory (Q1803017) → int.wmo.wigos-0-20000-0-74492
Source
Planned use Insert weather station items into Wikidata to allow external climate databases to be queried for climate data, adding further information to a Wikidata query. This can be useful for automatically generating climate data for a city by finding the nearest weather station, then fetching external climate data for that closest weather station.
Robot and gadget jobs Almost all weather stations from Legacy format station report (in use until 2018) can likely be imported automatically in bulk, as there are currently ~50 weather station items listed in Wikidata.
Motivation

The WIGOS identifier is used by the WMO and other meteorological organisations to uniquely identify weather stations around the world. By creating a new Wikidata item for each weather station around the world, it becomes possible to query Wikidata for the weather station(s) closest to a particular city, obtain the WIGOS identifier(s) and then query external climate information databases to obtain real time, near real time and/or historical climate data recorded by the particular station. Dhx1 (talk) 14:19, 6 February 2017 (UTC)

Discussion
  • Symbol support vote.svg Support This sounds useful. The idea is to have an item for every weather station in the world? Do we have some of these in wikidata now? ArthurPSmith (talk) 17:00, 6 February 2017 (UTC)
  • Symbol support vote.svg Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:15, 6 February 2017 (UTC)

Bureau of Meteorology station number[edit]

   Under discussion
Description identifier of an Australian meteorological station issued by the Bureau of Meteorology
Represents Bureau of Meteorology station number (Q28691558)
Data type External identifier
Domain weather station (Q190107)
Allowed values [0-9]{6}
Example Flinders Island Airport (Q28692248)099005
Source List of all sites
Planned use Insert weather station items into Wikidata to allow external climate databases to be queried for climate data, adding further information to a Wikidata query. This can be useful for automatically generating climate data for a city by finding the nearest weather station, then fetching external climate data for that closest weather station.
Formatter URL https://www.bom.gov.au/clim_data/cdio/metadata/pdf/siteinfo/IDCJMD0040.$1.SiteInfo.pdf
Robot and gadget jobs Almost all weather stations from List of all sites can likely be imported automatically in bulk, as there are currently ~50 weather station items listed in Wikidata.
See also WIGOS identifier
Motivation

The BoM station number is used by the BoM to uniquely identify weather stations within Australia. By creating a new Wikidata item for each weather station within Australia, it becomes possible to query Wikidata for the weather station(s) closest to a particular city, obtain the BoM station number(s) and then query external BoM climate information databases to obtain real time, near real time and/or historical climate data recorded by the particular station. The BoM station number also allows external lookup of BoM station information documents which provide highly detailed information about data capture configuration, instruments installed, periods of record capture, etc for each Australian station. Dhx1 (talk) 14:46, 6 February 2017 (UTC)

Discussion
  • Symbol support vote.svg Support ChristianKl (talk) 11:57, 8 February 2017 (UTC)
  • Symbol support vote.svg Support. I'm concerned at the formatter URL is a PDF. Might that causes issues elsehere? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:31, 14 February 2017 (UTC)
  • @Dhx1: Can you address the concerns, that this property points to a PDF? ChristianKl (talk) 15:53, 16 February 2017 (UTC)
  • Pictogram voting comment.svg Comment @Pigsonthewing: We could remove the formatter URL from this property, but why? A formatter URL doesn't currently seem to guarantee much about the resource being pointed to. What are formatter URLs meant to point to? HTML only? If so, which version of HTTP and TLS are to be expected? Which version of HTML (or set of extensions), version of CSS, JavaScript, etc are required to load the resource? For HTTP, a browser would have to wait for a Content-Type header to be returned from a server before deciding how to render the content (HTML versus XHTML versus PDF versus other file formats). Dhx1 (talk) 14:11, 19 February 2017 (UTC)

GPnotebook person ID[edit]

   Under discussion
Description ID of a general practitioner in the British medical database GPnotebook
Represents GPnotebook (Q5514379)
Data type External identifier
Template parameter en:Template:GPnotebook
Domain various
Allowed values -?\d+
Example dyspnea (Q188008)825557022
Formatter URL https://www.gpnotebook.co.uk/simplepage.cfm?ID=$1
Robot and gadget jobs from Wikipedia
Motivation

see usage GZWDer (talk) 18:24, 18 February 2017 (UTC)

Discussion
  • I added a description for this property based on the Wiki description. ChristianKl (talk) 22:26, 20 February 2017 (UTC)

Evidence & Conclusion Ontology ID[edit]

   Under discussion
Description Evidence & Conclusion Ontology ID
Represents Evidence & Conclusion Ontology (Q28445410)
Data type External identifier
Domain evidence items. To be used with the qualifier determination method (P459)
Allowed values ECO:[0-9]{7}
Example enzyme assay evidence used in manual assertion -> ECO ID -> ECO:0005801
Source http://evidenceontology.org/
Planned use create all evidence items (~600 items)
Motivation

The Evidence Ontology (ECO) is a structured, controlled vocabulary for capturing evidence in biological research, but can be applied to other fields as well. ECO includes diverse terms for categorizing evidence that supports annotation assertions including experimental types, computational methods, author statements and curator inferences. Using ECO, annotation assertions can be distinguished according to the evidence they are based on such as those made by curators versus those automatically computed or those made via high-throughput data review versus single test experiments.

A small subset of ECO is already being used with determination method (P459) on protein items with GO terms, for example here. This will expand the number, specificity, and organization of evidence items in Wikidata, allowing more powerful queries based on types of evidence, and interoperability with other ontologies using ECO. Gstupp (talk) 20:20, 22 February 2017 (UTC)

Discussion