Wikidata

Wikidata:Property proposal/Archive/52

< Wikidata:Property proposal‎ | Archive
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

This archive page is full. Use Wikidata:Property proposal/Archive/53 or subsequent ones.

The previous archive page is Wikidata:Property proposal/Archive/51.

Wikidata example external identifier

   Withdrawn
Descriptionspecify sample external ID for property
Data typeExternal identifier
Template parameterQualifier for Wikidata property example for properties (P2271) or Wikidata property example (P1855), for {{Property documentation}}
DomainWikidata property
Example 1MISSING
Example 2MISSING
Example 3MISSING
Motivation

We have example properties for all types, such as P1858 (P1858) and P1859 (P1859) but not for new external ID type. Laboramus (talk) 05:21, 24 March 2016 (UTC)

Discussion

(Since Wikidata:Requests for comment/Reforming the property creation process "withdraw" is a proposal closure, that can only be done by someone entitled to do property creation. I therefore confirm this proposal being withdrawn. Lymantria (talk) 10:08, 5 May 2016 (UTC))

ARKive ID

Descriptionidentifier for a taxon, in the ARKive database
RepresentsARKive (Q433276)
Data typeString
Template parameteren:Template:ARKive
DomainTaxons
Allowed valuesValid Arkive URL slugs
ExampleHeteropoda davidbowie (Q1315848) → david-bowie-spider/heteropoda-davidbowie
Sourcehttp://www.arkive.org/
Formatter URLhttp://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)
An URL can change at any time, a ID shouldn't.   Oppose --Succu (talk) 21:58, 19 March 2016 (UTC)
We have many IDs based on URL stems. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:07, 19 March 2016 (UTC)
So what? Watson & Dallwitz family ID (P1761) is a problematic one. Stable but incomplete, because it did not inculde The families of gymnosperms. --Succu (talk) 22:26, 19 March 2016 (UTC)
There appears to be no connection between that and ARKive, whatsoever. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:39, 19 March 2016 (UTC)
You claimed „We have many IDs based on URL stems“ - I gave an example. That's the „connection“. --Succu (talk) 22:48, 19 March 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)
There are far more than "a few" pages. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:49, 19 March 2016 (UTC)
The site holds more than a few pages, but many of these deal with taxa where there is sufficient picture material available from other sources. So I am not convinced there are all that many pages "that are of interest" to this project. - Brya (talk) 06:57, 20 March 2016 (UTC)
The site, which is of course still growing, has circa 16,000 species and over 100,000 films & photos, according to ARKive today. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:00, 21 March 2016 (UTC)
So just another picture site provides knowledge about taxa? --Succu (talk) 22:43, 21 March 2016 (UTC)
No, not "just" that at all. As I said in my proposal (emphasis added), it is a "repository of high-quality, high-value media of endangered species". That media is provided by world-leading film makers, including PBS, the BBC natural History Unit, and National Geographic. I have also pointed out that its "strengths are in quality and rarity". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:51, 22 March 2016 (UTC)
  •   Support Per Andy. --Averater (talk) 06:18, 22 March 2016 (UTC)
  •   Support I don't see how this could be a bad thing at all, the more thngs like this, the better. Most websites we have IDs for does not have freely licensed content. (t) Josve05a (c) 21:40, 13 April 2016 (UTC)
  •   Support I agree with Andy. The strength of the argument about both the quality and rarity of the images has resulted in my support. Ambrosia10 (talk) 18:01, 27 April 2016 (UTC)
  •   Oppose I have visited a sample species (Cinnaber moth) of which I know a bit more than is in general sources. I'm far from impressed by the description, but okay, it is not seriously flawed either. The biology section may be valid for only a part of its range, as two British books form the main source. That also causes a weird GB-centric description of its range. But this source is presented as a source of quality media. I am seriously disappointed here. Photographs are small to medium sized, not exceptional, video's of its eating caterpillar are okay. But this does certainly not exceed the quality of commons:Category:Tyria jacobaeae, while commons has the favour of having photographs of the chrysalis (pupa) and mounted specimens. This sample species does not convince me that all or most pages of ARKive are of interest, while some special ones may be. I think external data available at URL (P1325) suits for the ones where indeed very valuable media are found. Lymantria (talk) 11:47, 29 April 2016 (UTC)
    I did not say or intend to say that there do not exist pages on ARKive with interesting media, where commons fails to have them (like the David Bowie spider), but my browsing through ARKive didn't convince me that a general ID for ARKive is something we should have at Wikidata.
    Indeed, one might argue that data as meant by external data available at URL (P1325) does not stretch to visuals. Perhaps a similar property for external media is a better idea. Lymantria (talk) 12:40, 29 April 2016 (UTC)

@Pigsonthewing, Averater, Josve05a, Ambrosia10:   Done, opinions slightly favor creation. User:Succu voiced concern about the possible instability of URLs, but the URLs chosen here seem pretty deliberate, so I don't think this is a great concern. This could have used an URL datatype as well, but this is just a matter of taste, and I used the type as proposed, especially since the hostname is redundant. User:Lymantria voiced concern about the site's quality. But this seems to be a minority opinion, considering the pro voices. Also, this is not a structurally important property, so the impact will be fairly small, if it turns out that this property was a mistake. --Srittau (talk) 20:43, 13 May 2016 (UTC)

gait

   Done: gait (P2839) (Talk and documentation)
DescriptionGait of an animal
Representsanimal gait (Q2370000)
Data typeItem
DomainItems
Allowed valueswalk (Q2236563), tölt (Q2337163), etc.
Example
Motivation

We should start to document better how living creatures eat, mate, move or come to life. This property would help. Thierry Caro (talk) 02:36, 10 April 2016 (UTC)

Discussion

  Comment Thierry Caro I assume (as in your example) we would generally expect multiple values for this property for a given taxon? ArthurPSmith (talk) 18:44, 11 April 2016 (UTC)

Yes. Thierry Caro (talk) 20:29, 11 April 2016 (UTC)

@Thierry Caro, Thryduulf, Pigsonthewing, Lymantria:   Done as there is certainly consensus to create this property. That said, Lymantria has concerns that should certainly be discussed on the property's discussion page. For now, I constrained the domain to animals. --Srittau (talk) 19:15, 16 May 2016 (UTC)

produced by

   Done: produced by (P2849) (Talk and documentation)
DescriptionLinks a biologic/biochemical entity with the entity it has been produced by
Data typeItem
Domainbiochemically active items, e.g. cells
Examplemelanosome (Q1065756) → melanocyte (Q247101)
Sourcescientific papers, databases, ontologies, stating a certain connection. E.g. ExoCarta
Robot and gadget jobsProteinBoxBot 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

  Support --Andrew Su (talk) 15:21, 2 October 2015 (UTC)

  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)

  Support lv_ra (talk) 16:05, 2 October 2015 (UTC)

  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.   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)      ⟩ produce Search ⟨ Q25314 ⟩
by process Search ⟨ Q183236 ⟩
to complete the model. author  TomT0m / talk page 08:15, 3 October 2015 (UTC)
@TomT0m: As the inverse property for 'produced by', 'product or material produced or service provided (P1056)' can be used. I initiated a discussion on its talk page. But as the inverse property of product or material produced or service provided (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   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)

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

  Notified participants of WikiProject Medicine

  Oppose as is. “melanosome <produced by> melanocyte” doesn't make any sense. Melanosomes are an integral part of melanocytes, the relation should be “exists in” or “part of”. “secreted by” may be a better wording for the property. —Tinm (d) 01:53, 7 February 2016 (UTC)

@Tinm: Melanosomes are produced by Melanocytes and then exported as extracellular vesicles to keratinocytes [1], so your argument cannot be regarded as valid. Production of extracellular vesicles is a common process in biology, this is one reason why we need that property. Sebotic (talk) 18:03, 17 May 2016 (UTC)

@Sebotic, Andrew Su, Gtsulab, Emitraka, Tinm, TomT0m:  Done Majority support. Hopefully the description limits the use enough. As alias "secreted by" is included as suggested by Tinm. Lymantria (talk) 20:54, 22 May 2016 (UTC)

miRBase pre-miRNA ID

Descriptionthe identifier for pre-miRNAs in miRBase, the reference database for microRNAs
RepresentsmiRBase (Q6826947)
Data typeExternal identifier
DomainMolecular biology
Allowed values'MI' as a prefix, followed by 7 digits
Examplehsa-mir-127 (Q6871648) → MI0000472
Sourcehttp://www.mirbase.org/
Formatter URLhttp://www.mirbase.org/cgi-bin/mirna_entry.pl?acc=$1
Motivation

microRNAs are important regulators of gene expression and therefore essential for understanding of biology, furthermore, there are attempt to use them as drugs. miRBase is the reference database for human and other species microRNAs. As there are already hundreds of microRNAs in Wikidata, this identifer would allow linking these to their reference database. This proposal is a joint proposal with the miRBase mature miRNA ID below. Sebotic (talk) 10:01, 19 May 2016 (UTC)


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

  Notified participants of WikiProject Medicine

Discussion

@Sebotic, Putmantime, I9606, Andrawaag, Emitraka:  Done miRBase pre-miRNA ID (P2870) -- Lymantria (talk) 14:38, 28 May 2016 (UTC)

miRBase mature miRNA ID

Descriptionthe identifier for mature miRNAs in miRBase, the reference database for microRNAs
RepresentsmiRBase (Q6826947)
Data typeExternal identifier
DomainMolecular biology
Allowed values'MIMAT' as a prefix, followed by 7 digits
Examplehsa-miR-127-3p (Q23839066) → MIMAT0000446
Sourcehttp://www.mirbase.org/
Formatter URLhttp://www.mirbase.org/cgi-bin/mature.pl?mature_acc=$1
Motivation

microRNAs are important regulators of gene expression and therefore essential for understanding of biology, furthermore, there are attempt to use them as drugs. miRBase is the reference database for human and other species microRNAs. Pre-microRNAs very frequently encode for 2 - 3 different mature microRNAs which have a different RNA sequence and therefore a different set of target genes. In order to properly represent this functional knowledge, each mature microRNA should be represented as a Wikidata item, linked to the pre-microRNA. This proposal is a joint proposal with the miRBase pre-miRNA ID Sebotic (talk) 10:01, 19 May 2016 (UTC)

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

  Notified participants of WikiProject Medicine

Discussion

@Sebotic, Putmantime, I9606, Andrawaag, Emitraka:  Done miRBase mature miRNA ID (P2871) -- Lymantria (talk) 14:39, 28 May 2016 (UTC)


NSC Number

   Done: NSC number (P2840) (Talk and documentation)
DescriptionThe 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 typeExternal identifier
Domainchemical compound
Allowed valuesnumber
Examplesparfosic acid (Q10851798) → 224131
Sourcehttps://dtp.cancer.gov/databases_tools/bulk_data.htm
Robot and gadget jobsYes
Discussion

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

  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)
  Support Snipre (talk) 18:31, 31 January 2016 (UTC)
  Support Sebotic (talk) 09:53, 13 March 2016 (UTC)
  Comment @GZWDer: Would this be a link that could give us a formatter URL? Lymantria (talk) 16:51, 21 April 2016 (UTC)

@GZWDer, Snipre, Sebotic:   Done --Srittau (talk) 20:00, 16 May 2016 (UTC)

has role (in ChEBI Ontology)

   Not done
Descriptionthe role of a certain compound in the context of the ChEBI (Chemical Entities of Biological Interest) ontology, e.g. anti-neoplastic agent
Data typeItem
Domainchemistry
Allowed valuesWikidata items which are part of the ChEBI ontology and therefore carry an ChEBI ontology ID ChEBI ID (P683)
Examplevemurafenib (Q423111) → antineoplastic (Q23987513)
Sourcehttps://www.ebi.ac.uk/chebi/init.do
Robot and gadget jobsProteinBoxBot will add this relation to drug items and other chemical entities.
Motivation

ChEBI is a central ontology for biology and chemistry. In order to represent the ChEBI ontology in Wikidata, a central requirement is the 'has role' property. The P794 (P794) is not suitable as it can only be used as a qualifier and the role property for actors is also restricted. Furthermore, biological process (P682), the one closes to the proposed property is not precise enough and also restricted to the Gene Ontology. subclass of (P279) does definitely not apply here (because it maps to 'is a') and instance of (P31) does not seem to fit as well for this purpose.

In principle, a 'has role' property could be used as a generalized property (for natural sciences), although redundancies with Gene Ontology need to be avoided. In addition, could we just use this property proposal to decide on all required properties to represent ChEBI in Wikidata at once [2]? Some of those already exist anyway. This would enormously speed up the process of getting complete ChEBI into Wikidata. thx! Sebotic (talk) 06:35, 3 May 2016 (UTC)

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

  Notified participants of WikiProject Chemistry

  Notified participants of WikiProject Medicine

Discussion
  •   Oppose @Sebotic: I don't think that the goal of WD is to integrate ChEBI. Doing that is the begin of a nightmare to be up-to-date with ChEBI modifications. WD is more a general ontology (top domain ontology) that a domain ontology. Snipre (talk) 13:18, 4 May 2016 (UTC)
    Just a detail: I am not opposed to a similar property but this property should be independent from ChEBI ontology. But again there is no sense to copy ChEBI: better map the WD items with ChEBI elements and people can then easily extracted ChEBI relations from WD items. Snipre (talk) 14:01, 4 May 2016 (UTC)
    • @Snipre: The reason that I want to import ChEBI is simply to give chemical compounds in Wikidata a structure. Currently, there is essentially no classification and structure in the chemical compound data in Wikidata. Moreover, it is not realistic to expect that such a structure will be created by the community nor can it be expected that a community-created structure will be of higher quality than ChEBI, which has been developed and maintained for many years now (since 2004). Nevertheless, I think for the usefulness of the chemical compound data in Wikidata, such a structure is a definite requirement. I agree that Wikidata itself is a high-level ontology, but it is not a help here but also not a hindrance. Importing and keeping Wikidata in sync with ChEBI is not a great challenge. I have done it before by importing the complete Gene Ontology structure. I have the code in place which keeps Gene Ontology in sync with Wikidata [3]. For ChEBI, this would work exactly the same way. ChEBI and Gene Ontology are approximately the same size (48,000 and 44,000 terms, respectively).
I would start with the backbone, which basically consists of 'is a' (subclass of (P279) in Wikidata) and 'has role', the rest of ChEBI can be imported if the properties are ready.
One very important point to make is that the ChEBI structure in Wikidata should serve as a backbone for the community to build on. So the import would essentially allow the community to expand ChEBI in the Wikidata space while still keeping compatibility with ChEBI (discrimination of contributions based on references and/or qualifiers). Sebotic (talk) 18:59, 4 May 2016 (UTC)
Sebotic You need to get approval by a several contibutors working in the field of chemistry/medecin/microbiology before doing that kind of importation: if you are the only doing that kind of importation and nobody knows what is the backbone of the classification, all your work will be destroy after some monthes. People can only respect the work of other contributors when they are aware of what is in front of them. Again I think that in term of maintenance this kind of initiatives are useless without a strong support of a large part of the community. I undo the work of several bots during the last monthes because they were not working properly: importing once is only the easy part of the job, maitain the structure over the time is the difficult one. Snipre (talk) 19:20, 5 May 2016 (UTC)
Snipre The goal of our effort is certainly to also do long term maintenance/sync of ChEBI in Wikidata, otherwise the value for Wikidata would be zero. As stated above, there is no technical challenge to keep ChEBI in sync with Wikidata. Shall I open a new thread on Project chemistry, so we can start a discussion? Sebotic (talk) 20:09, 16 May 2016 (UTC)
  •   Oppose I agree with Snipre - also, unless I'm misunderstanding, the meaning of this seems clearly along the lines of what instance of (P31) is intended for and is used for in other areas. Can you argue more clearly why it "does not seem to fit as well" here? ArthurPSmith (talk) 13:55, 4 May 2016 (UTC)
    ArthurPSmith Here instance of is a bad way to describe use of some items: we can have dozen of use/role for some items and this becomes difficult after to extract the correct values among 10 or 15 possibilities. A general property use/role is needed but not only for chemicals. Snipre (talk) 14:04, 4 May 2016 (UTC)
'has role' maps to http://purl.obolibrary.org/obo/RO_0000087 in the Relations Ontology and is being used by several other ontologies as well (see list at the bottom of the page the purl resolves to) Sebotic (talk) 20:17, 4 May 2016 (UTC)
Sebotic The definition should be more clearly defined in order to avoid any use of this property as another "instance of". The quality of the item using the property and the one of the property value should be given. Ex. Is D-penicillamine (Q421239) has role medication (Q12140) correct ? Or should we have D-penicillamine (Q421239) has role chelating ? Snipre (talk) 12:22, 11 May 2016 (UTC)
Snipre Sorry for the delayed reply! The properties instance of (P31), subclass of (P279) and a potential 'has role' property are all be mapped OBO/OWL terms in order to connect them to knowledge bases or knowledge organization systems which are already out there. I think that is very important. Regarding your example: instance of (P31) is mapped to [4] so it might be better to replace instance of (P31) with subclass of (P279) (is a) for chemical compounds in Wikidata, because this better describes the relationship (many other ontologies make heavy use of 'is a'). For me, there is a clear semantic distinction of 'is a' and 'has role' and I think this should also be modeled in Wikidata, as it makes the data more useful for others. For chemical compounds, 'is a' can be used to organize stuff in Wikidata, but also to fully represent ChEBI. Differentiation where a certain relation comes from, can just be organized via the references. So if I want to import/update ChEBI, only touch statements with ChEBI references or equal values, leave the other statements intact. So in my opinion, several structures could exist together. Sebotic (talk) 20:09, 16 May 2016 (UTC)

@Sebotic:   Not done, no consensus, but Wikidata:Property proposal/has role seems to have good chances. --Srittau (talk) 16:27, 19 May 2016 (UTC)

PubChem BioAssay ID (AID)

Descriptiona central identifier in PubChem, used as accession number for biological and biochemical assays
RepresentsPubChem (Q278487)
Data typeExternal identifier
Domainchemistry
Allowed valuesarbitrary number of digits
Examplevemurafenib (Q423111) → 1055888
Format and edit filter validationdigits only
Sourcehttps://www.ncbi.nlm.nih.gov/pcassay
Formatter URLhttps://pubchem.ncbi.nlm.nih.gov/bioassay/$1
Robot and gadget jobsProteinBoxBot will make use of this property to establish compound to assay links and especially references.
Motivation

PubChem is undoubtedly a central, open resource for high quality chemical data. In order to represent chemical information in Wikidata, two of the three central PubChem identifiers have already been established in Wikidata as properties, namely PubChem CID (P662) and PubChem Substance ID (SID) (P2153). In order to complete the list of essential PubChem identifers in Wikidata, I hereby propose the PubChem assay ID (AID). Although bioassays are complex and contain more than one chemical compound or substance, I consider the AID important in Wikidata, because it allows linking to high quality activity data. More importantly, this property allows PubChem bioassays to be referenced directly and so the assay id can be used to support claims about biochemical effects on proteins, etc. Sebotic (talk) 19:13, 18 May 2016 (UTC)


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

  Notified participants of WikiProject Chemistry

  Notified participants of WikiProject Medicine

Discussion

@Sebotic, I9606, Putmantime, Andrawaag, Emitraka:  Done now PubChem BioAssay ID (AID) (P2874) --Lymantria (talk) 08:26, 29 May 2016 (UTC)

SureChEMBL ID

   Done: SureChEMBL ID (P2877) (Talk and documentation)
Descriptionthe chemical compound identifier for the EBI SureChEMBL 'chemical compounds in patents' database
RepresentsSureChEMBL (Q24091097)
Data typeExternal identifier
Domainchemistry
Allowed valuesSURECHEMBL([0-9]\d)
Examplevemurafenib (Q423111) → SCHEMBL298931
Sourcehttps://www.surechembl.org/
Formatter URLhttps://www.surechembl.org/chemical/$1
Robot and gadget jobsProteinBoxBot will add statements based on this property.
Motivation

SureChEMBL has been established as a unique, open service by EBI, mining through usually cryptic patent application texts and extracting chemical compound information, giving hints on new, interesting compounds. This property would allow Wikidata chemical compound items be linked to patent applications and would also make it easier to find novel compounds not present in any other database yet. This is relevant, as patent applications are a much underestimated source of scientific data and knowledge. Sebotic (talk) 22:08, 18 May 2016 (UTC)

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

  Notified participants of WikiProject Chemistry

  Notified participants of WikiProject Medicine

Discussion

@Sebotic, I9606, Putmantime, Andrawaag, Emitraka, Egon Willighagen:   Done now SureChEMBL ID (P2877) --Lymantria (talk) 16:23, 29 May 2016 (UTC)

onset

   Done: age of onset (P2841) (Talk and documentation)
DescriptionThe age group in which disease manifestations appear
Representsage of onset (Q4691924)
Data typeItem
Template parameternot yet available
Domainphysiological condition (Q7189713)
Allowed valuescongenital onset (Q21953121), neonatal onset (Q21953125), childhood onset (Q21955201), juvenile onset (Q21955202), adult onset (Q21955204);
Examplegout (Q133087) -> adult onset (Q21955204); neonatal jaundice (Q1755487) -> neonatal onset (Q21953125)
SourceSubclasses 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)

  Notified participants of WikiProject Medicine

Discussion

@Emw, Daniel Mietchen:   Done as age of onset. The constraints say that all sub-classes of age of onset (Q4691924) are allowed as values, so any missing classes can be added. --Srittau (talk) 20:40, 16 May 2016 (UTC)

disease burden

   Done: disease burden (P2854) (Talk and documentation)
Descriptionimpact 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.
Representsdisease burden (Q5282120)
Data typeNumber (not available yet)
Template parameternot yet used but would be important with diseases and health risk factors
Domainevaluation of importance of diseases and public health policies
Allowed values-INF - INF with e.g. units disability-adjusted life year (Q23893342), disability-adjusted life year (Q23893342) or quality-adjusted life year (Q23893355)
Exampletuberculosis (Q12204) → 15 900 000 disability-adjusted life year (Q23893342); qualifier point in time (P585) 2013 location (P276) Earth (Q2)
Sourcegood external sources exist, e.g. http://vizhub.healthdata.org/gbd-compare/
Robot and gadget jobsnot yet available
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

  SupportMatleenat (talk) 07:36, 31 January 2016 (UTC)

  Notified participants of WikiProject Medicine Two property suggestions: incidence and disease burden.

I updated the example to show a unit of measurement for disease burden. --Jtuom (talk) 13:30, 20 April 2016 (UTC)

  Support -ArjaA (talk) 09:09, 17 May 2016 (UTC)

@Jtuom, Matleenat, ArjaA:  Done --Lymantria (talk) 05:52, 25 May 2016 (UTC)

Micro-organisms, by environmental specialisation

   Not done
DescriptionEnvironmental factors that influence growth
Data typeItem
Domaintaxon (Q16521) AND strain (Q855769)
Allowed valuesHypolith (Q4138781) OR Metallotolerant (Q2072873) OR oligotroph (Q45279) OR osmophile (Q739374) OR Polyextremophile (Q2985071) OR xerophile (Q980491) OR capnophile (Q2072863) OR Psammophile (Q2397508) OR lithophile (Q6648108) OR Methanogen (Q1169785) OR Thermoacidophile (Q2345861) OR Cryozoa (Q4208454) OR hyperthermophile (Q1784119) OR psychrophile (Q913343) OR thermophile (Q834023) OR Piezophile (Q808724) OR halophile (Q946633) OR alkaliphile (Q917110) OR acidophile (Q196188) OR obligate aerobe (Q7075150) OR obligate anaerobe (Q2915932) OR facultative anaerobic organism (Q1091848) OR microaerophile (Q548321) OR photoheterotroph (Q2473042) OR lithoautotroph (Q2075139) OR chemotroph (Q747472) OR mesophile (Q669652)
ExamplePseudomonas putida KT2440 (Q21079489) → mesophile (Q669652)
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourcehttps://en.wikipedia.org/wiki/Mesophile
Robot and gadget jobsWe are planning this to use in bots that add phenotypic characterisations
Motivation

This property indicates the growth range an organism can thrive in and is mostly used to characterise bacteria. For example mesophiles grow best in the range of 20-45 degrees celsius while acidophilus grow best under acidic conditions.

Discussion

  Notified participants of WikiProject Microbiology

  Comment Can we define a more general property to include all micro-organisms characteristics like Acidophile, Alkaliphile, Capnophile, Cryozoa, Endolith, Halophile, Hypolith, Lipophile, Lithoautotroph, Lithophile, Methanogen, Metallotolerant, Oligotroph, Osmophile, Piezophile, Polyextremophile, Psammophile, Psychrophile, Radioresistant, Thermophile / Hyperthermophile, Thermoacidophile, Xerophile ? ~Something like Micro-organisms metabolism. Snipre (talk) 12:05, 12 March 2016 (UTC)
  Comment In combination with the next property that is currently under proposal would something like: micro-organisms characteristics, be more suitable? This could contain acidic properties, oxygen properties and others...? --jjkoehorst (talk) 16:36, 12 March 2016 (UTC)
jjkoehorst I don't know, I am not an expert. So before creating some properties I recommand you to first try to define all characteristics of micro-organisms and to develop a whole system with one or several properties depending on the needs. We need a global overview before starting properties creation. Snipre (talk) 17:10, 12 March 2016 (UTC)
Snipre I'll contact some microbiologist experts to create a more complete overview at the university I work at and hopefully have an answer in a few days. --jjkoehorst (talk) 17:24, 12 March 2016 (UTC)
jjkoehorst If you have some contacts this can be a big help. If not you can take some reference books and have look at their classification or description of the micro-organism characteristics. Snipre (talk) 19:00, 12 March 2016 (UTC)
Snipre I have contacted some people and that did not yet came with new insights. Dusted of some old books and have created a 30+ list and still uncovering new terminologies but this creates a relatively clear picture. All topics are more or less related to pH, pressure, temperature, habitat (rocks), sunlight consumers. Thus maybe environmental type or habitat would be a more suitable terminologie for all of these terms? --jjkoehorst (talk) 06:57, 14 March 2016 (UTC)
jjkoehorst Thanks for your work. I propose you to start a section in the Wikidata: WikiProject Microbiology and to list the different parameters used to describe micro-organisms and to propose there some groups of values which will need a specific property. If you need more input (sorry I can't help you a lot because my knowledge is very deficient in that area) try to contact the project on WP:en (see en:Wikipedia:WikiProject_Microbiology). Snipre (talk) 09:44, 17 March 2016 (UTC)
Snipre I have been in contact with the other members of the microbiology group. We have identified good properties that can be used for the generic environmental growth factor property. This can then form the basis for the organisms and each item can be further annotated using other ontologies. --jjkoehorst (talk) 08:30, 24 March 2016 (UTC)
  Comment jjkoehorst I had the same issues as Snipre but I see you are already broadening the scope. I could get behind the two you proposed or even environmental growth factor. If I remember my microbiology correctly that's how it was used in Brock Biology of Microorganisms. Emitraka (talk) 14:35, 21 March 2016 (UTC)
  Comment User:Emitraka yes in this view it is wiser to have one property for as you called it environmental growth factor which I must say sounds pretty good instead of a fair amount of separate entities for acidity, oxygen, temperature etc. Within the items that are representing such factors we can describe them further. --jjkoehorst (talk) 21:31, 23 March 2016 (UTC)
  Support OK, good enough for me. - Brya (talk) 11:37, 24 March 2016 (UTC)
  Oppose because it's a case of classification that can be handled by generic typing properties instance of (P31) and subclass of (P279). For example we have
⟨ thermophile (Q834023)      ⟩ subclass of (P279)   ⟨ ornganism ⟩
is a subclass of organism because any instance of thermophile is an organisme. You'll just need a metaclass to mark thermophile (Q834023) as an environmental condition used to classify organisms, with something like
⟨ thermophile (Q834023)      ⟩ instance of (P31)   ⟨ class of organism whose growth is influenced by some environmental condition ⟩
and do the same for all of the values classes. Assuming
⟨ taxon ⟩ subclass of (P279)   ⟨ class of organisms ⟩
,
⟨ strain (Q855769)      ⟩ subclass of (P279)   ⟨ class of organisms ⟩
and
⟨ class of organisms ⟩ instance of (P31)   ⟨ class of organism influenced by some environmental condition ⟩
.
But I'd support a properties that can describe the kind of envrironments like "temperature inteval" for "extreme temperature environment". author  TomT0m / talk page 13:31, 24 March 2016 (UTC)
@TomT0m: Can you argument your opposition ? Just saying that the characteristics of some micro-organisms can be described using instance of (P31) is not enough especially when this is not a strict rule of Wikidata: we are using occupation (P106) to say that an human is a painter or a writer or an engineer, not instance of (P31). Snipre (talk) 22:48, 28 March 2016 (UTC)
@Snipre: I think I did. I did not just oppose, I gave an alternative modelling. It's not the first time I argue like this for a lot of reasons : consistency in using regular classification tools, preference for generic properties especially when the property proposal process is imho broken ... I also value parsimony to make the whole model both predictible and flexible. A few principles are better than a lot of endless discussion with not enough votes for the property proposers, especially if we can do without. What's important is to provide solutions anyway. That say in this case I could revise my judgement because we actually would need a better model for envirnometal factor and to describle classes like thermophilia, describe environments and so on. But this would need a more complete consistent proposition to actually have something worth discussing. author  TomT0m / talk page 11:21, 29 March 2016 (UTC)
Oh, one more thing : we also have has characteristic (P1552)   who could be relevant here. Extremophilia, a property of organisms, could be used to describle the extremophile class for example. We are well equiped in generic properties now. Let's discuss how to use it, not do one step in one direction, then one step in the over. author  TomT0m / talk page 11:26, 29 March 2016 (UTC)
@TomT0m: The issue with a generic property statement is that when querying the endpoints of wikidata it is not explicit enough to make clear what a statement indicates. Therefor I proposed this property to more explicitly state what is being described about such organism. I agree also that more in-depth information could be useful such as minimum, maximum, optimum which could indicate the exact range the organism can grow in. --jjkoehorst (talk) 16:05, 13 April 2016 (UTC)
@TomT0m: +1 with jjkoehorst. When we have several statements using instance of (P31) describing different characteristics like the taxon and the metabolism, how can we extract the wanted information ?
Example for organism Sulfolobus (Q1209791). If we use instance of (P31) to describe it as taxon (Q16521) (classification), heterotroph (Q159344) (metabolism), autotroph (Q131427) (metabolism), acidophile (Q196188) (environmental growth factor) and thermophile (Q834023) (environmental growth factor), how can we extract the information ? If we want to get only the environmental growth factors we have to perform a second query to define which are the elements describing the environmental growth factors and to combine both queries or to create a very complex query. Snipre (talk) 14:22, 22 April 2016 (UTC)
I agree with Snipre: sometimes, as espoused by TomT0m, using "instance of" is better than creating a new property. This is not the case here: using "instance of" here would be overuse, and would be confusing. - Brya (talk) 08:56, 23 April 2016 (UTC)
Mmh 
select ?taxon ?factor where { ?factor wdt:P31 "growth factor class" . ?taxon wdt:P279*/wdt:P31 wd:Q16521 ?taxon wdt:P279* ?factor . }
Try it!
(not functional, just a sketch atm) is far from being very complex and is not really confusing if we follow this scheme consistently. author  TomT0m / talk page 06:42, 25 April 2016 (UTC)
@Snipre: All of this "IS" classification. We just use different way to classify : by environment they are efficient by (growth factor), or by parenthood/organisms they can reproduce with (taxon) ... author  TomT0m / talk page
Well, I did not say that it could not be made to work, just that it is confusing. It is less confusing to create this proposed property and make it a subproperty of "instance of"/"subclass of". - Brya (talk) 10:38, 25 April 2016 (UTC)
What's confusing to me is to have a "growth factor", for what I'd expect a type of environment for subject, which actually have classes of organisms as subjects. "hot weather" would make sense as subject in a natural language sentence to me, "this organisms growth factor is hot weather", and not "this organism growth factor is organisms who like hot weather". author  TomT0m / talk page 16:33, 25 April 2016 (UTC)
Yes, I see what you mean. Perhaps "micro-organisms, by environmental specialization" would work better as title? - Brya (talk) 16:57, 25 April 2016 (UTC)
This would fit for the metaclass indeed. author  TomT0m / talk page 16:59, 26 April 2016 (UTC)
First of all, sorry for my slow replies, somehow the notifications are not coming across. I agree "micro-organisms, by environmental specialisation" is a good terminology. Shall I transform it to that title? --jjkoehorst (talk) 05:30, 29 April 2016 (UTC)
Yes, I was hoping to come up with something that was a little tighter (the items that can be excepted as values, all have a title that is an adjective, uses as a noun), but this does seem to cover it. - Brya (talk) 05:52, 29 April 2016 (UTC)
As can be seen the item has been updated --jjkoehorst (talk) 05:56, 29 April 2016 (UTC)
I am not particularly happy with the new property name. The property is not "micro-organisms" by specialisation, but the specialisation itself. Perhaps it is an idea to change into "specialisation of micro-organisms". Lymantria (talk) 06:42, 29 April 2016 (UTC)
Yes, but we are now getting close to three thousand properties, and in my view it helps a lot to start with a word that indicates in what ball-park the property belongs, so I quite like starting off with "Micro-organism ...". After all, we are getting by with a title like "taxonomic type", which gets the general idea across, although this actually is quite a misdescription (a type is nomenclatural in nature). - Brya (talk) 16:41, 29 April 2016 (UTC)
Well, Micro-organism specialisation then? Lymantria (talk) 17:12, 29 April 2016 (UTC)
Nice and compact, sounds good to me. --jjkoehorst (talk) 04:52, 30 April 2016 (UTC)
OK, although the spelling "specialization" with a "-z-" would be preferable. - Brya (talk) 07:46, 1 May 2016 (UTC)
@Lymantria, Brya, TomT0m, Jjkoehorst: These characteristics are not specific to micro-organisms so it is wrong to 1) defined a property only for micro-organisms, and 2) then to consider that halophile is a restricted class of micro-organism. You can have plants which are halophile or acidophile. So first we have to consider that halophile item is not a class of microorganisms but growth feature and as already metioned by Brya this term is an adjective and not a noun. The correct noun for halophile is halophily.
So we have to decide if we want to create two items, one describing class of micro-organisms and the second describing growth characteristics. Example: halophile (micro-organisms class) and halophile (growth characteristic of organisms like plant and micro-organisms). Snipre (talk) 09:48, 30 April 2016 (UTC)
Well, I pointed out that "halophile" is an adjective, used as a noun, so it is a noun (as well as an adjective). Other nouns are "halophily" and "halophyte". - Brya (talk) 10:28, 30 April 2016 (UTC)
(edit conflict)
Still not convinced this solves the issues I raised. There is still a confusion beetween the type of environment and the type of organisms who like the environment. "very hot environment" versus "individual animal who likes very hot environment" versus "species or strain (Q855769) who likes very hot environment". Also the domain of the property is specified by listing all the allowed values, it would be more flexible to have an item "type of environment", to mark
⟨ very hot environment ⟩ instance of (P31)   ⟨ type of environment ⟩
. The property then could be renamed "growth factor" back without any problem.
A more advanced stuff : we need to link classes like "hyperthermophile -" - a class of organisms to the class of environments "super hot environment" and the like (instances of "type of environment") - which could have some subclasses like hot spring (Q177380)      - just an idea with an item I could find quickly, probably incorrect in practice, maybe "super hot spring" would fit better - from which we could infer in the future framework of WikiProject Reasoning that, say, organisms who likes super hot springs are extremophiles. Then we would have
⟨ hyperthermophile ⟩ subclass of (P279)   ⟨ extremophile ⟩
. One way to link the environment to the class of organisms could (should?) be has characteristic (P1552)  , as any extremophile cell likes very hot environment. Say that we write this as
⟨ hyperthermophile (Q1784119)      ⟩ has quality Search unknown value Help
growth factor Search ⟨ very hot environment ⟩
. This would imply that any thermophile subclass has the same (class of) growth factor. A SPARQL query can easily sketch what can be done by the inference project soon and check the inconsistencies in what we decide to do with this. But this is worth to discuss an expressive framework, and we can do this just by trying to define things consistently ... author  TomT0m / talk page 09:59, 30 April 2016 (UTC)

  Not done - Lack of support, instance of (P31) can be used in stead. Lymantria (talk) 05:09, 25 May 2016 (UTC)

  Support I think this is a good idea. --Tobias1984 (talk) 14:17, 26 May 2016 (UTC)

OTRS ticket number

   Not done
DescriptionOTRS ticket number to identify data which was released under a special agreement
Data typeExternal identifier
Domainall
Allowed values20((0[0-9])|(1[0-6]))((0[1-9])|(1[0-2]))((0[1-9])|([1-2][0-9])|(3[0-1]))\d{8}
ExampleOnly used as qualifier or only used in reference section ?
Formatter URLhttps://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom&TicketNumber=$1
Robot and gadget jobs?
Motivation

To identify data provided after a special agreement with the author. We should have an external list in order to be able to correct any vandalism or bad modifications and perhaps a bot which periodically check the presence of the OTRS ticket number for claims delivered with a special agreement. Snipre (talk) 08:10, 18 March 2016 (UTC)

Discussion

@Snipre:   Not done, no support at this point. --Srittau (talk) 10:50, 13 May 2016 (UTC)

Leidse Hoogleraren ID

DescriptionIdentifier in the Leidse Hoogleraren, a catalogue of University Professors of Leiden University since 1575.
RepresentsLeidse Hoogleraren (Q23667505)
Data typeExternal identifier
Domainuniversity teacher (Q1622272) or lector (Q1553123) of Leiden University (Q156598)
Allowed values[1-9]\d*
ExampleHugo Krabbe (Q12989630) → 1441
Sourcehttp://hoogleraren.leidenuniv.nl/search
Formatter URLhttp://hoogleraren.leidenuniv.nl/id/$1
Motivation

Leidse Hoogleraren (Q23667505) contains at this moment 2458 (former) university professors of the Leiden University (Q156598), since 1575, with valuable information on each of them. Hence a useful source. Lymantria (talk) 09:44, 31 March 2016 (UTC)

Discussion

Catalogus Professorum Academiae Rheno-Traiectinae ID

DescriptionIdentifier for a Professor at Utrecht University
RepresentsCatalogus Professorum Academiae Rheno-Traiectinae (Q23825128)
Data typeExternal identifier
Domainuniversity teacher (Q1622272) of Utrecht University (Q221653)
Allowed values(\d+/){3}\d
ExampleC. H. D. Buys Ballot (Q441099) → 360/24/174/0
Sourcehttps://profs.library.uu.nl/index.php/browse_menu
Formatter URLhttps://profs.library.uu.nl/index.php/profrec/getprofdata/$1
Robot and gadget jobsAlready in Mix'n'Match 194.
Motivation

The database Catalogus Professorum Academiae Rheno-Traiectinae (Q23825128) contains the university professors of the Utrecht University (Q221653), since 1636, with information on employment, some academic history and personal data on each of them. Useful as Authority Control and source. --Lymantria (talk) 19:24, 15 April 2016 (UTC)

Discussion

Nederlandse Molendatabase ID

DescriptionIdentifier of mills in the Nederlandse Molendatabase, with records of all functioning mills, windmills and watermills, in the Netherlands.
Data typeExternal identifier
Template parameternl:Sjabloon:Infobox molen: "molendatabase-nl" - Template:Infobox windmill (Q13383928)
Domainmill (Q44494)
Allowed values[1-9]\d*
ExampleDe Hoop (Q2741671) → 928
Watermill at Kollen (Q2117023) → 516
Sourcehttp://www.molendatabase.nl/nederland/index.php
Formatter URLhttp://www.molendatabase.nl/nederland/molen.php?nummer=$1
Robot and gadget jobsCan be imported by "Harvest templates" gadget
Motivation

The Nederlandse Molendatabase (Dutch Milldatabase) contains a lot of interesting and detailed information on each functioning mill in the Netherlands. The majority of records is on the many windmills in this country. Used in nlwiki infobox, but also e.g. in enwiki. Lymantria (talk) 08:36, 21 April 2016 (UTC)

Discussion

Hollandsche Molen ID

DescriptionIdentifier of mills in by "Vereniging de Hollandsche Molen", an organization that focusses on preservation of wind- and watermilles in the Netherlands.
Data typeExternal identifier
Template parameternl:Sjabloon:Infobox molen: "molendatabase-Hollandsche Molen" - Template:Infobox windmill (Q13383928)
Domainmill (Q44494)
Allowed values[1-9]\d*
ExampleDe Oude molen (Q5513402) → 1147
Watermolen van Staverden (Q14517905) → 403
Sourcehttp://www.molens.nl/
Formatter URLhttp://www.molens.nl/nl/molen/zoek-een-molen/zoekresultaten-molenbestand/molendetail/?molenid=$1
Robot and gadget jobsCan be imported by "Harvest templates" gadget
Motivation

The database by Hollandsche Molen contains a lot of interesting and detailed information on wind- and watermills in the Netherlands. Used in nlwiki infobox, but also e.g. in enwiki. Lymantria (talk) 08:36, 21 April 2016 (UTC)

Discussion

Molenecho's ID

   Done: Molenecho's ID (P2867) (Talk and documentation)
DescriptionIdentifier of mills in Molenecho's, a database on windmills and watermills in Belgium.
Data typeExternal identifier
Template parameternl:Sjabloon:Infobox molen: "molendatabase-be" - Template:Infobox windmill (Q13383928)
Domainmill (Q44494)
Allowed values[1-9]\d*
Example
Sourcehttp://www.molenechos.org/indexdb.php
Formatter URLhttp://www.molenechos.org/molen.php?AdvSearch=$1
Robot and gadget jobsCan be imported by "Harvest templates" gadget
Motivation

The database Molenecho's contains a lot of interesting and detailed information on wind- and watermills in Belgium. Used in nlwiki in infobox, but also e.g. in frwiki. Lymantria (talk) 08:36, 21 April 2016 (UTC)

Discussion

OpenCritic ID

   Done: OpenCritic ID (P2864) (Talk and documentation)
Descriptionidentifier in OpenCritic
RepresentsOpenCritic (Q21039459)
Data typeExternal identifier
DomainQ7889
Allowed values[0-9]*\/[\w,-]*
ExampleTitanfall (Q13473778) → 857/titanfall
Sourcehttp://opencritic.com
Formatter URLhttp://opencritic.com/game/$1
Motivation

Similar to Metacritic ID (P1712), this property would hold scores from another video game score aggregator, OpenCritic (Q21039459). We're starting to convert our video game reviews templates at enwp to pull from Wikidata, so it would be nice to start incorporating our other aggregators too. czar 04:13, 23 April 2016 (UTC)

Discussion
  •   Oppose - This site is very new and unproven in the industry. It also has no api yet, and en:Template:Video game reviews doesn't have any parameters to import ID numbers. w:Special:WhatLinksHere/OpenCritic only has about 30 links, so the encyclopedia isn't even using these reviews. Seems like this would result in a ton of manual work right now, to support a very new website with limited value. Let's revisit it (way) in the future. --Netoholic (talk) 11:04, 23 April 2016 (UTC)
    • Hi, I'm one of the major contributors at enwp's video games WikiProject and one of the biggest proponents against implementing OpenCritic in our templates (for now), so perhaps that can help explain why enwp doesn't have many links to it. The point isn't to use their aggregate scores in enwp's templates alone, but other language Wikipedias (such as ptwp, anecdotally) use OpenCritic. We're hoping to work with them so they can provide aggregate scores of games that predate Metacritic/GameRankings/current aggregators. Also their API is in alpha. czar 15:51, 24 April 2016 (UTC)
      • I think there's an important separation that needs to happen. I don't think wikimedia projects should "work with them". Its not our job to help promote or improve an external service. We should wait until society at-large has adopted a service, and published sufficient third-party independent reviews of its reliability, before we incorporate it. -- Netoholic (talk) 03:20, 25 April 2016 (UTC)
        • No one is helping them promote or improve their service. Metacritic is the industry standard but OpenCritic is used by enough sources to warrant tracking its metadata. czar 00:48, 27 April 2016 (UTC)
  •   Support. None of the arguments above (objecting to use in Wikipedia, or the presence of an API) mitigate against us having a property here. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:35, 27 April 2016 (UTC)
    Do we have no standards for inclusion here? Could I create a web service called "Netoholic's Index of Awesome" and then get a property created here in order to help legitimize and publicize my service? -- Netoholic (talk) 05:02, 29 April 2016 (UTC)
    Does such an index actually exist? :) We judge each property on its merit. --Izno (talk) 11:25, 24 May 2016 (UTC)

@Czar, Pigsonthewing:  Done Sufficient support for, now OpenCritic ID (P2864) -- Lymantria (talk) 05:39, 27 May 2016 (UTC)

Internet Wrestling Database person id

Descriptionidentifier for a professional wrestling performer at the Internet Wrestling Database
Data typeExternal identifier
Domainhuman
ExampleJohn Cena (Q44437) → john-cena-350
Sourcewww.profightdb.com
Formatter URLhttp://www.profightdb.com/wrestlers/$1.html
Robot and gadget jobsWe could possibly scrape wikipedias, but there don't seem to be templates for this.
Motivation

Internet Wrestling Database is a database of professional wrestlers and matches/events. They claim to have a full list of results for a large number of wrestling promotions (see the FAQ). Silverfish (talk) 12:27, 3 May 2016 (UTC)

Discussion
@Silverfish, Edgars2007:  Done --Lymantria (talk) 05:31, 11 May 2016 (UTC)

Online World of Wrestling id

Descriptionidentifier for a professional wrestling performer or tag team at Online World of Wrestling
Data typeExternal identifier
Domainhuman (Q5) or tag team (Q1066670)
ExampleTitus O'Neil (Q196166) → t/titus-oneil, The Prime Time Players (Q800099) -> p/prime-time-players
Sourcehttp://www.onlineworldofwrestling.com/
Formatter URLhttp://www.onlineworldofwrestling.com/bios/$1
Robot and gadget jobsWe may be able to dscrape wikipedias, but I am not aware of any templates for this.
Motivation

Online World of Wrestling is a website about professional wrestling that has profiles on a number of wrestlers and tag teams. I don't think we should have separate identifiers for performers and tag teams, as I think it would cause confusion, as they have the same url prefix. Silverfish (talk) 14:24, 3 May 2016 (UTC)

Discussion

@Silverfish, Edgars2007:  Done --Lymantria (talk) 05:50, 11 May 2016 (UTC)

Benezit

   Done: Benezit ID (P2843) (Talk and documentation)
Descriptionfrench dictionary of artists
RepresentsBenezit Dictionary of Artists (Q2929945)
Data typeExternal identifier
Domainhuman
Allowed valuesstring pattern
ExampleMartinus Lengele (Q16915458) → B00107631
Sourcehttp://oxfordindex.oup.com/view/10.1093/benz/9780199773787.article.B00107631
Formatter URLhttp://oxfordindex.oup.com/view/10.1093/benz/9780199773787.article.$1
Robot and gadget jobshttps://tools.wmflabs.org/mix-n-match/?mode=catalog_details&catalog=143
Motivation

There are already over 8,000 matches with this identifier to artist biographies on enwiki and over 6,000 to artist biographies on frwiki. It would be nice to have this property and also include it in the enwiki authority control template. Jane023 (talk) 08:25, 8 May 2016 (UTC)

Discussion
  •   Support. --Edgars2007 (talk) 15:56, 9 May 2016 (UTC)
  •   Support. It's already in Mix'n'Match so we can quickly fill this property. Spinster (💬) 06:04, 10 May 2016 (UTC)
  • Support, even though full access requires subscription. Thas said, Benezit has had several editions in several languages. I am not totally sure wether the id links to a) the text of the 2006, English-language edition only - or b) a semi-independent resource that can be updated at any time, even without a new printed edition. I looks like it is a). If so the name should be something like "Benezit 2006 online id", for precision's sake. --Zolo (talk) 08:42, 10 May 2016 (UTC)
    • I think it is the other way around; if someone quotes Benezit 1911 for whatever reason (maybe because it got deleted from the modern version), then that one should be Benezit 1911. Saying 2006 just sounds dated. Jane023 (talk) 10:25, 10 May 2016 (UTC)
      • And in a way it is dated. Unlike ULAN and RKD, Bénézit, does not try to keep the data up to date, they just keep the text of the 2006 version until they get a new, wholly updated version. I think it makes sense to tell readers that we link to one version of a static resource rather than to a continuously updated online database. Anyhow, it is just a label, that does not make much difference. --Zolo (talk) 11:39, 10 May 2016 (UTC)
        • Well I suppose it would be nice to have the pubic domain 1911 version even if it's only available in French. Do you know if there is a copy online anywhere? Not sure if this is the place to post that link though. Jane023 (talk) 12:01, 12 May 2016 (UTC)
          • I can't find any online copy of the 1911 version. If there is one, it is probably just a raw copy of the text, and as such would not identify artists through individual ids, and so would not really be fit for an authorit control property. --Zolo (talk) 09:20, 13 May 2016 (UTC)
            • Thanks for looking! It would be nice to link to such a text-based resource from the item. Theoretically it could be done, as the document is in the Public Domain. Sometimes, as I am sure you have noticed, the artist entries in Bénézit reference other artists as teachers or pupils, so being able to run a full text search would be great. Jane023 (talk) 11:02, 16 May 2016 (UTC)
  •   Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:00, 16 May 2016 (UTC)
  •   Support. The Oxford Art Online Website adverises: Nearly 170,000 entries on artists from the first English edition (2006), plus revisions and new biographies exclusively available nline. So labelling the property as Benezit Dictionary of Artists in all languages should make halfway clear what it is about... -- Gymel (talk) 06:19, 18 May 2016 (UTC)

@Jane023, Edgars2007, Spinster, Zolo, Pigsonthewing, Gymel:  Done --Lymantria (talk) 06:57, 18 May 2016 (UTC)

EU Surface Water Body Code

DescriptionUnique EU identifier for a surface water body
Data typeExternal identifier
Domainlakes/watercourses etc.
ExampleOrlången (Q3424558) → SE656833-162888
Format and edit filter validation3-42 characters with the first two being the Member State's 2-alpha character ISO code (format for the rest of the string varies between countries)
Source[6]
Formatter URLhttp://dd.eionet.europa.eu/vocabularyconcept/wise/WaterBody/euSurfaceWaterBodyCode.$1
Motivation

This are the identifiers used by each country in their reporting to the EU in accordance with the Water Framework Directive (Q1508115). As such it is the key to loads of data about these bodies of water. André Costa (WMSE) (talk) 11:29, 9 May 2016 (UTC)

Discussion

For Sweden a Property has already been created for this (Lake ID (Sweden) (P761)). It is however limited to Sweden since the "SE" bit of the identifier has been omitted. Rather than creating one such identifier per country (out of the ones which follow this scheme) I suggest extending Lake ID (Sweden) (P761) or (to not risk breaking links) creating a new property and deprecating the old one.

For transparency/clarity this was discussed in passing during the creation of P761 (the referenced discussion is this one) but the difference here is that all of thes identifiers are connected through the EU reporting framework (the Russian one isn't). /André Costa (WMSE) (talk) 11:29, 9 May 2016 (UTC)

Another reason for having a joint property for this is that some water bodies spanning two countries might keep the same code across the boundary. E.g. a stream on the border of Sweden and Norway might have the NO prefix in both countries (e.g. [7]/[8]). /André Costa (WMSE) (talk) 12:39, 9 May 2016 (UTC)
  Support IMHO this means that Lake ID (Sweden) (P761) can be removed and this one comes in its place. Lymantria (talk) 16:56, 17 May 2016 (UTC)

@André Costa (WMSE):  Done EU Surface Water Body Code (P2856) -- Lymantria (talk) 07:03, 26 May 2016 (UTC)

RAN-ID

   Done: RAN ID (P2845) (Talk and documentation)
DescriptionNumber in National archaeological register (Q12739297)
RepresentsNational archaeological register (Q12739297)
Data typeExternal identifier
Template parameterro:Template:Infocaseta Davă ref:RO:RAN
Domaininstance of historic monument (Q916620)
Allowed values\d+\.\d+
ExampleBănița Fortress (Q618020) → 87255.07
Sourcesee ro:Repertoriul Arheologic Național
Formatter URLhttp://ran.cimec.ro/sel.asp?codran=$1
Robot and gadget jobsimport by Kasparbot from rowiki
Motivation

official register for archeological sites in Romania T.seppelt (talk) 19:35, 11 May 2016 (UTC)

Discussion

@T.seppelt, Strakhov, Pigsonthewing:  Done --Lymantria (talk) 05:30, 20 May 2016 (UTC)

WWE.com superstar id

Descriptionidentifier for a professional wrestling performer or tag team at WWE.com
Data typeExternal identifier
Template parameter1 or |id= in en:Template:wwe superstar and possibly equivalent templates in other language wikis
Domainhuman or tag team
Example
SourceWWE.com/superstars
Formatter URLhttp://www.wwe.com/superstars/$1
Robot and gadget jobsbots could import from templates
Motivation

WWE.com has profiles on current and former WWE wrestlers and other performers (managers, announcers, etc), and former WCW and ECW alumni (as they own WCW and ECW). I've included diva/ as part of the identifier, as there seems to be only a few wrestlers who need it as part of their link, so it seems better to lump them in here, rather than having a separate property. WWE have recently abandoned the term Diva for their female performers, so I assume they will eventually just use the same link for all of them. [9] is one example where the divas link now redirects to the version without it. en:template:WWE diva is used on enwiki to link to those that remain. [10] is an isolated example, as wwealumni is included in the the official link, but the link works without, so I don't think we need to include that part of the identifier. I think we should include tag teams as they use the same link formats for both. It seems this could be suitable for mix and match, as you could scrape the page for links, and then remove those few with unusual formatting. Silverfish (talk) 23:13, 13 May 2016 (UTC)

Discussion

@Silverfish, Pigsonthewing:  DoneWWE.com superstar ID (P2857) -- Lymantria (talk) 07:14, 26 May 2016 (UTC)

KLOV ID

DescriptionKLOV game identifier
Data typeExternal identifier
Allowed values\d+
ExamplePac-Man (Q173626) → 10816
Sourcew:Template:KLOV game
Formatter URLhttp://www.arcade-museum.com/game_detail.php?game_id=$1
Motivation

Online website devoted to cataloging arcade video games. The Wikipedia template already links to 972 of the 4,650 machines in the database. Dispenser (talk) 23:13, 15 May 2016 (UTC)

Discussion

@Dispenser, Pigsonthewing:  DoneKiller List of Videogames ID (P2858) --Lymantria (talk) 07:26, 26 May 2016 (UTC)

BCN ID

Descriptionidentifier of a work, in the National Library of Argentine Congress
RepresentsLibrary of the National Congress of Argentina (Q5408662)
Data typeExternal identifier
Domainbook (Q571)
Allowed values\d+ (sorry, not sure)
ExampleCuentos... (Q24008412) → 91567
Sourcehttp://consulta.bcn.gob.ar/bcn/Catalogo.Buscar
Formatter URLhttp://consulta.bcn.gob.ar/bcn/catalogo.verRegistro?co=$1
Robot and gadget jobsDon"t think so, but maybe.
Motivation

One of the most important (and second in volume of books) libraries of Argentina.

We are working on the digitalization of XIX and XX century books with many institutions on Argentina (throught Wikimedia Argentina). We already have the "BN (Argentina) (P1143)" and would be nice to have another local control authority. Mauricio V. Genta (talk) 04:58, 18 May 2016 (UTC)

Discussion
  Comment From a library perspective there are the descriptions of "books" (concrete editions, sometimes in more than one exemplar) at the one hand, and "Authority Control" at the other. 19th and 20th century are quite recent past, so it is to be expected that more than one library will have holdings for it and that Wikidata will have to represent the work in the first place. Denoting specific editions becomes important when it comes to presenting a complete edition history or describing a digitization (which may yield to a trancscription project on Wikisource). At that stage also specific library holdings as expressed by your proposal become important since they can answer the question "Which exemplar has been digitizied?". Main use would be as a qualifier (a BN control number and a simultaneous BNC control number "directly" on the item would leave some ambiguity) but the main question is, whether some more generic property allowing reference to holdings in any (Argentinian ?) library would better suit your project than having several distinct properties with only a handful of usages each. -- Gymel (talk) 06:12, 18 May 2016 (UTC)
Thanks for the comment! The idea is to have two options (not use both of them), BN and BCN are both "national library's" and they don't really have everything in the online catalog. Indeed, both of them are a poor in quality compared to other nationals librarys. We are working to have them en Commons, Wikisource and wikidata (soon we are going to do a contest to promote it) for the end of june i expect to have at least the 120 books from our letter academy with their entry in wikidata. --Mauricio V. Genta (talk) 21:54, 18 May 2016 (UTC)
  Comment @Mauricio V. Genta: It would be helpful if you could provide English labels for Library of the National Congress of Argentina (Q5408662) and Cuentos... (Q24008412), please. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:59, 20 May 2016 (UTC)
Done.--Mauricio V. Genta (talk) 17:48, 20 May 2016 (UTC)
BCNA ID, maybe? thats the acronym in spanish including "Argentina" --Mauricio V. Genta (talk) 18:37, 27 May 2016 (UTC)
"BCN ID" and "BCNA ID" are probably best as aliases rather than the label for ease of non-specialist understanding. Thryduulf (talk: local | en.wp | en.wikt) 20:28, 27 May 2016 (UTC)

@Mauricio V. Genta, Pigsonthewing, ArthurPSmith, Thryduulf:  Done Now Library of the National Congress of Argentina ID (P2879) --Lymantria (talk) 10:45, 30 May 2016 (UTC)

mains voltage

   Done: mains voltage (P2884) (Talk and documentation)
Descriptionvoltage of residential mains electricity in a country or region
Representsmains electricity (Q387400)
Data typeNumber (not available yet)
Template parameterelectricity in voy:Template:Quickbar, Elektricitet in voy:sv:Mall:QuickbarCountry, possibly others in Template:Infobox country (Q14395495)
Domaincountries, sub-national regions
Allowed valuesnumbers with the unit volt (Q25250) and frequency (P2144) as a mandatory qualifier
Example
⟨ Japan ⟩ mains voltage (P2884)   ⟨  100 volt ⟩
frequency (P2144)   ⟨  50 hz ⟩

⟨ United Kingdom ⟩ mains voltage (P2884)   ⟨  230 volt ⟩
frequency (P2144)   ⟨  50 hz ⟩
Sourcew:Mains_electricity_by_country
Robot and gadget jobsimport from Wikipedia or Wikivoyage
Motivation

A similar proposal by Jura1 (see Wikidata:Property proposal/Archive/51#mains voltage/frequency) was unilatterally withdrawn despite getting large support. This is a restatement of the alternative proposal (using number with a mandatory qualifier rather than the originally proposed item datatype with combined voltage and frequency items) made by Nikki during that discussion. Thryduulf (talk: local | en.wp | en.wikt) 10:22, 25 May 2016 (UTC)

Discussion
  •   Support this approach for the reasons I gave on the original proposal. - Nikki (talk) 10:23, 25 May 2016 (UTC)
  • Pinging other people who commented on the previous proposal: @Pigsonthewing, K7L, Srittau, The Anome, Lymantria, T.seppelt: Thryduulf (talk: local | en.wp | en.wikt) 10:25, 25 May 2016 (UTC)
  •   Comment Well, the withdrawn proposal with item-datatype had some advantages. It looked far more generic to me. I have in my home a "400/230 V/50 Hz three-phase electric power (Q471846)". That looks simplier to describe with an item-datatype. And adding frequency (P2144) as mandatory qualifier to a direct current-system is not a good idea at all. That is maybe not standard anywhere today, but it used to be in the early days. -- Innocent bystander (talk) 10:39, 25 May 2016 (UTC)
  •   Support The mandatory frequency qualifier should not be a problem for DC systems: the frequency can simply be set to zero, which acts as an explicit indication that it's DC. -- The Anome (talk) 12:00, 25 May 2016 (UTC)
    RE:The Anome An electric current can have a non-zero frequency and being DC at the same time. But I have never heard of a power supply with such a behaviour, so it is probably a non-existing problem. But I would prefer to set frequency to novalue rather than setting it to 0 in those cases. -- Innocent bystander (talk) 14:09, 25 May 2016 (UTC)
    • While one could create pulsating DC with some fixed frequency, for instance pulse-width modulation (Q585184), it would make no sense to use this as the basis for a system of mains distribution, as each of those individual pulses would come with an infinite number of odd harmonics - an insurmountable interference problem. Zero as frequency is DC, novalue suggests that it could be AC but we have no idea what frequency. K7L (talk) 15:29, 25 May 2016 (UTC)
      • I think "frequency: 0" probably meets the w:principle of least astonishment here. At least it does for me. -- The Anome (talk) 15:59, 25 May 2016 (UTC)
        • RE:K7L. Pulsing DC is much more common than you may see, but the frequency in those cases are not very important. Regarding "AC but we have no idea what frequency" does not sound like frequency=novalue but rather as frequency=somevalue to me.
        • To make this usefull also outside of voy:, I would like to see some solution that tells if there is a three-phase electric power (Q471846) or not, and which voltage it has. (The connection 400/230 is simple math, but could still be good to add anyway.) Maybe as an optional qualifier? -- Innocent bystander (talk) 18:04, 25 May 2016 (UTC)
          • Is having more than single phase residentially the norm anywhere? If it is we could have a property indicating the number of phases used as standard (item I guess) with voltage and frequency qualifiers of that. In the UK three phase, different voltages, etc. are not uncommon but only in specialist applications (e.g. industrial, theatrical, etc) and almost never residentially. Indicating the availability of that would be a properties on the scale ofbuildings or industrial estates rather than countries or top level country subdivisions. Thryduulf (talk: local | en.wp | en.wikt) 19:55, 25 May 2016 (UTC)
            • RE:Thryduulf: It is standard here in Sweden to have 3-phase to the kitchen stove (Q182995). There exists of course single phase versions, but you then have much less to choose from. And it is also common for people to have 3 phase in the garage and in the hobby-room for your compressor (Q178898). This is not the kind of information that is very useful for Wikivoyage of course, but I am definitly not talking about industrial applications. In industrial applications you can have almost anything you like, as long as you are prepared to pay for it. An Aluminium industry I worked for had their own power suppy directly feeded from the Nuclear plant. -- Innocent bystander (talk) 05:51, 26 May 2016 (UTC)
              • I'm not saying that pulsating DC isn't common, I'm saying that its distribution as mains electricity (and not merely inside some shielded piece of equipment) is not feasible due to massive radio frequency problems which would render it illegal under Title 47 CFR Part 15 (Q7810092)-like regulations in most jurisdictions. If you want to feed DC pulses to your motorcar's spark plug coils, go ahead, although even there one must take measures to suppress the noise lest it wipe out mediumwave AM on the vehicle's own radio. As for three phase? Wikivoyage is mostly interested in power for portable devices which would fit into travel baggage; it's amusing to tell American visitors to Canada that they'll need to bring a huge three-phase stepdown transformer to run their 480V devices from our 600V mains, but if the devices in question are factory machinery they're not going to fit in the carry-on bag so it's a waste of time. It's great that the 40 gallon 230-volt don't particularly care what frequency electric water heater will work anywhere worldwide but, if it (or this, or your aluminium factory) doesn't fit in the suitcase, Wikivoyage really doesn't care about it. K7L (talk) 14:04, 26 May 2016 (UTC)
                • @K7L: What I said above is that I would like to see this valuable property usable also outside of Wikivoyage. As the proposal looks now, it is probably ready to be used at Wikivoyage, but it would be nice to be able to add it also to other things. If you do not encourage time travel on Wikivoyage, DC-power supply is probably never an option, but it was common in the early years. (And, yes, it is/was in general a bad idea by several reasons.) Observe that any building from the 1980's in Sweden can have other sorts of sockets in the bathrooms which gives you 110 V. And schools and experimental labs often have special sorts of power supply, that is less fatal if you stick your fingers in the socket. So I would like to see an option to add this to hotels and other buildings. -- Innocent bystander (talk) 16:49, 28 May 2016 (UTC)
  •   Support good approach for making Wikivoyage data more structured. --T.seppelt (talk) 13:33, 25 May 2016 (UTC)
  • @Jura1, Thryduulf, Nikki, The Anome, K7L, T.seppelt:   Done as mains voltage (P2884) -- Innocent bystander (talk) 06:59, 2 June 2016 (UTC)

Google+

   Done: Google+ ID (P2847) (Talk and documentation)
Data typeExternal identifier
Domainpeople, organizations, other
Allowed values\d{22}|\+[-\w_\u00C0-\u00FF]+ (64-bit int base10 encoded and vanity URL)
ExampleUbuntu (Q381) -> +Ubuntu
Michael Bloomberg (Q607) -> 10055787708941310856
Mitt Romney (Q4496) -> +MittRomney
see User:Nikki/P553#Google+ for current uses
For Wikivoyage:
⟨ Komische Oper Berlin (Q687694)      ⟩ googleplus Search ⟨ 102309912006062068078 ⟩
in de:Berlin would point to https://plus.google.com/102309912006062068078/
Sourcewebsite account on (P553) statements
Formatter URLhttps://plus.google.com/$1
Proposed byJura 09:51, 15 April 2016 (UTC)
Discussion
  •   Question @Jura1: How will this data be imported? Give properties that could be filled in using this external resource. Why are both a numerical ID (used by Google APIs) and the vanity URL allowed values? Considering most of its users were coerced into creating an account and subsequently forgot, how can we be assured the information is meant to be public? Dispenser (talk) 20:04, 15 April 2016 (UTC)
  •   Oppose No example; conflicting allowed values. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 18 April 2016 (UTC)
    •   Support Both number ID as well as strings like +Ubuntu are valid identifiers, so I don't see conflicting allowed values. All allowed values point to Google plus pages via the formatter URL.

@Jura1, K7L:   Done, points by Andy have been addressed. --Srittau (talk) 16:12, 21 May 2016 (UTC)

see also element (was see also)

   Not done
Descriptionuse more specific property if possible
Data typeItem
Examplepatron of the arts (Q15472169) → art patronage (Q214092)
alternative medicine (Q188504) → traditional medicine (Q771035)
Motivation

Customary last resort internal link tool. -- Abc82 (talk) 12:12, 1 May 2016 (UTC)

Discussion

A few years ago this proposal was not supported in Wikidata:Wiktionary project context, discussion did not take place. -- Abc82 (talk) 12:12, 1 May 2016 (UTC)

@Abc82:   Not done, no consensus (unfortunately). --Srittau (talk) 22:04, 17 May 2016 (UTC)

X-Sampa Code

   Done: X-SAMPA code (P2859) (Talk and documentation)
DescriptionX-Sampa Code for the phoneme
RepresentsX-SAMPA (Q614484)
Data typeString
Domainphoneme
Examplenear-open front unrounded vowel (Q740768) → {
voiceless palato-alveolar affricate (Q518603) → tS

Wikipedia pages such as en:Near-open front unrounded vowel list the property X-Sampa for all phonemes.

It would be great to also have that data in Wikidata. ChristianKl (talk) 15:23, 9 May 2016 (UTC)

Discussion

  Comment Could you give some more examples? NMaia (talk) 15:56, 19 May 2016 (UTC)

I added another example. In general phomenes with an IPA transcription also have an X-Sampa code. X-SAMPA provides a good list.ChristianKl (talk) 18:29, 20 May 2016 (UTC)
  Support NMaia (talk) 20:18, 20 May 2016 (UTC)

@ChristianKl, NMaia:  Done X-SAMPA code (P2859) -- Lymantria (talk) 08:39, 26 May 2016 (UTC)

document file

   Withdrawn
Descriptioncorresponding file for the item
RepresentsCategory:Office document file formats (Q9888493)
Data typeCommons media file
Domainworks
Allowed valuesWikimedia Commons files
ExamplePlena Manlibro de Esperanta Gramatiko (Q3906638) → File:PMEG 15.0 provizora PDF 17 Junio 2013.pdf
Motivation

We have most other Commons media types, but this one in particular will be useful for Wikibooks and Wikisource editors, chiefly. With this, one can unite an item about a work to the actual work itself. NMaia (talk) 03:38, 20 May 2016 (UTC)

Discussion

  Comment Nevermind, I just realized document file on Wikimedia Commons (P996) exists. Please disregard this proposal. NMaia (talk) 03:44, 20 May 2016 (UTC)

mouthpiece

DescriptionMedia that speaks for an organization, and that is usually edited by its members
Data typeItem
DomainSubclasses of organization (Q43229)
Allowed valuesSubclasses of media (Q340169)
Example
Motivation

This would document the relation between an organization and the media that speak on its behalf. Thierry Caro (talk) 10:57, 30 March 2016 (UTC)

Discussion

@Thierry Caro:   Done --Srittau (talk) 21:46, 5 May 2016 (UTC)

Corporate officer

DescriptionFor identifying corporate officers whose offices do not have their own properties, such as chief financial officer (Q623268), chief technology officer (Q5287861), chief marketing officer (Q1072339), chief information officer (Q2589465), and others. The specific office should be specified with qualifier position held (P39) or P794 (P794).
Data typeItem
Domaincompanies
Allowed valuespeople
ExampleESPN (Q217776) → Chuck Pagano (Q5115650) with qualifier position held (P39)chief technology officer (Q5287861)
Motivation

This property will allow the identification of specific corporate officers by their titles, without the need to create separate properties for each title. Of course, more sub-properties like chief executive officer (P169) can be made for common titles, but this property will allow for a way around that. Swpb (talk) 18:04, 31 March 2016 (UTC)

Discussion

@Swpb, Srittau:  Done --Lymantria (talk) 19:06, 9 May 2016 (UTC)

P-number

   Done: P-number (P2814) (Talk and documentation)
DescriptionP-number identifier from the Danish company register. It indicates a physical site linked to an organization.
Data typeExternal identifier
Template parameterProbably none yet
Domainbusiness (Q4830453) and related domains
Allowed values\d+ perhaps \d{10}
ExampleDistrict Court of Lyngby (Q12333322) -> 1003389328
Sourcehttps://datacvr.virk.dk/data/?language=en-gb&
Formatter URLhttps://datacvr.virk.dk/data/visenhed?enhedstype=produktionsenhed&id=$1
Robot and gadget jobsProbably not
Motivation

Wikidata already has a CVR number property, CVR number (P1059). This refers to a Danish organization/company/public institution. Such an organization may operate from multiple locations. The P-number is an identifier for these locations. — Finn Årup Nielsen (fnielsen) (talk) 22:11, 6 April 2016 (UTC)

Discussion

@Fnielsen:   Done --Srittau (talk) 22:08, 5 May 2016 (UTC)

deputy head of state

   Not done
Descriptionpolitical position in some systems
Representsvice president (Q42178)
Data typeItem
Domaincountries
ExampleBrazil (Q155) → Michel Temer (Q463533)
Motivation

Very useful for adding the vice president to a country item, just like the president. --AmaryllisGardener talk 02:06, 19 April 2016 (UTC)

Discussion

@AmaryllisGardener:   Not done: no consensus. For now use position held (P39). If we have a lots of such statements at some point, it might be worth reconsidering. --Srittau (talk) 22:14, 5 May 2016 (UTC)

Band Number

   Done: band number (P2865) (Talk and documentation)
DescriptionID of the Canadian First Nation
Data typeExternal identifier
Template parameter"numéro" in fr:Modèle:Infobox Bande indienne
DomainFirst Nation band (Q2882257)
Allowed values/d+
ExampleBeaver First Nation (Q4878079) -> 445
Formatter URLhttp://pse5-esd5.ainc-inac.gc.ca/fnp/Main/Search/FNMain.aspx?BAND_NUMBER=$1

The Canadian First Nations (Indian bands) are all identified by an official name and a number. It would be good to have a property to add this number to Wikidata. For example Q4878079 for the Beaver First Nation has the number 445 as we can see on the page for this band on the Aboriginal Affairs and Northern Development Canada's website.

(This is my first request for property on Wikidata, so I'm not sure if I gave all the required information or not) Amqui (talk) 21:35, 14 May 2016 (UTC)

Discussion
  1.   Support Seem usefull. --Fralambert (talk) 23:53, 14 May 2016 (UTC)
  2.   Support. Rational identifier. Benoit Rochon (talk) 20:42, 15 May 2016 (UTC)
  3.   Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 16 May 2016 (UTC)
  4.   Support As the one proposing it. Amqui (talk) 21:09, 25 May 2016 (UTC)
  5.   Support seems both useful and well structured. Marking as ready. Thryduulf (talk: local | en.wp | en.wikt) 21:20, 25 May 2016 (UTC)

@Amqui, Fralambert, Benoit Rochon, Pigsonthewing, Thryduulf:  Done band number (P2865) -- Lymantria (talk) 09:23, 27 May 2016 (UTC)

Thanks, Amqui (talk) 16:18, 27 May 2016 (UTC)

Category for stubs

   Not done
Descriptioncatégorie de Wikipédia contenant seulement les ébauches de la catégorie en cours (fr) – (Please translate this into English.)
RepresentsCategory:Stub categories (Q7046062)
Data typeItem
DomainItems about categories
Allowed valuesItems about subcategories of Category:Stub categories (Q7046062)
Example
Motivation

We need this property to link Wikipedia categories and the equivalent stub categories. Thierry Caro (talk) 12:35, 14 May 2016 (UTC)

Discussion
Is this really required? What will it be used for? We already link to a subject's main category, and I expect the stubs category to be a sub-cat of that. --Srittau (talk) 13:33, 14 May 2016 (UTC)
Yes. It is useful, for example for queries when you want to exclude stubs or, on the contrary, work on them exclusively. We may know that it is a often subcategory, but it's not always the case, at least on the French Wikipedia, where sometimes it is in the main category and sometimes not. Plus we don't know which one of the subcategories it is precisely. Thierry Caro (talk) 13:39, 14 May 2016 (UTC)

@Thierry Caro:   Not done Lack of support. Lymantria (talk) 06:20, 2 June 2016 (UTC)

tourist office

   Done: visitor center (P2872) (Talk and documentation)
Descriptionofficial tourist office of this area/region/country
Data typeItem
Template parametervoy:fr:Modèle:Info Ville includes various fields about the tourist office. This can be added as property to imte
Domaingeographic location
Allowed valuesitems for tourist offices
ExampleAustria > Austrian National Tourist Office (Q298700)
Robot and gadget jobsimport from Wikivoyage

@Jura1, T.seppelt, Srittau, Thierry Caro, K7L:   Done visitor center (P2872) --Lymantria (talk) 16:25, 28 May 2016 (UTC)


map zoom level

   Not done
DescriptionZoom level to control display of on-page maps
Data typeNumber (not available yet)
Template parameterzoom
Domaingeographic places, itineraries and travel topics which already have coordinate location (P625)
Allowed valuesnumber 1-18 where 1=entire world map, 18=one city block; a city map will usually be zoom=12 or 13, depending on size
ExampleLac-Mégantic (Q142020) has zoom=11 as the depicted travel destination is a circle tour of the entire lake
SourceWikivoyage Template:Mapframe (Q14395215) or voy:fr {{Info Ville}} Template:Infobox settlement (Q5683132) templates
Motivation

Automate display of mw:Maps for destinations whose (lat, long) co-ordinates are already on Wikidata. K7L (talk) 15:52, 20 May 2016 (UTC)

Discussion
  •   Oppose "zoom=11" is not a property of the town of Lac-Mégantic (Q142020). This sort of thing needs to be handled by Wikivoyage, or other reusers, locally. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:20, 20 May 2016 (UTC)
  •   Comment Perhaps something like w:Template:Coord#type:T would be more suitable? A "type" indicates whether this is a whole country, a province, a county, an individual city, whatever. Each individual client can then do what it wants with that info, perhaps choose a reasonable default map scale to zoom in on cities or out to fit an entire country? This should be a qualifier to coordinate location (P625) - so "these co-ordinates refer to a county-sized entity" describe the P625 (lat,long) and not the town or the lake. K7L (talk) 02:53, 21 May 2016 (UTC)
  •   Comment if it's something that is shared among several versions of Wikivoyage, it's likely to be something that can be stored at Wikidata. A qualifier on coordinates or another property should be possible. @The Anome:, a specialist contributor in the field, just started started a thread at Wikidata:Project_chat#.22Approximate_radius.22_for_geographical_features.
    --- Jura 04:28, 21 May 2016 (UTC)
  •   Oppose, as "zoom level" is entirely context-dependent and does not describe an objective attribute of the item being represented: as the proposal itself demonstrates, large and small cities, or large or small regions, can be quite different. At best, what is proposed is an alternative ad-hoc representation of approximate feature size, something we can encode directly, so that the correct settings can be ascertained for whatever mapping system, existing or future, is being used in that particular context.

    The feature size also has the advantages that it has a physical meaning with well-defined units, and can be used for other purposes such as geodata integration. (By the way, the feature size is a property of the object, not a property of the coordinate data. That doesn't mean that we shouldn't have a precision indicator as a qualifier for coordinates -- it just means that we should not confuse coordinate precision with object size, or object size precision -- we need to be able to represent all of these distinctions.) See here for my proposal for this, which is a generic solution which uses only existing properties and qualifiers.

    See Lac-Mégantic (Q142020), which I've annotated with a diameter in this way. -- The Anome (talk) 10:22, 21 May 2016 (UTC)

  •   Oppose, not unified and not should be unified across different language versions.--Ymblanter (talk) 15:35, 22 May 2016 (UTC)
    • @Ymblanter, K7L: Exceptional overrides should be possible. In regards to the fairly limited set of Wikivoyage articles, is the geographic scope that different between language versions?
      --- Jura 12:50, 23 May 2016 (UTC)
      Not necessarily, but in practice, if I want to include a new site on the map outside the frame, often I need to adjust the zoom (and also the center position). I am not sure why doing it would be of any benefit for other language versions. It might make sense if sets of attractions were standartized, but they are not.--Ymblanter (talk) 13:06, 23 May 2016 (UTC)
      Ideally, it would probably just need to zoom to fit all listings of an article. As MediaWiki probably requires the zoom level to be statically defined, we need to store it somehow. Supposedly the listings would differ between actively edited articles and ones that just display listings from elsewhere.
      --- Jura 13:19, 23 May 2016 (UTC)
  •   Oppose a bounding box is the best way to handle this, per other concurrent discussions. Thryduulf (talk: local | en.wp | en.wikt) 12:59, 23 May 2016 (UTC)
    • @Thryduulf:: Thanks for your feedback. Can you do you proof of concept for the above sample item?
      --- Jura 13:06, 23 May 2016 (UTC)
      • @Jura1: I don't understand what you are asking. There are existing properties coordinates of northernmost point (P1332), coordinates of southernmost point (P1333), coordinates of easternmost point (P1334) and coordinates of westernmost point (P1335) that should give plenty of examples. Alternatively, as is being discussed elsewhere, we could have properties for southwestern corner of bounding box and northeastern corner of bounding box. See those discussions for examples. Thryduulf (talk: local | en.wp | en.wikt) 23:05, 23 May 2016 (UTC)
        •   Comment Following the sample above, the purpose of this property is to set "zoom=11" on voy:fr:Lac-Mégantic and make this available to other Wikivoyage versions. This is used for the Wikivoyage OSM version that appears on that page. Unfortunately, the proposal wasn't formulated with reference to either of them. Still, if your suggestion is meant to provide a realistic alternative, would you provide us at least with the definition of the bounding box for the same sample? If this is too complicated, it may be that this is not a realistic solution for K7L's use case.
          --- Jura 06:15, 24 May 2016 (UTC)
          • The zoom level will necessarily differ based on window size and shape. A bounding box just records two corners of an enclosing rectangle that the map display will include all of. Neither Google Maps nor OSM show me boundaries for Lac-Mégantic (Q142020) and I'm not familiar with the locality at all, but a bounding box with southwest corner at 45.563386,-70.9504097 and northeast corner at 45.617683,-70.8384867 would seem to achieve the desired aim of displaying a map showing all of Lac-Mégantic (Q142020) at the greatest zoom level possible. Thryduulf (talk: local | en.wp | en.wikt) 09:50, 24 May 2016 (UTC)
            • In general, it is correct that the zoom level would differ, but I think across the 17+ Wikivoyage editions using their OSM version, it would be stable. Compared to the effort of simply storing the existing zoom factor, is it worth attempting to gather the two pairs of coordinates for each some 7000 70000 articles?
              --- Jura 09:05, 25 May 2016 (UTC)
  •   Oppose per multiple above users, especially Anome. --Izno (talk) 14:56, 23 May 2016 (UTC)

@K7L:   Not done, no consensus --Srittau (talk) 14:59, 29 May 2016 (UTC)

map feature size

   Not done
DescriptionMap feature size for use in selecting geographic scale for on-page maps
Data typeNumber (not available yet)
Template parameterzoom
Domaingeographic places, itineraries which already have coordinate location (P625)
Allowed valueslargest edge-to-edge distance (in kilometres) for a geographic feature or destination
Example
⟨ Canada (Q16)      ⟩ map feature size Search ⟨ 8050 ⟩
indicates any on-page maps should be scaled down to fit an entire country (8050 km)
SourceWikivoyage Template:Mapframe (Q14395215) or voy:fr {{Info Ville}} Template:Infobox settlement (Q5683132) templates
Motivation

Automate display of mw:Maps for destinations whose (lat, long) co-ordinates are already on Wikidata, proposed as an alternative to the map zoom level currently in use in Wikivoyage mapframes. K7L (talk) 17:16, 22 May 2016 (UTC)

Discussion
@Michiel1972: what are those four parameters? I see we have parameters for northern, southern, eastern and western extremal points, with a total of eight degrees of freedom, but these four points are not the same as a bounding box, which only has four. -- The Anome (talk) 18:13, 23 May 2016 (UTC)
  •   Support A diameter or radius is preferable to a bounding box, because it uses only one property instead of four and is not biased towards "straight" (north-south/west-east) shapes. It is also easier to derive a zoom level or something similar from a single value than having to do calculations, based on four properties. This property should not be unit-less, though, but require a "km" unit. --Srittau (talk) 00:40, 23 May 2016 (UTC)
    • How is a bounding box biased for or against any shape? Thryduulf (talk: local | en.wp | en.wikt)
      • For an extreme case, take two items that are the same size and quadratic. One is aligned with the equator, while the other one is turned at a 45 degree angle. The bounding box makes the latter appear much larger than the former. This will not happen with a circle. Another reason I prefer a diameter or radius is that it seems wrong to specify the bounding box for example for buildings, while I would have no such qualms about a diameter. --Srittau (talk) 14:49, 23 May 2016 (UTC)
        • @Srittau: In which case, you plan to provide a map also turned 45 degrees? That seems silly. :) I've seen some projections here and there that take a non-North = "up" point of view, but most of these are globular-projections and not of particular use to this use case. --Izno (talk) 14:59, 23 May 2016 (UTC)
        • @Srittau: how large an area something is not the same as how it should be displayed on a map. For the former we have properties for area, length, width and perimeter. For the latter a bounding box indicates the area needed to be displayed. Using the latter as a proxy for the former would lead to the implication that Marshall Islands (Q709) (area 181 km²) is larger than Poland (Q36) (area 312,000km²). Thryduulf (talk: local | en.wp | en.wikt) 22:59, 23 May 2016 (UTC)
    • Both circles and bounding boxes need two properties. For circles, you need a radius or diameter plus the centre point of the bounding circle. For boxes you need the NE and SW corners. Circles versus rectangles was already discussed on the project chat discussion and you can read that if you want to know why I think rectangles are better than circles. - Nikki (talk) 08:48, 24 May 2016 (UTC)
  •   Oppose: We already have the properties to describe this. --Izno (talk) 15:00, 23 May 2016 (UTC)
    • @Izno: Can you tell me what these properties are? We are having a lengthy discussion at the Project Chat about finding any kind of reasonable alternative to the above. Yes, a bounding box might be good, but at the moment, we don't seem to have any support for bounding boxes. -- The Anome (talk) 08:36, 24 May 2016 (UTC)
      • @The Anome: A bounding box with 2 points (bottom-left corner and top-right corner, or bottom-right and top-left) can be derived from knowing the 4 cardinal direction's most extreme points. --Izno (talk) 08:51, 24 May 2016 (UTC)
        • Basically, for a map using the lat long system and where north = up, the westernmost and northermost points have your upper-left corner's lat and long respectively; bottom right from your easternmost and southernmost. --Izno (talk) 08:55, 24 May 2016 (UTC)
          • The problem is that those properties can only be used to determine bounding boxes if we have the necessary statements, which means we need to get data from somewhere. The Anome mentioned that there is some CC0 bounding box data which we could use, but we can't import data from bounding boxes to the existing properties because a bounding box doesn't tell us the exact position of the extreme point, only its latitude (for north/south) or longitude (for east/west). While ideally we would have the exact extreme points for items, from a practical point of view, information about the bounding box may be the only data we have available to us and that is still more informative (and just as useful for the intended purpose) than having nothing, which is why I would support new properties which define the bounding box. - Nikki (talk) 20:49, 24 May 2016 (UTC)
  •   Weak oppose As per the project chat discussion, I think we should be using bounding boxes. - Nikki (talk) 08:48, 24 May 2016 (UTC)
    • Given other people's responses here, I'm happy to go with the bounding box idea. But, while the extremal points in each cardinal direction are sufficient to define the bounding box, they are massive overkill for what we need here, and the data for them not in general as easily available as bounding boxes, and misusing them to encode a bounding box would be actively misleading, as in some cases, where we have access to an accurate shapefile, we could indeed give them real values that meet their specification. If we had two new properties, "bounding box northeast corner" and "bounding box southwest corner", both with geographic point values, then we could easily implement this. -- The Anome (talk) 12:44, 24 May 2016 (UTC)
      • If that was intended as a reply to me rather than someone else, I already said in the project chat discussion that two properties for the NE/SW coordinates of a bounding box sounds good to me. :) - Nikki (talk) 20:29, 24 May 2016 (UTC)
        • Hi Nikki, thanks for clarifying that: I'd missed your comment. Given that this seems to be the approach that seems to have garnered most support, I think we should move forward on that basis. There are some interesting issues that can happen around the poles and the 180-degree line, so we should be careful in defining and using those properties, but I carefully written Lua code should be able to generate a valid scale or approximate feature size parameter from that box for any map system that requires one. And for map systems that explicitly want a bounding box, that data is there directly. -- The Anome (talk) 12:04, 25 May 2016 (UTC)

@K7L:   Not done no support (unfortunately) --Srittau (talk) 15:02, 29 May 2016 (UTC)

Minitel

   Done: Minitel code (P2878) (Talk and documentation)
Description
Français : code pour accéder au service
English: access code of a service on the Minitel Videotex
RepresentsMinitel (Q1133476)
Data typeExternal identifier
Domainorganizations, services
ExampleCrédit Mutuel (Q642627) → 3615 CMUT [11]
  Comment (A) what is the source of this information and is it really available under the right sort of license to be able to add to wikidata, and (B) is there actually a purpose to adding these codes? Are they really unique identifiers? If they are applied to organizations that existed in the past but have changed significantly in the mean time (for example many French universities have been significantly reorganized over the past few years) how would they be applied? I really think more information is needed on this, particularly to be used as an external ID, before I could support its creation. Also, really NO properties proposals from experienced wikidatans should go in "Unsorted" - Organizations would be fine, or Authority control if it's really appropriate as an external ID. ArthurPSmith (talk) 17:41, 27 May 2016 (UTC)
The sample above has a source for the statement. Is this suitable? Subject item explains what is about (mainly in French, but also in other languages). Maybe this should be under "Reference", but we tend to add them directly as property. The Organization subpage doesn't seem suitable has it's not exclusive to organizations. In any case, if you feel it's important, you could move it to a subpage of its own and add it to every topical subpage you feel it applies.
--- Jura 03:44, 28 May 2016 (UTC)

@Jura1, TomT0m, Tubezlob, Dispenser:  Done now Minitel code (P2878). I hope I made the correct regex. Lymantria (talk) 05:30, 30 May 2016 (UTC)

Spoken in

   Withdrawn
DescriptionCountries or regions where this language is widely spoken
Data typeItem
Domainlanguage or dialect items
ExampleCatalan (Q7026) is spoken in Catalonia (Q5705)

See above Lingveno (talk) 14:17, 22 May 2016 (UTC)

Discussion

exact match

   Done: exact match (P2888) (Talk and documentation)
DescriptionThe property exact match is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. (Tailored around skos:exactMatch (https://www.w3.org/2009/08/skos-reference/skos.html#exactMatch)
Data typeURL
Allowed valuesURI
Example
Motivation

Through the WDQS content from WIkidata can be extracted and integrated with federated queries on external SPARQL endpoints. To allow these queries a property is needed that captures the link between a concept in Wikidata and its URI. The property equivalent class Property:P1709 does exist, however using this property to express similarity is a bit problematic, as by the W3C definition : "NOTE: The use of owl:equivalentClass does not imply class equality." I would like to propose the propety exact match, tailored around skos:exactMatch, to be able to store mappings to external URIs, allowing querying Wikidata content in external SPARQL endpoints. --Andrawaag (talk) 19:46, 25 April 2016 (UTC)

Discussion
  •   Support since, as stated above, the equivalent class property is not suitable for this kind of use. The skos:exactMatch is a perfect fit for this. Emitraka (talk) 20:32, 25 April 2016 (UTC)
  •   Support another alternative would be owl:sameAs .. I think generally the skos approach will work in more cases than the OWL approach so I am supportive. But the reason that is the case also means that less powerful automated reasoning is possible so there is a downside.. e.g. numerous OWL reasoners could process sameAs and correctly merge nodes. Is there equivalent support for automating node merges via skos:exactMatch ? --I9606 (talk) 21:22, 25 April 2016 (UTC)
Skos has the following mapping properties: skos:closeMatch, skos:exactMatch, skos:broadMatch, skos:narrowMatch and skos:relatedMatch. skos:exactMatch, being a sub property of skos:closeMatch and also the transitivity property allowing some reasoning being applied to merge on nodes. --Andrawaag (talk) 12:20, 26 April 2016 (UTC)
  •   Support Egon Willighagen (talk) 06:26, 27 April 2016 (UTC)
  •   Support --jjkoehorst (talk) 10:23, 28 April 2016 (UTC)
  •   WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
  •   Comment There was already a proposal to create owl:sameAs (/Archive/15) which concluded in the creation of described at URL (P973). --Pasleim (talk) 21:46, 25 April 2016 (UTC)
    • Which ended up being schema:sameAs, it seems. I would be good if someone could compare owl:sameAs, schema:sameAs, and skos:exactMatch, especially the difference between the latter two, as the OWL version differs from them. --Srittau (talk) 00:18, 26 April 2016 (UTC)
      • owl:sameAs implies that both can be interchanged. Take for example a protein in Wikidata. This can be match to for example a record in Uniprot. However, the Wikidata entry contains multiple translations of the preferred label, whereas uniprot is english only. Skos:exactMatch is used to link two concepts indicating a high level of similarity, between the concepts both URI describe, but the properties are not necessarily interchangeable.schema.org:sameAs on the other hand is new to me. But according to its description (https://schema.org/sameAs). "URL of a reference Web page that unambiguously indicates the item's identity.". This seems to be more catered towards human readable website (e.g. schema.org/sameAs seems to be more appropriate to point to human readable websites (http://www.uniprot.org/uniprot/Pxxxxxx) in contrast to the URI needed in a SPARQL query (http://purl.uniprot.org/uniprot/Pxxxxxx). --Andrawaag (talk) 06:44, 27 April 2016 (UTC)
        • This "implication" means that a reasoner can apply the properties (and values) of one of the items to the properties of the over one isn't it ? Which means imho that the items has not to be exactly similar value by value. He will just make the union of both the facts he knows on both items. author  TomT0m / talk page 18:30, 30 April 2016 (UTC)
  •   Weak oppose I have a concern this will or could lead to a large number of redundant statements on items - for example almost all external identifiers could be considered (with their FormatterURL's) to be an "exact match" for the item (in the SKOS sense as well as other "same as" senses). And we just moved external identifiers to a separate section to avoid cluttering up the main statements on an item. But if it was made clear this property should only be used for linking between vocabularies represented with SKOS and which do NOT have external identifier properties in wikidata, then I think it could be a good idea to cover representing that data somehow here. But the examples as presently given do not meet this criterion - we have Disease Ontology ID (P699) already for the first which I don't think is a SKOS vocabulary anyway, and UniProt protein ID (P352) for the second. Can you come up with an example where this property really is helpful and not redundant? I will change my oppose to support with better examples. ArthurPSmith (talk) 11:55, 30 April 2016 (UTC)
    • @ArthurPSmith: Those examples are actually ones that are from actual use cases where such a property would be helpful. Take for example the one from Disease Ontology (http://purl.obolibrary.org/obo/DOID_2841) The literal version of that ID is "DOID:2841", which with the formatter URL resolves to http://disease-ontology.org/term/DOID:2841. The URI in the Disease Ontology is however http://purl.obolibrary.org/obo/DOID_2841. To my knowledge there is currently not a possibility to reproduce that URI as a formatter UR in wikidata, whereas these URIs are used in external (semantic web) resources. The same applies to other resources where the prefix became part of the actual identifier. (e.g. Gene Ontology ID (P686) and Mouse Genome Informatics ID ((P671)).In earlier version of the property descriptions the prefix was added as part of the formatterURL. This has lead to issues since for most if not all users the prefix is an intrinsic part of the identifier, leading to identifiers of the form DOID:DOID:2841. With a property that would capture these official URI, wikidata content would be more easily be integrated through federated queries in external SPARQL endpoints such as sparql.uniprot.org, with a query of the following type:
      • @jerven: Actually if the formatter could take a URL and format an ID in the interface, instead of taking an ID and formatting an URL then this property is not needed. Basically, the addition of this property is hack around that weakness in the formatter.
  SELECT DISTINCT ?wd_url ?wduniprot ?uniprot ?wdLabel ?upLabel 
  WHERE {
  # Wikidata graph
  SERVICE <https://query.wikidata.org/bigdata/namespace/wdq/sparql> {
      ?wd_url wdt:P279 wd:Q8054 ;
                     rdfs:label ?wdLabel ;
                     wdt:P352 ?wduniprot ;
                     wdt:Pxxx ?uniprot .
    FILTER(lang(?proteinLabel) = "en")
  }
  # uniprot graph
  ?uniprot rdfs:label ?upLabel .
  ?uniprot ?p ?o .
 }

--Andrawaag (talk) 20:16, 30 April 2016 (UTC)

@Andrawaag: well I suppose that's a reasonable argument but I am concerned about the UI implications for wikidata. If we can find examples that are not currently covered by an existing wikidata property I would be happier. Even better if the developers were looking at moving URI properties to a separate group similar to (or along with) the external id's group. Here's a different example - I don't believe we have a wikidata property covering the AGROVOC skos vocabulary from the UN FAO. soil (Q36133) ought to be logically a skos:exactMatch with http://aims.fao.org/aos/agrovoc/c_7156 (for instance)? ArthurPSmith (talk) 14:17, 2 May 2016 (UTC)
@ArthurPSmith: I am not entirely sure identifiers are skos:exactMatch... part of that discussion was actually about that in many cases, at least currently, they are not. This is because the concept modeled in Wikidata is conceptually similar but different from the remote database. Wikidata is not really clear in this matter, though some properties suggest more than really is the case. But assuming that any identifier is a skos:exactMatch is just going to cause a lot of trouble (factual inconsistencies). Therefore, IMHO, having this explicit statement is helpful, just because it's explicit, rather than implicitly assuming identifiers say something about equivalence. Egon Willighagen (talk) 08:26, 3 May 2016 (UTC)

@Markus Krötzsch: Maybe you want to comment on this proposal? --Pasleim (talk) 09:02, 3 May 2016 (UTC)

@ArthurPSmith: I share your concerns about the UI implications for wikidata. However, they are not specific for this proposed property. There are already 32 url properties implemented where the same UI concerns apply. I support a request to move URL properties to a separate group, but preferably outside the scope of this property proposal. Currently. Wikidata has a very powerful SPARQL endpoint, yet embedding Wikidata in the Linked data cloud is challenging. With a property capturing URI's on the same concept, would instantly allow linking to other resources in the linked data cloud. We might even make Wikidata the central node in the cloud. --Andrawaag (talk) 09:09, 3 May 2016 (UTC)
@Andrawaag, Egon Willighagen: could this be resolved better by a new property for wikidata external-id properties that works like formatter URL but provides a regular-expression transformation of the ID into a Linked Data URI string, perhaps with an additional qualifier on what kind of relationship it should represent on wikidata items (skosExactMatch, CloseMatch, or something else)? It seems to me adding huge numbers of new statements to items just because a ':' should be a '_' and similar concerns is wasteful and likely to lead to trouble (what if the ID is corrected on an item but not the "exact match" URI? Or the two statements are on different items?). ArthurPSmith (talk) 14:57, 3 May 2016 (UTC)
@ArthurPSmith: I think a main feature is that this property makes the 'additional qualifier' obligatory. I like the expressiveness of your proposal of a mix of, basically, three predicates (qualifier, RDF formatter, and external-id property), but also note that it sounds rather complex (I would support this proposal). This could ultimately replace the current proposal, I guess. However, the current proposal has the advantage that it does not depend on external-id properties, simplifying that part too. Regarding your consistency concerns, I agree, but see that similar with all the consistency issues that already exist; in fact, part of that could be addressed with this proposal. For these, however, I would suggest the established route of consistency testing, as now also done for, for example, ID strings against their expected string format. Egon Willighagen (talk) 15:16, 3 May 2016 (UTC)
* Ok after some thought I'm changing my view to   Weak support - I think the plan as it stands is imperfect, but doing this at least for now does seem useful in lieu of better solutions. ArthurPSmith (talk) 17:53, 27 May 2016 (UTC)


Time in space

   Done: time in space (P2873) (Talk and documentation)
DescriptionTime in space by an astronaut or cosmonaut
Data typeNumber (not available yet)
Template parameteren:template:Infobox astronaut
Domainastronaut
Allowed valuestime
ExampleBruce McCandless II (Q433608) → 18751, with unit = minute (Q7727)
Motivation

I think it's important to keep updated template and it is important in an astronaut's career Adert (talk) 23:21, 30 April 2016 (UTC)

Discussion

@Adert, ArthurPSmith:   Done now time in space (P2873) --Lymantria (talk) 07:02, 29 May 2016 (UTC)

Distance traveled

   Not done
DescriptionDistance traveled by spacecraft or other
Data typeNumber (not available yet)
Template parameteren:template:Infobox spaceflight
Domainspace mission
Allowed valuesvalue
ExampleSTS-1 (Q217543) → 1,074,000; with unit = mile (Q253276)
Sourceeg. [12]
Motivation

It's important in space mission Adert (talk) 23:21, 30 April 2016 (UTC)

Discussion
  •   Oppose I don't think this property is particularly useful or meaningful in general: it does have some meaning with regard to a reusable vehicle that flies to orbit and then returns, but that's a very limited set (and there are none of them around at the moment). Once you're in orbit, additional distance traveled comes for free - would you track the number of miles traveled by the space station? By any satellite? And distance traveled becomes even more meaningless for beyond-Earth missions: you have to pick a frame of reference different from the Earth's, so what reference frame do you use? I understand NASA put out these numbers for the space shuttles, but that doesn't mean they're a good idea. ArthurPSmith (talk) 20:15, 13 May 2016 (UTC)
    Well, not completely free, due to tidal forces, but that point is made. --Izno (talk) 13:52, 16 May 2016 (UTC)
  • Oppose per Arthur. --Izno (talk) 13:52, 16 May 2016 (UTC)

  Not done Lack of support. Lymantria (talk) 06:52, 29 May 2016 (UTC)

property usage tracking category

DescriptionItem linking categories tracking a Wikidata property in client projects. Create a property for each type of usage category. See samples.
Data typeItem
Template parameterN/A
Allowed valuessubcategories of Category:Page using Wikidata data (Q15574247)
Exampleimage (P18) -> Category:Pages using Wikidata property P18 (Q15907809)
  • Tracking: same Category:Local image same as Wikidata (Q16742292)
  • Tracking: differences Category:Local image different from Wikidata (Q16742291)
  • Tracking: usage Category:Pages using Wikidata property P18 (Q15907809)
  • Tracking: local no, WD yes Category:No local image but image on Wikidata (Q16742293)
  • Tracking: local yes, WD no Category:Local image but no image on Wikidata (Q16742294)
  • Tracking: local no, WD no Category:No local image and no image on Wikidata (Q16742295)
Proposed byZolo (talk) 17:41, 7 January 2015 (UTC)
Discussion

As a stopgap as long as they is no built-in way to do it. Using categories to track property usage can be useful to check if a property properly used, if a deprecated property is still in use etc.--Zolo (talk) 17:41, 7 January 2015 (UTC)

I added a few (item based) categories to Template:Property documentation. I found at least 7 different kinds of tracking categories. --- Jura 21:31, 16 June 2015 (UTC)

@Zolo, Jura1, Pasleim, Izno:   Done. There is at least support for this property linking to the top category. For now, I added a single value constraint, but its removal can be discussed on the property talk page. --Srittau (talk) 15:24, 29 May 2016 (UTC)

  • Actually, the revised proposal was for 6 or 7 such properties. Each would have had a single value constraint. I don't think there is something like "subcategories" on Wikidata and every Wikipedia has different views on what is a subcategory of what. I think the "main category" property is already being used for in the way P2875 would be used.
    --- Jura 15:51, 29 May 2016 (UTC)
  • As there doesn't seem to be a lot of interest for a single category (P2875), I think we should delete it.
    --- Jura 16:20, 29 May 2016 (UTC)

type of unit used for this property

Descriptionthe units for this property are all instances of this item
Data typeItem
Domainproperties
Allowed valuessubclasses of unit of measurement (Q47574), currency (Q8142)
Exampleprice (P2284) → currency (Q8142), duration (P2047) → unit of time (Q1790144), length (P2043) → unit of length (Q1978718),
Motivation

We have P2237 (P2237) for listing individual units that can be used with a property but lots of properties which use units aren't restricted to specific units but to specific types of units.

In some cases (e.g. temperature) it's not really a problem because there aren't many units used. In other cases though, there's a lot of possible units. For example, the units for length (P2043) are any unit of length. There are 167 instances of unit of length (Q1978718). length (P2043) already lists 15 different units and there are about another 15 showing up as constraint violations on Wikidata:Database_reports/Constraint_violations/P2043#Units_statistics. I think it would be useful to have a way to say that the units for length (P2043) are any unit of length instead of trying to list every unit of length as a unit for the property.

I'm not sure exactly how this would interact with P2237 (P2237). My suggestion would be to use P2237 (P2237) when the property is defined in terms of a specific unit and this property if it can use any unit of a specific type.

@Pasleim: Pinging you because HarvestTemplates appears to be using P2237 (P2237), so you might be interested in this.

- Nikki (talk) 12:43, 16 April 2016 (UTC)

Discussion
  Comment I think this would be somewhat redundant. measured physical quantity (P111) is here to link units to quantity types already. We could reuse this property to do the same on properties, then we would have the set of all appliable properties by a simple query. author  TomT0m / talk page 13:03, 16 April 2016 (UTC)
I'm not sure how well that would work. The uses of P111 include things which shouldn't show up in a list of units, e.g. unit of area (Q1371562) (and that statement does not seem wrong to me) and P111 doesn't seem to be very widely used either so lots of things which should show up in a list of units probably won't. I think it would also not discourage people from adding lots of P2237 (P2237) statements because it wouldn't be obvious that P111 is being (somehow) used to define acceptable units, whereas this proposal is explicitly about which units are acceptable. - Nikki (talk) 14:11, 16 April 2016 (UTC)
I proposed properties for dimensional analysis recently but it seems that it was rejected :/ But that statement seems wrong to me : an area is a measure of a surface. What's measured here is a surface (L*L in dimensional analysis (Q217113)     ). The physical quantity should be Surface (Q297895)     . The area is the number of surface units we can measure. author  TomT0m / talk page 14:34, 16 April 2016 (UTC)
  •   Comment The problem with P2237 (P2237) is that it's somewhat redundant with the constraint template. Eventually both would be replaced by a new system of constraint properties. Obviously, a constraint that works is better than any property. Even if we would want units of length, we might not want any unit of length. The lists of allowed units might be the same for several properties ..
    --- Jura 15:43, 16 April 2016 (UTC)
  •   Support The example Nikki is giving is convincing. I encountered similar problems with valuta. It's a bit silly to have to add a new currency to the possible units, when the property is applied to an item from a formerly unused country, while it is clear that it in accordance with the intended use of the property (like price (P2284)). In some cases P2237 (P2237) is still to be preferred. Lymantria (talk) 06:56, 4 May 2016 (UTC)
  •   Support I'd be in favor of replacing all uses of P2237 (P2237) with this and either constraining that property to be single-valued when used or deleting it altogether (are there good examples where it's really needed?) This solution seems much better for almost all cases I can think of anyway. ArthurPSmith (talk) 17:48, 27 May 2016 (UTC)

@Nikki, Pasleim, Lymantria, ArthurPSmith:   Done --Srittau (talk) 15:46, 29 May 2016 (UTC)

has role

Descriptionthe role of an item in a certain context or ontology
Data typeItem
Domaingeneric
Allowed valuesitems which define the role of the subject item
Examplevemurafenib (Q423111) → antineoplastic (Q23987513)
Sourceany, ontological relationships, e.g. from OBO
Robot and gadget jobsProteinBoxBot might use this property to establish ontological relations from OBO.
Motivation

A 'has role' property should be used as a generalized property in order to represent statements about an item fulfilling or having (a) certain role(s). This 'has role' relation is used in many ontologies, which is a clear sign that such a relation is needed to meaningfully represent knowledge. 'Has role' has been defined in the relations ontology as http://purl.obolibrary.org/obo/RO_0000087 and is being used in 25 other ontologies, showing the scale of its usage (clicking on the purl will bring you to an overview of where it is used). Existing properties like subclass of (P279) and instance of (P31) do not properly represent what 'has role' is meant for, as subclass of (P279) maps to 'is a' and instance of (P31) represents more a data type or class instance of an item, not so much the role of an item, because it maps to http://www.w3.org/1999/02/22-rdf-syntax-ns#type. Sebotic (talk) 19:05, 17 May 2016 (UTC)

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

  Notified participants of WikiProject Chemistry

  Notified participants of WikiProject Medicine

@Emw:

Discussion

@Sebotic, Yair rand, TomT0m, Thryduulf: moved into subpage --Srittau (talk) 16:24, 19 May 2016 (UTC)

@Sebotic, TomT0m, Srittau, Putmantime, Thryduulf, Andrawaag:  Done subject has role (P2868) -- Lymantria (talk) 20:37, 27 May 2016 (UTC)

translated into languages

   Not done
Data typeItem
Domainwork (Q386724)
Allowed valuessubclasses of language (Q34770)
ExampleBeltracchi: The Art of Forgery (Q16054614) → English (Q1860)
Motivation

There is an endless discussion going on to merge original language of film or TV show (P364) and language of work or name (P407). Main opposition arises from the feared effort of needing to create a new item for each translation of a work even if there is no information known about the translation. So people are using language of work or name (P407) to indicate in which languages a work was translated but this use is disputed. I therefore propose a new property “translated into languages” which allows people to add easily translations without the need of creating new items and without abusing language of work or name (P407). --Pasleim (talk) 10:34, 24 April 2016 (UTC)

Discussion
  Not done Lack of support. Lymantria (talk) 07:51, 27 May 2016 (UTC)

Official ship number

   Withdrawn
Descriptionidentifier for a merchant ship per Board of Trade of the British Government
Data typeString
Domainwatercraft (Q1229765) cargo ship (Q105999)
ExampleJane (Q23930837) → 760
SourceCLIP Crew list index project
Motivation

Planning on adding c.600 19th century merchant ships to Wikidata, all with official numbers. Further information will be added for each item by volunteers using various sources) Jason.nlw (talk) 13:30, 28 April 2016 (UTC)

Discussion
Hi Andy, that was my initial thought too, but when i spoke to Nav about the collection he suggested creating a new Property. If people are happy for me to use Inventory number that's fine - Cheers Jason.nlw (talk) 16:27, 28 April 2016 (UTC)
@Jason.nlw, Pigsonthewing: I'm not sure if inventory number (P217) is the right property for that. It's description is identifier for a physical object or a set of physical objects in a collection and needs the mandatory qualifier collection (P195). However, if I see it right the ships here are not part of a collection. --Pasleim (talk) 09:17, 29 April 2016 (UTC)
@Pasleim, Pigsonthewing: Not as such. It is more of a registrations number, a unique number assigned to each merchant ship in the united kingdom.Jason.nlw (talk) 09:26, 29 April 2016 (UTC)

  Comment

From 1855 the registers also record the vessel's official number, which was a unique number between 1 and 200,000. It was allocated to all ships afloat at that date at whichever port they first called, and reported back to her home port. Ships registered subsequently were allocated a number at the time of registration. The number was carved into a substantial part of the ships, such as the main bulkhead, and stayed with her throughout her life.
—http://crewlist.org.uk/registers/registernotes.php

. -- Gymel (talk) 15:19, 1 May 2016 (UTC)

How is this different from pennant number (P879)? --Pasleim (talk) 15:25, 1 May 2016 (UTC)
19th century british merchant vessels vs. 20th century european military vessels? Feels like a major difference, though. -- Gymel (talk) 16:51, 1 May 2016 (UTC)
  • @Jason.nlw: If you use this to cross-reference your entries, it can be useful. Maybe the label should include that it's meant for the British official number. Datatype in that case should be "external id".
    --- Jura 11:14, 6 May 2016 (UTC)

central government budget balance

   Not done
Descriptionbudget balance of the central government. revenue minus expenditure.
Data typeNumber (not available yet)
DomainCountries
Allowed valuesNumber, currency. positive or negative
Example-$35 billion
Robot and gadget jobsA robot should update this
Motivation

central government budget balance is an important economic statistic for analyzing the financial situation of an economy Mcnabber091 (talk) 22:57, 20 December 2015 (UTC)

Discussion

  Comment this property should be a single $ amount. it would not be calculated from government expenditure and government revenue. instead this property would come straight from the source.Mcnabber091 (talk) 23:06, 20 December 2015 (UTC)

  •   Oppose. Calculated item. 16:00, 22 December 2015 (UTC)

  Comment I think that for calculable properties, I would suggest having two references: the statistic from directly for a source and our internally calculated statistic. That way the reader would have both. Mcnabber091 (talk) 21:16, 25 December 2015 (UTC)

  Not done Unsupported. Lymantria (talk) 08:43, 26 May 2016 (UTC)

money supply type

   Not done
Descriptiontype of money supply definition
Data typeString
DomainCountries
Allowed valuesM0, M1, M2, M3
ExampleM0
Robot and gadget jobsA robot should update this
Motivation

For the property 'money supply' we need a qualifier for money supply type. Mcnabber091 (talk) 20:15, 25 December 2015 (UTC)

Discussion

  Comment @ArthurPSmith: this property is needed as a qualifier for money supply. There are a few important money supply definitions (M0, M1, M2, M3) and they all fall under the money supply property. Mcnabber091 (talk) 20:15, 25 December 2015 (UTC)

Would this be a string? Mcnabber091 (talk) 21:05, 25 December 2015 (UTC)
With only four values permitted, they should be items. Also, the example needs a subject. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:46, 8 January 2016 (UTC)

  Comment @Mcnabber091: This qualifier seems unnecessary. Use criterion used (P1013) and point to items created on M0, M1, MB, MZM, etc. Sad to see that money supply (P2296) has not at all been used so far, not even in an example. Lymantria (talk) 06:25, 7 May 2016 (UTC)

  Not done Use criterion used (P1013) instead. Lymantria (talk) 08:47, 26 May 2016 (UTC)

VAT rate

   Done: VAT rate (P2855) (Talk and documentation)
Descriptionapplicable rate in this country/region. Use qualifiers for specialised rates.
Representsvalue-added tax (Q128635)
Data typeQuantity
Domaincountries/states
Allowed values>=0%
ExampleGermany (Q183) → 19 percent (Q11229)

@Jura1, Srittau:  Done --Lymantria (talk) 13:45, 25 May 2016 (UTC)

FamilySearch ID

DescriptionID of a person in familysearch.org
RepresentsFamilySearch (Q3066228)
Data typeExternal identifier
Allowed values\w{4}-\w{3}
ExampleLomer Gouin (Q764557) → LV6K-8JT
Sourcehttps://familysearch.org
Formatter URLhttps://familysearch.org/tree/#view=ancestor&section=details&person=$1
Proposed byAlmondega (talk) 13:52, 12 May 2016 (UTC)
Motivation

It is an important source of genealogical information.

Discussion
  •   Support - I'm surprised this hasn't been proposed before but I can't find any record of it in the archives. HOWEVER - the website does require a sign-in (accounts are free) to see the record linked to. Is that a problem? ArthurPSmith (talk) 18:10, 27 May 2016 (UTC)

  Done as FamilySearch person ID (P2889) @ArthurPSmith, Almondega:. I still have to get the property setup, but should have the done by the end of the day (NYC time). --Izno (talk) 15:49, 6 June 2016 (UTC)

UMLS CUI

   Done: UMLS CUI (P2892) (Talk and documentation)
DescriptionNLM Unified Medical Language System (UMLS) controlled biomedical vocabulary unique identifier
RepresentsUnified Medical Language System (Q455338)
Data typeExternal identifier
Template parametercurrently none, most likely one in the future
DomainMedicine, Molecular Biology, Chemistry
Allowed values'C' as the prefix, followed by 7 digits
Examplevemurafenib (Q423111) → C3192263
Sourcehttps://www.nlm.nih.gov/research/umls/rxnorm/, NDF-RT (national drug file reference terminology)
Formatter URLhttps://rxnav.nlm.nih.gov/REST/Ndfrt/id?idType=UMLSCUI&idString=$1
Motivation

The UMLS metathesaurus, developed sind 1989 by the National Medical Library, is a controlled biomedical vocabulary metathesaurus, unifying several vocabularies. Having cross-references to UMLS in Wikidata will greatly improve interlinking with biomedical controlled terms and vocabularies outside Wikidata. These IDs will also help to better establish drug-disease, drug-drug and drug-side-effect relations. Sebotic (talk) 00:19, 26 May 2016 (UTC)

  Notified participants of WikiProject Medicine

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

Discussion

  Done as UMLS CUI (P2892). @Sebotic, I9606, Putmantime, Andrawaag, Emitraka, Pigsonthewing: I need to fill out the property documentation but it is otherwise ready for use. --Izno (talk) 17:27, 6 June 2016 (UTC)

cites

   Done: cites work (P2860) (Talk and documentation)
DescriptionCitation from one document to another, e.g., one scientific paper to another scientific paper
Representscitation (Q1713)
Data typeItem
Domaindocuments: scientific articles, books, legal texts, ...
ExampleScientific citations in Wikipedia (Q21172284) → Internet encyclopaedias go head to head (Q24239902)
Robot and gadget jobsProbably not
Motivation

During WikiCite there has been some discussion of such a property. I do not know what to think about it. It could potentially "blow up" Wikidata with millions of documents each citing tens/hundreds of other documents. Nevertheless I think it could be interesting. By having a "cites" we can build citation networks and list relevant similar articles based on co-citation network. It is already possible to build co-author networks. — Finn Årup Nielsen (fnielsen) (talk) 06:13, 26 May 2016 (UTC)

Clarification: I support the creation of the property and am not afraid of flooding Wikidata. I was just expressing the fear that others could be afraid of flooding Wikidata. — Finn Årup Nielsen (fnielsen) (talk) 08:43, 26 May 2016 (UTC)https://www.wikidata.org/wiki/Wikidata:Property_proposal/Creative_work#citerer
Discussion
  •   Support This is a very much needed property for representing basic relations between items that represent sources, per Wikidata:WikiProject_Source_MetaData. I want to strongly challenge the suggestion that the sheer creation of a property will result in flooding Wikidata with millions of items. How to create entries on Wikidata and what's appropriate in terms of data imports has little to do with the usefulness of the property. --Dario (WMF) (talk) 08:40, 26 May 2016 (UTC)
  •   Support I support the creation of this property. I agree that it is important to be able to represent citation relationships between pieces of scholarly literature --Hweyl (talk) 08:53, 26 May 2016 (UTC)
  Support I think this property is certainly useful to have. Of note, the most relevant ontology here &mdash the Citation Ontology (CiTO) — has an element "cites" that refers to basically the same thing proposed here, though it is more focused on scholarly publications specifically. --Daniel Mietchen (talk) 08:45, 26 May 2016 (UTC)
  •   Support I support the creation of this property. It is inconceivable that a property representing relationships between the foundations of knowledge would not exist. Porteclefs (talk) 09:43, 26 May 2016 (UTC)
  •   Support This is an essential property for mapping the literature network which would be very valuable to have as part of the project.--Konrad Foerstner (talk) 08:51, 26 May 2016 (UTC)
  •   Support This adds power to modeling bibliographic relations on WIkidata --Andrawaag (talk) 08:53, 26 May 2016 (UTC)
  •   Oppose we already had proposals for "mentions" and the like. This seems too granular.
    --- Jura 08:58, 26 May 2016 (UTC)
    For reference
    * Wikidata:Property_proposal/Archive/13#mentions
    * Wikidata:Property_proposal/Archive/33#mentions
    * Wikidata:Property_proposal/Archive/45#mentioned_in
    * Wikidata:Property_proposal/Archive/51#mentions
    ·addshore· talk to me! 09:07, 26 May 2016 (UTC)
    •   Comment For scientific articles the idea of a "citation" is a fairly confined idea. "Mentions" is a somewhat general ("hazy" to me), e.g., The Ugly Ducking "mentions" a "swane". Would that go into it the property? "cites" would corresponds to http://purl.org/spar/cito/cites as mentioned above. — Finn Årup Nielsen (fnielsen) (talk) 09:39, 26 May 2016 (UTC)
      •   Comment CiTO, the Citation Typing Ontology is far more granular, and in my opinion what we ultimately need. A mere 'cites' does not distinguish 'disagreesWith', 'supports', or 'citesAsAuthority' (i.e. citation like 'because he wears a nice hat'). CiTO does that. However, the world has not moved there yet, and cito:cites is the standing practice of tracking provenance of scholarly knowledge. Egon Willighagen (talk) 11:33, 26 May 2016 (UTC)
    •   Comment It is certainly true that a citation is an instance of a mention. It is also true that a citation is quite granular. However, the granularity is, in fact, quite meaningful. When a scholar cites prior knowledge, she is engaging in a very specific and explicit act that signals direct recognition of the influence upon current research of the cited item on the surrounding text. In this way, citations are not mere mentions. I can, in fact, imagine clear distinctions between citations and mentions in the scholarly literature. For instance, though Albert Einstein explicitly denies the veracity of many quantum state phenomena, no practicing physicist would explicitly cite this denial. Rather, in motivating work, she might opt to merely mention that this or that well established and observed phenomena was, at one time, denied by the world's most famous scientist. This mention is certainly a statement of fact. But, what it lacks is the granular force of idea propagation along an explicit citation. Rather, it is, in a word, conversational and, as such, is not preserved in the more explicit networked system of citations. Porteclefs (talk) 09:40, 26 May 2016 (UTC)
  •   Support for a specific reason. Many of the papers NIOSH (and our affiliates) publish are primary in nature and therefore unlikely to be cited directly on Wikipedia. However, review articles that use these papers are more likely to be cited. Modeling these relationships is a crucial component of determining (a) which papers are cited on Wikipedia and (b) of these papers, how many cite our research. This will help us measure our impact on Wikipedia. James Hare (NIOSH) (talk) 09:21, 26 May 2016 (UTC)
  •   Done cites work (P2860) --Tobias1984 (talk) 09:30, 26 May 2016 (UTC)
  •   Comment less than 3 hours from initial proposal to creation of a property is very far from good practice as it does not allow most people the opportunity to read, understand and comment on the proposal. Yes there was strong numerical agreement here, but there was no diversity of input and no ability for anyone to counter any groupthink that may be happening. I don't know whether this proposal has merit or not, but I do know that regardless of merit it should not have been created without several days discussion at absolute minimum. Thryduulf (talk: local | en.wp | en.wikt) 10:09, 26 May 2016 (UTC)
  • Some four minutes after creation, the property was nominated for deletion. --Yair rand (talk) 10:12, 26 May 2016 (UTC)
  • Very strong   Support. Formal citations are a key approach for providing provenance. In fact, implicitly Wikidata already uses this daily (in various ways). But as others pointed out, a mechanism is needed to link information sources at a different level: not within a single Wikidata entry, but between entries. Citations is how the world keeps track of the origin of information, and I support the idea that Wikidata follows what the world has been doing for ages already. Egon Willighagen (talk) 11:30, 26 May 2016 (UTC)
  •   Comment As a result of the issues around this speedy property creation I have started an RFC to try and prevent future controversies. You are invited to comment at Wikidata:Requests for comment/Standards for property proposal discussions, but note that the RfC is about the general case in future, not this specific property. Thryduulf (talk: local | en.wp | en.wikt) 12:14, 27 May 2016 (UTC)

skype

   Done: Skype username (P2893) (Talk and documentation)
DescriptionSkype instant messenger user name
Data typeURL
Template parameterskype in voy:de:vorlage:vCard at Template:Listing (Q14330485), used in German-language Wikivoyage only. See [13] for URL format
DomainWikivoyage listings (de)
Allowed valuestext, possibly an instance of website account on (P553)
Example
⟨ Grand Lodge ⟩ skype Search ⟨ participant1 ⟩
Formatter URLskype:$1

  Done as Skype username (P2893). However, @K7L, Jura1: please add an example at the property page. @Ymblanter, Nikki, Srittau, Pigsonthewing: --Izno (talk) 20:59, 6 June 2016 (UTC)


competitor or team promoted and competitor or team relegated

competitor or team promoted

   Done: promoted (P2881) (Talk and documentation)
Descriptionpromoted teams
Data typeItem
Template parameter"promoted" in en:template:Infobox football league season
Domainsports league (Q623109)
Allowed valuesQ template
Example2014–15 Football League (Q16820418) → AFC Bournemouth (Q19568) -->
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsYes

competitor or team relegated

   Done: relegated (P2882) (Talk and documentation)
Descriptionrelegated teams
Data typeItem
Template parameter"relegated" in en:template:Infobox football league season
Domainsports league (Q623109)
Allowed valuesQ template
Example2014–15 Football League (Q16820418) → Cheltenham Town F.C. (Q48932) -->
Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsYes
Motivation

Hello. At most leagues seasons in many sports some teams are promoting and some teams are relegated. For example, AFC Bournemouth (Q19568) had promoted when competed in 2014–15 Football League (Q16820418). I couldn't find a property that already exists to add these claims in wikidata pages. You can read Wikidata:Project chat#Properties for Promoted and Relegated teams. We can also have a qualifier "promoted to"/"relegated to" . Xaris333 (talk) 22:45, 21 May 2016 (UTC)

Discussion
We maybe also have to find a qualifier for those who have been promoted/relegated by other reasons than the pure results. "bankruptcy" is for example common reasons why teams are relegated here. -- Innocent bystander (talk) 08:05, 22 May 2016 (UTC)
has cause (P828) would work I think. Thryduulf (talk: local | en.wp | en.wikt) 11:19, 22 May 2016 (UTC)
Looks fine!   Stöder then! - -Innocent bystander (talk) 05:57, 23 May 2016 (UTC)

@Xaris333, Innocent bystander, Thryduulf, Edgars2007:   Done now properties promoted (P2881) and relegated (P2882) --Lymantria (talk) 20:30, 31 May 2016 (UTC)

most valuable player

   Withdrawn
Descriptionmost valuable player in tournament or game
Representsmost valuable player award (Q652965)
Data typeItem
Domainhuman (Q5)
Example2015 IIHF World Championship (Q4401): Jaromír Jágr (Q295345)
Motivation

Pretty important information for tournaments. It can be also for "player of the match", "best player of game/tournament". Edgars2007 (talk) 10:06, 22 May 2016 (UTC)

Discussion

NIOSHTIC-2 ID

   Done: NIOSHTIC-2 ID (P2880) (Talk and documentation)
DescriptionIdentifier in the NIOSHTIC-2 database
Data typeExternal identifier
Domainanything that is an instance of an item that is a subclass of publication
Allowed valuesintegers
ExampleEffect of microorganisms on in situ uranium mining (Q23923328) → 10003252
Sourcehttps://www2a.cdc.gov/nioshtic-2/
Formatter URLhttp://www.cdc.gov/niosh/nioshtic-2/$1.html
Motivation

I am working on migrating NIOSHTIC, the database of NIOSH sponsored research, to Wikidata. Many of the entries have DOIs, PubMed IDs, and/or PMC IDs. However, not all of them do. Adding the NIOSHTIC-2 ID will help with this process. James Hare (NIOSH) (talk) 04:24, 20 May 2016 (UTC)

Discussion

@James Hare (NIOSH), Pigsonthewing, Strakhov:   Done now NIOSHTIC-2 ID (P2880) --Lymantria (talk) 05:31, 31 May 2016 (UTC)

Swedish county letter

DescriptionLetter for county of Sweden
RepresentsCounty letter (Q10571932)
Data typeExternal identifier
Template parameterbokstav in sv:Mall:Länsfakta
Domainpresent and former countys of Sweden and Stockholm City (Q10680648)
Allowed valuesA-Z + AC, AB, BD
ExampleÖrebro County (Q104257):T
Format and edit filter validationA regex according to the above would be nice
SourceWikipedia
Robot and gadget jobsLimited usage. Can be done manually.
Motivation

This can be seen as a subproperty of ISO 3166-2 code (P300), but the format is different. (No land-code) And this code has probably been in use much longer than the ISO-codes. Regarding the string vs external-id question, I have still not understood the point of external-id yet, so I leave that to the discussion.

This information can partly be found in licence plate code (P395), but it is not an exact match, since the Stockholm City and Stockholm County has used other codes for registration plates than these codes. Stockholm County changed its code 1969. Some codes of former countys like "Malmöhus" and "Göteborgs och Bohus" have been reused by the new countys of "Skåne" and "Västra Götaland". -- Innocent bystander (talk) 05:58, 25 May 2016 (UTC)

Discussion
Innocent bystander - how do you plan to handle the code re-use issue, attach a date qualifier? In general external id properties shouldn't use qualifiers though I suppose if there are only a few cases it's ok. I assume there's no formatter URL that would link the code to a web page for the county? ArthurPSmith (talk) 20:58, 6 June 2016 (UTC)
@ArthurPSmith: No, there is no formatter URL I am aware of. Code re-use is not a problem, since "Göteborg and Bohus"/"Malmöhus" and "Västra Götaland"/"Skåne" did not coexist. The former was dissolved when the latter was founded. The only cases, when we have to use a qualifier is probably for Stockholm County and Stockholm City. Stockholm City was a "County free area" until 1968 and had a county letter of its own until then ("A"). And Stockholm County had "B" until the merge with the City and thereafter got the letter "AB". Those cases are the only cases in need of (time) qualifiers. Stockholm City maybe have to have "novalue" from 1968, when it became a part of Stockholm County. (Stockholm City was replaced by Stockholm Municipality in 1971, when all Swedish citys were dissolved.) One possible issue here is if Over-Governors office (Q4994097), who de facto was the county administration in Stockholm City, should have this letter too or if it should have it instead of Stockholm City. The "Over-Governor of Stockholm" is not really regarded as a territorial administrative entity like countys are, but it had its functions in Stockholm City. -- Innocent bystander (talk) 07:12, 7 June 2016 (UTC)
@ArthurPSmith, Jura1: et al. Is this "ready"? -- Innocent bystander (talk) 16:15, 9 June 2016 (UTC)
if it's intended to be restricted to Sweden only it should have a longer label including something about Sweden. If it's intended to be possible to use this property for other countries, I don't think it should be an external identifier (abbreviations generally should be string type unless they really are unique somehow). ArthurPSmith (talk) 19:20, 9 June 2016 (UTC)
@ArthurPSmith: It is not essential to restrict this to only Sweden. The Swedish set of items is so small, that I do not see such a generalization as a problem. I am just not aware of anywhere else where we have letter-non-ISO-codes for administrative levels. The label gives us no problems, it can easily be generalized. But if we should generalize this, the subject item cannot be County letter (Q10571932) since that item specifically describes Sweden (Q34). -- Innocent bystander (talk) 06:38, 10 June 2016 (UTC)
@Innocent bystander: ok I   Support this with the name change I just gave here (note it matches Swedish urban area code (P775) and several other related properties. ArthurPSmith (talk) 14:17, 10 June 2016 (UTC)
@ArthurPSmith, Jura1: Created as Swedish county letter (P2898) -- Innocent bystander (talk) 15:36, 10 June 2016 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Archive/52&oldid=1102554705"