Shortcut: WD:PP/SCI

Wikidata:Property proposal/Natural science

From Wikidata
Jump to: navigation, search

See also:
Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available.
Wikidata:Properties for deletion – proposals for the deletion of properties.


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 is already pending or has been rejected.
  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. See WD:WikiProject Infoboxes for suggestions.
  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. Creation can be done after 1 week by a property creator or an administrator.
  2. See steps when creating properties.

Add a request

This page is archived, currently at

To add a request, you should use this form:

=== {{TranslateThis | anchor = en
| en = PROPERTY NAME IN ENGLISH
| de = <!-- PROPERTY NAME IN German (optional) -->
| fr = <!-- PROPERTY NAME IN French (optional) -->
<!-- |xx = property names in some other languages -->
}} ===
{{Property documentation
|status                 = <!--leave this empty-->
|description            = {{TranslateThis
  | en = ...
  }}
|subject item           = <!-- <!-- item corresponding to the concept represented by the property, if applicable; example: item ORCID (Q51044) for property ORCID (P496) --> -->
|infobox parameter      = Wikipedia infobox parameters, if any; ex: "population" in [[:en:template:infobox settlement]]
|datatype               = put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)
|domain                 = types of items that may bear this property
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|source                 = external reference, Wikipedia list article, etc.
|example                = {{Q|1}} → {{Q|2}}
|formatter URL          = <!-- for external identifiers, URL pattern where $1 replaces the value -->
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|robot and gadget jobs  = Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
}}

;Motivation

(Add your motivation for this property here.) ~~~~

;{{int:Talk}}

For a list of infobox parameters, you might want to use table format:

{{List of properties/Header}}

{{List of properties/Row|id=
|title          = audio
|type           = media
|qualifier      =
|description    = Commons sound file
|example-subject= Q187 <!-- Il Canto degli Italiani -->
|example-object = Inno di Mameli instrumental.ogg
}}

</table>

For blank forms, see Property documentation and List of properties/Row


Physics[edit]

Biology / Biologie / Biologie[edit]

Please visit Wikidata:WikiProject Taxonomy for more information. To notify participants use {{Ping project|Taxonomy}}
Please visit Wikidata:WikiProject Biology for more information.
See also Wikidata:Property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes

gender of generic name[edit]

   In progress
Description grammatical gender of generic name (in taxonomy)
Represents grammatical gender (Q162378)
Data type Item
Domain generic names
Allowed values masculine gender (Q499327), feminine gender (Q1775415), neuter (Q1775461)
Example Cyclops (Q1421606)masculine gender (Q499327)
Source external references
Proposed by Brya (talk) 05:40, 19 July 2015 (UTC)
Motivation

To record grammatical gender of generic names. Seems like a very basic property (I cannot think why it is not here. Apparently grammatical gender is mostly used for inhabitants of countries: countries are inhabited by nouns with masculine grammatical gender and nouns with feminine grammatical gender). A lot of problems with adjectival epithets can be prevented by recording gender of generic names. It would seem handy to use this as a qualifier, but often it should be referenced. Brya (talk) 05:40, 19 July 2015 (UTC)

Discussion

Josve05a (talk)
FelixReimann (talk)
Infovarius (talk)
Daniel Mietchen (talk)
Soulkeeper (talk)
Brya (talk)
Klortho (talk)
Tobias1984 (talk)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm

Pictogram voting comment.svg Notified participants of Wikiproject Taxonomy

  • Symbol support vote.svg Support --Succu (talk) 09:59, 19 July 2015 (UTC)
  • Gender is language-dependent. Romance languages (Q19814) have only two genders and Finno-Ugric languages (Q79890) plus Japanese don't have any grammatical gender.
    In taxonomy there is only roman-greek gender.--Kopiersperre (talk) 10:42, 19 July 2015 (UTC)
    Yes, in nomenclature there are only the three genders. For other uses it would be possible to add more genders (not that I have knowledge of any language requiring more). Less genders does not sound problematic. - Brya (talk) 15:13, 19 July 2015 (UTC)
  • Should use be restricted to being a qualifier of taxon name (P225)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:57, 19 July 2015 (UTC)
    Perhaps, but the references could get very mixed up. - Brya (talk) 15:13, 19 July 2015 (UTC)
  • Pictogram voting question.svg Question Why is this proposal in the Biology section? Visite fortuitement prolongée (talk) 14:51, 19 July 2015 (UTC)
    It is needed in Taxonomy. Apparently there is no hurry to use it elsewhere. - Brya (talk) 15:13, 19 July 2015 (UTC)
    Move it in Wikidata:Property proposal/Generic and renamme it as "grammatical gender of latin language nouns". Visite fortuitement prolongée (talk) 16:27, 19 July 2015 (UTC)
  • Pictogram voting comment.svg Comment Rename taxonomic gender then. I would oppose a generic grammatical gender property as it's an open door to a mess. Genders are languagues dependants and belongs to wikitionary. I won't oppose but I won't support, seems more cosmetic than really useful and authoritative. Is there a taxonomic database with this information ? author  TomT0m / talk page 15:27, 19 July 2015 (UTC)
Cosmetic? No! The gender of the genus determines the ending of the epithet (e.g. -a/-us). An current example: The gender of the tortoise genus Chelonoidis Fitzinger, 1835 (Testudines: Testudinidae) (2014). --Succu (talk) 15:35, 19 July 2015 (UTC)
@Succu: Absolutely. that's what I define as cosmetic, this have nothing to do with the properties of the taxon itself and is totally arbitrary. The author would have chosen the other possibility this would have not changed anything. In such cases I personnaly would render a label a/us without losing more time for nothing :) Anyway, I don't understand, the terminations are not hardcoded into the labels of the names ? And if there is any plural to have, don't you refer to all the members of the taxon (that is to say, are not the instances all the organisms instances classified in this taxon) ?author  TomT0m / talk page 15:49, 19 July 2015 (UTC)
It determines which taxon name (P225) is correct according to the rules of nomenclature (Code of nomenclature (P944)). Another example from my talk page. --Succu (talk) 16:01, 19 July 2015 (UTC)
OK, go on guys :) I'm hermetic to such problems, and I don't understand why people still want to keep these rules and try to strictly enforce them, but if you really want to do the job why not ? But I don't really understand if some name are decided non correct, why it's not enough. Do you want to double check ? author  TomT0m / talk page 16:29, 19 July 2015 (UTC)
'grammatical gender' is a wiktionary property. we must not have a property with that name on wikidata or it will be terribly abused. I can only support this if the property name is changed to "gender of taxon name". Can someone reassure me that once this property is added then some basic logic will be able to generate all versions of a taxon name? Filceolaire (talk) 04:05, 21 July 2015 (UTC)
I don't understand the users who object because they would not use the new property themselves. But I have changed it to be restricted to generic names. The "some basic logic will be able to generate all versions of a taxon name?" suggests a misunderstanding: a taxon name has only one version (that is why a database is needed in the first place). To some degree the correct name can be generated by "some basic logic", but it will need more components (gender only applies to adjectives). - Brya (talk) 05:15, 21 July 2015 (UTC)
@Brya: I did not oppose, and you did not get the whole page : if gender of people is in the scope of Wikidata, gender of name is in the scope of Wiktionary, not Wikidata, so we're reluctant to vote for properties for names in general, and there is quite a few proposal about these. Taxonomy is a special case, but I did not understand your real use case I don't understand how it would be used for example in an infobox, so I'm still reluctant, although I did not oppose. author  TomT0m / talk page 07:46, 21 July 2015 (UTC)
There is no telling how popular this will be in an infobox, but there is no real reason not to include this. There are not all that many databes that include this information, but there are some. Mostly this would serve a structural function, to help in other items. - Brya (talk) 10:38, 21 July 2015 (UTC)
Brya I don't say I object because I won't use it. I say that I object because others will use it for all kinds of purposes for which it is not appropriate. If "a taxon name has only one version" then this property is not needed and I Symbol oppose vote.svg Oppose it.
If it a taxon name has a second version when it is used as an adjective and this property will enable us to automatically generate that adjectival version AND the name is changed to make it clear what it is for then I would reluctantly support it. Which is it? Your reply above says both. Can we change the property to "taxon name used as an adjective" and make it a string property with the adjectival version of the name as the object? Joe Filceolaire (talk) 16:22, 22 July 2015 (UTC)
Well, the "taxon name used as an adjective" does not exist at all. The taxon names that have a gender are generic names. Say, the name Schinus, which is feminine, but much of the literature assumes it is masculine. The gender is relevant for names below the level of species, which consists of two or three parts. For example, Schinus terebinthifolia is the name of a species, but those who assume Schinus is masculine will write Schinus terebinthifolius. At the moment lots of names in the genus are subject to great confusion, with several having a separate "masculine" item and a "feminine" item. Recording the gender of the generic name will make it doable to bring this in order. - Brya (talk) 16:45, 22 July 2015 (UTC)
(out of topic) this is not really a surprise to me, fighting for correction into such an arbitrary concept is doomed to fail because people won't really care for good reasons. This is like fighting a windmeal. So my personnal advice would be ... let it go. author  TomT0m / talk page 13:01, 23 July 2015 (UTC)
So a lot of scientists wasting their time with projects like Global Names Index, TomT0m? --Succu (talk) 14:44, 23 July 2015 (UTC)
@Succu: Mmmm, a lot of scientists have created this database especially to store the gender of names ? That's weird, it says that it's a database of name. author  TomT0m / talk page 14:14, 26 July 2015 (UTC)

flower colour[edit]

   In progress
Description colour of flowers of a plant species, hybrid or cultivar
Data type Item
Domain flowering plants
Allowed values colours
Example Jasminum officinale (Q515610)white (Q23444)
Motivation

Of interest to gardeners, florists, botanists and others. We may need to create items for colour ranges or groups, as used by reliable sources (e.g. en.WP describes Hyacinthoides non-scripta (Q164013) as "violet–blue"). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:18, 29 July 2015 (UTC)

Postscript: Prior discussion is at Wikidata:Project chat#Adding property colour (for flowers), and I should have mentioned that I posted this at the request of User:Timboliu, posting as an IP on my talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:59, 30 July 2015 (UTC)
Discussion

I really like it that we are venturing more and more into covering traits now (after things like eye color (P1340) and mushroom cap shape (P784)), but I have not seen a strategic discussion as to whether it would be better to use more generic properties on more specific items or more specific properties on more generic items, though the issue keeps popping up (see also the volcano eruption discussion). With this in mind, I am not sure about the benefit of this proposed property over starting an item for "flower of Jasminum officinale" and using colour properties like color (P462) on it. --Daniel Mietchen (talk) 01:12, 30 July 2015 (UTC)

Josve05a (talk)

FelixReimann (talk)
Infovarius (talk)
Daniel Mietchen (talk)
Soulkeeper (talk)
Brya (talk)
Klortho (talk)
Tobias1984 (talk)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm

Pictogram voting comment.svg Notified participants of Wikiproject Taxonomy --Daniel Mietchen (talk) 01:15, 30 July 2015 (UTC)

I think this may get complicated very quickly. For example, this means having to deal with "violet–blue", "violet and blue", and "violet or blue". I suggest first looking at existing databases (here is one, and another, but there should be lots of them). - Brya (talk) 04:54, 30 July 2015 (UTC)
There is WikiProject Identification Keys, but I'm not sure if it actually goes somewhere. --- Jura 05:02, 30 July 2015 (UTC)

Pictogram voting comment.svg Comment A flower consists of multiple parts. The proposal is refering to which one? Flora of North America says „violet-blue or rarely white or pink“. So we would need at least an additional qualifier. Characters (or traits) are not stable. They are depending from a certain taconomic viewpoint. I agree with Daniel. We need a more general discussion. Watson and Dallwitz are using 581 characters in their The families of flowering plants to describe flowering plants. GrassBase uses 1090 characters for species belonging to Poaceae (Q43238). We are far away from defining our own plant ontology. --Succu (talk) 08:37, 30 July 2015 (UTC)

Perhaps we need properties for petal colour, sepal colour, etc? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:59, 30 July 2015 (UTC)
@Pigsonthewing: I think not. Constructions like
< Flower of whatever > has part search < 107412) >
color search < blue >
number of elements search < 4 >
would be pretty nice in this case ... author  TomT0m / talk page 09:27, 30 July 2015 (UTC)
Symbol oppose vote.svg Oppose I guess there would be a discussion if the discussion for standard flower color representation, but it seems it's not that well defined, so I think here there would be absolutely no benefit to try to be specific for no precise reason. Even if the discussion of a specific color standard was at sake, this solution would work anyway with the item datatype for color, assuming there is an identifier property, an item for each color in the standard, with
< color as defined by standard S > subclass of (P279) miga < color >
< blue whatever > instance of (P31) miga < color as defined by standard S >
, and
< blue whatever > S standard identifier search < blueZZZZZ >
, used as in my comment above:
< Flower of whatever > has part search < petal (Q107412) (View with Reasonator) >
color search < blue whatever >
number of elements search < 4 >
 – The preceding unsigned comment was added by TomT0m (talk • contribs).
Pictogram voting comment.svg Comment I think before discussing this property, we should write up a RFC and let outsiders of this knowledge domain weigh in. I have been thinking about this a lot lately and see no clear path to follow. For example TomT0m's suggestion is nice, but it is hard to imagine that we can retrain a whole community to use constructs like that. There is also the problem of adding too much information in the qualifier-rows. Readability and editablity are concerns for Wikidata and we have to be pragmatic about that. - In my opinion the most manageable solution would be to create items for all subparts and dump all the metrics in there. There are some examples of that already on Wikipedia: sugar maple (Q214733) has part Canadian Gold Maple Leaf (Q119457). But that also means creating many items ("bee wing", "shark tooth", ..). --Tobias1984 (talk) 10:31, 30 July 2015 (UTC)
  • why not ? It's not that hard. And similar structure for the whole project greatly limit the amount of examples needed. I don't agree that this structure is hard to grab. author  TomT0m / talk page 15:04, 30 July 2015 (UTC)
  • Pictogram voting comment.svg Comment List of mushrooms seems to work mainly with specific properties, open to non-specialists and non-template editors. Maybe a similar sub-field could be identified to build a similar set of properties. --- Jura 11:11, 30 July 2015 (UTC)
    and a subproject specific to a kind of mushrooms would have its own set of incompatible but similar properties ? Please don't take that path /o\ author  TomT0m / talk page 09:15, 31 July 2015 (UTC)
    • I think it's a good path to follow collaboratively built samples that can be compatible. This way we are sure we don't just follow idle chat. --- Jura 09:25, 31 July 2015 (UTC)
    • @Jura1: So ... why chatting at all ? It's for that reason we have a property proposal process (plus I have a few stalled properties myself, easy to say I'm idle after that) but enough personal iddle chatting. On the list : in which way edibility is specific to mushrooms, to take an example in the list ? having specialized properties for no good reason could create the need for a merge later ... author  TomT0m / talk page 13:03, 31 July 2015 (UTC)
@TomT0m: Specialized properties don't necessarily need to be merged. They can also be subclassed to more generic properties. - And I still think the structure is hard to grab. If we have many properties that each take one or a few simple statements it is easier to work with than totally generic properties that can hold 1000s of statements each with their own qualifier structure. How would a user read such a list without thinking he is reading a programming language? - But I could also be totally wrong about this assertion. In any case I still think an RfC would be a better idea than dispersing the discussion over so many property proposals. --Tobias1984 (talk) 20:39, 31 July 2015 (UTC)
@Tobias1984: Yout RFC argument is also valid for discussion on similar properties spreads on a lot of property discussions. And the outcome of discussions in many specialised properties is likely to become inconsistent decisions. I also don't see an obvious way to subproperty "color of parts" like properties as the kind of part would not be specified by an item. A Rfc why not but ... This would not prevent property proposals anyway and I would not know what to ask. On the contrary the structure I propose can be used in a variety of usecase, and a few examples with the color ofthe flower of some plant and the color of the superhero costume pant should suggest it applies to anything ... Plus the fact that there will be property proposals for people who does not knows that is an opportunity to tell them that, and those who knows won't ever have to go through this and will just enter their statements smoothly. There is so many advantages for so less understanding problems ... author  TomT0m / talk page 21:06, 31 July 2015 (UTC)
@TomT0m: For example this RfC also proposed a really simple and generic way of handling images on Wikidata: Wikidata:Requests_for_comment/Image_properties:_many_properties_or_many_qualifiers. But even that rather simple scheme did not catch on and we still have all the specialized image properties as far as I know. So the topic might require an RfC that we need to make certain changes to the user interface that makes it easier for people to use generic properties. I might have time to draft something next week and I will ping you for your input. --Tobias1984 (talk) 21:28, 31 July 2015 (UTC)

Biochemistry and molecular biology / Biochemie und Molekularbiologie / Biochimie et biologie moléculaire[edit]

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

Chemistry / Chemie / Chimie / Химия[edit]

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

Decomposition point[edit]

   In progress
Description decomposition point of a substance
Data type Number
Template parameter pl:Szablon:Związek chemiczny infobox, ru:Шаблон:Вещество
Domain chemical substance (Q79529)
Example

copper(II) acetylide (Q9138794) → 100 °C (with remark explosively) [from: CRC Handbook of Chemistry and Physics (Q904273), 90th]

gold(III) chloride (Q174129) → >160 °C [from: CRC Handbook of Chemistry and Physics (Q904273), 90th]

possible remarks to indicate pressure and like explosively, violently
Source scientific literature (eg. CRC Handbook of Chemistry and Physics (Q904273))

Saehrimnir
Guerillero
Leyo
Snipre
Jasper Deng
Matt
CMBJ
Klortho
Dcirovic
Walkerma
Emw
the chemistds
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pictogram voting comment.svg Notified participants of Wikiproject Chemistry

Motivation

Annotation from Wikidata:WikiProject Chemistry/Properties made by user:Michał Sobkowski: "Decomposition is usually indicated in m.p. or b.p. records (as is proposed here, see above). However, it is not necessarily coincided with these values. Decomposition may take place without phase transition, e.g. in gas phase; an observed "boiling point" may be just decomposition into volatile product(s) without reaching the real b.p. of a substance; the phase of a decomposing substance may not be known. Thus, instead of adding unprecise remarks to the m.p./b.p.'s (which are reasonable only in printed material, to save place), an additional field assigned exclusively for this value would be advantageous." ∼Wostr (talk) 18:20, 12 June 2015 (UTC)

Discussion
  • Symbol support vote.svg Support But we have to be able to specify an interval. Snipre (talk) 19:35, 12 June 2015 (UTC)
  • Symbol support vote.svg Support Of course this will have to have constraints; preferably I would like to see the temperature in kelvins and this cannot be applied to elements (compounds only).--Jasper Deng (talk) 01:06, 13 June 2015 (UTC)

Uncertainty[edit]

   In progress
Description Statistical uncertainty
Data type Number
Example tbc
Source Freebase
Robot and gadget jobs Freebase import
Motivation

To be used as a qualifier. Needed to import https://www.freebase.com/chemistry/atomic_mass/uncertainty Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:05, 18 June 2015 (UTC)

Discussion
@Pigsonthewing: The Freebase link does not work for me at the moment, so I can't look at the exmaple. I think the proposal needs a more general discussion on how things like this should be handled. The measure is meaningless without knowing (1) how it was calculated and (2) what the calculated uncertainty is (3) if it is given as a fraction, percentage or in absolute values. For example en:Copernicium even has an asymmetric uncertainty: 357 (+112/−108)K given in the absolute measure and the mode of calculation should be mentioned in the source. I am not sure the number-datatype can handle this complexity. We need some kind of datatype that gives us a few fields for all these values. For example Uncertainty: (Field 1: +Uncertainty)[Number], (Field 2: -Uncertainty, Optional: only use when asymmetric)[Number], (Field 3: Relative, Absolute)[Item], (Field 4: Mode of Calculation)[Item]. --Tobias1984 (talk) 13:24, 18 June 2015 (UTC)
Link works for me (you need to select the "instances" tab for example values). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:26, 18 June 2015 (UTC)
Symbol oppose vote.svg Oppose Should be part of a global concept for uncertainty because uncertainty is not only one value. Snipre (talk) 12:58, 22 June 2015 (UTC)
+1 Symbol oppose vote.svg Oppose --Succu (talk) 21:51, 26 June 2015 (UTC)
Symbol support vote.svg Support Scientific data will stay a minority here. The general concept (± operator) is enough for the moment.--Kopiersperre (talk) 17:28, 27 June 2015 (UTC)
We will have tons of scientific data here in the future. But this should be done with datatype quantity. --Succu (talk)
Symbol oppose vote.svg Oppose in favor of the future built-in data types for this.--Jasper Deng (talk) 02:48, 3 July 2015 (UTC)

Periodic table block[edit]

   In progress
Description The section of the periodic table to which an element belongs
Represents periodic table block (Q193099)
Data type Item
Template parameter |block= in en:Template:Infobox element
Domain chemical elements
Allowed values Instances of periodic table block (Q193099)
Example oxygen (Q629)p-block (Q214483)
Source Freebase
Robot and gadget jobs Freebase import
Motivation

Needed to import https://www.freebase.com/chemistry/chemical_element/periodic_table_block Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:20, 18 June 2015 (UTC)

Discussion
BA candidate.svg Weak oppose I think we already discussed a similar property once, and I think the consensus was to use multiple values of subclass of (P279) for each element. An element can be part of a block and a period. Infoboxes can ask for all the subclass of (P279) values, and with arbitrary data access ask for which p279 leads to a block, and which p279 statement leads to a period. --Tobias1984 (talk) 13:29, 18 June 2015 (UTC)
@Tobias1984: Please can you link to that discussion, and/ or provide an example item which uses that model? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:06, 18 June 2015 (UTC)
@Pigsonthewing: see Help:Classification : blocks can be seen as classes of elements. For example we can write
< Hydrogen > instance of (P31) miga < s-block element >
, with
< s-block element > subclass of (P279) miga < chemical element >
. With the help of WD:Property proposal/Generic#subclass, we can even express that each s-block element atom is a member of exactly one of the subclasses. TomT0m (talk) 16:22, 18 June 2015 (UTC)
@TomT0m: Thank you. My request was for a link to the previous discussion of "a similar property" to the one proposed, and an example - if one exists - of where the model for periodic table blocks proposed by Tobias1984 is already used. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:22, 18 June 2015 (UTC)
@Pigsonthewing: The old discussion is at Wikidata:Property_proposal/Archive/20 --Tobias1984 (talk) 10:51, 14 July 2015 (UTC)
BA candidate.svg Weak oppose generic classification tools can handle this. As long as we have a good definition for the s-block element metaclass, which seems to me pretty clear (but I'm not an expert). TomT0m (talk) 16:27, 18 June 2015 (UTC)

State of matter at STP[edit]

   In progress
Description State of a substance at standard temperature and pressure
Represents phase (Q104837)
Data type Item
Domain chemical elements and compounds
Allowed values One of: solid (Q11438), liquid (Q11435), gas (Q11432)
Example sodium chloride (Q2314)solid (Q11438)
Source Freebase
Robot and gadget jobs Freebase import
Motivation

Needed to import https://www.freebase.com/chemistry/chemical_compound/phase_at_stp - not to be confused with phase of matter (P515). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:58, 18 June 2015 (UTC)

Discussion

electrons per shell[edit]

   In progress
Description Number of electrons per shell, of a chemical element. Qualified with the shell number.
Data type Number
Template parameter |electrons per shell= in en:Template:Infobox element
Domain instances of chemical element (Q11344)
Allowed values integers; max = 18
Example iron (Q677) → 2, 8, 14, 2 (shells 1-4 respectively)
Source Freebase
Robot and gadget jobs Freebase import
Motivation

Qualified with "electron shell number" (see below). Needed to import https://www.freebase.com/chemistry/chemical_element/electrons_per_shell Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:55, 18 June 2015 (UTC)

Discussion
Pictogram voting comment.svg Comment this should either be of datatype string, or if we stay with number, we need a qualifier to indicate which number corresponds to which shell. --Pasleim (talk) 13:07, 22 June 2015 (UTC)
A qualifier is already prosed; see next setion, below. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:20, 30 June 2015 (UTC)
Ah ok, the German translation confused me. --Pasleim (talk) 05:14, 4 July 2015 (UTC)

electron shell number[edit]

   In progress
Description Number of electron shell, of a chemical element.
Data type Number
Domain instances of chemical element (Q11344)
Allowed values integers; max = 7
Example iron (Q677) has shells 1-4
Source Freebase
Robot and gadget jobs Freebase import
Motivation

Qualifier of "electrons per shell" (see above). Needed to import https://www.freebase.com/chemistry/chemical_element/electrons_per_shell Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:55, 18 June 2015 (UTC)

Discussion

Which purpose has this value?--Kopiersperre (talk) 07:05, 19 June 2015 (UTC)

As I wrote: Qualifier of "electrons per shell" (see above). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:19, 30 June 2015 (UTC)
This should have datatype string or item, as the shell number is just a label of the shell. --Pasleim (talk) 05:12, 4 July 2015 (UTC)

electron configuration[edit]

   In progress
Description electron configuration
Data type String
Template parameter |electron configuration=, in en:Template:Infobox element
Domain Chemical elements
Example iron (Q677) → [Ar] 3d6 4s2
Source Freebase
Robot and gadget jobs Wikidata:Property proposal/Natural science#electrons per shell
Motivation

Needed to import https://www.freebase.com/chemistry/chemical_element/electron_configuration Could be qualified with the item for the corresponding element (argon (Q696) in the example given). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:07, 18 June 2015 (UTC)

Discussion

solvent[edit]

   In progress
Description Substance which will dissolve this item
Data type Item
Domain Solvents
Example Erythritol tetranitrate (Q417174)acetone (Q49546)
Source Freebase
Robot and gadget jobs Freebase import
Motivation

Needed to import https://www.freebase.com/chemistry/solubility_relationship/solvent Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:09, 18 June 2015 (UTC)

Discussion
  • Needs a qualifier (very soluble / freely soluble / soluble / sparingly soluble / slightly soluble / very slightly soluble)--Kopiersperre (talk) 07:05, 19 June 2015 (UTC)
@Kopiersperre: No, I think we have to go out of this non scientific way to classify solubility. I agree with the property solvent but not as main property but as qualfifier of the property solubility. Snipre (talk) 12:54, 22 June 2015 (UTC)
Label g·l−1
very soluble > 1000
freely soluble 100-1000
soluble 33-100
sparingly soluble 10-33
slightly soluble 1-10
very slightly soluble 0,1-1
not soluble < 0,1

Isn't this an option?--Kopiersperre (talk) 19:05, 22 June 2015 (UTC)

@Kopiersperre: This is not scientific because this is the result of an evaluation: you have to provide the reference of the table in order to be able to understand what soluble is. Solubility in g/l or mg/l is an absolute value and not a relative like the ones you proposed. Then this table doesn't allow to classify components having the same class of solubility: between 100 and 1000 g/l there is a huge gap. Better use absolute values and let later the data user filter or translate these data into relative index. Snipre (talk) 13:31, 23 June 2015 (UTC)
@Snipre: This convinces me.--Kopiersperre (talk) 13:58, 23 June 2015 (UTC)

Isomeric SMILES[edit]

   In progress
Description Dedicated SMILES for isomer
Data type String
Domain chemical compounds
Example 2-pentanol (Q210479) → CCC[C@H](C)O
Source Main databases about chemical xompounds

Saehrimnir
Guerillero
Leyo
Snipre
Jasper Deng
Matt
CMBJ
Klortho
Dcirovic
Walkerma
Emw
the chemistds
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pictogram voting comment.svg Notified participants of Wikiproject Chemistry

Motivation
There is alredy a property for the SMILES notation of chemical compounds, see SMILES (P233) but this property is not specific and mixes canonical and isomeric SMILES. This disturbs our constraints system which requires unique and single value for the use of p233. So the idea is to convert the current SMILES property into a canonical SMILES property and to create a new property for the isomeric SMILES notation. Snipre (talk) 14:11, 19 July 2015 (UTC)

Medicine / Medizin / Médecine[edit]

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

Mineralogy[edit]

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

Solid solution series with[edit]

   In progress
Description the mineral forms a continous or discontinous "solid solution series" with another mineral
Represents solid solution (Q787619)
Data type Item
Template parameter put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain Q templates
Allowed values valid minerals
Example chrysoberyl-mariinskite series; chrysoberyl forms a series with mariinskite and vice-e-versa; hedenbergite-petedunnite; hedenbergite forms a series with petedunnite and vice-e-versa
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source mindat.org (Q15221937) - [1]
Robot and gadget jobs no
Proposed by Chris.urs-o (talk)
Discussion

(Add your motivation for this property here.) Chris.urs-o (talk) 06:47, 4 January 2015 (UTC)

@Snipre: --Tobias1984 (talk) 08:13, 7 January 2015 (UTC)
Sorry too specific for me. I have only knowledge in chemistry and engineering stuff. Snipre (talk) 12:40, 7 January 2015 (UTC)
Symbol support vote.svg Support Looks useful. --Tobias1984 (talk) 08:13, 7 January 2015 (UTC)

Pseudo crystal habit[edit]

   In progress
Description the chemical compound may seem to have a higher symmetry
Data type Item
Template parameter put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
Domain Q templates
Allowed values pseudomonoclinic, pseudoorthorhombic, pseudotetragonal, pseudotrigonal, pseudohexagonal, pseudocubic
Example Leucite and CdCl2 have a orthorhombic crystal symmetry, but they show a pseudo cubic crystal habit
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source mineralienatlas.de, mindat.org
Robot and gadget jobs no
Proposed by Chris.urs-o (talk)
Discussion

(@Sbisolo:, @Tobias1984:, @John Mortimore:; it could be a subproperty of habitus; it is important to know that a mineral appears to have a higher symmetry although it is not perfect) Chris.urs-o (talk) 07:23, 4 January 2015 (UTC)

Pictogram voting comment.svg Comment I am wondering if it is also possible to query this. A mineral has a crystal structure that links to a symmetry. The habit of a mineral also has a symmetry. If the symmetries don't match, then the habit is called e.g. pseudocubic. But maybe this explicit approach would be good too. --Tobias1984 (talk) 08:16, 7 January 2015 (UTC)
  • Ok, let's try. The crystal system is a physical characteristic determined in the laboratory. The habit is a visual appearance of the species sample. I suppose that the pseudocrystal habit would be a subproperty of habit.
  • Halit (NaCl) has a cubic symmetry, with following cell parameters: a =5.6404(1) Å =b =c and α=90° =β =γ
  • Analcime (Na2(Al2Si4O12) · 2H2O) has a triclinic symmetry, but it always looks pseudocubic. Cell parameters: a =13.723 to 13.733 Å =b =c
  • Boracite (Mg3(B7O13)Cl) has a orthorhombic symmetry, but often a pseudocubic morphology. Cell parameters: a = 8.577(6) Å, b = 8.553(8) Å, c = 12.09(1) Å
  • Perovskite (CaTiO3) has a orthorhombic symmetry, but often a pseudocubic morphology. Cell parameters: a = 5.447(1) Å, b = 7.654(1) Å, c = 5.388(1) Å
  • Bernalite (Fe(OH)3 · nH2O (n = 0.0 to 0.25)) has a orthorhombic symmetry. Morphology: flattened pyramidal crystals, pseudo-octahedral to pseudo-cubic. Cell parameters: a = 7.544 Å, b = 7.56 Å, c = 7.558 Å
  • Pertlikite (K2(Fe2+,Mg)2Mg4Fe23+Al(SO4)12 · 18H2O) has a tetragonal symmetry, but often a pseudocubic morphology. Cell parameters: a = 19.2080 Å, c = 27.2158 Å
Regards --Chris.urs-o (talk) 05:57, 10 March 2015 (UTC)

Informatics[edit]

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

Kernel version[edit]

   In progress
Description put English description for property here, e.g. same as in the infobox documentation
Represents Linux kernel (Q14579)
Data type String
Domain Linux and BSD distributions
Allowed values Valid version numbers
Example Debian (Q7593): version (P348) => 7 with qualifier "kernel version" => 3.2.41
Source Distribution mailing lists
Proposed by --Tobias1984 (talk) 21:53, 1 December 2014 (UTC)
Discussion

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Pictogram voting comment.svg Notified participants of Wikiproject Informatics --Tobias1984 (talk) 21:53, 1 December 2014 (UTC)

  • This seems like an overly specific property. Wouldn't it be better to create a more general property that lists the packages supplied by a distribution, with the version number as a qualifier? (This would also imply making an item for each major version of a distribution. Also, some distributions ship multiple kernel versions over their lifetime, which I think would be difficult to express if kernel version already is a qualifier.) —Ruud 16:51, 19 December 2014 (UTC)
  • Symbol oppose vote.svg Oppose @Tobias1984:I would rather see the use of the has part (P527) property with a qualifier "version", or directly a "linux 3.2.41" item, subclass of "linux" or something, with a "version" statement.
    • Pictogram voting comment.svg Comment You can’t put qualifiers on qualifiers, so in the above example, this would require a separate item for Debian 7. —DSGalaktos (talk) 12:32, 28 March 2015 (UTC)

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Pictogram voting comment.svg Notified participants of Wikiproject Informatics : I think it would be better to use items for software versions, Python2.6 is an edition of python, for example, and that would make us aligned with Wikidata:WikiProject Books. TomT0m (talk) 12:11, 6 June 2015 (UTC)

Items for software versions would mean we create a new item for notepad++ 6.8.7.2 and InternetExplorer 11.0.9600.17801? --Pasleim (talk) 22:44, 6 June 2015 (UTC)
@Pasleim: I guess that when there is a lot of releases it's way overkill to go up to minor patch versions. But I guess not all of them are published anyway, even in that case there would not be 17801 items for 11.0.9600 :) If we would not maintain a history of versions with version search, nobody would create all the items anyway, except if this is done automatically. So I don't think we really have to worry about that. What we would gain is that when several distros includes Linux 4.2.1, we just have to say
< RHEL4.6 > has part search < Linux 4.2.1 >
 and not
< RHEL4.6 > has part search < Linux >
version search < 4.2.1 >
and
< Ubuntu Zeta Zebra > has part search < Linux >
version search < 4.2.1 >
, that we will be able to put statements about Linux 4.2.1, for example added feature, and regularity of the model, so less special cases in query or in infobox templates. TomT0m (talk) 11:33, 7 June 2015 (UTC)
@TomT0m, Pasleim: Notability for software releases is a really difficult topic. If we make items for versions will also mean that we run 2 approaches parallel. In any case we can only gather data about programs that have some kind of written release information. But we also need to ignore the bugfix releases if we want to keep the whole system manageable. Wikidata is also really bad for inputting long lists of data into a single property, which makes version history editing difficult. --Tobias1984 (talk) 15:44, 7 June 2015 (UTC)
@Tobias1984: Why would that be difficult ? We can make it very simple if we want. Like I said, it's not because we create items that the history on software that we will store be longer than if we do not. It's a separate question. It's because (hypothetically) we chose the create items solution that this will modify the number of statements per page. TomT0m (talk) 16:42, 7 June 2015 (UTC)

Lithography[edit]

   In progress
Description lithography in nanometers
Data type Item
Domain central processing unit (Q5300) / electronic circuit (Q1815901)
Allowed values 22, 32, 45, 65, 90, 130, 180, 250.
Example Xeon 3040 (Q15229424) : 65 nm
Source Intel website, for Intel processors
Robot and gadget jobs Robots can gather info on the Intel website and fill the property with it.
Proposed by MisterSanderson (talk)
Discussion

I want to add information to the CPU items, but there aren't enough properties to that. MisterSanderson (talk) 00:48, 25 November 2013 (UTC)

changed datatype. Filceolaire (talk) 22:44, 25 November 2013 (UTC)
Why "number with dimension" instead of simply "number"?--MisterSanderson (talk) 00:48, 26 November 2013 (UTC)
Because this is a measurement of length. Remember that while current processors are measured in nanometers past processors were measured in micrometers and future processors will be measured in picometers. Filceolaire (talk) 07:46, 30 November 2013 (UTC)
Given the diameter of a silicon atom (over 0.2 nm), I think it will be fairly unlikely that we will ever need the measure lithographic processes in picometers ;) —Ruud 17:29, 19 December 2014 (UTC)
Symbol support vote.svg Support the dimension would be the physical unit "meter". I think everybody uses simply number because the other thing doesn't seem to work with the template. --Tobias1984 (talk) 16:04, 27 November 2013 (UTC)
What about AMD?--Kopiersperre (talk) 13:38, 11 November 2014 (UTC)
@Kopiersperre: I am not an expert where else this measurement is used, but I think the domain "semiconductors" would probably sum it up? --Tobias1984 (talk) 22:02, 21 November 2014 (UTC)
@Tobias1984: I must point out, that a 22 nm processor does not have any element, which is 22 nm long. (See Keine 14-Nanometer-Struktur in Broadwell) --Kopiersperre (talk) 14:10, 23 November 2014 (UTC)
@Kopiersperre: That certainly makes things more complicated. In that case we should rely on independent measurements and not the marketing words. Maybe even require a qualifier that states how the measurement was made (e.g. with an ion probe). --Tobias1984 (talk) 15:02, 23 November 2014 (UTC)
I think what Kopiersperre means is that the term "22 nm" is the name of a particular lithographic process (sometimes it's qualified by the name of the semiconductor foundry), and should not be directly interpreted as a physical quantity (nor should we try to make it into one by relying on "independent measurements"). We can be pragmatic and make it into a number with dimension as the names of lithographic processes have always followed the convention of being a number followed by "micrometer" or "nanometer". —Ruud 17:00, 19 December 2014 (UTC)
Actually, Wikipedia already has articles on the various processes and Wikidata thus has items on them: 22 nanometer (Q1059061), 1.5 µm process (Q1135912), Category:International Technology Roadmap for Semiconductors lithography nodes (Q7003854), ... We should probably link them to those instead. —Ruud 17:22, 19 December 2014 (UTC)
@Ruud Koot: - It might be a good idea to make this an item-datatype instead. That way we can avoid the situation described by User:Kopiersperre. --Tobias1984 (talk) 20:35, 19 December 2014 (UTC)

Listed in PackageIndex[edit]

   In progress
Description Many programs available for Linux have public listings of their packages. Connecting to these indexes would allow to check up on version numbers using bots.
Data type URL
Template parameter ?
Domain software
Allowed values Valid package indexes or repositories
Example Inkscape (Q8041) → "https://apps.fedoraproject.org/packages/inkscape" (+Qualifier: Fedora), "https://launchpad.net/ubuntu/+source/inkscape" (+Qualifier Ubuntu)
Motivation

As usual this should improve Wikidatas interlinking between relevant software pages. Bots can use these pages to check if a newer version of a program exists. --Tobias1984 (talk) 21:35, 12 June 2015 (UTC)

Discussion
 Pictogram voting comment.svg Comment @Tobias1984: I think it's a good idea, I would however prefer a different model, for example a more generic property. Either part of (P361) qualified with a package index reference qualifier, or something like a packaged in/by property instead of has part. What do you think ? TomT0m (talk) 10:48, 9 July 2015 (UTC)

(

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Pictogram voting comment.svg Notified participants of Wikiproject Informatics)

  • @TomT0m: - I think using part of (P361) in this case would dilute the meaning of the property too much. Maybe something like "is listed in" would be better for this case. --Tobias1984 (talk) 21:01, 9 July 2015 (UTC)

Geology[edit]

Please visit Wikidata:WikiProject Geology for more information.

Geography[edit]

Maths[edit]

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

statement describes[edit]

   In progress
Description a formalization of the statement contains a bound variable in this class
Data type Item
Domain statement (Q2684591), conjecture (Q319141)
Allowed values mostly mathematical objects
Example Pythagorean theorem (Q11518) => right triangle (Q158688), abc conjecture (Q306393) => natural number (Q21199)
Proposed by Danneks (talk)
Discussion

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

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

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

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

image of a function[edit]

   In progress
Description the set of values that a function actually has
Represents image of a function (Q1806121)
Data type Item
Domain instances of map (Q370502), function (Q11348), morphism (Q1948412), binary relation (Q130901)
Allowed values instances of set (Q36161), class (Q217594)
Example square function (Q3075175)non-negative real number (Q18729403)
Proposed by Petr Matas
Discussion

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

Opensofias
Tobias1984
Micru
Arthur Rubin
Cuvwb
Danneks
TomT0m
Pictogram voting comment.svg Notified participants of Wikiproject Mathematics

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

admissible in[edit]

   In progress
Description this logic inference rule is admissible in that logical system
Represents Admissible rule (Q1560157)
Data type Item
Domain Rule of inference (Q1068763) (View with Reasonator)
Allowed values type(s) d'éléments liés (modèle Q ou texte), liste ou intervalle de valeurs permises, format de chaîne de caractères...
Example
< Modus ponens (Q655742) (View with Reasonator) > admissible in search < classical logic (Q236975) (View with Reasonator) >
Format and edit filter validation (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
Source external reference, Wikipedia list article, etc.
Robot and gadget jobs Devrait-il y avoir ou existe-t-il des bots ou des gadgets qui effectueront des tâches avec cette propriété? Par exemple: vérifier les autres propriétés afin d'être cohérent, collecter des données, automatiser un lien externe, etc.
Discussion

Motivation:

Proposed by: TomT0m (talk)


Opensofias
Tobias1984
Micru
Arthur Rubin
Cuvwb
Danneks
TomT0m
Pictogram voting comment.svg Notified participants of Wikiproject Mathematics

The items exists, the relation also exists, there is an article about it and they gives useful informations about the logics. TomT0m (talk) 18:35, 1 April 2015 (UTC)

All sciences[edit]

study of[edit]

   In progress
Description the subject is a science or domain studing the object
Data type Item
Template parameter indiquez ici les attributs d'infobox de Wikipédia correspondants, s'il en existe, par exemple : « population » dans fr:Modèle:Infobox Subdivision administrative
Domain branch of science (Q2465832), broader
Allowed values pretty much anything
Example exemple d'élément qui utiliserait cette propriété, avec une valeur proposée; par exempl : algorithmics (Q13636890) => algorithm (Q8366) ; physics (Q413) => matter (Q35758) physics (Q413) => motion (Q79782) ;
< mathematics (Q395) (View with Reasonator) > study of search < quantity (Q309314) (View with Reasonator) >
< mathematics (Q395) (View with Reasonator) > study of search < number (Q11563) (View with Reasonator) >
< mathematics (Q395) (View with Reasonator) > study of search < calculus (Q149972) (View with Reasonator) >
 ;
< biology (Q420) (View with Reasonator) > study of search < life (Q3) (View with Reasonator) >
< biology (Q420) (View with Reasonator) > study of search < organism (Q7239) (View with Reasonator) >
...
Format and edit filter validation (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
Robot and gadget jobs Devrait-il y avoir ou existe-t-il des bots ou des gadgets qui effectueront des tâches avec cette propriété? Par exemple: vérifier les autres propriétés afin d'être cohérent, collecter des données, automatiser un lien externe, etc.
Proposed by TomT0m (talk)
Discussion

Help scoping a lot of items and linking object to their sciences. A lot of structuring power, a help on automatic item disambiguation, a help on scoping Wikipedia article who sometimes mixes the two subjects. Can potentially help restoring lost interwikis : if some Wikipedia has an article on the science and the other one on the object, the interwiki language link might have been lost, as this is a common pattern a custom template can propose a link to the Wikidata item and redirect to the corresponding article in the other language. TomT0m (talk) 10:28, 20 September 2014 (UTC)

Symbol support vote.svg Support, it can be very useful as a replacement of categorization. Danneks (talk) 13:48, 1 October 2014 (UTC)
Symbol oppose vote.svg Oppose, is just part of (P361) for science--Kopiersperre (talk) 14:26, 14 October 2014 (UTC)
This is not "part of", it would be more like has part (P527), but I do not think it is exactly that either. I support the idea, but as a general rule, I think it should be used only with more generic values. If "number: subclass of: mathematical object", and "mathematics: study of: mathematical object", then it does not seem necessary to add "mathematics: study of: number" (else where do we stop ?) --Zolo (talk) 16:03, 14 October 2014 (UTC)
@Zolo: I just took the statements from the Wikipedia articles. Study of numbers is a pretty common definition of maths, so there is no harm, and numbers (or sets in maths foundations) can pretty much the starting point to encode any other math objects. So it's just a matter of choice, there is no problem with beeing somewhat redundant if their is no contradiction, it's not a big deal. And it's just a detail, I think it's important to link a science to the type of concept it studies (way more) :) TomT0m (talk) 11:43, 21 February 2015 (UTC)
Symbol support vote.svg Support, but wouldn't calculus be the study rather than the subject, with e.g. integral(s) and derivative(s) as the subject? —SamB (talk) 14:21, 15 April 2015 (UTC)

Pictogram voting question.svg Question Is

< microscopy (Q1074953) (View with Reasonator) > study of search < microorganism (Q39833) (View with Reasonator) >

a good or a bad one? study of gives no sense to me. I think it's vice versa:

< calculus (Q149972) (View with Reasonator) > is studied by search < mathematics (Q395) (View with Reasonator) >
(or )
< organism (Q7239) (View with Reasonator) > are studied by search < biology (Q420) (View with Reasonator) >
(nothing to put here)

--Succu (talk) 20:43, 26 June 2015 (UTC)

@Succu: I can't tell if microscopy (Q1074953) (View with Reasonator) is the study of the microscope themselves or what's looked at, I'm sorry. We got a problem of definition with maths. If maths are a set of knowledge about abstract object, like logics or theorems, then yes I's say we can use part of. If maths are the process of finding or studying knowledges about those objects, then this property fits. That's the first sentence of the enwiki article : Mathematics (from Greek μάθημα máthēma, “knowledge, study, learning”) is the study of topics such as quantity (numbers),[2] structure,[3] space,[2] and change.[4][5][6]. I'm not sure about the vice versa thing, what's important is to make a link. But I think a science item should link to the objects it is about, it's a defining property of a science. On the other hand it's not a defining property of the stars to be studied by astronomy, there was stars before astronomy and there probably be stars after ... TomT0m (talk) 17:31, 4 July 2015 (UTC)
I think it's more convincing to say
< no label (Q1519541) (View with Reasonator) > is/are studied by search < astronomy (Q333) (View with Reasonator) >
< star (Q523) (View with Reasonator) > is/are studied by search < astronomy (Q333) (View with Reasonator) >
and so on, including the generalisation
< astronomical object (Q6999) (View with Reasonator) > is/are studied by search < astronomy (Q333) (View with Reasonator) >
If you use study of you end up with a very long (uncomplete) list. --Succu (talk) 18:31, 4 July 2015 (UTC)
@Succu: It's more effective to keep the wording as is and stay with a rule : if celestial objects is studied by astronomy, then any of their subclasses is studied by astronomy. That way we keep only the most general statements an your problem vanish. This is already implied by the subclass relationship anyway, as planets are of course astronomical objects. I don't think that the is studied by inverse property is better in that matter, because you would just end up with an endless and incomplete list of redundant statements localized anywhere on the items in the subclass tree ... TomT0m (talk) 09:42, 5 July 2015 (UTC)
With respect to grammar "pneumonia is studied by pulmonology" makes more sense. Doc James (talk · contribs · email) (if I write on your page reply on mine) 07:41, 12 July 2015 (UTC)
@Doc James: English grammar maybe, but Wikidata is a multilingual project and must rely on definitions … It's not a good idea to think in terms of natural languages, as there is probably languages for which languages in which that woks just fine, in french astronomy studies stars. In the end there is probably a better label in english if that's the only problem, like «scope» maybe ? TomT0m (talk) 08:58, 12 July 2015 (UTC)

solves[edit]

   In progress
Description the subject is an algorithm or a method to solve a type of problem
Represents problem solving (Q730920)
Data type Item
Domain algorithm (Q8366) (View with Reasonator), maybe other heuristic or non mathematical problem solving methods
Allowed values computational problem (Q3435924) (View with Reasonator), others ?
Example DPLL algorithm (Q2030088)Boolean satisfiability problem (Q875276), , ...
Motivation

A defining property of algorithms. TomT0m (talk) 15:41, 1 July 2015 (UTC)

Discussion

Tobias1984
Emw
Zuphilip
Danrok
Bene*
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Pictogram voting comment.svg Notified participants of Wikiproject Informatics (fixed). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:41, 10 July 2015 (UTC)

Colour Index International Constitution Number[edit]

   In progress
Description Colour Index International ID for manufactured colour products
Represents Colour Index International (Q868387)
Data type Number
Domain chemicals
Allowed values Numbers (CI 15510 not allowed, 15510 allowed)
Example 73000 → indigo dye (Q422662)
Source Colour Index International
Motivation

(Add your motivation for this property here.) Teolemon (talk) 18:21, 12 July 2015 (UTC)

Discussion
Symbol support vote.svg Support Quite useful to look for chemical compounds responsible of colors. Snipre (talk) 22:17, 12 July 2015 (UTC)
There is a C.I. Generic Name and the consecutive C.I. Constitution Number. For example indigo dye (Q422662) is C.I. 73000 but also C.I. Pigment Blue 66. Probably only the Constitution Number is meant here.--Kopiersperre (talk) 06:02, 13 July 2015 (UTC)
Symbol support vote.svg Support. author  TomT0m / talk page 18:07, 30 July 2015 (UTC)

Colour Index International Generic Name[edit]

   In progress
Description Colour Index International Generic Name for manufactured colour products
Represents Colour Index International (Q868387)
Data type String
Domain chemicals
Allowed values Text : C.I. Pigment Blue 66
Example C.I. Pigment Blue 66 → indigo dye (Q422662)
Source Colour Index International

HMDB ID[edit]

   In progress
Description ID in Human Metabolome Database
Represents Human Metabolome Database (Q5937262)
Data type String
Domain Metabolites
Allowed values HMDB##### (or #####?)
Example 2-Pentanone (Q209460) → HMDB34235 or 34235 [2]
Formatter URL http://www.hmdb.ca/metabolites/(HMDB)$1
Robot and gadget jobs Probably
Motivation

Database with 37170+ compounds. GZWDer (talk) 10:56, 16 July 2015 (UTC)

Discussion