Wikidata:Property proposal/Archive/27

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Discussion

The BBC have just launched their Genome database of all their broadcast programmes, based on listings in the Radio Times. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:22, 16 October 2014 (UTC)

 Support But I would change the name to "BBC Radio Genome identifier", otherwise it seems to have something to do with genomes.--Micru (talk) 09:48, 18 October 2014 (UTC)

These identifiers are not just for radio programmes. I don't see any realistic possibility of harm from such a misunderstanding. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:57, 18 October 2014 (UTC)

 Support clearly useful. If anyone wishes to educate me, I'm curious whether this also falls under Wikidata:Property_proposal/Authority_control or not. --Mike Linksvayer (talk) 20:34, 18 October 2014 (UTC)

I can't see a statement of scope on that page. Strictly, Genome is not an Authority Control service; practically its IDs can function in that way, though semantically, they refer to a listing entry, not a programme. BBC programme ID (Q17361898) (see en:BBC Programme Identifier) performs that function better, but for a much smaller (post 2007, mainly) set of BBC programmes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:01, 19 October 2014 (UTC)

 Done @Pigsonthewing, Mike Linksvayer:--Micru (talk) 16:53, 21 October 2014 (UTC)

Discussion

Motivation. We need this property to link items to their lists.Oursana (talk) 13:26, 12 August 2014 (UTC)

•  Question: I fail to see why we need to link items to lists. And I fail to see the purpose of items such as island of Japan (Q17308006) in the example. The items for any Japanese island, can just have statements declaring them to be 1) Japanese, and 2) islands, so why should they need island of Japan (Q17308006)? Please explain, regards Dipsacus fullonum (talk) 23:40, 15 August 2014 (UTC)

 Not done Lack of support and probably redundant with queries.--Micru (talk) 08:53, 18 October 2014 (UTC)

Discussion

See discussion at en.WP. Alternative property name could be "MalaCard". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:01, 27 October 2014 (UTC)

Tobias1984
Doc James
Bluerasberry
Gambo7
Daniel Mietchen
Andrew Su
Andrux
Pavel Dušek
Mvolz
User:Jtuom
Chris Mungall
ChristianKl
Gstupp
Sintakso
علاء
Adert
CFCF
Jtuom
Drchriswilliams
Okkn
CAPTAIN RAJU
LeadSongDog
Ozzie10aaaa
Marsupium
Netha Hussain
Abhijeet Safai
Seppi333
Shani Evenstein
Csisc
TiagoLubiana
ZI Jony
Antoine2711
JustScienceJS
Scossin
Josegustavomartins
Zeromonk
The Anome
Kasyap
JMagalhães
Ameer Fauri
CorraleH

Notified participants of WikiProject Medicine -Tobias1984 (talk) 16:31, 27 October 2014 (UTC)

 Support I support the property and the inclusion in Wikidata, but the inclusion in the disease-infobox on en-wiki is, and the same goes for all those cryptic identifiers, a sub-optimal usage of infoboxes. 99 % of readers will not read those codes, nor follow the links to the sites, which are usually intended to be consumed by experts. In my opinion the infobox should give basic information to basic questions a reader might have: "how can I get this disease?", "how do I know I have it?", "is it treatable?". Even if we simplify, what is a very complex multi-variate system, we can still offer a quick overview and link to the sections within the text, where we can place all the statistic information and the "and, or, if else" information. I would rather have some over-simplified information and guide the reader to the appropriate section than these codes which probably lead many people to give up reading the information in the first place. -Tobias1984 (talk) 16:31, 27 October 2014 (UTC)

That's not really relevant here, but thanks for your support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:48, 27 October 2014 (UTC)

 Support I support the property as the data linked to clearly looks valuable. However, I do have some reservations based on their licensing.. "If you are not an academic non-profit institution, in order to access and use MalaCards, you must obtain a license by paying applicable licensing fees".  – The preceding unsigned comment was added by Genewiki123 (talk • contribs).

I'll put that to them, but like many website ToU's they're unenforceable legalistic bullshit ("these ToU shall constitute a legally binding agreement between you and YEDA"). Not to worry, as all we'd be storing is, effectively, URLs. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:48, 27 October 2014 (UTC)

 Support I support the addition of the property in Wikidata, their data look quite comprehensive, as long as there is no issue with the licensing. What I'd like to discuss more is what should be in the infoboxes of Wikipedia, as Tobias1984 mentioned above. Emitraka (talk) 02:30, 28 October 2014 (UTC)

 Support, precisely per Tobias1984. Emw (talk) 11:45, 28 October 2014 (UTC)

 Done @Pigsonthewing, Tobias1984, Genewiki123, Emw: --Micru (talk) 19:02, 28 October 2014 (UTC)

Discussion

This property will be used to separate the plant from the fruit it produces. In cases like wine making, it makes no sense to say that the wine is made out of the plant, but out of the fruit. The inverse property (fruit of) is also needed. --Micru (talk) 12:31, 17 August 2014 (UTC)

 Comment - I think that "fruit of" would be the better property as most properties go this direction (e.g. part of, subclass of). We don't really need the inverse property because it is a simple query. Just to be critical we should also consider making a qualifier to "part of" which could be named "part concerned --> fruit". Also: how well is "fruit" defined in Biology? -Tobias1984 (talk) 12:39, 17 August 2014 (UTC)

WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. -Tobias1984 (talk) 12:39, 17 August 2014 (UTC)

perhaps better "product of". It is not just fruits, but also seeds, leaves, roots, wood, etc. It is possible for one plant to yield more than one product (flax gives oil and fiber). And fruits are well definied in biology but this does not match with the culinary definition (tomatos are fruits biologically, but a vegetable culinary; strawberries are fruits culinary, but not biologically, etc). Also, the same may apply to animals; should there be two properties or just one? - Brya (talk) 13:03, 17 August 2014 (UTC)

@Tobias1984, Brya: I have realized that we have the property product, material, or service produced or provided (P1056) but only for manufacturing, I think it could be generalized. As for this one I have changed the label to "product of" which is generic enough to cover all cases. What do you think?--Micru (talk) 13:05, 22 August 2014 (UTC)

@Micru, Tobias1984, Brya: seems useful for all kind of processes. we almoest could have a input/output property pairs, for maths I'll suggest a function range / function domain property pair. TomT0m ^(talk) 13:52, 22 August 2014 (UTC)

Good. I would like it to be limited to products of living things. That is big enough. Generalizing it more may lead to unforeseen complications. - Brya (talk) 17:30, 22 August 2014 (UTC)

@Brya, Micru: With the current name this property will be used in a lot of places. But after a few months we might be able to see patterns in the data and will be able to split it into different properties (Or we might see that we don't have any problems. -Tobias1984 (talk) 09:29, 24 August 2014 (UTC)

@Tobias1984, Brya: What do you think of calling it "raw product of" without limitation to living organisms? That way we'd avoid unintended uses, or we could create two properties at once, the other one being "manufactured product of". One of the examples reads Zinfandel wine (Q17329207) => Zinfandel (Q204433), and that is actually a manufactured product since it requires a human-staged process.--Micru (talk) 11:50, 24 August 2014 (UTC)

@Tobias1984, Micru: I don't like the look of "raw product of", and was thinking of either "natural product of" or "product of taxon"? - Brya (talk) 14:39, 24 August 2014 (UTC)

@Tobias1984, Brya: Changed the label to "natural product of taxon". If there are no objections, I will create it in a couple of days.--Micru (talk) 10:17, 19 October 2014 (UTC)

OK. - Brya (talk) 10:20, 19 October 2014 (UTC)

 Support --AmaryllisGardener ^talk 14:52, 21 October 2014 (UTC)

 Support - belatedly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:04, 21 October 2014 (UTC)

 Done @Brya, Pigsonthewing, Tobias1984, AmaryllisGardener, TomT0m:.--Micru (talk) 18:45, 28 October 2014 (UTC)

Good, this is progress. - Brya (talk) 06:39, 29 October 2014 (UTC)

Discussion

It would be used to store WLM data that at the moment is not on Wikidata. KRLS (talk) 19:59, 27 October 2014 (UTC)

 Support - but please populate Q1019352. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:15, 27 October 2014 (UTC)

 Support --Micru (talk) 21:39, 30 October 2014 (UTC)

 Support --Davidpar (talk) 15:14, 31 October 2014 (UTC)

•  Done -Tobias1984 (talk) 16:56, 31 October 2014 (UTC)

Discussion

See above for motivation. This one could also be useful to track subjects of an eventual Wiki Loves Monuments competition (not organized in the country yet because the lack of FOP is a problem, but it should be overcome some day). — Yerpo ^Eh? 17:05, 29 October 2014 (UTC)

•  Support But datatype has to be string. -Tobias1984 (talk) 19:11, 29 October 2014 (UTC)

  You're right, I fixed the proposal. — Yerpo ^Eh? 19:23, 29 October 2014 (UTC)

•  Done -Tobias1984 (talk) 16:59, 31 October 2014 (UTC)

Discussion

This would be genuinely helpful for modern authors, musicians, and maybe even corporations that maintain blogs seperate from their official websites. DunDunDunt (talk) 12:09, 8 October 2014 (UTC)

 Support--Micru (talk) 10:30, 18 October 2014 (UTC)

 Support --AmaryllisGardener ^talk 14:45, 21 October 2014 (UTC)

 Support sounds sensible--Giftzwerg 88 (talk) 08:08, 26 October 2014 (UTC)

Why not use 'Official website', with a qualifier? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:42, 25 October 2014 (UTC)

official blog and official website are a little bit different entities. Also maintaining, adding, using and etc. different properties is more simple, this is importaint for popular properties like this. — Ivan A. Krestinin (talk) 18:40, 27 October 2014 (UTC)

Thank you. I understand the differences, but you haven't said convincingly why we need separate properties, rather than the 'qualifier' solution I proposed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:18, 27 October 2014 (UTC)

 Support — Ivan A. Krestinin (talk) 18:40, 27 October 2014 (UTC)

 Done @DunDunDunt, AmaryllisGardener, Pigsonthewing, Ivan A. Krestinin: --Micru (talk) 18:40, 28 October 2014 (UTC)

Discussion

Pleiades is "a community-built gazetteer and graph of ancient places" collecting more than 34,000 places of the Ancient world (mostly Greek-Roman but expanding to other regions and periods). Each place is given a unique URI. Resources available for each place include geographic locations, names and references. In some cases DBPedia/Wikipedia are linked as references, facilitating the semi-automated addition of data here. As of now an experimental alignment with GeoNames has been tried https://github.com/ryanfb/pleiades-plus . Either the full URI or the numeric ID could be used as property value. As the author of this proposal I also disclose that I am a contributor and reviewer of Pleiades. Steko (talk) 13:35, 19 August 2014 (UTC)

For similar indices we have used the 'string' datatype to just store the code number rather than storing the full 'URI'. A little automagic is then used to turn this into a 'URI'. That way a change in the make-up of the URI can be accommodated without having to change every instance. Filceolaire (talk) 05:24, 28 August 2014 (UTC)

Yes, that makes sense, even though Pleiades URIs are meant to be "cool URIs" that won't change, they aren't really special compared to e.g. VIAF ones. Feel free to edit the proposal as you see fit - especially for the datatype and example usage. Thank you for your feedback.--Steko (talk) 15:33, 1 September 2014 (UTC)

I have changed the dataype. The example is still using URLs to be more clear.--Steko (talk) 16:43, 3 September 2014 (UTC)

 Support --Micru (talk) 07:25, 21 October 2014 (UTC)

 Support Eurodyne (talk) 19:57, 29 October 2014 (UTC)

 Support -Tobias1984 (talk) 20:30, 29 October 2014 (UTC)

• @Steko, Filceolaire, Micru, Eurodyne, Tobias1984:  Done --Jakob (talk) 19:24, 30 October 2014 (UTC)

Discussion

Das IBGE, Instituto Brasileiro de Geografia e Estatística (Q268072), hat sämtlichen municípios, vergleichbar unseren Gemeinden (Q3184121) als territoriale Verwaltungseinheit eines brasilianischen Bundesstaates, einen eindeutigen 7-stelligen Code vergeben, beginnend mit der 2-stelligen Bundesstaatnummer. Es handelt sich um 5.570 municípios.

Unter diesen Codierungen sind sämtliche statistische Angaben zu einer Gemeinde in den Datenbanken des IBGE abrufbar, diese Seiten werden mit den Ortsartikeln verlinkt. Die Verankerung (parameter) in den Infoboxen (in der de:WP zu brasilianischen Orten ist vorgesehen - neue erweiterte Infobox), ebenso wird sie bereits bei Ortsartikel in der pt:WP unsichtbar erfasst, aber wird z.B. in Q14407124 noch nicht angezeigt (dortiger Änderungsantrag in der pt:WP ist ebenfalls notwendig).

Vergleichbar sind: P771 Schweiz, P911 Südafrika, P964 Österreich. Do not confuse with (Q17294166) for Portugal.

Motivation? Like to bring some life into Wikidata:Country subdivision task force/Brazil, step one. Emeritus (talk) 01:11, 10 July 2014 (UTC)

•  Support--Micru (talk) 09:12, 18 October 2014 (UTC)
•  Support--Pasleim (talk) 17:46, 26 October 2014 (UTC)
•  Comment The datatype should be string instead of number. --Pasleim (talk) 17:48, 26 October 2014 (UTC)
• @Emeritus, Micru, Pasleim:  Done as a string. --Jakob (talk) 19:28, 30 October 2014 (UTC)

A desa is an administrative village in Indonesia. Each entity has a code desa used in statistics. masin use is for villages, although property can also be used for indicating regency or subdistrict (shorter number). A string is used instead of number (because code of a subdistrict starts with 0, e.g. 030). Michiel1972 (talk) 09:37, 4 September 2014 (UTC)

•  Support --Micru (talk) 09:12, 18 October 2014 (UTC)
•  Support --Pasleim (talk) 17:51, 26 October 2014 (UTC)
•  Done -Tobias1984 (talk) 17:10, 31 October 2014 (UTC)

Discussion

Мотивация Dimon4ezzz (talk) 12:05, 12 July 2014 (UTC)

 Oppose. We have software version identifier (P348), it could be renamed to "last version" with qualificator of (P642) related to stable version (by default) or to beta version (Q14946400) for beta versions. -- Vlsergey (talk) 07:52, 21 July 2014 (UTC)

•  Not done -Tobias1984 (talk) 17:16, 31 October 2014 (UTC)

Discussion

I would like to make Pokémon items as complete as possible with as many data as needed to. Ju gatsu mikka (talk) 08:57, 25 September 2014 (UTC)

 Oppose "Type" properties are discouraged. Use subclass of (P279) to build the ontology. -Tobias1984 (talk) 15:27, 29 September 2014 (UTC)

 Oppose per Tobias. --AmaryllisGardener ^talk 16:02, 29 September 2014 (UTC)

 Not done -Tobias1984 (talk) 17:17, 31 October 2014 (UTC)

Discussion

Like number of deaths (P1120), this property would be used to track basic data about the human cost of accidents, natural disasters, military conflicts and other events. Emw (talk) 14:26, 28 September 2014 (UTC)

•  Support Could be useful. --Eurodyne (talk) 14:12, 7 October 2014 (UTC)
•  Strong support highly important property. --Jakob (talk) 21:58, 11 October 2014 (UTC)
•  Support --AmaryllisGardener ^talk 15:00, 21 October 2014 (UTC)
•  Comment @Jakec, Eurodyne, Emw: Waiiit a minute... number of injured (P1339), created in June, by Jakob. --AmaryllisGardener ^talk 15:06, 21 October 2014 (UTC)

Discussion

In disasters, it is often unclear how many of those adversely affected are dead and how many are injured. In such cases the term "casualty" is used. This property would be used in cases where data for number of deaths (P1120) and number of casualties (see proposal above) are unavailable. Emw (talk) 14:38, 28 September 2014 (UTC)

•  Support Eurodyne (talk) 00:24, 17 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:03, 2 November 2014 (UTC)

 Done -Tobias1984 (talk) 17:25, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done -Tobias1984 (talk) 17:32, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done -Tobias1984 (talk) 17:37, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done -Tobias1984 (talk) 17:39, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done -Tobias1984 (talk) 17:41, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done --Tobias1984 (talk) 17:42, 3 November 2014 (UTC)

Discussion

One of a series of related proposals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 20 October 2014 (UTC)

•  Support --AmaryllisGardener ^talk 15:10, 21 October 2014 (UTC)
•  Support. This will need qualifiers. 'Fine' will need a qualifier with the amount. 'Probation' will need a duration. 'Imprisonment' will need qualifiers for 'sentence duration', 'time served', 'release date', 'place of imprisonment'. Filceolaire (talk) 15:19, 2 November 2014 (UTC)
•  Support. Emw (talk) 13:34, 3 November 2014 (UTC)
•  Done --Tobias1984 (talk) 17:44, 3 November 2014 (UTC)

Discussion

An official designation of cultural heritage (structures, events) by the Slovene government, would be useful to track existing/missing articles about cultural heritage. See also the request below. — Yerpo ^Eh? 17:05, 29 October 2014 (UTC)

 Support If you like you could add the information about Slovenia in the table at Wikidata:WikiProject Cultural heritage. -Tobias1984 (talk) 19:40, 29 October 2014 (UTC)

That table is meant for countries with existing WLM database entries, no? The thing is, we tried to get the raw dataset for monuments from the authorities a few years ago, but they wouldn't release it because some objects aren't in a "presentable" state. We got a subset of 2000 objects, but that one we aren't allowed to share with a third party. So we are limited to making individual queries in the web search engine to retrieve IDs and designations. — Yerpo ^Eh? 14:27, 30 October 2014 (UTC)

@Yerpo: I understand. We will just have to work with what we got. -Tobias1984 (talk) 19:41, 31 October 2014 (UTC)

 Support--Giftzwerg 88 (talk) 14:39, 1 November 2014 (UTC)

 Done --Tobias1984 (talk) 17:48, 3 November 2014 (UTC)

Discussion

In many parts of the Christian Church (Q34651), the legitimacy of each bishop (Q29182) is tied to apostolic succession (Q49482): the chain by which each bishop (Q29182) received his new holy orders (Q662862) from an existing bishop (Q29182), in a line putatively back to an apostle (Q43412). Not all Christian denominations practice this, but it's very important for Catholic Church (Q9592) and some others.

This property's parameter is called the consecrator and co-consecrator (Q4231232) of the item: one or more earlier bishop (Q29182) by which this item received legitimacy as a new bishop (Q29182).

Each item that is a bishop (Q29182) (or subclass) should have multiple of this property, each with an earlier bishop (Q29182) (or subclass) as the parameter. This is because, even though only one consecrator and co-consecrator (Q4231232) is necessary, the apostolic succession (Q49482) is so important that usually there are 2 or 3 "principal" people performing the act: the main bishop (Q29182) performing the ceremony is the "principal consecrator"; another 1 or 2 assist with the ceremony and are called "principal co-consecrators"; the presence of these at the ceremony is well-documented, so that even if the principal consecrator is somehow invalid, the principal co-consecrators cause the ceremony to be valid. Apparently, there are often many other of bishop (Q29182) at the ceremony, who are simply called "co-consecrators" and are less-documented.

This property is not the same as appointed by (P748). A person must first achieve the personal status of bishop (Q29182): the people responsible for that act are named by this parameter; and those people must already have the status of bishop (Q29182). The new bishop (Q29182) then is assigned to one or more of episcopal see (Q2902010); in the Catholic Church (Q15924454), for example, the appointed by (P748) for each assignment is almost always a pope (Q19546). --Closeapple (talk) 00:01, 25 October 2014 (UTC)

•  Support --- Jura 17:28, 27 October 2014 (UTC)
•  Support -- Gymel (talk) 23:52, 27 October 2014 (UTC)
•  Support Filceolaire (talk) 22:49, 31 October 2014 (UTC)
•  Support --Giftzwerg 88 (talk) 15:06, 1 November 2014 (UTC)
•  Done -Tobias1984 (talk) 17:51, 3 November 2014 (UTC)

Discussion

Info199 (talk) 21:17, 13 October 2014 (UTC)

•  Support--Micru (talk) 09:19, 18 October 2014 (UTC)
•  Support --AmaryllisGardener ^talk 14:56, 21 October 2014 (UTC)
•  Oppose In my opinion this is a query and not a property. We have a lot of notable geographic items that can have the property "elevation". Finding the lowest or highest is a simple query. The lowest and highest point of any country will always be notable and we can create items for them if they are missing. -Tobias1984 (talk) 17:24, 26 October 2014 (UTC)
•  Support Tobias1984 in some cases the lowest point is only notable for being the lowest point so I think a separate property is useful. Filceolaire (talk) 21:15, 31 October 2014 (UTC)

@Filceolaire: I think stating this properties is also fine. But the problem with that approach is, that the second highest/lowest point is also notable and then the third highest/lowest. In that case it would be better to just have "notable point" with a qualifier to describe the notability? In any case this property has enough support so I will create it. -Tobias1984 (talk) 21:41, 31 October 2014 (UTC)

 Done -Tobias1984 (talk) 22:20, 31 October 2014 (UTC)

@Info199, Micru, AmaryllisGardener, Filceolaire: -Tobias1984 (talk) 22:21, 31 October 2014 (UTC)

Discussion

Alumni Cantabrigienses is a ten-volume directory listing all known students of the University of Cambridge up to 1900, with around 130,000 entries. The University Library at Cambridge has supported an online version of this ("ACAD", at venn.lib.cam.ac.uk) which has assigned an identifier to every entry and allows a static URL to be generated (see, eg, PRKR685T).

There are currently around 5000 links to ACAD on enwiki. Andrew Gray (talk) 17:32, 15 September 2014 (UTC)

• This would be useful to have. It can be noted that many Oxford graduates are also included, where their degrees were recognised by Cambridge, something quite common in past centuries. So for British history the site is a substantial resource including notable people. Charles Matthews (talk) 11:03, 18 September 2014 (UTC)
•  Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:05, 19 October 2014 (UTC)
•  Support Mushroom (talk) 11:53, 26 October 2014 (UTC)
•  Support Fabian Tompsett (WMUK) (talk) 19:42, 5 November 2014 (UTC)

 Done -Tobias1984 (talk) 16:45, 7 November 2014 (UTC)

Discussion

It would be used to store WLM data that at the moment is not on Wikidata. KRLS (talk) 16:28, 31 October 2014 (UTC)

@KRLS: We can probably save the identifier without the "IPAC-" prefix? -Tobias1984 (talk) 16:41, 31 October 2014 (UTC)

@Tobias1984: Changed. "IPAC" prefix is not necessary.--KRLS (talk) 19:05, 3 November 2014 (UTC)

 Support--Kippelboy (talk) 11:48, 3 November 2014 (UTC)

 Support--Davidpar (talk) 21:49, 3 November 2014 (UTC)

 Done --Tobias1984 (talk) 16:49, 7 November 2014 (UTC)

Discussion

This proposal follows a discussion on Project chat in which I described my work on making this resource available on Wikisource as part of a scientific project. One participant of the discussion encouraged me to propose a new property. The address book, issued over a period of 21 years, contains data about some 22,000 early Esperantists (see sample page). First analyses suggest that approximately 8 % of them are notable (at least on Esperanto Wikipedia and the Wikipedia in the person's mother tongue). This should eventually yield some 1750 uses of this property on Wikidata and lead to easier infobox data sharing across languages. A script could link the individual records in the digitized version of the address book on Wikisource to the corresponding Wikidata items. Blahma (talk) 01:36, 3 November 2014 (UTC)

•  Support assuming the number is stable across the editions. --- Jura 08:03, 3 November 2014 (UTC)

The number is stable indeed. Every person got listed only once and each part of the series added new people but did not modify the previous lists. All subsequent reprints (that I work with) are merely photocopies of the original lists. Publications on the history of Esperanto tend to mention the person's number as a proof of his/her activity at certain time. --Blahma (talk) 14:55, 3 November 2014 (UTC)

 Support. Filceolaire (talk) 20:21, 3 November 2014 (UTC)

 Support. Tout à fait utile pour les rubriques sur des espérantistes et cela constituera un levier pour l'utilisation du wikidata. --Pinof (talk) 07:56, 4 November 2014 (UTC)

 Support Sound reasonably and useful, Blahma in general know what he is doing. --KuboF (talk) 20:36, 4 November 2014 (UTC)

 Support. Eminently sensible. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:28, 4 November 2014 (UTC)

•  Done --Tobias1984 (talk) 16:51, 7 November 2014 (UTC)

Discussion

We already have Art UK artist ID (P1367) for artists. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:53, 17 October 2014 (UTC)

•  Support --Micru (talk) 09:21, 18 October 2014 (UTC)
•  Support - PKM (talk) 22:02, 27 October 2014 (UTC)
•  Support --Oursana (talk) 22:09, 5 November 2014 (UTC)

 Done --Tobias1984 (talk) 18:03, 7 November 2014 (UTC)

Discussion

Number of cases is a basic epidemiological measurement of disease occurrence. Together with number of deaths (P1120), it helps quantify the burden of outbreaks. As seen in e.g. the Ebola Response Roadmap Situation Report, the World Health Organization defines number of cases as the sum of the number of confirmed, suspected and probable cases.

Data on disease outbreaks is often at different level of geography. For example in the 2014 Ebola outbreak, there is notable coverage in both the region of West Africa and also at the national level, e.g. Liberia. This also occurred in the 2009 flu pandemic. Because qualifiers will not be queryable in the foreseeable future, and to encourage creation of new items where applicable, it would be best to have 'number of cases' appear as a ground-triple in a specific item, and not as a qualifier in the general item. For example:

As ground-triple (recommended):

• Western African Ebola virus epidemic (Q15989108)

number of cases 13,703 point in time (P585) October 25, 2014

number of deaths (P1120) 4,922

has part(s) (P527) 2014 Ebola virus epidemic in Liberia (Q18208679)

• 2014 Ebola virus epidemic in Liberia (Q18208679)

number of cases 6,253

number of deaths 2,704

part of (P361) Western African Ebola virus epidemic (Q15989108)

As qualifier (not recommended):

• Western African Ebola virus epidemic (Q15989108)

number of cases 13,703 point in time (P585) October 25, 2014

number of deaths (P1120) 4,922

has part(s) (P527) 2014 Ebola virus epidemic in Liberia (Q18208679)

number of cases 6,253

number of deaths 2,704

Feedback welcome! Emw (talk) 03:24, 31 October 2014 (UTC)

Notified participants of WikiProject Medicine

Please see the properties proposed below, also. Thanks, Emw (talk) 04:24, 31 October 2014 (UTC)

Notified participants of WikiProject Medicine -Tobias1984 (talk) 20:32, 31 October 2014 (UTC)

Repinging: I don't think the first ping went through the system. -Tobias1984 (talk) 20:34, 31 October 2014 (UTC)

 Support -Tobias1984 (talk) 20:34, 31 October 2014 (UTC)

 Support. Filceolaire (talk)

 Support. Emitraka (talk) 14:22, 3 November 2014 (UTC)

•  Done --Tobias1984 (talk) 18:06, 7 November 2014 (UTC)

Of interest for pathogenic organisms. Emw (talk) 13:00, 31 October 2014 (UTC)

 Support Mvolz (talk) 23:16, 31 October 2014 (UTC)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

 Done -Tobias1984 (talk) 18:14, 7 November 2014 (UTC)

For pathogenic organisms. I.e. Ebola -> fruit bat, West nile virus -> mosquitoes, mers-cov -> camels. Mvolz (talk) 23:16, 31 October 2014 (UTC)

•  Support. Mvolz, good idea. What do you think of changing the proposed label to "natural reservoir"? That seems to be the conventional label used in virology for this concept. Emw (talk) 12:56, 1 November 2014 (UTC)

A few more things!:

• Could we clarify in the description that pathogens can multiple natural reservoirs, e.g. "bubonic plague has natural reservoir marmots, black rats, prairie dogs, chipmunks and squirrels" per Natural_reservoir#Examples?

Done! Mvolz (talk) 17:53, 1 November 2014 (UTC)

• How about having an inverse property 'natural reservoir of' for this and tacking on 'has' to the front of the this property? This would be useful for users browsing around in a linked data UI who stumble upon, e.g. fruit bat, to learn it's a natural reservoir for Ebola. Emw (talk)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

Why not use host organism (Q221673)? Anopheles gambiae is a host for Plasmodium falciparum. Emitraka (talk) 14:28, 3 November 2014 (UTC)

•  Done --Tobias1984 (talk) 18:19, 7 November 2014 (UTC)

In addition to seeing that, for example, fruit bats are a natural reservoir for Ebola on the page for Ebola, it'd be convenient to also see that information on the page for fruit bats. Emw (talk) 13:24, 1 November 2014 (UTC)

 Support. Filceolaire (talk) 23:25, 2 November 2014 (UTC)

•  Done --Tobias1984 (talk) 18:22, 7 November 2014 (UTC)

→ Property:P1571

   Done: definition domain (P1568) (Talk and documentation)

Description	relations to link definition domains domain of a function (Q192439)    of functions or partial function and relations ; (domain/codomain are for the subsets of the input/set where a (partial) function always a value , input / output sets are for any relation.
Data type	Item
Domain	domain and codomain : mapping (Q370502) / function (Q11348) / morphism (Q1948412) (?) / morphism (Q1948412)  ; input set / output set : binary relation (Q130901)
Allowed values	set (Q36161) / class (Q217594) (?) / morphism (Q1948412) (?) in category theory (Q217413)
Example	⟨ square function (Q3075175) ⟩ domain Search ⟨ real number (Q12916) ⟩  ; ⟨ square function (Q3075175) ⟩ range Search ⟨ real number (Q12916) > 0 ⟩ (don't have any partial function item yet)
Proposed by	TomT0m (talk)

Discussion

There is a lot of mathematical functions and so on articles. TomT0m ^(talk) 15:47, 22 August 2014 (UTC) }}

•  Support. Maybe it would be better to call it domain and codomain of a mapping, it would also apply to functors. Some people use the word "function" only for number-valued functions and "mapping" in other cases, for example there are rational mapping (Q987226) and rational function (Q41237). Danneks (talk) 05:05, 23 August 2014 (UTC)

• Yes, terminology issues can be complex :/ (I lost myself in Wikipedia writing this proposal ^^) (not to mention idiosyncrasys). I tend to agree we should have a scope as big as possible for properties and to split them only for good reasons. Still can't decide if it is useful to have two distinct pairs of properties. I guess we must be careful not to introduce ambiguities. TomT0m ^(talk) 11:11, 23 August 2014 (UTC)

• Technically speaking, we have several distinct concepts here. I'm not sure that we need "domain of a functor" property right now, since we don't have many such items, and terminology of domains is not much used. For most of morphisms, it will be enough to specify category to which this morphism belongs (and "part of" applies perfectly here). So we only need domain and codomain of a function; we can write in description "(co)domain of a mapping between sets" to avoid ambiguity. Danneks (talk) 14:28, 23 August 2014 (UTC)

•  Support. I would use only "domain" and "codomain" for clarity and simplicity. Cuvwb (talk) 19:07, 12 October 2014 (UTC)
• @TomT0m, Danneks, Cuvwb:  Done --Jakob (talk) 18:42, 18 October 2014 (UTC)
  • @Jakec: Thank you, but what about domains? Danneks (talk) 20:31, 18 October 2014 (UTC)

@Jakec, Danneks:. I think this was (implicitly) proposing 2 propoerties. I have changed the label of fr:P1568 to domain and created codomain (P1571).--Zolo (talk) 09:03, 19 October 2014 (UTC)

@TomT0m:, shouldn't the French label be "fr:ensemble de définition" rather than "fr:ensemble de départ" ?--Zolo (talk) 09:03, 19 October 2014 (UTC)

→ Property:P1607 → Property:P1608 → Property:P1609 → Property:P1610

Discussion

@Totemkin, HombreDHojalata: Use by Totemkin and other Spanish editors. --Akron stevens (talk) 01:33, 7 September 2014 (UTC)

 Comment ¡Discúlpame por no commentar en español! Dialnet and BNE Authorities National Library of Spain ID (P950) seem to have mutual knowledge about their respective identiifers: Dialnet links to VIAF using the BNE identifier, and the BNE authority view under "Obras" proves a link to Dialnet using the Dialnet codigo. It might be more useful to implement separate properties for authors (under "Authority control", cf. Template:Authority control properties), journals (comparable to ISSN (P236) and ZDB ID (P1042) - those don't seem to be kept together at some place yet) and articles. -- Gymel (talk) 12:48, 7 September 2014 (UTC)

Hi! Great idea! I agree with Gymel the best approach would be separated properties for "autor", "artículo" y "revista"... for example: "Identificador de autor en Dialnet" (Dialnet author identifier), "Identificador de artículo en Dialnet" (Dialnet article identifier), "Identificador de revista en Dialnet" (Dialnet magazine identifier). If not... we would have a single property named "Dialnet" in which we would have to add something like articulo?codigo=2234765 with articles, autor?codigo=307390100 with articles, etc. Weird. I don't know if (with a future development of Wikidata) we would be able to do this with a single property, through statements kinda "código Dialnet = 307390100" and qualifiers in the mold of "type=article", "type=magazine",... but I think it's science fiction right now. Cheers! —Totemkin (talk) 14:02, 7 September 2014 (UTC)

Hi @Totemkin:, how will this new property work with the template w:es:Plantilla:Dialnet? It is not quite elaborated (and only deals with persons). Best regards [07:34, 9. Sep. 2014‎ Discasto]

Uhmmm. @Discasto: Pues viéndolo así, desde la distancia, no veo mucha interacción posible a estas alturas del proyecto. Estas propiedades estarán, por ahora, enfocadas exclusivamente a Wikidata. Una vez se produzca la preconizada interacción Wikidata-Wikipedia (si algún día lo hace.. hehe) pues Wikipedia podrá usar estos datos. En concreto los de "Dialnet autor" podrían mostrarse automáticamente por ejemplo en una barra de "Authority control" junto con los VIAF's, ISNI's, etcéteras en los artículos respectivos de cada autor, con lo que todo el código de estas plantillas comenzaría a ser redundante. Ahora bien, esto hoy día está muy lejos (además las Wikipedia no confían lo suficiente en Wikidata para mostrar nuestra información de aquí). Ni siquiera hemos conseguido plantearnos centralizar los enlaces a las categorías de Commons solamente a través de Wikidata (básicamente hoy día se siguen mostrando a través del {{commonscat}}), así que todavía queda tiempo. Poniéndonos en plan constructivo, la única interacción posible en estos momentos se me ocurre que sería simplemente el importar datos desde esta plantilla en Wikipedia a Wikidata. Para ello haría falta alguien puesto en bots. (también se podría modificar la plantilla para que poniendo simplemente algo como {{Dialnet}} esta "chupara" el código desde Wikidata) Un saludo. (sorry for the Spanish)Totemkin (talk) 21:03, 10 September 2014 (UTC)

@Gymel, Totemkin, Discasto: You're right. I've now separated the different types of identifiers. So we need three properties: Dialnet authors, Dialnet journals and Dialnet works (mostly articles but also books). --Akron stevens (talk) 20:42, 10 September 2014 (UTC)

That's correct, there's also books! Totemkin (talk) 21:03, 10 September 2014 (UTC)

... and they have their own identifiers: So we need four properties. --Akron stevens (talk) 01:24, 11 September 2014 (UTC)

Actually above I had not noticed that one needs different URLs to access the notices of the individual kinds. So, definitely, distinct wikidata properties should be implemented. I'm quite in favor of the proposal for autores (classical "authority control" and there is existing data from the template on es:WP - oops: less than 50 inclusions) and revistas (Dialnet often lists individual volumes and provides their tables of contents for its 9000+ journals - that's impressive), however I'm not so sure about the individual listings for libros and articulos: They might be handy as "reference" as proposed and the articulos are cross-linked to the revistas, but especially for libros I don't see any advantage in comparison to taking more rich and detailed e.g. BNE notices as "reference" (nobody has proposed that yet, maybe only because it does not seem technically possible). Thus perhaps we should discuss four different proposals with their pro's and con's? -- Gymel (talk) 10:23, 11 September 2014 (UTC)

 Support Likely - like Gymel says - the book id is in this case less important, but imho we should add all four properties together and leave the decision which are the major Dialnet properties to the users. We don't know how Dialnet will develop (maybe books will be more important later). Beside we did the same in other cases. For example: We have added all 6 MusicBrainz IDs and it works well. --Kolja21 (talk) 23:54, 11 September 2014 (UTC)

 Support 4 properties though this should probably be on the Wikidata:Property proposal/Authority control page. Filceolaire (talk) 22:13, 31 October 2014 (UTC)

 Done --Tobias1984 (talk) 18:30, 7 November 2014 (UTC)

Discussion

(IRC is more relevant than Property:P553 for free software. see http://directory.fsf.org/ to see what I mean. I would love to add such entries as I do there.) genium ⟨✉⟩ 16:51, 30 October 2014 (UTC)

•  Support -Tobias1984 (talk) 18:02, 30 October 2014 (UTC)
•  Support Danrok (talk) 00:29, 31 October 2014 (UTC)

WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. Tobias1984 (talk) 18:02, 30 October 2014 (UTC)

• We still have to wait for the datatype. See bug report.
  Tracked in Bugzilla
  Bug 72924
  
  --Tobias1984 (talk) 21:31, 3 November 2014 (UTC)

•  Done --Tobias1984 (talk) 09:36, 17 November 2014 (UTC)

Discussion

Requested on Mix'n'match by GLAM community. Magnus Manske (talk) 10:02, 19 November 2014 (UTC)

 Support --Tobias1984 (talk) 10:07, 19 November 2014 (UTC)

 Support --Jane023 (talk) 10:21, 19 November 2014 (UTC)

 Support But should we just store the entity ID value ("942" in the example given) as a string? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:48, 19 November 2014 (UTC)

 Support and updated the proposal to remove possible confusion about what we're going to store. I'm quite sure Sarah will be pleased with this property too. Multichill (talk) 19:38, 21 November 2014 (UTC)

•  Done --Tobias1984 (talk) 21:47, 21 November 2014 (UTC)

Discussion

All French organisations and administrations have a legal identifier known as "numéro SIREN". (this is mandatory for having a legal identity, for any commercial billings, for ownning bank accounts, for requesting public subsidies; all billing forms MUST display it).

It is needed to create unique identifiers for many territorial collectivities and it is more precise than the "code INSEE" (for example used for communes but for various usages including the municipality itself, or any resident in that commune, or any other orgnisation or administration located in that area).

Basically it is NOT a geographical identifier (even if it may be assigned to entities defined geographically). Communes, prefectures, subprefectures, groupments of communes (EPCI), all have this identifier. Associated communes (within a commune) also have their distinctive Insee number and SIREN (because they manage their own "état-civil", even if they don't have a deliberating council and are not autonomous financially).

Its format is 9 digits (including the last "check digit" computed with the Luhn algorithm). Normally, all public administrations have a SIREN number starting by 2:

• For a commune in the French Metropole, its format is usually "21dd0nnnk" where dd is the department number (20 for both departements of Corsica), nnn is the commune number (the last three digits from its Insee code), and k is the Luhn check digit.
• For a commune in the French Overseas, its format is usually "219ddnnnk", where 9dd is the departement number (971 or higher), and "nnn" is also the last three digits of its Insee code (i.e. the last digit of he departement number repeated, and the two digits of the commune number)
• For any EPCI (groups of communes, including non-autonomous syndicates, and the new metropoles), its format is usually "240nnnnnk" (they are allocated sequentially without reference to a departement number. The SIREN code is the only valid unique identifier : Insee does not allocate a separate geographic code for them (like for national administrative subdivisions: regions, departement, arrondissement, commune) simply because EPCIs can span communes from several regions or departements. Note: for administrations competent within the same departement or same region (same Insee code) there are several SIREN numbers : one for the local council, a separate one for prefectures/subprefecture, possibly others for academies, or offices of tourism controled by a municipality (but the SIREN may encompass establishements or public properties located outside the territory of the public authority).

I request a new property similiar to the "code commune INSEE" for "numéro SIREN". It will be especially useful for EPCIs, but could be assigned to communes, departements, regions (for their local councils), prefectures and subprefectures. And of course for companies and associations.

Note:

The SIRET is an extension of the SIREN, but for geographic-specific establishments of the registered organisation. All organisations have a SIRET, assigned sequentially within the scope of their SIREN. The SIRET is made with the 9 digits of the SIREN, plus the 5 digits of a "NIC" number for the establishment (a number from 0001 to 7999, 0000 is reserved as a filler for data meant to cover the whole organisation without distinguishing its establishements, followed by a check digit), for a total of 14 digits (including the last check digit computed on the 14 digits of the whole SIRET with the Luhn algorithm).

I don't think we need SIRET numbers in data, but it's possible that we could reuse the same property, taking either 9 or 14 digits (SIREN or SIRET).

The "European VAT number" for organisations in France is made of a prefix ("FR" followed by 2 digits) and the 9 digits of the SIREN (there's a basic check algorithm which apparently uses a modulo 97 algorithm in the 2 digits of the prefix, but the format varies between European countries, so if needed it could be another separate property. It could be a substitute for the French SIREN, but only if we can confirm that the EU VAT number will keep this format in France so that we can safely extract the SIREN from it.

Verdy p (talk) 21:34, 10 November 2014 (UTC)

Could you clarify "It could be a substitute for the French SIREN, but only if we can confirm that the EU VAT number will keep this format in France so that we can safely extract the SIREN from it.". You mean it's not acceptable to print the FR prefix? --Dereckson (talk) 00:00, 11 November 2014 (UTC)

 Support. It appears that it can indeed be inferred from the VAT number, but it works both ways. Country-specific properties like SIREN seems to ne more convenient than the VAT number, because their format is more standardized which makes automated checks simpler. --Zolo (talk) 06:43, 20 November 2014 (UTC)

@Verdy p, Dereckson: property created as P:P1616 . ---Zolo (talk) 07:57, 22 November 2014 (UTC)

Discussion

I will ask the BBC for reciprocal links. (Update: Already includes reciprocal links; see http://www.bbc.co.uk/things/ddabf049-3cbe-4c83-a37f-94076caded7c ) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:57, 21 October 2014 (UTC)

Wow, the link gives „Torbay Council is an organisation” back. Thats a lot of usefull information.  Oppose --Succu (talk) 20:04, 21 October 2014 (UTC)

It also gives aliases, and other systems' identifiers. Did you examine any other items? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:35, 21 October 2014 (UTC)

 Wait I see that this database is still beta. Wouldn't it be better to wait until they officially release it? The structure of the identifiers might still change and it would just cause a lot of work. In general we have so much other work piling up, that something like this seems rather like a low priority. -Tobias1984 (talk) 20:18, 21 October 2014 (UTC)

No; it's functional and available, and the identifiers (and URLs) will persist. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:35, 21 October 2014 (UTC)

Checking your link I got a popup: „Let us know what you think”. I think, we don't need this, as a mentioned before. --Succu (talk) 21:43, 21 October 2014 (UTC)

The popup is a user-satisfaction survey, similar to those used by a number of sites to which we link. It has no bearing on this proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:48, 21 October 2014 (UTC)

 Oppose I saw value in other BBC identifiers, but not in this one. Maybe in the future.--Micru (talk) 22:00, 21 October 2014 (UTC)

@Micru: What leads you to suppose that this type of identifier has no value? Why is the timing an issue? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:20, 21 October 2014 (UTC)

 Support I see no reason why this cannot be added now. Should the identifiers ever change (and given that they are UUIDs, I don't see that happening) this property can always be renamed "BBC Things Beta ID". Adding it will allow data input to commence now, rather than delay it without good reason. Nickshanks (talk) 21:02, 24 October 2014 (UTC)

@Nickshanks: I see no real argument of yours. But again: What information we get regarding references etc. supporting a beta solution? --Succu (talk) 21:14, 24 October 2014 (UTC)

@Succu: I wasn't trying to present an argument, just stating my support. To back up my claim, I do not believe the identifiers will change because they (http URIs used to identify each concept) have been used behind the scenes at the BBC for several years. Only now are they publicly dereferencable. See [5], and the comment at foot of [6] for some background. Nickshanks (talk) 23:09, 24 October 2014 (UTC)

 Support Filceolaire (talk) 20:38, 31 October 2014 (UTC)

 Support per Nickshanks. Emw (talk) 13:42, 2 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:17, 23 November 2014 (UTC)

Discussion

Used in infoboxes. --AmaryllisGardener ^talk 02:29, 11 November 2014 (UTC)

 Support But is this a number-datatype? We won't be doing any calculations with it; We don't need floating points; Some sports have leading 0 on their jerseys. I think string-datatype would be more appropriate and just as easy to check constraints for. -Tobias1984 (talk) 16:25, 13 November 2014 (UTC)

Also, there are teams that have used both 0 (zero) and 00 (double zero), even if they used single digits for 1 to 9. See "Double-zero (00) on sports jerseys—why?" (general discussion); All-Time Numerical Roster for the New York Mets; NBA & ABA Players Who Wore Uniform Number 00 vs. NBA & ABA Players Who Wore Uniform Number 0 (and also 3 vs. 03, 7 vs. 07, 9 vs. 09, which only happened in the 1950s). --Closeapple (talk) 17:48, 13 November 2014 (UTC)

Changed to string. --AmaryllisGardener ^talk 18:11, 13 November 2014 (UTC)

•  Support --- Jura 18:01, 19 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:24, 23 November 2014 (UTC)

Discussion

Needed in addition to officially opened by (P542). --P1433-2014 (talk) 03:49, 14 October 2014 (UTC)

•  Support Could be useful. Eurodyne (talk) 00:28, 17 October 2014 (UTC)
•  Support --AmaryllisGardener ^talk 15:07, 21 October 2014 (UTC)

( Comment Wouldn't significant event (P793) be used for this? Filceolaire (talk) 15:08, 2 November 2014 (UTC)

•  Support. I've changed the proposed label from 'officially opened in' to 'date of official opening' to clarify that the range of the property is a time, not a place. significant event (P793) requires qualifiers, which will not be queryable in the foreseeable future. It also isn't as conducive to a controlled vocabulary as simple properties, which is a drawback. Emw (talk) 13:29, 3 November 2014 (UTC)

 Done--Tobias1984 (talk) 11:34, 23 November 2014 (UTC)

Discussion

Called "plaintiff" in Australia, Hong Kong, Canada, Northern Ireland, the Republic of Ireland, and the United States, "claimant" in England and Wales, and "pursuer" in Scotland, the plaintiff is the party who initiates a lawsuit. It's a basic term in law that makes sense to consider in the same batch as "defendant", etc. Emw (talk) 13:22, 3 November 2014 (UTC)

Andy, Amaryllis, Filceolaire, Tobias, could you please vote or comment? This proposed property would be in line with defendant (P1591), prosecutor (P1592), defender (P1593) and judge (P1594). Thanks, Emw (talk) 19:31, 16 November 2014 (UTC)

•  Support --Tobias1984 (talk) 19:36, 16 November 2014 (UTC)
•  Support - obvious addition to the set. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:17, 16 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:39, 23 November 2014 (UTC)

Discussion

Motivation Property 'locator map image' is sometimes used to contain a detail map of the province/district/region instead of the location within surrounding country. Both are useful but should not be interchanged. A correct 'locator map' for Sicily is file:Sicily_in_Italy.svg whereas file:Provinces_of_Sicily_map.png might be a 'detail map' for Sicily Bemoeial (talk) 19:42, 20 October 2014 (UTC)

 Support Filceolaire (talk) 21:07, 31 October 2014 (UTC)

 Support--Oursana (talk) 22:13, 5 November 2014 (UTC)

 Support--- Jura 18:46, 18 November 2014 (UTC)

 Support May be usefull for battle map or a building plan. --Fralambert (talk) 01:55, 19 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:46, 23 November 2014 (UTC)

Discussion

This property's importance is evident in being in en:Infobox country. --AmaryllisGardener ^talk 00:15, 9 November 2014 (UTC)

 Support How are we going to handle trains? Austria for example has right driving for roads, but for multiple train tracks it depends on the route. Separate property for trains? Tobias1984 (talk) 00:20, 9 November 2014 (UTC)

Separate property, I guess. Trains run, they don't drive. --AmaryllisGardener ^talk 15:40, 11 November 2014 (UTC)

•  Support --- Jura 18:00, 19 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:50, 23 November 2014 (UTC)

Discussion

These links provide live mapping to last known position, declared destination, etc. - see example, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:05, 28 June 2014 (UTC)

Indeed useful, but make it a simple string, like other such properties; indicate in "robot and gadget jobs" that the hyperlink is to be supplied by AuthorityControl gadget: http://www.marinetraffic.com/en/ais/details/ships/$1. LaddΩ chat ;) 02:14, 29 June 2014 (UTC)

 Comment - Should be string if it is an ID. Why not use one property for ports and ships? There is no ambiguity if you also query if it is p31 "ship" or "port"? -Tobias1984 (talk) 19:39, 19 July 2014 (UTC)

 Support - I have combined the Ship and Port ID properties into one, and changed the data type to string. Josh Baumgartner (talk) 10:23, 9 November 2014 (UTC)

 Comment @Joshbaumgartner, Tobias1984, Pigsonthewing: not sure this was a good move - ships and ports have different formats, different URL... -- LaddΩ chat ;) 15:54, 9 November 2014 (UTC)

I agree with Laddo; these should be separate. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:24, 11 November 2014 (UTC)

 Support In the current form. -- LaddΩ chat ;) 18:37, 11 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:55, 23 November 2014 (UTC)

Discussion

These links provide live lists of recent arivals, birthed vessels, etc. - see example, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:19, 28 June 2014 (UTC)

Similarly, please make it a text string (e.g. "107") and indicate in "robot and gadget jobs" that the hyperlink is to be supplied by AuthorityControl gadget: http://www.marinetraffic.com/en/ais/details/ports/$1. LaddΩ chat ;) 02:20, 29 June 2014 (UTC)

 Not done Proposal merged into MarineTraffic ID property proposal. Josh Baumgartner (talk) 10:20, 9 November 2014 (UTC)

I object to these proposals being merged; the URL pattern for each type is different and the numbers may not be unique between types. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:27, 11 November 2014 (UTC)

 Support In this form. -- LaddΩ chat ;) 18:34, 11 November 2014 (UTC)

 Done --Tobias1984 (talk) 11:56, 23 November 2014 (UTC)

Discussion

 Support. Add aliases "To the tune of" and "TTTO". Filceolaire (talk) 21:54, 31 October 2014 (UTC)

 Support. Emw (talk) 03:45, 16 November 2014 (UTC)

 Done --Tobias1984 (talk) 12:01, 23 November 2014 (UTC)

Discussion

Unique identifier for Thai heritage sites, i.e. sites registered by the Fine Arts Department (Q1416884). Complete list of this sites compiled by the Thai Wikipedia as part of their local WLM contest, this ID will make them identifiable easier and also allow to link with the Fine Arts Department website - http://www.gis.finearts.go.th/fad50/fad/display_data.aspx?id=0005123 is the official page for ID 0005123 (Wat Phatthanaram (Q16862605)). Ahoerstemeier (talk) 19:16, 17 October 2014 (UTC)

•  Support. Filceolaire (talk) 13:52, 2 November 2014 (UTC)

 Support -- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:06, 19 November 2014 (UTC)

 Support --- Jura 15:10, 19 November 2014 (UTC)

 Done --Tobias1984 (talk) 12:07, 23 November 2014 (UTC)

Discussion

 Support Paweł Ziemian (talk) 16:54, 17 October 2014 (UTC)

 Support. Filceolaire (talk) 13:49, 2 November 2014 (UTC)

 Done --Tobias1984 (talk) 12:12, 23 November 2014 (UTC)

Discussion

Originally requested by User:Filceolaire at Wikidata:Project_chat/Archive/2013/10#Equivalent property: "links to equivalent properties in other ontologies." -- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

Original discussion (Oct 2013)

 Support It would allow us to do automatic mapping. It's similar to owl:sameAs. Tpt (talk) 19:12, 9 October 2013 (UTC)

 Comment. Since we're talking about properties, we should call this 'equivalent property' and have its semantics match those of owl:equivalentProperty. ('Same as' should match owl:sameAs and thus apply only to individuals, i.e. items that have 'instance of' claims.) As with other property properties here, I would support storing 'equivalent property' claims only if the semantics matched those of owl:equivalentProperty. A 'same as' property proposal (permlink) recently garnered significant discussion from Wikidata developers and Semantic Web researchers. A relevant excerpt:

The property owl:sameAs is used to say that two things are exactly equal. One could also say that sameAs declares two identifiers to be synonymous. So anything that was said for the one identifier could also be said for the other. In particular, this means that both things have the same properties. It is a very strong statement of absolute and unlimited identity.

—Markus Krötzsch

Even though Markus isn't referring to this specific property, I have a hunch that he would issue similar cautions about this property. Emw (talk) 15:56, 14 October 2013 (UTC)

 Comment Per my comment immediately above, I've changed the name of this proposed metadata field from 'Same as' to 'Equivalent property'. Emw (talk) 13:19, 19 October 2013 (UTC)

 Conditional support I would support storing 'equivalent property' claims only if the semantics matched those of owl:equivalentProperty. Emw (talk) 13:19, 19 October 2013 (UTC)

More discussion

•  Support. Filceolaire (talk) 17:19, 13 November 2014 (UTC)
•  Support --Paperoastro (talk) 21:27, 15 November 2014 (UTC)
•  Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:30, 26 November 2014 (UTC)

Discussion

Necessary to replace field subject item of {{Property documentation}}. -- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

•  Support. Filceolaire (talk) 15:49, 15 November 2014 (UTC)
•  Support --Paperoastro (talk) 21:26, 15 November 2014 (UTC)
•  Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:26, 26 November 2014 (UTC)

 Support This would be great for all sorts of string/number properties to make them IRI-like. For example in biology and genetics, it is useful to know that the gene CDK2 has the Entrez Gene ID of 1017. Although that identifier is useful to know for many contexts, it is also good to note that http://www.ncbi.nlm.nih.gov/gene/1017/ is the link where that identifier is defined. Andrew Su (talk) 18:55, 14 March 2013 (UTC)

•  Support Espeso (talk) 06:06, 15 March 2013 (UTC)
•  Comment I have to say I do not see how it is supposed to work. From what I see, that should be a property of a property (here a property of p214), but we do not have that. --Zolo (talk) 09:04, 15 March 2013 (UTC)

  Not yet! --Ricordisamoa 09:07, 15 March 2013 (UTC)

  But is there any hint that the development team has plans for that ? --Zolo (talk) 09:28, 15 March 2013 (UTC)

  I don't think it's very different from having properties on items; ask someone! --Ricordisamoa 09:30, 15 March 2013 (UTC)

  I thought you meant that the item pages like Q54919 (VIAF), would contain this statement. Espeso (talk) 14:21, 15 March 2013 (UTC)

•  Oppose We have now the reference structure so we can directly use the whole URL as a reference link. If the idea is just to create a link I thinkthat will transform wikidata in a links directory. Perhaps I don't see the utility but if you give an example that would be clearer. Right now for viaf we have a property so no need to create a new property just to have the link: you can put the link as a reference. Snipre (talk) 20:12, 22 March 2013 (UTC)

  I conceived this property to replace the internal 'database' in MediaWiki:Gadget-AuthorityControl.js, to provide a standard and Wikibase-level way to build links from claims; if this can be achieved differently, or it is not technically possible, or the community does not want it, I can smoothly withdraw this proposal. --Ricordisamoa 22:34, 2 August 2013 (UTC)

  Snipre: Web sites do sometimes change the way they format urls. This function means we only need to change one property when this happens and every link is back working again. Filceolaire (talk) 20:53, 20 August 2013 (UTC)

•  Support As long as it can be added to property pages.--Micru (talk) 22:10, 17 August 2013 (UTC)
•  Support. Add to the Q items for that corresponds to the Authority file property for now even if we don't yet know how to make this work to automatically convert authority file IDs into web addresses. Having this info in an editable form will be important the next time some website changes their url format. Filceolaire (talk) 22:56, 18 August 2013 (UTC)
• It would be neat to use this on the property page. I'm not sure I agree that we should do Filceolaire's suggestion—it could seep out into the wild as any site with a URL of any sort might end up with it, even when that was not the intention or desired use, and I'm pretty sure that would be bad. --Izno (talk) 03:29, 17 September 2013 (UTC)
•  Support I think the merge of all AuthorityControl-properties in combination with the use of this in the item would do fine, as soon as the other problems are solved! -- Lavallen (talk) 05:54, 17 September 2013 (UTC)
•  Support I also suggested this as a way to clean up the dozens of Database ID's that are being created - could use <Apple> database ID <"APL1">{for database: FruitPedia} and then <FruitPedia> formatter URL <"www.f.com/fruit?$1">. Otherwise the problem we are going to have is hundreds of properties for marginally notable properties. Macadamia1472 (talk) 09:38, 16 October 2013 (UTC)

Discussion

The website contains data about Chinese officials, mostly about the functions they hold. Data come mostly from Chinese-gouvernment affliated institutions [7], which may not be among the most reliable sources on political matters, but for this type of information, this seems to make sense in most cases. It appears to be the most comprehensive English-language source on the topic. Zolo (talk) 06:47, 19 November 2014 (UTC)

 Support -- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:04, 19 November 2014 (UTC)

@Pigsonthewing:: done: P:P1631. --Zolo (talk) 11:49, 29 November 2014 (UTC)

1
1
2
m
2/m
222
mm2
mmm
4
4
4/m
422
4mm
42m
4/mmm
3
3
32
3m
3m
6
6
6/m
622
6mm
6m2
6/mmm
23
m3
432
43m

Discussion

Kopiersperre (talk) 13:33, 11 November 2014 (UTC)

• Question: Should there be an item for each of the 32 possible values? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:56, 13 November 2014 (UTC)
  • @Pigsonthewing: We have already created the 32 items representing the point groups. Snipre (talk) 12:59, 13 November 2014 (UTC)
    • Do you mean, for example, tetragonal crystal system (Q503601)? That seems to have no relation to Hermann–Mauguin notation (Q903232), but is a subclass of crystal structure (Q895901) and instance of crystal system (Q898786). Where can I find all 32 items? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:31, 13 November 2014 (UTC)
      • @Pigsonthewing: This is a handy list: Wikidata:WikiProject Mineralogy/Crystallography --Tobias1984 (talk) 16:02, 13 November 2014 (UTC)
        • Indeed it is, thank you - but I was looking for a discrete list of 32, as a "subclass of" something, or using "what links here". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:23, 13 November 2014 (UTC)
•  Support @Kopiersperre: This property should be a string property used in the 32 items describing the point groups. See point group (P589). Snipre (talk) 12:59, 13 November 2014 (UTC)
•  Support I changed datatype to string. Does anyone know if we can do all the symbols with the string property? --Tobias1984 (talk) 15:59, 13 November 2014 (UTC)
• @Chris.urs-o: Can you still look over this proposal and see if it will work? The space groups will need lower case numbers. Do you think that is manageable? --Tobias1984 (talk) 22:16, 21 November 2014 (UTC)
•  Support We have point group (Q899720), I think that it is the same. Wikidata is young, we have problems with the units: Mohs hardness has to be written as 1.5±1 instead of 1½-2½. The idea was to get the space group of the crystallographic solved minerals. And add crystal system and point group with a bot. Almost 5,000 minerals, added manually. I think that there is no CC-0 database available. The point group could be converted in Hermann–Mauguin notation, before adding it to the infobox. --Chris.urs-o (talk) 10:24, 22 November 2014 (UTC)

@Chris.urs-o: First I was confused, but now I know what you mean. The example says that the minerals should get the notation, which I also think is a bad idea. I think only the crystallographic groups should get the Hermann–Mauguin statements, and the minerals can link to those groups via the existing properties. The "International Tables For Crystallography" were apparently published in 1935. Are those values still under copyright? --Tobias1984 (talk) 11:05, 22 November 2014 (UTC)

I don't know really (I was talking about bot requests). But this is notation, unit, glossary. You can't express yourself without this convention. --Chris.urs-o (talk) 12:20, 22 November 2014 (UTC)

 Done --Tobias1984 (talk) 14:54, 29 November 2014 (UTC)

Discussion

Nuns, brothers and other religious folk take a particular name when they enter their specific community. There's no real way I can tell to indicate this right now. It's more specific than an alias and more in line with birth name (monolingual). (I think I did this wrong the first time I tried to ask for this property.) :) Sweet kate (talk) 22:43, 18 November 2014 (UTC)

•  Support. Emw (talk) 01:42, 20 November 2014 (UTC)
•  Support but not sure about the datatype. For instance, en:Hilarion (Ohienko), uk:Іларіон (Огієнко), pl:Iwan Ohijenko show different language variants of the same religious name Hilarion/Іларіон/Iłarion. This should be consistent with properties like given name and should be either all of datatype Item (like it is now) or Multilingual text (I support this more because of some problems with Item - see here and here) --DixonD (talk) 08:18, 20 November 2014 (UTC)

I agree. Emw (talk) 13:04, 20 November 2014 (UTC)

Yep. Of the two I prefer Multilingual text. I'm new to Wikidata but not to data in general and it didn't take me long to recognize the given name/Item problems referenced by DixonD. Sweet kate (talk) 15:24, 21 November 2014 (UTC)

•  Support — Ayack (talk) 08:52, 20 November 2014 (UTC)

 Done — Ayack (talk) 07:59, 1 December 2014 (UTC)

I believe there was clear consensus not to make it monolingual text. Now more mess is introduced when some name properties are items, some are supposed to be multilingual texts, and this one is monolingual text. --DixonD (talk) 05:37, 3 December 2014 (UTC)

That confused me too. Can it be switched to multilingual? Sweet kate (talk) 18:02, 3 December 2014 (UTC)

 Comment I wonder if it can also be used for pen name or art name?--Giftzwerg 88 (talk) 23:20, 3 December 2014 (UTC)