Shortcut: WD:PP/SCI

Wikidata:Property proposal/Natural science

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

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.
  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.

Add a request

This page is archived, currently at Archive 44.

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


Property proposal: Generic Authority control Person Organization Event
Place Space Economics Transportation Natural science
Property metadata Creative work References Term Unsorted Sister projects

Physics and astronomy[edit]

Observed separation (en)[edit]

   In progress
Description en:Observed separation
Data type Number
Template parameter en:Template:Starbox relpos
Domain term
Example MISSING
Proposed by GZWDer (talk) 11:04, 8 July 2013 (UTC)
Discussion
@Paperoastro: Shouldn't this have units (degrees?) Filceolaire (talk) 21:49, 24 February 2014 (UTC)
Yes! I missed it! Thanks! I'd like to correct it, but I don't know what value put in "datatype" element of property documentation! I correct it. --Paperoastro (talk) 21:56, 24 February 2014 (UTC)
Symbol support vote.svg Support Filceolaire (talk) 06:44, 26 February 2014 (UTC)

Time2wait.svg On hold TBD when the right datatype is available.--Micru (talk) 13:00, 1 May 2014 (UTC)

@GZWDer, Paperoastro, Filceolaire, Micru: Quantity datatype is available, with degree (Q28390) (or minute of arc (Q209426) second of arc (Q829073 ) etc) as unit here. Can one of you confirm and update the proposal? ArthurPSmith (talk) 15:05, 2 December 2015 (UTC)

  • Pictogram voting comment.svg Comment The format of the data for the separation of a double star would usually be in seconds of arc specified for a particular date of observation or a future epoch as computed from orbital elements. See WDS SUMMARY CATALOG KEY used in the w:Washington Double Star Catalog for example. For multiple star systems such as w:Epsilon Lyrae the value will change slowly over a millennium. For close binaries this data might prove difficult to keep up to date as it will change over time. For example, w:Sirius#Sirius_B has changed significantly since 1994. See the diagram at How to see Sirius B. There is also the problem of a lack of reliable sources for some star systems. --Mu301 (talk) 19:21, 5 February 2016 (UTC)
Note: I just noticed that the IAU Style Manual states that "it is becoming common in astronomy to use the milliarcsecond as the unit." However, I would recommend arcsecond as a more useful unit. --Mu301 (talk) 21:58, 5 February 2016 (UTC)

Right Ascension / Declination / Distance[edit]

   In progress
Description Angle measured eastward along the celestial equator from the vernal equinox, at epoch J2000
Represents Right ascension (Q13442)
Data type Number
Template parameter "ra" in en:template:Starbox observe
Domain Astronomical objects
Example Crab Pulsar (Q1044623) → 276.366786666 degrees
   In progress
Description Angle measured north or south of the celestial equator, at epoch J2000
Represents Declination (Q76287)
Data type Number
Template parameter "dec" in en:template:Starbox observe
Domain Astronomical objects
Example Crab Pulsar (Q1044623) → 22.8683333 degrees
   In progress
Description Distance from Earth
Represents distance (Q126017)
Data type Number
Template parameter "dist_ly" or "dist_pc" in en:template:Starbox astrometry
Domain Astronomical objects
Example Crab Pulsar (Q1044623) → 2200 parsecs (7175 light-years)
Motivation

Defines the location in the sky and estimated distance to astronomical objects. Swpb (talk) 16:19, 14 January 2016 (UTC)

Discussion
Symbol support vote.svg Support right ascension and declination - those are definite standard astrophysical properties we should have, useful for every astronomical object (at least outside the solar system). Distance from Earth I'm not entirely sold on - should it be a more generic distance property with Earth as a qualifier? ArthurPSmith (talk) 21:56, 28 January 2016 (UTC)
A generic distance property (with mandatory qualifier relative to (P2210)) would allow for lots of arbitrary statements of distance from insignificant points of origin. Swpb (talk) 17:09, 29 January 2016 (UTC)
Pictogram voting comment.svg Comment (s) from Mu301 (talk) 20:14, 5 February 2016 (UTC)
  1. The examples above give RA and DEC in decimal degrees, but HH MM SS.nnn and DD AM AS.nnn are more the norm and that is the current format for the {{Starbox observe}} template. The formatting should conform to what reliable sources use. While I support the RA and DEC in general, I strongly oppose decimal degrees as the units. It impairs readability of the numbers and is not what a professional astronomer would use in most contexts.[1]
  2. For many objects ly or pc works fine, but it breaks down for the most distant objects where it is difficult to convert from redshift to distance without a large error in magnitude. Also see the footnote to the table at [2] which correctly points out that for the most distant objects in the universe this value "has no direct physical significance". This causes problems for astronomical objects like BDF-3299 which give misleading information in the {{Galaxy infobox}}. If this is not used for extra-galactic astronomical objects it would be fine.
  3. Will "distance from Earth" cause problems outside the context of starbox usage? A generic distance from Earth could reasonably need a wide variety of units. For a planet it might be AU while a near earth asteroid might need a multiple of Lunar distance or even Earth radii (for a close approach) as this is what a reliable source would use. I think this should be narrowed from all "astronomical objects" to just those outside the solar system (but not objects at cosmological distances.)
@Mu301: Are you suggesting a string datatype rather than a quantity datatype? Or to try to create a new datatype for angular degree units? I think that's really unnecessary -I don't think there's any essential difference between HH MM SS.nnn and a decimal formulation other than formatting. String datatype might be ok but I'm a little wary in this case. ArthurPSmith (talk) 21:13, 5 February 2016 (UTC)
@ArthurPSmith: I have a few concerns. One is that someone entering data manually will consult a source that gives HMS and there will be transcription errors when converting to decimal. Another is the display of significant figures. In the example[3] above the RA for the Crab Pulsar is given as 05 34 31.93830. Notice the significant trailing zero in the decimal portion of the seconds. The number of digits in a decimal representation should be equivalent to that precision. I'm not terribly concerned about how the data is machine readable formatted but it should render prettyprinted in an infobox. This is how sources represent the data in the majority of cases and it is what an astronomer (amateur or professional) would expect to see. Decimal RA would be like using JD 2457423.5 for today's date in my signature. It is a perfect choice for a computer program, but not very user friendly. But to answer your question I do think this warrants an angular data type as this is common usage in the field. It's not really a string of characters but a specific formatting of a numerical value. The w:IAU Style Manual specifically notes the common use of base 60 coordinates but only encourages decimal in examples like "formulae for numerical calculations." Readability is part of the reason why scientific publications use this style. --Mu301 (talk) JD 2457424.407639

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

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)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm
MPF
Abbe98
Rod Page
Joel Sachs

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)
    • Well, at some point one has to evaluate if all the talk of participants actually leads to some collaboration within the project or not. --- Jura 07:20, 1 August 2015 (UTC)
    • @Jura1: Let's be clear : should I consider this a personal attack ? You should be clear on what you consider a "contribution". There is many ways to contribute. Mine is not "maximising the editcount on the main namespace". author  TomT0m / talk page 10:25, 1 August 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 of the 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)
I'm not sure if Wikidata actually has the technology for this RFC nor if it's planned to develop it in the long term. --- Jura 07:20, 1 August 2015 (UTC)
@Jura1: As a lot of your post, I don't understand what you mean. author  TomT0m / talk page 10:25, 1 August 2015 (UTC)
  • Symbol support vote.svg Support I support the flower color proposal as a generic property. The values have to be added as needed. There are many standards, but most data sources use their own vocabulary, which needs to be matched. As to petal color, sepal color etc.: It may be desirable to add this, but it will not replace the unspecified flower color. For practical reasones, unspecific "flower color" is relatively highly used property in botany, without specifying the parts. Thus data available for flower color cannot be easily mapped to (often unavailable) data for the color of specific parts). --G.Hagedorn (talk) 11:47, 8 August 2015 (UTC)
  • Symbol support vote.svg Support as above. If different parts have different colours then use applies to part (P518) as a qualifier to identify the part associated with each colour. Joe Filceolaire (talk) 17:34, 8 August 2015 (UTC)
    @Filceolaire: Excuse me but such a model is prone to give me headeaches :) Flowers are parts of a plant. To tell the color of the flower, or the color of any other part, like leaves, we will use either part of (P361) qualified, or ... a property "color of the part", and when the part has several color, we will use applies to part (P518) ? OK, but we could also put statements like
    < plant > color search < yellow >
    applies to search < flower >
    ... I really don't like this. We should try to stay consistent in the ontology and limit the number of ways to express the same thing. This means that we should try to adopt the most straightforward rule with as few exceptions as possible, and "in the case of part colors use has part qualified with colors except for the case of flowers where we use "flower color" and when the color has parts we put several "flower color" statements qualified with "applies to" seems to me where we cross a complexity line. author  TomT0m / talk page 08:10, 10 August 2015 (UTC)
  • Symbol support vote.svg Support somehow the discussion got side-tracked. --- Jura 06:08, 15 August 2015 (UTC)
  • Symbol oppose vote.svg Oppose The property color (P462) already exists, and can be used together with applies to part (P518) without problem. I see no benefit to creating a new property for flowers. --Yair rand (talk) 06:46, 16 December 2015 (UTC)
Yes we have, but how would you describe the colorparts of Union Jack (Q3173323) with a generic property and applies to part (P518)? --Succu (talk) 23:17, 25 December 2015 (UTC)

The Swedish Species Information Center conservation status[edit]

   In progress
Description The conservation status for taxa in Sweden according to The Swedish Species Information Centre
Represents Swedish Species Information Centre (Q16497181)
Data type Item
Template parameter sverigestatus in sv:Mall:Taxobox
Domain taxa in Sweden (Q34)
Allowed values More or less the same as those for IUCN conservation status (P141)
Example Canis lupus lupus -> vulnerable
Source The Swedish Species Information Centre
Motivation

We are, as we speak, solving the Copyright-problems. A OTRS-ticker can probably be provided shortly! -- Innocent bystander (talk) 18:08, 10 November 2015 (UTC)

@Innocent bystander: Is that now resolved?
Discussion

Josve05a (talk)
FelixReimann (talk)
Infovarius (talk)
Daniel Mietchen (talk)
Soulkeeper (talk)
Brya (talk)
Klortho (talk)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm
MPF
Abbe98
Rod Page
Joel Sachs

Pictogram voting comment.svg Notified participants of Wikiproject Taxonomy

Australasian Pollen and Spore Atlas Code[edit]

   In progress
Description Code identifying a pollen or spore listed in the Australasian Pollen and Spore Atlas managed by the Australian National University
Data type String
Template parameter No existing property is known to exist, however a link to the atlas entry could be included somehow within en:template:taxobox
Domain pollen (Q79932) and spore (Q177332)
Allowed values string pattern: \d+(\-\d+)*(\(\d+(\-\d+)*\))?
Example Parietaria judaica (Q147991)62-14-3
Source Australasian Pollen and Spore Atlas
Formatter URL http://apsa.anu.edu.au/sample/$1
Robot and gadget jobs Codes could be scraped from the Australasian Pollen and Spore Atlas and mix-and-match used for import into Wikidata
Motivation

The Australasian Pollen and Spore Atlas website is designed to enable simple online access to the largest collection of pollen and spores information in the Australasian region. The APSA collection and office is currently located at the Australian National University in Canberra, Australia. This database contains numerous fields of information on pollens and spores for flora both endemic and common to Australia. Database fields include description of the pollen and spore shapes, their arrangement and patterns. Addition of this property would signifanctly enhance Wikidata's understanding of pollens and spores, particularly those endemic within Australia (Q408). Dhx1 (talk) 11:56, 22 November 2015 (UTC)

Discussion
Pictogram voting comment.svg Comment Not sure. A quick browse does not turn up real content? I would rather have something like FloraBase. - Brya (talk) 13:54, 22 November 2015 (UTC)
Pictogram voting comment.svg Comment The unique content is demonstrated better for Acanthus ebracteatus ACANTHACEAE, Pseudowintera traversii WINTERACEAE, Dicliptera brachiata ACANTHACEAE and Bouganvillaea spectabilis NYCTAGINACEAE. I am unaware of this level of detail being provided by other organisations, including FloraBase. A quick survey of samples in this database shows that most entries have useful detail (morphology, images, etc) - Dhx1 (talk) 16:04, 22 November 2015 (UTC)
Pictogram voting comment.svg Comment OK, that is better, although I seem to recall having seen more extensive sites covering pollen. - Brya (talk) 05:49, 23 November 2015 (UTC)

FAO 2007 genetic ressource ID[edit]

   In progress
Description (constructed) ID of a domestic animal species or breed in the FAO Animal Genetic ressources report 2007 breed list ftp://ftp.fao.org/DOCREP/fao/010/a1250e/annexes/Breeds-documented-GlobalDbank-AnimalGeneticResources/List_breeds.pdf http://www.fao.org/docrep/010/a1250e/a1250e00.htm
Represents Breeds Currently Recorded In The Global Databank For Animal Genetic Resources (Q21335650)
Data type String
Domain animal species or breed
Example
< horse (Q726) (View with Reasonator) > FAO id search < Horse >
 ;
< Anglo-Arabian (Q541046) (View with Reasonator) >  Wikidata property  < Horse:Anglo-Arab >
Format and edit filter validation (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
Source Breeds Currently Recorded In The Global Databank For Animal Genetic Resources (Q21335650) The State Of The World's Animal Genetic Resources For Food And Agriculture (Q21335767) imported in mix'n'match see this catalog
Robot and gadget jobs Matching with mix'n'match

The source file of the import is the pdf of the FAO report. The ids have been constructed by concatenating the first column (animal species name) with the column breed name, as is. There is a csv version of the file : http://pastebin.com/6BF5Aawg used to build the data imported in mix'n'match. The case should be ignored in the strings. The ":" character present in one of the breed name has been substituded with a "-". author  TomT0m / talk page

Motivation

This is necessary to do the mapping to exploit the datas of the report, which are to be used for FAO risk status (P2371) miga and to store the mix'n'match mapping. author  TomT0m / talk page 19:04, 10 December 2015 (UTC)

The Biology WikiProject does not exist. Please correct the name

Discussion

this zoological name is coordinate with[edit]

   In progress
Description links coordinate zoological names
Data type Item
Domain items on zoological names/taxa, at the rank of superfamily down to subgenus (inclusive)
Allowed values items on zoological names/taxa, at the rank of superfamily down to subgenus (inclusive)
Example Macroglossinae (Q134858) (subfamily) <> Macroglossini (Q251656) (tribe); Aedes (Q310911) (genus) <> Aedes (Q21440470) (subgenus)
Source literature
Robot and gadget jobs perhaps
Motivation

With the integration of Wikispecies, we are getting lots of new zoological names, especially for lots of subgenera. Under the International Code of Zoological Nomenclature there are sets of names that have "coordinate status": if there is a name MACROGLOSSINAE (subfamily Q134858), then there is automatically also a name MACROGLOSSINI (tribe Q251656), etc (for all possible ranks). Also, if there is a generic name Aedes (Q310911), then there is automatically also a subgeneric name Aedes (Q21440470) (and vice versa). These names with "coordinate status" have the same author, year, place of publication, type, etc. Therefore, it would be convenient to have these items linked, if only to facilitate checking the correctness of data. -- Brya (talk) 11:49, 13 December 2015 (UTC)

Josve05a (talk)
FelixReimann (talk)
Infovarius (talk)
Daniel Mietchen (talk)
Soulkeeper (talk)
Brya (talk)
Klortho (talk)
Delusion23 (talk)
Andy Mabbett (talk)
Dan Koehl (talk)
Achim Raschka (talk)
TomT0m
Tinm
MPF
Abbe98
Rod Page
Joel Sachs

Pictogram voting comment.svg Notified participants of Wikiproject Taxonomy

Discussion

Symbol support vote.svg Support I can support this, am a little wary of the use of the word automatic. By this I mean that under coordination a subgenus Name only exists under genus Name if another subgenus Name2 exists. That is its not automatic in all cases, only when the taxa has been formally subdivided. However once it has yes there must be a coordinated name also. As a suggestion I would recommend that when this is used reference to the paper doing the combination in question is cited. Cheers Faendalimas (talk) 02:10, 15 December 2015 (UTC)

@Faendalimas:: Art. 43.1: it is automatic ("simultaneously established"). - Brya (talk) 04:30, 15 December 2015 (UTC)
PS. Pragmatically, the applicability of this is not restricted to cases where a genus is to be split, but also to cases when a taxon is to be raised or lowered in rank. - Brya (talk) 04:51, 15 December 2015 (UTC)
@Brya: Your misinterpreting Art. 43.1. What it is saying is that the authorship of the sub name is the same as the original name for purposes of nomenclature. For example: Chelidae (Q583074) Gray 1825 and Chelinae (Q2962189) Gray 1825 have the same author and date despite the fact that the subfamily Chelinae was not established until 1893, by G. Baur. The authorship for these names is coordinated. Cheers, Faendalimas (talk) 14:01, 15 December 2015 (UTC)
@Faendalimas: Sounds like the classic distinction between nomenclature and taxonomy. Nomenclaturally, the publication of the name of a genus creates, "simultaneously", the name of a subgenus. Taxonomically, this name becomes relevant only once somebody actually recognizes a corresponding taxon. For the purposes of Wikidata, this is academic, as a name, by itself, usually will not be "notable" (and a good thing that is, otherwise we would be buried in them). - Brya (talk) 17:47, 15 December 2015 (UTC)
@Brya: yes see your pont, just remember the name does not exist until a taxonomic decision to create it occurs, so the full citation for Chelinae (Q2962189) is Chelinae (Q2962189) Gray 1825 (sensu Baur, 1893). Like I said it is Baur's 1893 taxonomic decision that created the name Chelinae not Gray's 1825 taxonomic decision to name the family Chelidae. Chelinae is the nominotypical subgenus, the others being the Hydromedusinae and the Chelodininae. Until the three were created, ie the taxonomic act, the nominotypical was not in existence and not needed. Its more accurate to say the name is created posthumously than simultaneously, is my point here. Cheers, Faendalimas (talk) 22:16, 15 December 2015 (UTC)
@Faendalimas: The Code says "simultaneously". See also the Example to Art. 36.1. - Brya (talk) 06:22, 16 December 2015 (UTC)

ARKive ID[edit]

   In progress
Description identifier for a taxon, in the ARKive database
Represents ARKive (Q433276)
Data type String
Template parameter en:Template:ARKive
Domain Taxons
Allowed values Valid Arkive URL slugs
Example Heteropoda davidbowie (Q1315848)david-bowie-spider/heteropoda-davidbowie
Source http://www.arkive.org/
Formatter URL http://www.arkive.org/$1/
Motivation

ARKive is a non-profit repository of high-quality, high-value media of endangered species. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:37, 11 January 2016 (UTC)

Discussion
Looks not as a stable ID for me. Maybe datatype should be URL. --Succu (talk) 19:22, 12 January 2016 (UTC)
How would that be any more stable? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:48, 15 January 2016 (UTC)
As these pictures are not freely usable, this will be of very limited value to Wikimedia projects? - Brya (talk) 04:49, 13 January 2016 (UTC)
There are no requirements for us to only include links to pages with free media; or that are specifically of use to Wikimeda projects. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:48, 15 January 2016 (UTC)
No, but it helps. And although there are some great pictures, there don't seem to be all that many of hem. - Brya (talk) 18:41, 15 January 2016 (UTC)
I think the strengths are in quality and rarity. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:50, 15 January 2016 (UTC)
Yes, but it is already possible to use a reference URL to access pages. If there are only a few pages that are of interest, is it worth making a separate property? - Brya (talk) 17:22, 17 January 2016 (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}}

produced by[edit]

   In progress
Description Links a biologic/biochemical entity with the entity it has been produced by
Data type Item
Domain biochemically active items, e.g. cells
Example melanosome (Q1065756)melanocyte (Q247101)
Source scientific papers, databases, ontologies, stating a certain connection. E.g. ExoCarta
Robot and gadget jobs ProteinBoxBot will use this for certain types of relations
Motivation

Although Wikidata has several generic properties, there is no property which allows to link a biological/biochemical product to its producer. For genes, this has been modeled quite well already (encodes (P688) and encoded by (P702)). But for all other things, no property seems to exists which could establish this link. Use cases are anything that a cell/organ/tissue/glad exkretes, be it exosomes, protein complexes (e.g. colesterol particles) milk, urine. This concept might seem broad, but as the biological details are often still lacking, therefore I think this would be a very valuable property for representing biological knowledge . Sebotic (talk) 09:49, 2 October 2015 (UTC)

Discussion

Symbol support vote.svg Support --Andrew Su (talk) 15:21, 2 October 2015 (UTC)

Symbol support vote.svg Support At the molecular biology level, it would be good to have some sort of relationship property for relationships further downstream of the gene and this property is a logical next step following the relationship properties linking genes/gene products. Many biosynthetic entities are products of multiple genes/gene products, and are not sufficiently represented by the currently existing/proposed properties. Eg- would be able to link Dopamine and the Dopamine Biosynthetic process. This property would offer more specificity than Natural Product of taxon (which is great for non-recombinant organisms). Gtsulab (talk) 15:44, 2 October 2015 (UTC)

Symbol support vote.svg Support lv_ra (talk) 16:05, 2 October 2015 (UTC)

Pictogram voting comment.svg Comment I'd like add an inverse "produces" property, which would have as a domain "processes" (biological or not). Another interesting related pair would be "process uses"/"used by process" to link a process to its input materials. Pictogram voting question.svg Question Do we agree on generalizing the domain ? author  TomT0m / talk page 16:21, 2 October 2015 (UTC)

I'm hesitant about creating this rather generic property for this purpose. There is another property already called "product" that seems suited to the general concept. I think my thought here is to create one that more specifically describes the nature of the biology you intend to capture. --I9606 (talk) 18:22, 2 October 2015 (UTC)
@I9606: Is there actually some practical reason not to use the generic property ? If the process item is a subclass of biological process, or a type of biological entity, then we know the products of this process captures the process nature of the process, is'nt it ? We could more simply expand the scope of the other property. (Although I think we should differentiate processes like Parthenogenesis (Q183236) and biological entities). By the way we should find a qualifier to link the process by which an entity produces something, like
< angiosperms (Q25314) (View with Reasonator) > produce search < angiosperms (Q25314) (View with Reasonator) >
by process search < Parthenogenesis (Q183236) (View with Reasonator) >
to complete the model. author  TomT0m / talk page 08:15, 3 October 2015 (UTC)
@TomT0m: As the inverse property for 'produced by', 'product (P1056)' can be used. I initiated a discussion on its talk page. But as the inverse property of product (P1056) is manufacturer (P176), manufacturer sounds a bit awkward to me in the context of biology (for cells, tissues, etc.). If it could be renamed to 'producer' or 'producer' could be added as a alias and the scope could be extended, property 'produced by' would not be required. Why I think we need a property like this: For many products, it is still unclear what's the detailed process/source they are produced by and for many circumstances, simply being able to state thing X produced by Y can be very useful. Furthermore, the property biological process (P682) is rather reserved for Gene Ontology defined biological processes (see target items in its property definition). Sebotic (talk) 07:24, 4 October 2015 (UTC)
@I9606, Sebotic: OK, I get the issue : in one case we refer to an "instance" entity, in the other to a class of entities, per Help:Classification. Hence I'm in favor to use generic property anyway as opposed to specific domain properties, but that make clear that in one case the producer is a real world entity, like "Iphone : <produced by entity : Apple>" vs. Iphone : <fruit> : <type of producer : Plant> for example. author  TomT0m / talk page 10:33, 4 October 2015 (UTC)
@TomT0m, Sebotic: I support the use of the generic produces/product properties as long as the definitions of the originating properties can be expanded. I also like the optional extension of the qualifier to describe how the production happens. I do think there will be room for more specific properties, but happy to get things started with the more generic version and either utilize the qualifier pattern or sub properties to specialize as needed. --I9606 (talk) 20:24, 5 October 2015 (UTC)
@I9606: I agree, becoming more specific as new knowledge becomes available will be a good and realistic way to go Sebotic (talk) 20:37, 5 October 2015 (UTC)
@I9606, Sebotic, TomT0m:Be wary of combining two concepts because there is an English word that covers both. The same may not be true in other languages.Ford is a manufacturer (P176) of cars. Apples are natural product of taxon (P1582) apple trees. Proteins are encoded by (P702) genes. All of these are similar relationships. I think there is a case for a specialist property for biological processes so I Symbol support vote.svg Support but I would like the property to have a name which makes it's specialist nature obvious. Unfortunately I can't think of one. The inverse property could be called 'Biological product of' but 'Biologically produced by' seems awkward, at least in English. Anyone else have any ideas? Joe Filceolaire (talk) 00:06, 4 November 2015 (UTC)
@Filceolaire: Which two concepts ? In one case, the product is the result of a transformation process, in the other the prouct is the result of the transformation process. It's the same concept and this has little to do with language peculiarities. author  TomT0m / talk page 12:34, 4 November 2015 (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
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
Pictogram voting comment.svg Notified participants of Wikiproject Molecular biology


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
sebotic
Pictogram voting comment.svg Notified participants of Wikiproject Medicine

UCSC Genome Browser assembly ID[edit]

   In progress
Description The identifier of a UCSC's release of a genome.
Data type String
Domain Genomes
Example Genome assembly GRCh38 (Q20966585) → "hg38"
Source UCSC genome releases
Motivation

As a property linked from a genome assembly item like https://www.wikidata.org/wiki/Q20966585 that facilitates clients in selecting the most appropriate build for their application. Andrawaag (talk) 00:08, 9 January 2016 (UTC)

Symbol support vote.svg Support Fully support as UCSC is a great resource for genome data.

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
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
Pictogram voting comment.svg Notified participants of Wikiproject Molecular biology

Discussion

Genomic Strand[edit]

   In progress
Description Orientation of gene on double stranded DNA molecule
Data type String
Domain gene (Q7187)
Allowed values "1" or "-1"
Example type III secretion system chaperone CT_043 (Q21173613) = 1
Source http://www.ncbi.nlm.nih.gov/gene
Motivation

Wikidata contains genomic start genomic start (P644) and genomic stop genomic end (P645) properties indicating the position of a gene on a DNA molecule (i.e. chromosome/plasmid). To give this statement more context it is import to denote which strand the gene is located on (i.e. 1(+, positive/sense strand) or -1(-, negative/antisense strand)). This context will allow gene annotations stored in Wikidata to be displayed accurately on a genome browser. Putmantime (talk) 22:38, 5 February 2016 (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
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
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}}

minimal lethal concentration[edit]

   In progress
Description Lowest concentration of a toxic substance in an environmental medium that kills individual organisms or test species under a defined set of conditions.
Represents minimal lethal concentration (Q21346369)
Data type Number
Template parameter LCLo
Domain chemicals
Allowed values numbers with units mg/m3 or ppm over a time period, in a specific animal through a defined route of administration (time period, route of administration and animal should be qualifiers)
Example dichlorine (Q1904422): 800 ppm, applies to taxon (P2352): Canidae (Q25324), route of administration (P636): inhalation (Q840343), duration (P2047): 30 minutes
Source External references
Motivation

Provide full set of toxicological data. Snipre (talk) 17:25, 21 January 2016 (UTC)

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

median lethal dose[edit]

   In progress
Description Statistically derived median dose of a chemical or physical agent (radiation) expected to kill 50% of organisms in a given population under a defined set of conditions.
Represents median lethal dose (Q711849)
Data type Number
Template parameter LD50
Domain chemicals
Allowed values numbers with units in amount per kilo for a specific animal using a specific administration route (administration route and animal should be qualifiers)
Example methanol (Q14982): 4710 mg/kg, applies to taxon (P2352): house mouse (Q83310), route of administration (P636): intravenous injection (Q1369403)
Source External references
Motivation

Provide full set of toxicological data. Snipre (talk) 17:26, 21 January 2016 (UTC)

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

median lethal concentration[edit]

   In progress
Description Statistically derived median concentration of a substance in an environmental medium expected to kill 50% of organisms in a given population under a defined set of conditions.
Data type Number
Template parameter LC50
Domain chemicals
Allowed values numbers with units in amount per volume for a specific animal over a certain time through a defined route of administration (time duration, animal, route of adminsitration should be qualifiers)
Example dichlorine (Q1904422): 137 ppm, applies to taxon (P2352): house mouse (Q83310), route of administration (P636): inhalation (Q840343), duration (P2047): 1 hour
Source External references
Motivation

Provide full set of toxicological data. Snipre (talk) 17:26, 21 January 2016 (UTC)

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

no-observed-adverse-effect level (NOAEL)[edit]

   In progress
Description Greatest concentration or amount of a substance, found by experiment or observation, which causes no detectable adverse alteration of morphology, functional capacity, growth, development, or life span of the target organism under defined conditions of exposure.
Represents No observable adverse effect level (Q1755926)
Data type Number
Domain chemicals
Allowed values numbers with units in amount per kilo per day for a specific animal using a specific administration route during a defined duration (administration route, animal and duration should be qualifiers)
Example chlorobenzene (Q407768): 27.25 mg/kg bw/day, applies to taxon (P2352): dog, route of administration (P636): oral exposure, duration (P2047): 13 weeks
Source External references like toxnet
Motivation

Provide full set of toxicological data.

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

lowest-observed-adverse-effect level (LOAEL)[edit]

   In progress
Description Lowest concentration or amount of a substance (dose), found by experiment or observation, which causes an adverse effect on morphology, functional capacity, growth, development, or life span of a target organism distinguishable from normal (control) organisms of the same species and strain under defined conditions of exposure.
Represents Lowest-observed-adverse-effect-level (Q2446987)
Data type Number
Domain chemicals
Allowed values numbers with units in amount per kilo per day for a specific animal using a specific administration route during a defined duration (administration route, animal and duration should be qualifiers)
Example chlorobenzene (Q407768): 54.5 mg/kg/day, applies to taxon (P2352): dog, route of administration (P636): oral exposure, duration (P2047): 13 weeks
Source External references like toxnet
Motivation

Provide full set of toxicological data.

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

Acceptable daily intake (ADI)[edit]

   In progress
Description Estimate by JECFA of the amount of a food additive, expressed on a body weight basis, that can be ingested daily over a lifetime without appreciable health risk.
Represents Acceptable daily intake (Q680142)
Data type Number
Domain food additive
Allowed values numbers with units in amount per kilo
Example Pentachlorobenzene (Q425468): 0.0167 mg/kg
Source External references like toxnet
Motivation

Provide full set of toxicological data.

Discussion

Symbol support vote.svg Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. Tolerable daily intake (TDI), limit value, and some other properties could be added as well. --Jtuom (talk) 14:52, 29 January 2016 (UTC)

AUSNUT Food Identifier[edit]

   In progress
Description Identifier of a food within the Australian Food, Supplement and Nutrient Database (AUSNUT) which is managed by Food Standards Australia New Zealand (FSANZ)
Represents food (Q2095)
Data type String
Template parameter No infobox parameter is known to exist at present, however a new parameter could be added to en:template:nutritional value (or another infobox)
Domain food (Q2095)
Allowed values string pattern: \d{2}[A-Z]\d{5}
Example kangaroo meat (Q1795395) → 08B10068
Source AUSNUT 2011-13 food nutrient database
Robot and gadget jobs Suggest that this database be included into mix-and-match similar to the existing NDB mix-and-match
Motivation

This property request is similar to existing property USDA NDB number (P1978) where an American database USDA National Nutrient Database (Q7866379) is linked to foods on Wikidata. The AUSNUT database is Australian and New Zealand specific and includes foods which are more common to Australian and New Zealand populations (for example, kangaroo meat (Q1795395)). AUSNUT 2011‒13 is a set of files that enables food, dietary supplement and nutrient intake estimates to be made from the 2011‒13 Australian Health Survey (AHS). It was first published in May 2014 and included data related to the National Nutrition and Physical Activity Survey (NNPAS) component of the AHS only. It was updated in September 2014 to include additional data related to the National Aboriginal and Torres Strait Islander Nutrition and Physical Activity Survey component of the AHS. This in an authoritative source of nutritional information for foods, and addition of this property to Wikidata will further enhance understanding of nutrition and foods via the ability to link AUSNUT to Wikidata items. Dhx1 (talk) 14:36, 22 November 2015 (UTC)

Discussion


NUTTAB Food Identifier[edit]

   In progress
Description Identifier of a food within the Nutrient Tables for use in Australia (NUTTAB) which is managed by Food Standards Australia New Zealand (FSANZ)
Represents food (Q2095)
Data type String
Template parameter No infobox parameter is known to exist at present, however a new parameter could be added to en:template:nutritional value (or another infobox)
Domain food (Q2095)
Allowed values string pattern: \d{2}[A-Z]\d{5}
Example lemon juice (Q1375049)01B30288
Source NUTTAB 2010
Formatter URL http://archive.foodstandards.gov.au/consumerinformation/nuttab2010/nuttab2010onlinesearchabledatabase/onlineversion_code.cfm?&action=getFood&foodID=$1
Robot and gadget jobs Suggest that this database be included into mix-and-match similar to the existing NDB mix-and-match
Motivation

This property request is similar to existing property USDA NDB number (P1978) where an American database USDA National Nutrient Database (Q7866379) is linked to foods on Wikidata. The NUTTAB database is Australian and New Zealand specific and includes foods which are more common to Australian and New Zealand populations (for example, indigenous foods from flora endemic to Australia). NUTTAB (NUTrient TABles for use in Australia) is Australia’s reference nutrient database. NUTTAB 2010 contains nutrient data for 2668 foods available in Australia and up to 245 nutrients per food. The nutrients reported in NUTTAB will vary between foods, according to the data currently available to FSANZ. This in an authoritative source of nutritional information for foods, and addition of this property to Wikidata will further enhance understanding of nutrition and foods via the ability to link NUTTAB to Wikidata items.

Note: this identifier is essentially the same as the AUSNUT Food Identifier, except that some identifiers exist in NUTTAB and not AUSNUT, whilst other identifiers exist in AUSNUT but not NUTTUB. An alternative to having two properties (one each for AUSNUT and NUTTAB) would be to define a generic "FSANZ Food Identifier" and then set a boolean qualifier for each use of the property as to whether it is listed in NUTTAB or AUSNUT. Dhx1 (talk) 15:12, 22 November 2015 (UTC)

Discussion

analytical method[edit]

   In progress
Description method used to analyze the concentration of a chemical
Represents analytical technique (Q4751159)
Data type Item
Domain chemicals
Allowed values instances of analytical technique (Q4751159)
Example Acetic acid (Q47512)Acetic Acid (Q21761556)
Source Pocket Guide to Chemical Hazards (Q20022913)
Robot and gadget jobs Part of mass import of Pocket Guide
Motivation

The Pocket Guide to Chemical Hazards include a list of analytical methods that can be used to determine the presence and concentration of chemicals. The Pocket Guide refers to ID numbers of analytical methods published in the NIOSH Manual of Analytical Methods (Q21757411). I have created items for each of these methods and plan on modeling the relevant data on Wikidata and transcribing the text of this manual on Wikisource. I originally considered using determination method (P459) but I believe that property is meant to be used as a qualifier, plus it's confusing: chemicals don't have determination methods; their concentrations have determination methods. James Hare (NIOSH) (talk) 19:25, 18 December 2015 (UTC)

Discussion

Saehrimnir
Guerillero
Leyo
Snipre
Jasper Deng
Matt
CMBJ
Klortho
Dcirovic
Walkerma
Emw
the chemistds
Egon Willighagen
Daniel Mietchen
Andy Mabbett
Kopiersperre
Emily Temple-Wood
Pablo Busatto (Almondega)
TomT0m
Pictogram voting comment.svg Notified participants of Wikiproject Chemistry. James Hare (NIOSH) (talk) 18:00, 20 December 2015 (UTC)

BA candidate.svg Weak oppose This not really a property of a chemical and this depends on too many parameters like solvents, concentrations or contaminants. I prefer to use the identifier to link to the web page and to be able to recover that information there instead of importing all the stuff in WD. I think WD is not a compilation of all data especially when we speak about complex processes. Snipre (talk) 10:53, 14 January 2016 (UTC)
Snipre, the goal of the property is not to describe the entire analytical process within the statement, or even within a dedicated Wikidata item. Rather, the goal is to link a chemical with a specific method, which has a Wikidata entry that corresponds with a Wikisource entry. The Wikidata entry will contain some basic structured data but most of the complex information would be on the Wikisource page. Do you have alternative recommendations for associating an analytical method item with the chemical(s) the method is designed to measure? James Hare (NIOSH) (talk) 13:57, 14 January 2016 (UTC)

3DMet ID[edit]

   In progress
Description import Template:Chembox 3DMet (Q6871237)
Data type String
Domain chemical compound
Allowed values ?
Example ethanol (Q153) → B01253
Formatter URL http://www.3dmet.dna.affrc.go.jp/html/$1.html
Robot and gadget jobs Yes
Discussion

--GZWDer (talk) 08:32, 6 October 2015 (UTC)

Symbol support vote.svg Support Snipre (talk) 09:53, 14 January 2016 (UTC)

NSC Number[edit]

   In progress
Description The NSC number is a numeric identifier for substances submitted to the National Cancer Institute (NCI) for testing and evaluation. It is a registration number for the Developmental Therapeutics Program (DTP) repository. NSC stands for National Service Center.
Data type String
Domain chemical compound
Allowed values number
Example N-phosphonacetyl-L-aspartate (Q10851798) → 224131
Source https://dtp.cancer.gov/databases_tools/bulk_data.htm
Robot and gadget jobs Yes
Discussion

--GZWDer (talk) 08:49, 6 October 2015 (UTC)

Pictogram voting comment.svg Comment ChemSpider is not an Open Data database (certainly not CCZero) and I wonder under what conditions this info can be extracted and used. What is the plan here? Are they involved? Egon Willighagen (talk) 21:12, 11 December 2015 (UTC)
@Egon Willighagen: Data can be downloaded and matched with CAS numbers or SMILES. Snipre (talk) 18:31, 31 January 2016 (UTC)
Symbol support vote.svg Support Snipre (talk) 18:31, 31 January 2016 (UTC)

Global-warming potential (100 years)[edit]

   In progress
Description heat trapped by a certain gas in CO2 equivalents
Represents Global-warming potential (Q901028)
Data type Number
Template parameter "GWP" in Infobox Chemikalie
Domain chemical compound (Q11173) and mixture (Q169336)
Example Trichlorofluoromethane (Q423000) → 5352
Source Global warming potentials and radiative efficiencies of halocarbons and related compounds (doi:10.1002/rog.20013) or IPCC Fifth Assessment Report (Q3429705) Supplementary Material ([4])
Motivation

GWP for 100 years.--Kopiersperre (talk) 13:54, 31 January 2016 (UTC)

Discussion
  • Pictogram voting question.svg Question Would a single property with a duration qualifier work better here? Thryduulf (talk: local | en.wp | en.wikt) 20:28, 31 January 2016 (UTC)
In nearly all cases in German Wikipedia the GWP is given for 100 years. But for completeness I added also the 20 years value.
If every duration would be possible, of course the qualifier approach would fit better. Because of the benefit of much easier querying I would urge to create two properties here.--Kopiersperre (talk) 23:37, 31 January 2016 (UTC)
Symbol support vote.svg Support I support this property but I agree with Thryduulf that there should be a generic property Global warming potential, for which the duration is specified as a qualifier. As many GWPs are given for 100 years, it might be possible to create a sub-property which already has the duration 100 years embedded. But I would add this generic property rather than another specific GWP for 20 years. --Jtuom (talk) 11:29, 2 February 2016 (UTC)
Pictogram voting comment.svg Comment I would support a generic property with duration as qualifier. Snipre (talk) 21:34, 2 February 2016 (UTC)

Global-warming potential (20 years)[edit]

   In progress
Description heat trapped by a certain gas in CO2 equivalents
Represents Global-warming potential (Q901028)
Data type Number
Template parameter "GWP" in Infobox Chemikalie
Domain chemical compound (Q11173) and mixture (Q169336)
Example Trichlorofluoromethane (Q423000) → 7020
Source Global warming potentials and radiative efficiencies of halocarbons and related compounds (doi:10.1002/rog.20013) or IPCC Fifth Assessment Report (Q3429705) Supplementary Material ([5])
Motivation

GWP for 20 years.--Kopiersperre (talk) 13:54, 31 January 2016 (UTC)

Discussion

Medicine / Medizin / Médecine[edit]

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

onset[edit]

   In progress
Description The age group in which disease manifestations appear
Represents age of onset (Q4691924)
Data type Item
Template parameter not yet available
Domain physiological condition (Q7189713)
Allowed values congenital onset (Q21953121), neonatal onset (Q21953125), childhood onset (Q21955201), juvenile onset (Q21955202), adult onset (Q21955204);
Example gout (Q133087) -> adult onset (Q21955204); neonatal jaundice (Q1755487) -> neonatal onset (Q21953125)
Source Subclasses of "onset" in Human Phenotype Ontology (http://compbio.charite.de/hpoweb/showterm?id=HP:0003674)
Motivation

This property is intended to model the age group in which disease manifestations appear. It precisely aligns with the Human Phenotype Ontology (HPO), a widely-used clinical ontology for which much open data exists. Emw (talk) 23:09, 3 January 2016 (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
sebotic
Pictogram voting comment.svg Notified participants of Wikiproject Medicine

Discussion
  • Pictogram voting comment.svg Comment I agree that having a property for age of onset (Q4691924) is useful. However, I think more values should be allowed: all those listed under the given URL. Another issue is whether to limit this property to humans or to include other species, which may get complex easily. --Daniel Mietchen (talk) 03:37, 4 January 2016 (UTC)
  • Pictogram voting comment.svg Comment Whether age groups or numerical values are allowed, the name of the property should be the less ambiguous "age of onset". Swpb (talk) 18:10, 26 January 2016 (UTC)

incidence[edit]

   In progress
Description probability of occurrence of a given condition in a population within a specified period of time
Data type Number
Template parameter Wikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
Domain diseases, events
Allowed values 0 - INF cases per unit of person-time
Example Tuberculosis (Q12204) → 1000 cases per 100000 person-years globally; qualifier point in time (P585) 2013
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source en:Incidence
Robot and gadget jobs Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Motivation

There is already a fairly similar property prevalence (P1193) which is about proportion of population with a specified disease at a given timepoint. Incidence is about occurrence of disease or other events in a population. It is a very useful metric in medicine and it describes the importance of a disease. Prevalence is not an illustrative metric for diseases with very different durations; instead, incidence correctly describes the rate of becoming sick. Also, it has wide applicability and large use in epidemiology in both descriptive and predictive modelling. Jtuom (talk) 14:45, 28 January 2016 (UTC)

Discussion

Symbol support vote.svg Support

disease burden[edit]

   In progress
Description impact of a health problem as measured by financial cost, mortality, morbidity, or other indicators. It is often quantified in terms of quality-adjusted life years (QALYs) or disability-adjusted life years (DALYs), both of which quantify healthy years gained or lost due to disease and different health conditions.
Data type Number
Template parameter Wikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
Domain evaluation of importance of diseases and public health policies
Allowed values -INF - INF disability-adjusted years of life lost
Example Tuberculosis (Q12204) → 15 900 000 disability-adjusted life years globally; qualifier point in time (P585) 2013
Format and edit filter validation (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source en:Disease burden
Robot and gadget jobs Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
Motivation

There is already a related property prevalence (P1193) and a suggested property incidence. With disease burden, these three properties together are able to give a rich quantitative understanding of the public health impacts of different diseases, outcomes, and risk factors. Prevalence and incidence are good metrics for disease-specific descriptions, but they do not work when aggregating mild but prevalent and severe but rare diseases; the numbers of cases are incompatible. With burden of disease and one of its units, such as en:DALYs, the public health importance of diseases can be meaningfully compared. Also, disease burden has wide applicability and large use in public health policy and predictive modelling for decision support. Such issues are important in Wikidata as well for e.g. comparisons of countries. Jtuom (talk) 15:05, 28 January 2016 (UTC)

Discussion

Symbol support vote.svg SupportMatleenat (talk) 07:36, 31 January 2016 (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}}

L2 Cache[edit]

   In progress
Description Amount of L2 Cache of the CPU in Bytes (or maybe bits?)
Data type Number
Domain CPU
Example Core2 Quad Q6600 (Q15218754): 8MB
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) 15:33, 21 November 2013 (UTC)

Symbol support vote.svg Support I created an item for the processor. Hopefully we will get both bit and byte in the numeric datatype. --Tobias1984 (talk) 16:10, 21 November 2013 (UTC)
Pictogram voting comment.svg Comment I think this is best left until we have the number type, and know how it will function, because we may only need one generic property for "size in bytes" which can be used as a qualifier. So, for example, we may be able to claim that a CPU has part L2 cache with qualifiers, quantity = 2, size = 8MB. Let's not create 100s of properties for speeds and dimensions. Danrok (talk) 02:11, 27 January 2014 (UTC)

Time2wait.svg On hold To be re-opened when the right datatype is available.--Micru (talk) 13:57, 23 May 2014 (UTC)

@MisterSanderson, Tobias1984, Danrok, Micru: So quantity datatype is now available, and we have megabyte (Q79735) and related items so in principle we can move ahead. However Danrok 's comments should be taken into account. We don't actually have any property (that I can find) that would give a generic "size" suitable for showing the number of megabytes, pixels etc - I think that property should be created first and may be all we need. Also I couldn't find an item corresponding to L2-cache: the only related one I think is cache (Q165596) (which has aliases include L2 and L3). Please look into some of these and let's have a more organized proposal for computing properties here! Is "has part" generally a suitable way to document the components of a CPU, camera, phone, etc, rather than having separate properties for each piece? That makes sense to me... ArthurPSmith (talk) 20:11, 11 December 2015 (UTC)

We have a maximum capacity (P1083) property and this probably should become a generic "capacity" property, to be used to indicate how many things the item can hold, such as people, cars, bytes, etc. Danrok (talk) 01:27, 12 December 2015 (UTC)
Well maximum capacity (P1083) seems very specific to counting people, has constraints that would need to be modified, it's been used by a Russian project etc (see discussion page). I think a new more generic property is warranted. Maybe let's add it under Wikidata:Property_proposal/Generic @Danrok: can you take care of making the proposal? Or maybe I will try later this week if it's not done yet. And @MisterSanderson: - what we are specifically proposing here is as an alternative to your property, to use the combination has part (P527) with an item for "L2 cache" and a qualifier specifying "capacity" (size) in MB or GB or whatever appropriate unit. This seems reasonable to me and I think it's preferable as a rule to use more generic properties where they make sense. What are your feelings on the matter? ArthurPSmith (talk) 20:34, 14 December 2015 (UTC)
I could not understand what you said about not existing a generic size property.--MisterSanderson (talk) 16:34, 12 December 2015 (UTC)
@MisterSanderson: I think he was thinking like
< proc > has part search < L2 cache >
size search < whatever Mb >
. author  TomT0m / talk page 13:15, 11 January 2016 (UTC)

Geology[edit]

Please visit Wikidata:WikiProject Geology for more information.

Australian Geological Provinces Database Entity ID[edit]

   In progress
Description Unique identifier of a geologic province in the Australian Geological Provinces Database published by Geoscience Australia (government agency responsible for geological mapping)
Represents geologic province (Q2140450)
Data type String
Template parameter None known to exist, however this property would be suitable to add to a new or existing infobox
Domain geologic province (Q2140450) shield (Q852013), Platform (Q666258), orogeny (Q184554), structural basin (Q749565), large igneous province (Q792425), crust (Q16760598), perhaps others more specific (subclasses)
Allowed values string format: \d+
Example Amadeus Basin (Q451785)22078
Source Australian Geological Provinces Database and Australian Geological Provinces (front page describing the database)
Formatter URL http://www.ga.gov.au/provexplorer/provinceDetails.do?eno=$1
Robot and gadget jobs I can scrape database entries from the Australian Geological Provinces Database (all results) and add them to mix-and-match. Most have Wikipedia articles with matching names, so it'll be easy.
Motivation

Existing property Australian Stratigraphic Units Database ID (P2367) is an identifier for stratigraphic units in the Australian Stratigraphic Units Database also produced by Geoscience Australia. This proposed Australian Geological Provinces Database Entity ID property is linked directly to stratigraphic units listed in the Australian Stratigraphic Units Database. By adding this property to Wikidata, further context is provided for which geologic province each stratigraphic unit is contained within. A large number of provinces within this database have existing Wikipedia (English) articles and thus this property will assist these articles with inclusion of lists of stratigraphic units for each province. Dhx1 (talk) 10:28, 1 December 2015 (UTC)

Discussion

Moment magnitude scale[edit]

moment magnitude scale
Scale used to mesure the magnitude of an earthquake.
Description One of the scales used to mesure the magnitude of an earthquake.
Represents moment magnitude scale (Q201605)
Data type Number
Template parameter magnitude
Domain earthquake (Q7944)
Allowed values I think it's from 0 to 10, but I'm not sure.
Example 2010 Haiti earthquake (Q43777) -> 7.0 to 7.3
Source référence externe, article de liste de Wikipédia, etc.
Robot and gadget jobs I don't know.
Motivation

IMHO, theses properties are fundamentals to qualify earthquakes. It is possible now to create property with numbers and I think we must create theses. Simon Villeneuve (talk) 21:45, 17 January 2016 (UTC)

Symbol support vote.svg Support Usefull property. --Fralambert (talk) 23:14, 18 January 2016 (UTC)
Symbol support vote.svg Support. Thryduulf (talk: local | en.wp | en.wikt) 03:08, 19 January 2016 (UTC)
Symbol support vote.svg Support Aude (talk) 21:42, 3 February 2016 (UTC)
Discussion
@Simon Villeneuve, Fralambert, Thryduulf, Aude: Done! ArthurPSmith (talk) 21:31, 5 February 2016 (UTC)
Thank you! :) Aude (talk) 22:14, 5 February 2016 (UTC)

Richter magnitude scale[edit]

Richter magnitude scale
scale used to mesure the magnitude of an earthquake
Description One of the scale used to mesure the magnitude of an earthquake.
Represents Richter scale (Q38768)
Data type Number
Template parameter magnitude
Domain earthquake (Q7944)
Allowed values I think it's from 0 to 10, but I'm not sure.
Example 2007–2008 Nazko earthquakes (Q4610352) -> < 4.0
Source référence externe, article de liste de Wikipédia, etc.
Robot and gadget jobs I don't know.
Motivation

IMHO, theses properties are fundamentals to qualify earthquakes. It is possible now to create property with numbers and I think we must create theses. Simon Villeneuve (talk) 21:45, 17 January 2016 (UTC)

Symbol support vote.svg Support Usefull property. --Fralambert (talk) 23:15, 18 January 2016 (UTC)
Symbol support vote.svg Support magnitude is pretty fundamental to earthquakes. Thryduulf (talk: local | en.wp | en.wikt) 03:09, 19 January 2016 (UTC)
General support for having a property for earthquake magnitude, but oppose restricting this to Richter scale measurements. The en:Moment magnitude scale is more commonly and generally used now to measure earthquakes. The scale used could be indicated perhaps with the unit? or a qualifier. Aude (talk) 23:43, 23 January 2016 (UTC)
OK, duh. I see the proposal above for Moment magnitude scale as a separate property. I am ok with two separate properties for each. Aude (talk) 23:44, 23 January 2016 (UTC)
Symbol support vote.svg Support Snipre (talk) 21:37, 2 February 2016 (UTC)
Discussion
@Simon Villeneuve, Fralambert, Thryduulf, Aude, Snipre: Done! Wasn't sure how to implement the example with a '<' value though, so I picked a different example. ArthurPSmith (talk) 21:51, 5 February 2016 (UTC)

Geography[edit]

salinity[edit]

   In progress
Description salinity of a body of water
Represents salinity (Q179615)
Data type Number
Template parameter ?
Domain bodies of water
Allowed values non-negative numbers with units of concentration, e.g grams per litre (g/L)
Example Salton Sea (Q503301) → 44 grams per litre; Pacific Ocean (Q98) → 35 g/L; Great Salt Lake (Q178741) → 50 g/L (qualifier: maximum (Q10578722)), 70 g/L (qualifier: minimum (Q10585806));
Source external reference, Wikipedia list article, etc.
Motivation

I discovered this apparently missing when improving the Salton Sea (Q503301) entry, en:Salton Sea makes a big deal about the salinity of the lake. Thryduulf (talk: local | en.wp | en.wikt) 01:02, 12 November 2015 (UTC)

Discussion
Symbol support vote.svg Support But needs qualifiers like 'average', 'surface water' or numeric qualifiers 'at depth: 10 m below surface', etc... - Large bodies of water are usually layered in their physico-chemical properties so we really need to make it clear where salinity was measured. --Tobias1984 (talk) 11:03, 29 November 2015 (UTC)
We have and
< 35 g/L > height (P2048) miga < -10 >
metre search < {{{5}}} >
already, although qualifiers "measurement taken at location" (item) and "measurement taken at point" (number with unit) would be possibly better. Thryduulf (talk: local | en.wp | en.wikt) 02:18, 3 December 2015 (UTC)
  • Symbol oppose vote.svg Oppose. These situations should use a generic property to indicate the makeup of the body of water, instead of having one for salt and one for each other substance. --Yair rand (talk) 06:55, 16 December 2015 (UTC)
    • @Yair rand: which property do you propose to use for that? Which other substances do you forsee that property being used for? Thryduulf (talk: local | en.wp | en.wikt) 00:44, 17 December 2015 (UTC)
      • @Thryduulf: Use has part (P527), with proportion (P1107) as a qualifier. P1107 was proposed with material composition as an explicit example: "Earth atmosphere is composed of 80% dinitrogen and 20% dioxygen". --Yair rand (talk) 02:28, 17 December 2015 (UTC)
        • That doesn't seem like it is capable of expressing the qualifiers Tobias1984 talks about. has part (P527) is a very blunt instrument - e.g. and are very different uses of the same properties and are not easy to parse separately. Thryduulf (talk: local | en.wp | en.wikt) 02:58, 17 December 2015 (UTC)
          • I agree that this isn't as specific as it should be (see further discussion here), but it's still generally usable. In a little project that I'm working on, I distinguish between the first and second kinds by checking whether the target has any wdt:P279|^wdt:P279|^wdt:P31 values. Regarding extra qualifiers for applying the statement proportions to a particular altitude, I'm not sure what properties should be used. --Yair rand (talk) 03:22, 17 December 2015 (UTC)
            • My reading of that discussion seems to contradict your assertion that subclass of (P279) is usable - we need to be more specific about the nature of parts not increasing the overloading of subclass of (P279). Requiring checks as your project does will not scale as it requires knowing all classes of items that are/may be noted as being a part of the class you are interrogating and determining what properties those class of items you are interested in all have have that none of the others classes of items do (or vice versa). Requiring two or three levels of interrogation and processing before you can interrogate seems a rather inefficient alternative to a simple specific property with relevant qualifiers. Thryduulf (talk: local | en.wp | en.wikt) 21:49, 19 December 2015 (UTC)

(Lowest) atmospheric pressure / Niedrigster Atmosphärendruck[edit]

   In progress
Description Lowest atmospheric pressure in millibars (mbar)
Data type Number
Template parameter See en:Template:Infobox_hurricane: Pressure
Domain Term — hurricanes/tropical cyclones, winter storms, European windstorms (think Freie Universität Berlin), etc.
Allowed values Numeric — two-digit, three-digit
Example Q264, Q187621, Q2110774, Q3045816
Source HURDAT
Robot and gadget jobs Manual to avoid human error.
Proposed by Hurricanefan24 (talk) 13:50, 18 March 2013 (UTC)
Symbol support vote.svg Support --Goldzahn (talk) 19:11, 18 March 2013 (UTC)
Wrong data type. Should be deferred until QuantityValue implemented. --EugeneZelenko (talk) 13:41, 19 March 2013 (UTC)
Symbol oppose vote.svg Oppose A property proposal for pressure is proposed seeWikidata:Property_proposal/Term#Pressure. Merge with this one and use qualifier to indicate upper or lower. Snipre (talk) 14:07, 29 April 2013 (UTC)
Symbol support vote.svg Support Lowest atmospheric pressure is a measurement of hurricane strength, and so I support having it as a separate property specifically for hurricanes. Sven Manguard Wha? 20:21, 15 June 2013 (UTC)
Symbol support vote.svg Support per Sven Manguard. Macadamia1472 (talk) 09:38, 16 October 2013 (UTC)
Symbol support vote.svg Support Thryduulf (talk: local | en.wp | en.wikt) 14:33, 13 January 2016 (UTC)
Symbol support vote.svg Support needed for en:Template:Infobox_storm etc. and representing such info. Aude (talk) 00:54, 24 January 2016 (UTC)

Maximum sustained winds / Maximaler kontinuierlicher Wind[edit]

   In progress
Description Maximum sustained wind evaluated by agency.
Data type Number
Template parameter See en:Template:Infobox hurricane: 1-min winds, 5-min-winds, 10-min-winds
Domain Term — hurricanes/tropical cyclones, winter storms, European windstorms (think Freie Universität Berlin), etc.
Allowed values Numeric — two-digit, three-digit
Example Q264, Q187621, Q2110774, Q3045816
Source HURDAT
Robot and gadget jobs Manual to avoid human error.
There are differences in the usage of the number of minutes in different countries; this would result in misleading information, might need to be disambiguated. Also, consider adding a "classification" property — i.e. "Category 1," "super typhoon," "severe tropical storm," etc.? Hurricanefan24 (talk) 13:50, 18 March 2013 (UTC)
Symbol support vote.svg Support --Goldzahn (talk) 19:10, 18 March 2013 (UTC)
Wrong data type. Should be deferred until QuantityValue implemented. --EugeneZelenko (talk) 13:43, 19 March 2013 (UTC)
Appears that's been fixed.

topographic prominence[edit]

   In progress
Description height of a mountain or hill relative to the lowest contour line encircling it.
Represents topographic prominence (Q656751)
Data type Number
Template parameter Prominence in en:Template:Infobox_mountain
Domain mountains
Allowed values any numeric value, preferably measured in meters (for consistency)
Example 8,848 m (e.g. for Mount Everest / Mount Everest (Q513))
Motivation

Would like to be able to represent more parts of en:Template:Infobox mountain in Wikidata. Aude (talk) 03:24, 14 January 2016 (UTC)

Discussion

snow accumulation[edit]

   In progress
Description snow accumulation or snow height, qualified with location and point in time. (a maximum value could be pulled out via lua, in the infobox wants to show just the maximum)
Data type Number
Template parameter "hauteur neige" in fr:Infobox Événement météorologique or "maximum snow" in en:Template:Infobox storm
Domain storms, such as January 2016 United States winter storm (Q22222608) and February 5–6, 2010 North American blizzard (Q2071241)
Allowed values amount, usually measured and reported in cm or inches
Example 38.3 inches, qualifiers: location - location (P276): Elkridge (Q755962), point in time (P585): February 6, 2010 (for February 5–6, 2010 North American blizzard (Q2071241))
Source external reference (e.g. http://www.wpc.ncep.noaa.gov/discussions/nfdscc2.html)
Robot and gadget jobs possibly bots could help, but think this is more an editorial decision regarding what places to include (since we probably wouldn't want to include them all, just a selection like the major airports)
Motivation

I am struggling to add information to January 2016 United States winter storm (Q22222608). I think snow accumulation is expected information in items such as this, and is one of the things represented in the infobox on Wikipedia articles. I would be open to instead just use height, but then would want a qualifier property to indicate height of what? (not sure P1629 is appropriate for that, or not sure what/if anything we have) Aude (talk) 23:39, 23 January 2016 (UTC)

Discussion
  • A more general purpose "precipitation" might be better, qualified as to the type (e.g. snow, rain, freezing rain, etc.). --Izno (talk) 14:20, 25 January 2016 (UTC)
    • Would be ok with generalizing this to "precipitation", with a qualifier. Aude (talk) 03:58, 27 January 2016 (UTC)
      • Required qualifier instance of (P31)? Also, snow accumulation/height isn't exactly precipitation e.g. some precipitated snow may melt prior to "sticking" to the ground, which would affect the height. Is that fine? --Izno (talk) 13:05, 27 January 2016 (UTC)
        • Or maybe just "depth" would be better, though that doesn't apply to all precipitation types but might apply to other things? Aude (talk) 22:39, 31 January 2016 (UTC)
  • Symbol support vote.svg Support either a specific or generic property with a qualifier. I don't think instance of (P31) is the correct qualifier, material used (P186) is the best I can find from existing properties with but I think better would be a new generic qualifier "of" or "type" (or maybe "of type"). Thryduulf (talk: local | en.wp | en.wikt) 14:50, 27 January 2016 (UTC)
    • We have generic "of" lying around somewhere used exclusively as a qualifier; the notion of "type" is equivalent to "instance of" (it correlates to "rdf:type", among other things). So this also is the one you're looking for. No opinion on either.
    • Ah, I didn't see generic of but I did see generic as (P794). --Izno (talk) 19:59, 27 January 2016 (UTC)
      • If we have a generic "of" (I can't find it though) then I'd prefer that as the qualifier. Thryduulf (talk: local | en.wp | en.wikt) 20:47, 31 January 2016 (UTC)
        • @Thryduulf: Here it is: within the scope of (P642) Swpb (talk) 14:30, 2 February 2016 (UTC)
          • Hmm, the English label "within the scope of" suggests a narrower/different focus that what would work here. As an English sentence "35mm precipitation, within the scope of: snow" doesn't make sense (nor really does "35mm precipitation, instance of: snow") unlike "35mm precipitation, of: snow" or "35mm precipitation, type: snow". Thryduulf (talk: local | en.wp | en.wikt) 21:26, 2 February 2016 (UTC)
            • This is actually why I like "as": "Precipitation: 75cm as snow, 4mm as sleet".

              And I'm still confused why you think instance of != type when they are in fact the same. --Izno (talk) 00:58, 3 February 2016 (UTC)

Maths[edit]

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

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 instances of logic (Q8078)
Example
< Modus ponens (Q655742) (View with Reasonator) > admissible in search < classical logic (Q236975) (View with Reasonator) >
Proposed by TomT0m (talk)
Discussion

Motivation:

Proposed by: TomT0m (talk)


Opensofias (talk) Tobias1984 (talk) Micru (talk) Arthur Rubin (talk) Cuvwb (talk) Danneks (talk) TomT0m (talk) Tylas (talk) 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)
Symbol support vote.svg Support --Almondega (talk) 12:50, 19 October 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
< celestial body (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)
Pictogram voting comment.svg Comment @TomT0m, Succu, Doc James, Filceolaire, Almondega, Danneks: I suggest we create two properties here as near-inverses, similar to has part (P527) and part of (P361), and use for the English names "studies" and "studied by". I think that would resolve the above discussion, agreed? I think these are important relationships to capture in wikidata and go beyond what part of (P361) can indicate so I do support creating them. If one of you could edit the proposal to specify two properties with those or other suitable names, I think that's the next step here. ArthurPSmith (talk) 16:09, 7 December 2015 (UTC)

ISO 4063 process number[edit]

   In progress
Description – (Please translate this into English.)
Represents no label (Q22443162)
Data type Number
Template parameter Infobox lastechniek: procesnummer (ISO 4063)
Domain Technical processes
Example shielded metal arc welding (Q1992360) → 111
Source Official document, Complete Table, (en/de/fr)
Motivation

ISO-approved classification scheme for welding & soldering processes.--Kopiersperre (talk) 15:02, 2 February 2016 (UTC)

Discussion