Wikidata:Property proposal/Archive/21
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion. |
Patent number
Description | patent (Q253623) : Things that are (or were) patented have a unique patent number |
---|---|
Data type | String |
Template parameter | en:Template:US patent field #1 - See also Template:Patent (Q6020246). |
Domain | Things that can be patented |
Allowed values | Format is two letters (country code) followed by 1-10 digits (some countries pad with 0s some don't according to [1]) |
Example | Kinetite (Q15982768) => GB10936, computer mouse (Q7987) => US3987685 |
Format and edit filter validation | ? |
Robot and gadget jobs | Auto URL, e.g. http://www.google.com/patents/US3987685 or http://worldwide.espacenet.com/publicationDetails/biblio?CC=US&NR=3987685&KC=&FT=E&locale=en_EP |
Proposed by | Thryduulf (talk: local | en.wp | en.wikt) |
- Discussion
A patent number is something that is uniquely tied to a given thing that has (or had) a patent and can be used as a reference to find more information. I discovered the absense of this property when trying to fill out Kinetite (Q15982768). I don't understand many of these fields so, sorry if I haven't filled them out correctly. If you want more information please explain what you are looking for. Thryduulf (talk: local | en.wp | en.wikt) 01:07, 31 March 2014 (UTC)
- Support --Jakob (talk) 01:26, 31 March 2014 (UTC)
- Support -- LaddΩ chat ;) 15:08, 31 March 2014 (UTC)
- Stöder -- Lavallen (talk) 17:27, 31 March 2014 (UTC)
- Support --Casper Tinan (talk) 07:54, 1 April 2014 (UTC)
- Support - AdamBMorgan (talk) 20:02, 1 April 2014 (UTC)
- Support -- SERutherford (talk) 21:38, 6 April 2014 (UTC)
- @Thryduulf, Laddo, Casper Tinan, AdamBMorgan, Lavallen, SERutherford: Done. Even though I participated in this one, there is such overwhelming support that it shouldn't matter. --Jakob (talk) 18:40, 8 April 2014 (UTC)
- Template:DiscussionA late note: According to [2] the letters
WO
for World Intellectual Property Organization, is also used. In other words a ISO 3166-1 alpha-2 code should not be strictly required. Rotsee (talk) 07:07, 9 April 2014 (UTC)
- Template:DiscussionA late note: According to [2] the letters
is currently part of
Description | Location of a former administrative unit, country, etc. |
---|---|
Data type | Item |
Template parameter | "nuvarande kommun" in sv:template:Historisk kommun |
Domain | administrative territorial entity (Q56061) |
Allowed values | administrative territorial entity (Q56061) |
Example | sv:Karlshamns stad => sv:Karlshamns kommun |
Proposed by | Rotsee (talk) |
- Discussion
I realise that this can be achieved by traversing succeeded by, until the end, but that requires an unknown, and potentially large number of calls, and there is no knowing how branched the tree will be, or if there is a loop somewhere on the way. This property should hold the most relevant value(s), like Benin for Dahomey, or Greater London for County of London. Rotsee (talk) 18:24, 8 April 2014 (UTC)
- Comment I think the need is a real one but the request is not mature enough. Maybe we don't really need to use a new property and deal with this with located in or part of properties with qualifiers to note the validity of the claims, or even just have the geographical locations as coordinates or something and a tool to show this on a map together with nowdays locations. is currently part of seems too dependant of the instant, and can be obsoleted, which imply imo it is not really better than the properties that exists now used in combination. TomT0m (talk) 18:34, 8 April 2014 (UTC)
- Many properties are easily obseleted, so while it is a a bit troubling, it wouldn't have to be a showstopper. I'm sure you are right that there might be better ways to address the need, though I'm not sure how. Rotsee (talk)
- @Rotsee: I have already started to work with this parameter in this template, and that with parameter located in the administrative territorial entity (P131). Look at Västra Kinda Municipality (Q14934211) where Kinda Municipality (Q515299) have this value with normal rank.
- The "prefferred rank" here is used for the county and province the municipality was located in when it existed, and the "normal rank" without "enddate" has the value it is located in now. Using succeeded by am I worried that it would sometimes give a misleading result, since the succession looks very complicated in some cases. (A small municipality is merged into a larger municipality who is later split, take Nyköping as an example.) The consequence is that you cannot use a simple parser to get this value, but it's fully solvable with Lua.
- @TomT0m: I do not trust a solution based on coordinates at all today. I have seen such files and they are very simplified, and may give a lot of false positive. -- Lavallen (talk) 07:02, 9 April 2014 (UTC)
- @Lavallen: I really like that approach! And I agree that trying to follow succeeded by can be very misleading, or, in some extreme cases, even unsolvable (e.g. loops created when entities are reintroduced). Rotsee (talk) 07:20, 9 April 2014 (UTC)
- In "reintroduced entities" have I created separate items for the two entities. Look at Salem Municipality (1971-73) (Q14943851) and Salem Municipality (Q1255130). I do not consider them as the same entity, rather as a new entity with the same name as the old one.
- And I started to work with this before "ranks" was introduced, so you will find many examples where I haven't finished the work with this parameter yet. -- Lavallen (talk) 07:25, 9 April 2014 (UTC)
- @Lavallen: I really like that approach! And I agree that trying to follow succeeded by can be very misleading, or, in some extreme cases, even unsolvable (e.g. loops created when entities are reintroduced). Rotsee (talk) 07:20, 9 April 2014 (UTC)
- Many properties are easily obseleted, so while it is a a bit troubling, it wouldn't have to be a showstopper. I'm sure you are right that there might be better ways to address the need, though I'm not sure how. Rotsee (talk)
- Resolved and therefor marked as Not done -- Lavallen (talk) 11:38, 10 April 2014 (UTC)
Box Office Mojo film ID
Description | films' IDs on Box Office Mojo (Q223142) |
---|---|
Data type | String |
Domain | creative work |
Example | Subway (Q634729) => subway |
Source | Template:Mojo title (Q7363953), http://boxofficemojo.com/ |
Robot and gadget jobs | Import from Template:Mojo title (Q7363953). |
Proposed by | 31.46.253.173 |
- Discussion
Could be used in Template:Mojo title (Q7363953). 31.46.253.173 13:15, 8 December 2013 (UTC)
- Support Filceolaire (talk) 04:44, 25 February 2014 (UTC)
- Support. Seems useful. Mushroom (talk) 22:41, 6 April 2014 (UTC)
- @31.46.253.173, Filceolaire, Mushroom: Done --Jakob (talk) 22:44, 6 April 2014 (UTC)
Parsons Code
Description | describe the Parsons code of a music https://en.wikipedia.org/wiki/Parsons_code |
---|---|
Data type | String |
Domain | creative work (music) |
Allowed values | type of linked items, allowed values (if limited) |
Example | Samples: Twinkle, Twinkle, Little Star (Q1058356) => *rururddrdrdrd urdrdrdurdrdrd drururddrdrdrd Stille Nacht Heilige Nacht (Q172152) => *udduuddurdurdurudddudduruddduddurudduuddduddd ) |
Format and edit filter validation | (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17) |
Source | http://en.wikipedia.org/wiki/Parsons_code |
Robot and gadget jobs | Should or are bots or gadgets doing any task with this? (Check other properties for consistency, collect data, etc.) |
Proposed by | Xmlizer (talk) |
- Discussion
Motivation. Xmlizer (talk) 16:14, 30 December 2013 (UTC)
- Support Xmlizer (talk) 16:16, 30 December 2013 (UTC)
- Comment You shouldn't vote in your own request. --Rezonansowy (talk) 22:03, 20 January 2014 (UTC)
- 'Course you should. Just do it 'as moninator'. Filceolaire (talk) 04:46, 25 February 2014 (UTC)
- Comment You shouldn't vote in your own request. --Rezonansowy (talk) 22:03, 20 January 2014 (UTC)
- Oppose That's only an experimental markup, rather not a taxonomic statement. --Rezonansowy (talk) 22:03, 20 January 2014 (UTC)
- How do you mean it's an experimental markup? According to the Wikipedia article Parsons code was proposed in 1975. --Bensin (talk) 22:24, 6 April 2014 (UTC)
- Support Filceolaire (talk) 04:46, 25 February 2014 (UTC)
- Support - Any musical work with a melody can be described with Parsons code: musical work (Q2188189), composed musical work (Q207628), single (Q134556), symphony (Q9734), sonata (Q131269), melody (Q170412), cantata (Q174873), nocturne (Q194172), overture (Q202287), étude (Q207841), march (Q211025), leitmotif (Q221117), movement (Q929848), chorale (Q724473), concerto (Q9748) and theme music (Q1193470). As for allowed values, the first character is always "*" subsequent characters are either "r", "u" or "d" (" " should perhaps be allowed for readability but have no meaning when interpreting the code). Parsons code can possibly be derived by bots from sheet music. It is also a way to describe a melody without violating copyright and you don't have to be able to read music or play an instrument to search for a melody. It is used in Musipedia so a sharing of data with them would be great. --Bensin (talk) 22:24, 6 April 2014 (UTC)
- @Xmlizer, Rezonansowy, Filceolaire, Bensin: Done, as there appears to be sufficient consensus to create. --Jakob (talk) 22:40, 6 April 2014 (UTC)
- Awesome! This made my day! --Bensin (talk) 14:59, 7 April 2014 (UTC)
- @Jakec:, I think it's just "Parsons code" (without apostrophe as the guy's name was "Parsons")
- Thanks for that. Fixed. --Jakob (talk) 15:21, 7 April 2014 (UTC)
- Thank you! --Bensin (talk) 15:36, 7 April 2014 (UTC)
- Thanks for that. Fixed. --Jakob (talk) 15:21, 7 April 2014 (UTC)
native file format
Description | subject's own file format |
---|---|
Data type | Item |
Example | JPEG (Q2195)=>.jpg, .jpeg, .jpe, .jif, .jfif, .jfi |
Proposed by | Rezonansowy |
- Discussion
- Comment Native file format sounds like it is the file format that a program saves files as default. Photoshop for example uses "psd" and Excel "xls". In its current form I don't understand this proposal. Should this be "file extension"? --Tobias1984 (talk) 12:49, 22 February 2014 (UTC)
* Support Very good idea. --Jakob (talk) 00:35, 31 March 2014 (UTC)
- Oppose. Redundant to file extension (P1195). Mushroom (talk) 23:07, 6 April 2014 (UTC)
- Switching to Oppose per Mushroom. I didn't know we had that property. --Jakob (talk) 00:13, 7 April 2014 (UTC)
- Not done - duplicate property. --Jakob (talk) 00:13, 7 April 2014 (UTC)
JSTOR journal code
Description | JSTOR code for each journal |
---|---|
Data type | String |
Template parameter | en:template:infobox journal#JSTOR |
Domain | creative work |
Allowed values | periodicals |
Example | American Literature (Q4744368) => amerlite, Irish Monthly (Q6070992) => irishmonthly |
Format and edit filter validation | [a-z][a-z0-9]* |
Source | Wikipedia & JSTOR |
Robot and gadget jobs | JVbot can already populate from Wikipedia |
Proposed by | John Vandenberg (talk) |
- Discussion
English Wikipedia infoboxes use the ISSN based way to link to JSTOR. e.g. w:American Literature (journal) includes JSTOR = 00029831 which is the ISSN for the journal. However we already record ISSNs in ISSN (P236), so it doesnt seem sensible to have another property which is the ISSN that JSTOR recognises, stored in a different encoding. I have randomly reviewed old journals in JSTOR, and it appears they always have an ISSN, so I assume JSTOR or someone else is arranging ISSNs to be issued for these old journals, even for single volume series like this.
However JSTOR also has a textual code for each journal. For the items with a value in the English Wikipedia journal infobox, the JSTOR ISSN value can be transformed into a JSTOR journal code by parsing the JSTOR page. e.g. http://www.jstor.org/journals/20419988.html includes 'londonjmed' in the HTML source in a simple to extract manner - I am happy to do that as a batch job. John Vandenberg (talk) 21:50, 2 March 2014 (UTC)
- Support. TomT0m (talk) 17:24, 3 March 2014 (UTC)
- Comment John, can you explain to me what the advantage is for having these codes? As you say, the enWP infobox uses the ISSN (minus the dash) to link to JSTOR. I don't see that as a problem, because the reader will not even see this (just a bluelinked "JSTOR" appears in the infobox). Thanks. --Randykitty (talk) 17:31, 20 March 2014 (UTC)
- Whether we use the JSTOR ISSN or the JSTOR journal code is of no consequence to Wikipedia - the template will display a link that goes to the same location.
- The difference is what we store on Wikidata, and how re-usable / useful is it. If we try to use the JSTOR ISSN, we need to somehow annotate which specific ISSN is the one that works in JSTOR URLs. It cant use any ISSN for the journal - only one works. What might be worth exploring is whether the JSTOR ISSN is the Linking-ISSN (see Property talk:P236#Unique constraint). I see two options for achieving this.
- create a new property for the JSTOR ISSN
- attach a qualifier to one of the ISSN to mark it as the JSTOR ISSN
- IMO, the first of those options is silly - it is a duplication of data. The second option could work.
- The advantage of recording the JSTOR journal code is that avoid the above problem of JSTOR ISSNs, and I am willing to bet that the JSTOR journal code is more stable than the JSTOR ISSN and even the Linking-ISSN. John Vandenberg (talk) 01:58, 22 March 2014 (UTC)
- Support. Per above explanation. --Randykitty (talk) 11:57, 3 April 2014 (UTC)
- @John Vandenberg, Randykitty, TomT0m: Done --Jakob (talk) 14:20, 3 April 2014 (UTC)
Danish Bibliometric Research Indicator (BFI) Level
Description | A research quality indicator given to journals and publications in the Danish research evaluation framework. |
---|---|
Data type | String |
Domain | creative work |
Allowed values | Valid on periodical (Q1092563) and publishing company (Q2085381) |
Example | example item and/or example value (please add one or several sample uses of the property. Sample: Universe (Q1) => Earth (Q2)) |
Format and edit filter validation | Literal values '1' or '2' only |
Source | Danish journal list |
Robot and gadget jobs | user:JVbot can populate |
Proposed by | John Vandenberg (talk) |
- Discussion
This is the Danish authorities simplistic quality indicator, like the (Australia) ARC journal rank. According to this English summary, in Denmark "Publishing in series of level 2 earns more points than publishing in series of level 1." John Vandenberg (talk) 07:32, 6 March 2014 (UTC)
- The Norwegian official journal list also uses the same two level ranking[3]. It will be interesting to compare all these rankings using Wikidata. ;-) John Vandenberg (talk) 08:00, 6 March 2014 (UTC)
- The Norwegian list includes many journals that have changed levels over the years[4].
- I have looked for other Scandinavian countries that might share the same property, but didnt find any. What I did find is European Reference Index for the Humanities (Q15904698) which has gone through two major iterations (2007 and 2011) and looks likely to be gearing up to start the process again. Initially it had categories "A, B, C"[5] but has renamed and reordered them to "NAT (C) INT1 (A), INT2 (B)". The French journal ranking system was similar to ERIH. Interestingly hosting and maintenance of ERIH is in the process this semester of being delegated to the Norwegian organisation w:Norwegian Social Science Data Services that is responsible for their national registry. Searching ERIH also shows journals that have changed category from 2007 to 2011. The ERIH category is provided a few times on Wikipedia articles[6]. John Vandenberg (talk) 14:18, 7 March 2014 (UTC)
- The Norwegian official journal list also uses the same two level ranking[3]. It will be interesting to compare all these rankings using Wikidata. ;-) John Vandenberg (talk) 08:00, 6 March 2014 (UTC)
- Comment I don't really see the usefulness of including these obscure rankings that are produced by small research communities. Like the French exercise, these things come and then often go again without leaving much trace. --Randykitty (talk) 17:36, 20 March 2014 (UTC)
- Randykitty, I dont think size matters! The Scandinavian countries are well known for having high class research - i.e. in the top of the OECD. These indicators are part of the qualitative assessment which feeds government policy and funding decisions which produce high class research.
- Secondly, The Norwegian system has been in operation since 2004, and they regularly review and revise the ranking of journals. e.g. Ramus (Q15763952) 's history can be seen here.
- Thirdly, as seen over on Wikidata:Property proposal/Authority control, these journal lists are used by Danish and Norwegian Wikipedia, due to their importance for the readership of those Wikipedias. John Vandenberg (talk) 06:00, 6 April 2014 (UTC)
- Support Per the reasoning that this is of value for the Scandinavian-language wikis. (I'm still not fully realizing that Wikidata is for all wikis, I guess... :-) --Randykitty (talk) 11:43, 7 April 2014 (UTC)
- Support per above. Mushroom (talk) 11:47, 7 April 2014 (UTC)
- @John Vandenberg, Randykitty, Mushroom: Done --Jakob (talk) 11:53, 7 April 2014 (UTC)
- @Jakec, Randykitty, Mushroom: firstly thanks, this property is a bit hard to populate/use without the Danish SNO/CNO identifier over on Wikidata:Property proposal/Authority control, and the Norwegian DBH periodical ID is tightly related as they use the same ranking system (it looks like the Danish adopted it from the Norwegians, but I havent analysed the data to see whether there is data sharing also going on). I'm happy to wait for consensus on those identifiers though. John Vandenberg (talk) 13:54, 7 April 2014 (UTC)
Notable works
Description | Names of notable works (WP:NN) |
---|---|
Data type | chaîne de caractères-invalid datatype (not in Module:i18n/datatype) |
Template parameter | « œuvres principales » dans fr:Modèle:Infobox Écrivain |
Domain | personne (Q215627) |
Allowed values | Texte |
Example | exemple d'élément qui utiliserait cette propriété, avec une valeur proposée; par exemple : Universe (Q1) => Earth (Q2) |
Format and edit filter validation | (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17) |
Source | infobox |
Robot and gadget jobs | ? |
Proposed by | Chris a liege (talk) |
- Discussion
Motivation. Chris a liege (talk) 16:03, 28 March 2014 (UTC)
- Oppose Please use notable work (P800). --Kolja21 (talk) 17:53, 28 March 2014 (UTC)
- Oppose per above. Mushroom (talk) 11:49, 7 April 2014 (UTC)
- Not done Duplicate of notable work (P800). --Jakob (talk) 15:11, 7 April 2014 (UTC)
- Oppose per above.--Oursana (talk) 00:59, 18 April 2014 (UTC)
Theatricalia play id
Description | Identity of a play on Theatricalia |
---|---|
Data type | String |
Template parameter | "theatricalia_id" in en:template:infobox play |
Domain | work (Q386724) (creative work) |
Example | Frozen (Q5506278) => 834 |
Source | http://theatricalia.com |
Robot and gadget jobs | Could be mass imported by looking up Wikipedia links on Theatricalia, or from en.Wikipedia infoboxes. |
Proposed by | Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits |
- Discussion
Alternatively, we could store the properties as URIs, e.g. http://theatricalia.com/play/834/frozen
Note that Theatricalia also has IDs/ URIs for people, venues, etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:16, 1 April 2014 (UTC)
- Support, since used by infobox. --Kolja21 (talk) 06:04, 6 April 2014 (UTC)
- Support. Mushroom (talk) 11:48, 7 April 2014 (UTC)
@Pigsonthewing, Kolja21, Mushroom: Done --Jakob (talk) 15:09, 7 April 2014 (UTC)
Iconclass ID
Description | ID of a topic in Iconclass (Q1502787), a useful classification system for visual arts |
---|---|
Data type | String |
Domain | anything with a Iconclass equivalent |
Allowed values | not sure of the structure of the IDs |
Example | milkmaid (Q1934482): Iconclass ID: 47I22311 |
Format and edit filter validation | (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17) |
Source | http://www.iconclass.org/help/outline |
Proposed by | mentionned previously by user:Jane023, user:Marsupium; Zolo (talk) 13:27, 15 April 2014 (UTC) |
- Discussion
Support per Wikidata talk:WikiProject Visual arts#Rijksmuseum. Though I would prefer the label Iconclass notation following the term used by the project itself (cf. http://www.iconclass.org/media/help.pdf). --Marsupium (talk) 11:55, 18 April 2014 (UTC)
Support I would like to see this used in Commons categories (especially for artworks of scenes in the Bible, as the names are sometimes really confusing across languages)
Support--Oursana (talk) 22:40, 21 April 2014 (UTC)
- @Marsupium, Oursana: Done --Jakob (talk) 22:45, 22 April 2014 (UTC)
depicts Iconclass
Description | Iconclass ID of a topic depicted by an artwork-item |
---|---|
Data type | String |
Domain | visual artworks (and other creative works ?) |
Allowed values | not sure of the structure of the IDs |
Example | The Milkmaid (Q167605): depicts Iconclass ID 47I22311 |
Source | https://www.rijksmuseum.nl/en/rijksstudio etc. |
Proposed by | Zolo (talk) |
- Discussion
The Iconclass of something shown on the artwork (as opposed to "equivalenet to Iconclass ID", proposed in the previous item). A complete and stable mapping of Wikidata to Iconclass + a consistent data structure on Wikidata would make this inferrable from Iconclass ID of the topic + depicts (P180) of the artwork. But we are still far from there, so this property seems needed for practical reasons. See also Wikidata talk:WikiProject Visual arts#Rijksmuseum.--Zolo (talk) 13:27, 15 April 2014 (UTC)
- Support per Wikidata talk:WikiProject Visual arts#Rijksmuseum. Though I would prefer the label depicts Iconclass notation which expresses that an identifier is used (as you proposed here) and follows the term used by the project itself (cf. http://www.iconclass.org/media/help.pdf). --Marsupium (talk) 11:55, 18 April 2014 (UTC)
- Support--Oursana (talk) 22:53, 22 April 2014 (UTC)
slogan / motto
Description | motto or phrase used in advertising or other purposes |
---|---|
Data type | String |
Template parameter | en:template:Infobox organization, en:template:Infobox website |
Domain | creative work |
Example 1 | MISSING |
Example 2 | MISSING |
Example 3 | MISSING |
Source | slogan (Q30515) |
Proposed by | Rezonansowy (talk) |
- Discussion
Motivation. Rezonansowy (talk) 09:42, 28 January 2014 (UTC)
- String would not be the correct datatype for this. Monolingual text would make more sense. --Yair rand (talk) 12:58, 28 January 2014 (UTC)
- On hold - Indeed, a Monolingual text proposal is already approved but pending in Wikidata:Property_proposal/Pending/3#Motto_.2F_Wahlspruch_.2F_Devise -- LaddΩ chat ;) 01:45, 25 February 2014 (UTC)
Not done Redundant request, already on hold.--Micru (talk) 20:51, 25 April 2014 (UTC)
Openpolis ID
Description | identity code of Openpolis page about Italian politician |
---|---|
Data type | Number (not available yet) |
Template parameter | none. Used ad single template in it.wiki (Template:Openpolis) in external links |
Domain | Persons |
Allowed values | numbers |
Example | Bartolomeo Pepe (Q15943581) => 687073 |
Source | |
Robot and gadget jobs | A bot can parse it.wiki page in order to add links. Sometimes OP's pages have been added as value of reference URL (P854), so the bot should remove every Openpolis URL in that property. |
Proposed by | ★ → Airon 90 |
- Discussion
- Support --Jaqen (talk) 22:47, 25 March 2014 (UTC)
- Support --Rippitippi (talk) 01:51, 30 March 2014 (UTC)
- @Airon90, Jaqen, Rippitippi: Done, although I used the string datatype instead of the number datatype. --Jakob (talk) 15:49, 2 April 2014 (UTC)
Slovenska biografija ID
Description | ID in the Slovenska biografija project (Slovene Biography) by the Slovenian Academy of Sciences and Arts |
---|---|
Data type | Number (not available yet) |
Template parameter | "id" in sl:Template:SloBio |
Domain | human (Q5) |
Allowed values | 6-number strings |
Example | Ivan Regen (Q1051) => 496396 |
Format and edit filter validation | a filter analogous to Special:AbuseFilter/17, but for 6-number strings |
Source | http://www.slovenska-biografija.si/ |
Robot and gadget jobs | other biographical data can be extracted from the Text Encoding Initiative XML file contained on the page |
Proposed by | — Yerpo Eh? |
- Discussion
- Support I've created Slovenska biografija (Q15975890). --Kolja21 (talk) 17:42, 23 March 2014 (UTC)
- Thanks, but can an item exist without any Wikipedia pages linking to it? We don't (yet) have an article about Slovenska biografija at :slwiki — Yerpo Eh? 18:59, 23 March 2014 (UTC)
- No problem, see WD:N. -- Lavallen (talk) 19:45, 23 March 2014 (UTC)
- Oh, ok, it's been a while since I looked at WD:N. — Yerpo Eh? 20:08, 23 March 2014 (UTC)
- Support --Recherchedienst (talk) 08:30, 3 April 2014 (UTC)
- Oh, ok, it's been a while since I looked at WD:N. — Yerpo Eh? 20:08, 23 March 2014 (UTC)
- No problem, see WD:N. -- Lavallen (talk) 19:45, 23 March 2014 (UTC)
- Thanks, but can an item exist without any Wikipedia pages linking to it? We don't (yet) have an article about Slovenska biografija at :slwiki — Yerpo Eh? 18:59, 23 March 2014 (UTC)
- Support -- SERutherford (talk) 21:26, 6 April 2014 (UTC)
- @Yerpo, Kolja21, Innocent bystander, Recherchedienst, SERutherford: Done --Jakob (talk) 20:14, 22 April 2014 (UTC)
Founder of
Description | organization, association or event founded by a person. |
---|---|
Data type | Item |
Template parameter | "founder" in en:template:infobox company; "known for" in en:template:infobox person, etc. |
Domain | persons |
Allowed values | place, organization, event, creative work |
Example | Sample: Barry Jackson (Q4864345) => The Malvern Festival (Q15302272)) |
Robot and gadget jobs | Could detect |
Proposed by | Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits |
- Discussion
Reverse of founded by (P112). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:11, 12 December 2013 (UTC)
- Support, seems useful. (Minor note: inverse, rather than 'reverse', is the conventional term used to describe the relationship between this property and founded by (P112).) Emw (talk) 17:27, 21 December 2013 (UTC)
- Support --Konggaru (talk) 09:14, 28 January 2014 (UTC)
- Shouldn't you move this proposal to proposal/organization--Oursana (talk) 22:47, 28 January 2014 (UTC)
- Comment Why do we need an inverse property for founder? --Wylve (talk) 10:05, 8 February 2014 (UTC)
- Good point; when running a query like "what did x found?" it would use the regular property for founder. This one could create duplication of information with no real benefit. Ajraddatz (Talk) 00:39, 14 February 2014 (UTC)
- Oppose. Redundant, no need. --Yair rand (talk) 13:42, 23 February 2014 (UTC)
- @Yair rand : Redundant with which property ? Casper Tinan (talk) 13:52, 23 February 2014 (UTC)
- founded by (P112). Adding the inverse adds no useful data. --Yair rand (talk) 14:12, 23 February 2014 (UTC)
- @Yair rand : Redundant with which property ? Casper Tinan (talk) 13:52, 23 February 2014 (UTC)
- Oppose per my previous comment on redundancy, unless the proposer can suggest a valid necessity. —Wylve (talk) 09:13, 5 March 2014 (UTC)
- Oppose per above. Mushroom (talk) 22:31, 6 April 2014 (UTC)
- @Pigsonthewing, Emw, 콩가루, Oursana, Wylve, Ajraddatz: @Yair rand, Casper Tinan, Mushroom: Not done - Consensus is against creation of this property. --Jakob (talk) 01:09, 13 April 2014 (UTC)
Point of view coordinates
Description | Coordinates of the point from which the photo was taken / the artwork was made |
---|---|
Data type | Geographic coordinates |
Domain | visual artworks (photographs, arguably paintings) |
Allowed values | ~ |
Example | Boulevard du Temple (Q848570) -> 48° 52′ 07,02″ N, 2° 21′ 50,6″ E |
Proposed by | Zolo (talk) |
- Discussion
Perhaps some of the can be retrieved from Commons:Template:Depicted_place.
Notified participants of WikiProject Visual arts --Zolo (talk) 17:15, 31 March 2014 (UTC)
- This is more appropriate to the proposed Commonsdata - the wikidata for describing files on Commons. Note that in addition to the Point of view coordinates you will also need the point of view direction (which way the photographer was facing when he took the photo) and point of view elevation (how high above ground the camera was). Filceolaire (talk) 14:50, 14 April 2014 (UTC)
- @Filceolaire: yes this would also be useful on Commons. But for photographs that have their own item, it seems sensible to store the info on Wikidata (actually if we get Wikibase for Commons, I suspect it would be useful to commonize or at least synchronize some properties across the two projects). --Zolo (talk) 13:08, 15 April 2014 (UTC)
- @Filceolaire:: done coordinates of the point of view (P1259) (I needed it). Yes, we would also need direction, an it can be used on Commons but that will complement the property without making it useless or even obsolete. --Zolo (talk) 07:23, 26 April 2014 (UTC)
- @Filceolaire: yes this would also be useful on Commons. But for photographs that have their own item, it seems sensible to store the info on Wikidata (actually if we get Wikibase for Commons, I suspect it would be useful to commonize or at least synchronize some properties across the two projects). --Zolo (talk) 13:08, 15 April 2014 (UTC)
representing organisation
- Discussion
This seems to be the cleanest solution to indicate that a member of parliament represents a particular constituency or a particular party. Already discussed a bit with user:Lavallen here and user:Avenue here. Zolo (talk) 09:11, 5 December 2013 (UTC)
- Support. As I said in that thread: Adding membership in political party is not without problem, since such claims always needs a source, and you are not always member of the political party you are representing. -- Lavallen (talk) 14:52, 5 December 2013 (UTC)
- While I would prefer to make the inverse claim, given the problems with places like Sweden and elsewhere, I will weakly support this property. Should this be used on the person item or the item representing the political position? --Izno (talk) 14:58, 5 December 2013 (UTC)
- @Izno: How does the inverse claim look like? -- Lavallen (talk) 16:22, 5 December 2013 (UTC)
- administrative item "has representative" person item. As I said, that probably doesn't align very well in some (insane! 8) countries. --Izno (talk) 18:19, 5 December 2013 (UTC)
- Just a note of the French case, to see if that sounds acceptable:
- MPs are elected by geographic constituencies, and are usually members of a party.
- I do not think party affiliation has any official status, but "parliamentary groups" have. Parliamentary groups are MPs that bunch together on political affinity. Normally, all members of the same party are in the same group, but there can be more than one party in one group).
- So would it be ok this way ?
- Jean Dupond
- instance of: human
- member of political party (P102): Fooparty
- position held (P39): MP
- qualifier: representing: Foo Town
- qualifier: member of: Foo Parliamentary Group
- Just a note of the French case, to see if that sounds acceptable:
- administrative item "has representative" person item. As I said, that probably doesn't align very well in some (insane! 8) countries. --Izno (talk) 18:19, 5 December 2013 (UTC)
- @Izno: How does the inverse claim look like? -- Lavallen (talk) 16:22, 5 December 2013 (UTC)
- Zolo (talk) 20:18, 5 December 2013 (UTC)
- And a note on New Zealand, which elects MPs under the hybrid MMP system: some MPs (electorate MPs) represent an electorate and other MPs (list MPs) have no electorate, but essentially represent just their party. We have even had a law (since expired) forcing list MPs to resign from parliament if they leave the party they were elected to represent. So here party affiliation can indeed have official status. --Avenue (talk) 02:26, 6 December 2013 (UTC)
- Zolo (talk) 20:18, 5 December 2013 (UTC)
- On another discussion about presidents, we concluded it would be beneficial to use items like <president of the united states> instead of <president> (quelified) of <United States>. I guess to be consistent we would have to create one deputee items for parliement posts. TomT0m (talk) 21:22, 5 December 2013 (UTC)
- I think it makes sense to create items like "French député of the Fifth Republic", but all members of the parliament have the same status (for France at least), so I do not think it would be necessary to create items for "representative of constituency XX". And given that constituencies can change from one election to the next, that would require many additional items (on the other hand, I guess we will need items for the constituencies ("French constituency XX (period 2012-2017). --Zolo (talk) 21:57, 5 December 2013 (UTC)
- I think we already have a property somewhere for electoral districts. -- Lavallen (talk) 15:33, 6 December 2013 (UTC)
- I think it makes sense to create items like "French député of the Fifth Republic", but all members of the parliament have the same status (for France at least), so I do not think it would be necessary to create items for "representative of constituency XX". And given that constituencies can change from one election to the next, that would require many additional items (on the other hand, I guess we will need items for the constituencies ("French constituency XX (period 2012-2017). --Zolo (talk) 21:57, 5 December 2013 (UTC)
- Oppose -- I'd rather just broaden the applicability of electoral district (P768) to allow it to include representation of groups that aren't geography-based. --Arctic.gnome (talk) 19:48, 7 December 2013 (UTC)
- Comment I did not know (or had forgotten about) electoral district (P768). It is true that there seems to be sufficient overlap to make it confusing. So I would also support extending p768, but how do we do that ? The only solution I see would be to rename p768 to "representing". --Zolo (talk) 09:45, 8 December 2013 (UTC)
- Or perhaps rename it "representing group or district"? --Avenue (talk) 10:08, 8 December 2013 (UTC)
- Support This property could also be used to indicate many types of representation such as Mona Lisa (Q12418) representing "Lisa Gherardini" or France national rugby union team (Q518116) representing French Rugby Federation (Q1479321). I think this is worth considering. Casper Tinan (talk) 21:56, 24 February 2014 (UTC)
- @Casper Tinan: France national rugby union team (Q518116) representing French Rugby Federation (Q1479321) seems like a good idea to me, but not Mona Lisa (Q12418) representing "Lisa Gherardini". We can use the word "represent" in some languages here, but that probably does not work for all languages. In any case, the semantics is a bit different (even though there are arguably commonalities as well). Keeping a separate depicts (P180) sounds better to me. --Zolo (talk) 09:24, 1 March 2014 (UTC)
- @Zolo: I am not opposed to having separate properties for the different meaning of "represents" : depicts/portrays, symbolizes/embodies, acts on the behalf of. Yet, it would make it difficult to correctly label the different properties in some languages. For instance, the french label for depicts (P180) should also be "représente". (the label "décrit" for this property is totally wrong as it implies a description only with words). Casper Tinan (talk) 11:32, 1 March 2014 (UTC)
- I agree. The POINT of wikidata is to have monosemantic relationship, needlessly duplicating english polysemy just makes the data useless. Circeus (talk) 14:31, 26 April 2014 (UTC)
- @Zolo: I am not opposed to having separate properties for the different meaning of "represents" : depicts/portrays, symbolizes/embodies, acts on the behalf of. Yet, it would make it difficult to correctly label the different properties in some languages. For instance, the french label for depicts (P180) should also be "représente". (the label "décrit" for this property is totally wrong as it implies a description only with words). Casper Tinan (talk) 11:32, 1 March 2014 (UTC)
- @Casper Tinan: France national rugby union team (Q518116) representing French Rugby Federation (Q1479321) seems like a good idea to me, but not Mona Lisa (Q12418) representing "Lisa Gherardini". We can use the word "represent" in some languages here, but that probably does not work for all languages. In any case, the semantics is a bit different (even though there are arguably commonalities as well). Keeping a separate depicts (P180) sounds better to me. --Zolo (talk) 09:24, 1 March 2014 (UTC)
- Support Changed label to "representing organisation", so it doesn't get mixed with similar properties.--Micru (talk) 12:18, 29 April 2014 (UTC)
- @Zolo, Innocent bystander, Arctic.gnome, Izno, Avenue, Casper Tinan: @Circeus, Micru: Done --Jakob (talk) 12:41, 30 April 2014 (UTC)
valid in period
Description | the claim is valid in the historical period or era |
---|---|
Data type | Item |
Template parameter | mettez les paramètres de l'infobox de Wikipédia ici s'ils existent. Exemple : « population » dans fr:Modèle:Infobox Subdivision administrative |
Domain | any claim |
Allowed values | type d'éléments liés, valeurs autorisées (si limité) |
Example | |
Format and edit filter validation | (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17) |
Source | Référence externe, article de liste de Wikipédia (soit infobox, soit source) |
Robot and gadget jobs | Devrait-il y avoir/Existe-t-il des robots ou des gadgets qui effectueront des tâches avec cela ? (Vérifiez les autres propriétés afin d'être cohérent, de collecter des données, etc.) |
Proposed by | TomT0m (talk) |
- Discussion
Motivation. TomT0m (talk) 15:33, 12 February 2014 (UTC)
- Support. Useful for many items. --Paperoastro (talk) 16:00, 22 February 2014 (UTC)
- Concerned support It seems that it could have some uses, but at the same time I am worried that it won't be possible to combine queries to statements qualified with "start/end dates", to statements qualified with this property. Perhaps it would be necessary to create a bot that whenever detects "valid in period", also adds the "start/end date" corresponding to that period.--Micru (talk) 12:25, 29 April 2014 (UTC)
- @TomT0m, Paperoastro, Micru: Done --Jakob (talk) 14:33, 29 April 2014 (UTC)
position in list
Description | The position of an item within an ordered list, with a qualifier for the list, if it is notable |
---|---|
Data type | Number (not available yet) |
Example | A (Q9659) --> 1 (list-->Latin alphabet (Q41670)) hydrogen (Q556) --> 1 (list --> periodic table (Q10693)) |
Proposed by | --Jakob (talk) |
- Discussion
- Oppose A list is always defined by an order so put this order element as a qualifier or use follows (P155) or followed by (P156). Snipre (talk) 11:26, 3 April 2014 (UTC)
- Support@Snipre: But how to query the position in list?--GZWDer (talk) 10:34, 10 April 2014 (UTC)
- Query the whole list, sort according to your order criterion, look at the list which is the position of your item: lua. Snipre (talk) 12:05, 10 April 2014 (UTC)
- Oppose, this is pending property "ranking". Circeus (talk) 20:12, 17 April 2014 (UTC)
Not done It is already pending as "ranking", but the datatype is not available yet.--Micru (talk) 12:27, 29 April 2014 (UTC)
Wikipedia Importance
Description | the Importance assigned to this topic on (English?) Wikipedia |
---|---|
Data type | Item |
Template parameter | none |
Domain | items linked to Wikipedia articles |
Allowed values | Vital Articles Level 1, VA Level 2, VA Level 3, VA Level 4, Top, High, Mid, Low, Unassessed |
Example | Muhammad Ali (Q36107) => 'Core' |
Source | Wikipedia Categories |
Robot and gadget jobs | none existing |
Proposed by | Filceolaire (talk) |
- Discussion
Recording the importance of articles here on wikidata will help monitor and manage the translation of these articles. When quality badges are added to Wikidata this will work with those badges to help manage the production of selections and editions of wikipedia. Other users may find lots of other uses for this information. Where different wikipedias have different importance assessment these can all be recorded here using suitable qualifiers, and having these differences recorded here will itself be interesting information for users to analyse, Filceolaire (talk) 18:59, 4 March 2014 (UTC)
- Support per nom. @Filceolaire: See also the proposal below. --Jakob (talk) 19:35, 4 March 2014 (UTC)
- CommentThe importance assessment is language version dependent. Maybe it would be better to handle this with badges?--Micru (talk) 20:14, 4 March 2014 (UTC)
- Oppose. This is specific to each Wikipedia, so this would need to be done with badges and not properties. --Yair rand (talk) 21:56, 4 March 2014 (UTC)
- @Yair rand: We can use applies to part (P518), so it's not a problem. – The preceding unsigned comment was added by Rezonansowy (talk • contribs).
- Comment I believe it will be useful to associate the importance(s) of a topic with Wikidata items, but this is indeed language/project dependent. Helder.wiki 11:00, 5 March 2014 (UTC)
- Oppose I agree with Yair rand. The importance is specific to each project in each wikipedia and should not be handled with properties. Casper Tinan (talk) 11:36, 15 March 2014 (UTC)
- Comment @Casper Tinan: applies to part (P518) doesn't solve this? --Rezonansowy (talk) 11:21, 16 March 2014 (UTC)
Not done Consensus not reached. Try with badges instead.--Micru (talk) 12:44, 29 April 2014 (UTC)
Quality rating
Description | Quality rating for a Wikipedia article, as determined by the article's assessment. |
---|---|
Data type | Item |
Domain | Articles. |
Allowed values | FA, A, GA, B, C, Start, Stub |
Example | Fishing Creek (Q5455008) --> Wikipedia:Good articles (Q19765) |
Source | Talk pages |
Robot and gadget jobs | Could be done. |
Proposed by | --Jakob (talk) |
- Discussion
See above proposal. --Jakob (talk) 19:34, 4 March 2014 (UTC)
- Oppose. I thought about this when I proposed the property above but the problem with this is that quality is a property of the Wikipedia article, not the wikidata item, and the quality is different for each language version of the article.
- There is a proposal to add 'badges' to each sitelink to show the quality level of that article which will do this job better than a new property would and this will work with the Importance property above to enable automatic assessment of and comparisons between wikipedia. Filceolaire (talk) 20:30, 4 March 2014 (UTC)
- @Filceolaire: Couldn't the importance rating also differ from Wikipedia to Wikipedia? --Jakob (talk) 21:11, 4 March 2014 (UTC)
- It could differ within one single project, depending on the perspective. Public toilets in Stockholm could be important within Wikiproject Stockholm (it's actually a featured article). But it's of none importance for Wikiproject Astronomy. Oppose, please let us see how these badges work first. -- Lavallen (talk) 11:39, 5 March 2014 (UTC)
- Oppose As explained above. Snipre (talk) 11:23, 3 April 2014 (UTC)
- @Filceolaire: Couldn't the importance rating also differ from Wikipedia to Wikipedia? --Jakob (talk) 21:11, 4 March 2014 (UTC)
Not done Consensus not reached. Try with badges instead.--Micru (talk) 12:46, 29 April 2014 (UTC)
First match
Description | First match ever played in a competition, by a notable team or a notable sportsperson |
---|---|
Data type | Item |
Template parameter | premier match officiel in fr:Modèle:Infobox Équipe nationale de rugby à XV |
Domain | sports competition (Q13406554) |
Allowed values | sports event only |
Example | France national rugby union team (Q518116) > "first match" (Pxxxx)> "France vs New Zealand, 1 January 1906" Thierry Dusautoir (Q1349233) > member of sports team (P54) > France national rugby union team (Q518116) ("first match" (Pxxxx) > "France vs Romania, 17 june 2006" |
Proposed by | Casper Tinan (talk) |
- Discussion
Motivation : This property will be useful to indicate the first match ever played by a notable team or in which match a sportsperson began his international career. For the latter case, the property would be used as a qualifier. Casper Tinan (talk) 14:33, 15 March 2014 (UTC)
- Oppose the key event significant event (P793) property seems highly usable for this. TomT0m (talk) 19:47, 16 March 2014 (UTC)
- @TomT0m: I disagree. If you look at the example mentioned above, the infobox mentions for each national rugby team its first official match, its largest victory and its largest defeat. How could an infobox model choose which claim correspond to each case if you only use the key event property ? Casper Tinan (talk) 21:17, 16 March 2014 (UTC)
- @Casper Tinan: the details needs to be figured out, but see Property_talk:P793 : there is several complex example that solves this kind of problems using qualifiers. Plus with claime on the match item itself we can also check things in the model code. We need to think at a higher level than just the property level imho. TomT0m (talk) 21:45, 16 March 2014 (UTC)
- @TomT0m: I just had a look at the page you mentioned. The problem is that you almost always need a qualifier and then cannot use the property itself as a qualifier. This would make it impossible to handle basic cases such as
- @Casper Tinan: the details needs to be figured out, but see Property_talk:P793 : there is several complex example that solves this kind of problems using qualifiers. Plus with claime on the match item itself we can also check things in the model code. We need to think at a higher level than just the property level imho. TomT0m (talk) 21:45, 16 March 2014 (UTC)
- @TomT0m: I disagree. If you look at the example mentioned above, the infobox mentions for each national rugby team its first official match, its largest victory and its largest defeat. How could an infobox model choose which claim correspond to each case if you only use the key event property ? Casper Tinan (talk) 21:17, 16 March 2014 (UTC)
Jonathan Sexton (Q1400144) > member of sports team (P54) > Ireland national rugby union team (Q599903) ("first match" (Pxxxx) > "Ireland vs Fiji, 21 november 2009" Jonathan Sexton (Q1400144) > member of sports team (P54) > British & Irish Lions (Q733600) ("first match" (Pxxxx) > "Australia vs British and Irish Lions, 22 june 2013" Casper Tinan (talk) 21:17, 17 March 2014 (UTC)
- @Casper Tinan: Hmm, seems weird, why is the first match so important that it really needs a special treatment ? To retreive the first match it seems simpler to have a match database and to query the set of matches in which the player played for the team and show the first one sorted by date ... TomT0m (talk) 11:50, 18 March 2014 (UTC)
- First and last matches are used to populate table such as this one fr:Liste des sélectionnés en équipe de Nouvelle-Zélande de rugby à XV. I hope it would be possible in the future to use wikidata to generate this kind of list.
- @Casper Tinan: Hmm, seems weird, why is the first match so important that it really needs a special treatment ? To retreive the first match it seems simpler to have a match database and to query the set of matches in which the player played for the team and show the first one sorted by date ... TomT0m (talk) 11:50, 18 March 2014 (UTC)
Casper Tinan (talk) 13:12, 18 March 2014 (UTC)
- @Casper Tinan: For infobox, use lua to screen the qualifiers and to select the appropriate data set. This mean you have to build a lua infobox. Snipre (talk) 11:21, 3 April 2014 (UTC)
Not done Consensus not reached. Select appropriate data set with Lua.--Micru (talk) 12:50, 29 April 2014 (UTC)
Instance of group of
Description | the item is exclusively made of instances of |
---|---|
Data type | Item |
Example | Tsavo Man-Eaters (Q2510263) -> lion (Q140), Bonnie and Clyde (Q219937) -> human (Q5) |
Proposed by | Zolo (talk) |
- Discussion
Note: Not sure it has been already proposed are just discussed in other talk pages. Many items are about several things of the same type, like groups of people. Note that using "subclass of" does not seem correct here, are we are more interested in the properties of the group than in the properties of items that make up the group. One way to see this is that "Tsavo Man-Eaters" takes an "s": the item describes a pair of lions taken as a unit, not the common features shared by two lions. For instance, it would not be correct to say "species: Panthera Leo": each individual is a Panthera Leo, but the item as a whole is not.
- create items about "groups of people", "groups of lions. But for humans that requires a) the creation of many items, and probably b) the creation of a special property linking "group of lion" to "lion". And for the querying software, that requires a) check the value of p279 for all p31 values so that it knows that a group of lion is a subclass of group, b) have a special function telling it how it should behavee when encountering subclasses of group. So I think my proposed solution is all round better than that.
- Just have "p31: group" and add a qualifier "of humans" etc. That is more or less equivalent to this proposal but using qualifiers for essential information does not seem to be a super idea, as qualifiers are somewhat cumbersome to deal with (wikidataquery and other tools do not currently handle them, apparently it is not foreseen to use them in the near future for in-Wikidata queries etc.).
These two alternative solution also mean that in order to make valid inferences about groups of things, we should have ad hoc function telling what sort of special behavior the querying engine should have when encountering subclasses of group (case 1), or instances of group (case 2). I think having a separate "instance of group of" would make things simpler and much more efficient. --Zolo (talk) 08:15, 25 January 2014 (UTC)
- I would prefer having two statements ("p31:human" and "p31:group") and then qualify "instance of" with quantity (P1114) when the size of the group is known.--Micru (talk) 13:00, 22 March 2014 (UTC)
- Does not make really sense, being and instance of human meaning is beeing a human beeing. A group is not a human beeing. TomT0m (talk) 13:30, 22 March 2014 (UTC)
- @Zolo: I guess we can do the same using and TomT0m (talk) 13:30, 22 March 2014 (UTC)
- Also I prefer not to use a double instance of P31. I like the solution proposed by TomT0m. --Paperoastro (talk) 14:05, 22 March 2014 (UTC)
- @TomT0m, Paperoastro:. Something like that could work but the current usage of "composed of" seems to be enumerating individual elements (composed of: first lion, second lion) rather than indicating the type of the elements (composed of: lion). And in a way, that is more powerful this way, as it allows to use "composed of" for heterogeous groups. --Zolo (talk) 08:17, 23 March 2014 (UTC)
- Good point, the composed of description in basic membership properties help page said its usage was disambiguated by wether or not we apply it to a class item or an instance item. I used composed of when I created items untitled group of superheros, for example, this worked fine for me. TomT0m (talk) 11:52, 23 March 2014 (UTC)
- you are right, Zolo: P527 is used also to list the element of multiple star system, as Alpha Centauri (Q12176). --Paperoastro (talk) 19:13, 24 March 2014 (UTC)
- @Paperoastro:, but is also valid :). TomT0m (talk) 19:22, 24 March 2014 (UTC)
- Yes, sure! But the two use are compatible? I don't have problem to continue to use P527 for astronomical objects. --Paperoastro (talk) 21:25, 24 March 2014 (UTC)
- @Paperoastro:, but is also valid :). TomT0m (talk) 19:22, 24 March 2014 (UTC)
- you are right, Zolo: P527 is used also to list the element of multiple star system, as Alpha Centauri (Q12176). --Paperoastro (talk) 19:13, 24 March 2014 (UTC)
- Good point, the composed of description in basic membership properties help page said its usage was disambiguated by wether or not we apply it to a class item or an instance item. I used composed of when I created items untitled group of superheros, for example, this worked fine for me. TomT0m (talk) 11:52, 23 March 2014 (UTC)
- @TomT0m, Paperoastro:. Something like that could work but the current usage of "composed of" seems to be enumerating individual elements (composed of: first lion, second lion) rather than indicating the type of the elements (composed of: lion). And in a way, that is more powerful this way, as it allows to use "composed of" for heterogeous groups. --Zolo (talk) 08:17, 23 March 2014 (UTC)
Not done As per comments, similar expression can be reached with has part(s) (P527).--Micru (talk) 13:02, 29 April 2014 (UTC)
Rotten Tomatoes ID
Description | films' and TV series' (and maybe people's) IDs on Rotten Tomatoes (Q105584) |
---|---|
Data type | String |
Domain | creative work, person |
Example | Subway (Q634729) => m/subway/ and Sherlock (Q192837) => tv/sherlock/ (and maybe Luc Besson (Q484779) => celebrity/luc_besson/) |
Source | Template:Rotten Tomatoes (Q5615409), http://www.rottentomatoes.com/ |
Robot and gadget jobs | Import from Template:Rotten Tomatoes (Q5615409). |
Proposed by | 31.46.253.173 |
- Discussion
Could be used in Template:Rotten Tomatoes (Q5615409). 31.46.253.173 13:15, 8 December 2013 (UTC)
- Comment this could be useful, but it's not an ID. Perhaps, a URL type property would be better? Danrok (talk) 13:09, 30 January 2014 (UTC)
- @Danrok: It's not a numeric ID but it's still a unique string. As Jakob says, we can use AuthorityControl.js to make the URL, just like IMDb ID (P345) and Box Office Mojo film ID (former scheme) (P1237). Would that be OK with you? Mushroom (talk) 21:41, 10 April 2014 (UTC)
- Support. Filceolaire (talk) 04:40, 25 February 2014 (UTC)
- Strong support It is a notable and large database. I'd suggest using a string and utilizing AuthorityControl.js. --Jakob (talk) 18:34, 19 March 2014 (UTC)
- Support. Widely used database. Mushroom (talk) 22:40, 6 April 2014 (UTC)
Done Notifying Danrok, Mushroom, Filceolaire.--Micru (talk) 20:32, 25 April 2014 (UTC)
Tomatometer value
Description | The "tomatometer" value for a movie on the review website Rotten Tomatoes (Q105584) |
---|---|
Data type | Number (not available yet) |
Template parameter | tomatometer parameter in w:Template:Rotten Tomatoes score |
Domain | work (Q386724) |
Allowed values | 0-100 |
Example | The Hunger Games: Catching Fire (Q574583) --> 89 |
Robot and gadget jobs | Easily done. Theo's Little Bot maintains these values on enwiki. |
Proposed by | --Jakob (talk) |
- Discussion
Comment. I'm not sure we can freely use their ratings, they have licensing restrictions. Mushroom (talk) 22:55, 6 April 2014 (UTC)
- @Mushroom: Thank you for commenting. AFAIK the ratings are just the percentage of reviewers giving it a positive review. --Jakob (talk) 00:15, 7 April 2014 (UTC)
Not done Jakob: Redundant with review score (P444) with qualifier review score by (P447) (see example on: The Hunger Games: Catching Fire (Q574583)).--Micru (talk) 20:35, 25 April 2014 (UTC)
completed
Description | Date or year when the painting/recording/sculpture/etc was completed. |
---|---|
Data type | Point in time |
Template parameter | "year" in en:template:infobox Painting |
Domain | Any creative work, except perhaps Litterature which already has publication date (P577) |
Example | Guernica (Q175036) => 1937) |
Proposed by | Nicolas1981 (talk) |
- Discussion
One of the most basic properties of a creative work, and also a thing that greatly needs more coherence between the various Wikipedias. Nicolas1981 (talk) 09:11, 29 January 2014 (UTC)
- Comment Hi Nico, if you define the infobox artwork parameter "year" as "artwork completed" what's with "artwork started"? Wikidata:Books task force is using inception (P571) for the time a work has been created. This can be used for artworks as well. There is also point in time (P585) as an alternative. BTW: What I really miss is an origin property for artists (= painters etc., not musicians). creator (P170) was meant for this task but unfortunately it is now used as a placeholder for every kind of "creator" making no difference between software, television series, and paintings. --Kolja21 (talk) 21:03, 14 February 2014 (UTC)
- Oppose @Nicholas1981: isn't significant event (P793) for for miscellaneous events like this? @Kolja21: that is how properties are meant to work on Wikidata, as genarally applicable to the data. Filceolaire (talk) 05:08, 25 February 2014 (UTC)
- @Filceolaire: 1) "creator": the properties should be generally held yes, but not ambiguous. We have author (P50), editor (P98), developer (P178), designed by (P287), programmer (P943) etc., but no property for artists (= painter). 2) I'm, like you, not convinced of "completed" but imho we need for performing arts and broadcasting "first performance" (see below). --Kolja21 (talk) 06:03, 25 February 2014 (UTC)
- Support a property like this one could see thousands of uses across different kinds of items, including creative works but not limited to them. Theoretically everything with the date datatype could be handled by significant event (P793), but there are properties which would be used often enough to deserve to be created, and this is one of them.--Underlying lk (talk) 16:50, 19 March 2014 (UTC)
- Oppose see Kolja21--Oursana (talk) 00:48, 18 April 2014 (UTC)
Not done--Micru (talk) 20:41, 25 April 2014 (UTC)
next edition (version?)
Description | replace some use of followed by (P156). different from "Next episode", It's not different work but different edition of work. |
---|---|
Data type | Item |
Example | The Plant List 1.0 (Q15628807)=>The Plant List 1.1 (Q15628808) |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 10:17, 6 February 2014 (UTC)
- @GZWDer: I think you need to have an rfc about all these proposals for Replaced by/Followed by properties, or at least move them to the general page. Filceolaire (talk) 05:17, 25 February 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:42, 25 April 2014 (UTC)
previous edition (version?)
- Discussion
Motivation. GZWDer (talk) 10:17, 6 February 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
next episode
Description | replace some use of followed by (P156). different from "Next edition", It's completely two different work (though in a sreies), not rewrite/republish/update. |
---|---|
Data type | Item |
Example | Cougars (Q5176063)=>Secrets and Lies (Q7444489) |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 10:17, 6 February 2014 (UTC)
- Comment An episode number property may be better, so Cougars (Q5176063) = 7. The next, previous, first, etc. can then be determined using that one property. Danrok (talk) 14:40, 22 February 2014 (UTC)
- I don't think it is better than the generic solutions, it as exactly the same problems (followed in the season, a multiepisode, the series ?) we need to add informations in both cases, execpt if with create several properties, but I don't really think it's a good idea. TomT0m (talk) 15:32, 22 February 2014 (UTC)
- Oppose. @GZWDer: This is the job followed by (P156) was created to do. I can see why we need separate generic properties for followed by and replaced by but I am opposed to domain specific properties unless you can come up with a better justification than you have here. Filceolaire (talk) 05:23, 25 February 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
previous episode
- Discussion
Motivation. GZWDer (talk) 10:17, 6 February 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
ERA 2010 journal rank
Description | a ranking of all journals on the w:Excellence in Research for Australia 2010 journal list; ranking discontinued in subsequent ERA journal lists. |
---|---|
Data type | String |
Domain | periodical (Q1092563) |
Allowed values | A*, A, B, C |
Example | Science (Q192864) => A*; Aboriginal History (Q4668339) => A; ABA Journal (Q4650020) => B; AACN Advanced Critical Care (Q4649787) => C |
Source | official dataset |
Robot and gadget jobs | user:JVbot has the code&data ready to populate this property. |
Proposed by | John Vandenberg (talk) |
- Discussion
While the journal ranking was abandoned in the ERA 2012 journal list, it is still used by academics and administrators as a good approximation of journal importance. John Vandenberg (talk) 09:01, 28 February 2014 (UTC)
- Oppose Not only has this ranking been abandoned so that it will not be updated any more, but I doubt it has found much use (if any) outside of Australia (and even there, I fear that the much-maligned impact factor was more influential in steering researchers to certain journals than this ranking). --Randykitty (talk) 17:12, 20 March 2014 (UTC)
- Hi Randykitty, good to see you getting involved here in property development ;-) All Wikidata claims should not need updating. They should be sufficiently qualified claims. See for example the impact factor on Nature (Q180445). This data would be a record of a very large and ground breaking cross-discipline exercise of journal ranking. Academics outside of Australia probably have little interest in this, however research evaluation/bean-counters around the world refer to it, both because the data is very useful, and because the data contains some significant problems. This ranking is accused of being responsible for several Australian journals shutting down because they were a 'C' and universities instructed staff to not publish in them, causing much uproar. Universities in Australia still refer to it, and have typically created their own internal journal rankings which are derivations of it with only minor differences to correct the 'errors' as they perceive them. In ERA, impact factor was not relevant. In ERA 2012, for the sciences, citation count and journal ranking were the primary drivers in the assessment. John Vandenberg (talk) 23:19, 21 March 2014 (UTC)
- @Randykitty:, are you still opposed to this? If so, it can be rejected and archived. John Vandenberg (talk) 00:41, 22 April 2014 (UTC)
- Comment The Danish equivalent property was approved and Danish Bibliometric Research Indicator (BFI) SNO/CNO (P1250)/Danish Bibliometric Research Indicator level (P1240) has been populated for all of the journals that are also on the ERA journal lists (the overlap suggests they are truly international journals). See Wikidata talk:Periodicals task force#April import update for more details on the update. John Vandenberg (talk) 08:58, 21 April 2014 (UTC)
- Support It's not amazingly important, but a reasonably large effort went into it, so it's probably a useful metric to store... it's not like we're space-limited. --99of9 (talk) 09:13, 21 April 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
indexed in
Description | bibliographic databases that a periodical is indexed in. |
---|---|
Data type | Item |
Domain | creative work |
Allowed values | instances of bibliographic index (Q2033233) |
Example | Journal of Experimental and Theoretical Physics (Q23973) => Science Citation Index (Q1379084) |
Source | Wikipedia articles about academic journals contain wikilinks to bibliographic indexes, which could be used for semi-automated data population. A better source will be the bibliographic indexes themselves. |
Robot and gadget jobs | JVbot has been populating Scopus source ID (P1156); items with a Scopus ID are (obviously) indexed by Scopus. The source data used by JVbot also provides coverage information. |
Proposed by | John Vandenberg (talk) |
- Discussion
While many indexes provide unique identifiers for the periodicals they include (i.e. act as authority control, such as Scopus source ID (P1156)), some indexes do not (especially older print only indexes, which tend to be very authoritative), and it will be a lot of work to define properties for each index. 'indexed in' allows data to be input for indexes which dont have unique identifiers (yet), and provides a simple way to access this information for all indexes (rather than testing the existence of each property). Indexes usually have only partial coverage. An 'indexed in' property could have qualifiers for coverage, such as start-end dates, ranges, etc, to better describe whether the indexing and provide a way to determine whether a journal article is indexed by the bibliographic index. When coverage data is populated, it would be possible to answer questions like 'Does Scopus (Q371467) have better coverage of list of sociology journals (Q2731858) than Academic Search (Q1273969). John Vandenberg (talk) 02:27, 1 March 2014 (UTC)
- Support. Filceolaire (talk) 14:56, 14 April 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
Google Scholar venue identifier
Description | Identifier used in Google Scholar Citations for a venue (academic journal) |
---|---|
Data type | String |
Template parameter | Brede Wiki Template:Journal param googlescholar |
Domain | creative work |
Example | Nature (Q180445) => 1Cv1bkrS5GIJ; NeuroImage (Q1981225) => QPz2joEs61IJ |
Source | Brede Wiki; Google Scholar |
Proposed by | John Vandenberg (talk) |
- Discussion
Google Scholar venue is an alternative to Scopus source ID (P1156), etc. The Google Scholar venue database can be navigated by top 100 (per publication language), by discipline[7], or by title[8]. The venue IDs have .20121115 or .2013 at the end to indicate which set of Google Citation data being used (November 2012 vs July 2013) btw Google Scholar has another way to look at a venue, which is publications in a venue using the as_publication advanced search field, but I havent fully worked out how well that works at distinguishing between journals of similar names. e.g. this is articles in Nature. John Vandenberg (talk) 05:52, 1 March 2014 (UTC)
Not done Lack of support.--Micru (talk) 20:47, 25 April 2014 (UTC)
Inflation rate
Description | Percent change increase in CPI in one year |
---|---|
Data type | Number (not available yet) |
Domain | Countries, regions and cities |
Allowed values | A positive or negative percentage |
Source | http://data.worldbank.org/indicator/FP.CPI.TOTL.ZG |
Robot and gadget jobs | Global Economic Map Bot can do this |
Proposed by | Mcnabber091 (talk) 19:01, 14 April 2014 (UTC) |
- Support, rather straightforward (with a point in time (P585) qualifier. --Zolo (talk) 07:51, 26 April 2014 (UTC)
- Created Vogone (talk) 19:35, 1 May 2014 (UTC)
NARA-ARC
Description | National Archives and Records Administration (Q518155), Used in zh:Template:Authority control |
---|---|
Data type | String |
Example 1 | MISSING |
Example 2 | MISSING |
Example 3 | MISSING |
Source | http://arcweb.archives.gov/arc/action/ExternalPersonIdSearch?id=***&jScript=true |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 16:16, 2 December 2013 (UTC)
- Support Tentative support, but could you give some examples? @Dominic:..? John Vandenberg (talk) 17:07, 2 December 2013 (UTC)
- Support not only the Chinese WP but of cause also the English WP is using NARA. Please add infos and compare 1) en:Template:NARA and 2) en:Template:NARA catalog record. Do we need two properties? How should the properties be named? --Kolja21 (talk) 17:02, 5 December 2013 (UTC)
- Support. I'll ping Dominic. Emw (talk) 04:11, 3 January 2014 (UTC)
Hi all. Thanks, Eric; sorry I didn't get your ping, John. I don't log into Wikidata enough. I like the idea of adding support for NARA, but we might need to think a bit before implementing it. First is that NARA's "ARC" catalog is no longer supported. It is only maintained right now as a legacy for old incoming links. So, for example, the given link should actually be "http://research.archives.gov/person/xxx
". This is the same authority record with the same IDs, just in an improved interface. I have changed all the URLs in English Wikipedia and Commons templates, but obviously some old links persist. The second issue is that there are several different URL structures within the NARA authority file for the type of authority. The URL above is only for person authority records, and there are different URLs (and sets of IDs) if it is an organization, geographical, subject, or specific records type authority record.
I would have to check and make sure I haven't forgotten any more types. As far as I know, only the first three are used with in any large volume on Wikimedia projects so far. And finally, of course, NARA has both an online catalog and an authority file, so catalog records themselves are also different, using the form:
Catalog record IDs go by the name "National Archives Identifier", but I am not sure if there is a preferred name for authority record IDs (it would not be "ARC"). I will have to check on that.
- Dominic, do you think it would be reasonable to have 1 property for NARA-ARC ID and 1 property for each of the NARA types -- e.g. 'NARA person ID', 'NARA organization ID', etc.? Regarding this 'NARA-ARC' property, even though the ARC catalog is no longer supported, I'm guessing that there might be users interested in looking up things by legacy ARC ID. Perhaps having both the new and old NARA IDs on the same item would help users like zh:Template:Authority control migrate from NARA ARC to the new recommended NARA type IDs. Emw (talk) 01:30, 6 January 2014 (UTC)
- Sorry if I was unclear. What I meant was that ARC and the new catalog ("Online Public Access", OPA) are the same in all respects—same data, same IDs—except it's a different URL structure that takes you to a catalog with a better interface and different name. But they are interchangeable, which was why I was able to the vast majority of ARC links on Wikimedia projects already just by changing a few of the templates that generate archives.gov links. So what I am saying is that all NARA IDs should be generating research.archives.gov links, and arcweb.archives.gov links are never necessary; this doesn't break anything, just offers more functionality. Similarly, no properties should be named with "ARC" in them.
- To your other point, I would suggest 1 property for catalog records, i.e. "National Archives Identifier", and 1 property for each of the authority record types (unless you think we should limit it only to the most common types). It is conceivable that there could be multiple authority record IDs with different types for the same Wikidata item—for example, the state of Mississippi could be an organization, an geographical location, and a subject. I think we would probably want to call them something like "NARA person authority record identifier" to be specific. I sent an email to our authorities staff to ask if they want to weigh in on any of these issues. Dominic (talk) 04:04, 6 January 2014 (UTC)
- Support -- SERutherford (talk) 11:50, 28 April 2014 (UTC)
Not done Dominic, SERutherford, Eric, John, Kolja21: Already done as P1231 (P1231). According to Dominic, the nara ARC-ID is legacy and is equivalent to the NARA ID (same number, just a different base url), besides "no properties should be named with "ARC" in them". The other requested authority properties have been already created too (see from P1222 to P1226).--Micru (talk) 12:32, 30 April 2014 (UTC)
Cultural heritage database in Sweden
Description | Swedish National Heritage Board (Q631844) has set up a webservice for the cultural monuments, protected buildings and items that are connected to a number of museums in Sweden. |
---|---|
Data type | String |
Template parameter | Commons and svwp have a number of templates based on this. Some examples are: sv:Mall:RAÄ-nummer and commons:Template:Fornminne are some examples. |
Domain | cultural heritages in Sweden |
Example | runestone: raa/fmi/html/10028200010001 -> Uppland Runic Inscription 932 (Q7899135), church: raa/bbr/html/21300000003265 -> Hidinge church (Q2892790) |
Robot and gadget jobs | yes |
Proposed by | Lavallen (talk) |
- Discussion
The exact syntax of this property, am I asking @Lokal Profil: about. Lavallen (talk) 14:09, 6 March 2014 (UTC)
- Having one property for all of these might be a good solution. I would skip the "/html/" part though and instead just use "raa/fmi/10028200010001" etc. Links to the entityUri would then be generated though http://kulturarvsdata.se/{{kulturarvsdata}}. The Initial part of the string could also be limited to only a list of valid combinations.
- It's worth noticing that an entity could have several of these entries. My worry therefore would be that it might be harder to identify which of these is which for inclusion in templates. To give a practical example
- Lund Cathedral (Q1236689) has both raa/bbr/21300000022524 (facility-level) and raa/bbr/21400000439699 (building-level) and in this case it is the only building in the facility;
- from a usability point of view it would then be easier to split the property up into 'bbr-facility', 'bbr-building' etc. (there are a lot of them though). /André Costa (WMSE) (talk) 16:55, 6 March 2014 (UTC)
- The version without
/html/
links to an api-version of the file, that's great! It's simple to modify the link in WP/Commons to make it readable for ordinary users. The only drawback is that it's maybe not as simple to make human readable links with the present Gadget, but that is of less importance. - The 'building/facility-level'-problem, I think, could be solved by some kind of qualifier. As far as I have understood, it's ~25 museums related to kulturarvsdata, except for the buildings, old tombs and rockcarvings etc. That could make an awful amount of properties. -- Lavallen (talk) 17:46, 6 March 2014 (UTC)
- A qualifier could probably solve this yes. For some of these museums the URI is built up using the internally used code/name of the object, for others a separate property (such as RAÄ-number below) might still be needed. Still that would not diminish the value of this property. /André Costa (WMSE) (talk) 11:22, 7 March 2014 (UTC)
- @André Costa (WMSE): Can you provide more examples, than
fmis
andbbr
? -- Lavallen (talk) 11:39, 10 March 2014 (UTC)- sv:Kategori:Externa länkmallar via K-samsök has the current encoded ones. Many of these are for specific objects in museums though and are as such less likely to be useful on wikidata. But as an example we have http://kulturarvsdata.se/LSH/objects/32631 for the quite famous File:Porträtt, Rudolf II som Vertumnus. Guiseppe Arcimboldo - Skoklosters slott - 87582.tif.
- All the available services are listed at [9] but the descriptions aren't always clear, some of them should be grouped and they don't always coincide with the uri. /André Costa (WMSE) (talk) 12:58, 10 March 2014 (UTC)
- @André Costa (WMSE): Can you provide more examples, than
- A qualifier could probably solve this yes. For some of these museums the URI is built up using the internally used code/name of the object, for others a separate property (such as RAÄ-number below) might still be needed. Still that would not diminish the value of this property. /André Costa (WMSE) (talk) 11:22, 7 March 2014 (UTC)
- The version without
- @Innocent bystander:: I'd suggest we create this with the structure suggested above. Additionally a filter can be set up to only accept existing services. Could a filter also be set up for the qualifiers? /André Costa (WMSE) (talk) 14:59, 28 April 2014 (UTC)
- Done as Swedish Open Cultural Heritage URI (P1260) @André Costa (WMSE), Laddo: I ask Laddo to review the constraints here. -- Innocent bystander (talk) (The user previously known as Lavallen) 17:01, 28 April 2014 (UTC)
- Thanks. Ping me if you need more info on the constraints. Which would the suitable property be for the dataset/service qualifier? Also would the value for this qualifier best be an object in it's own right which in turn has a claim stating that it is a subset/dataset of kulturarvsdata.? /André Costa (WMSE) (talk) 15:07, 29 April 2014 (UTC)
- I tested catalog (P972) now in Uppland Runic Inscription 932 (Q7899135). I have doubts if it is a correct use of that property, but maybe we can propose a new property for this. @Paperoastro, Zolo: applies to part (P518) may fit when there is several database-items for the same item. Like when both fmis (cultural heritage) and bbr (protected buildings) have an item for the same object. -- Innocent bystander (talk) (The user previously known as Lavallen) 15:29, 29 April 2014 (UTC)
- I now also tested to use RAÄ number (P1262) as qualifier when fmis is used. I also tested an unorthodox way of using P387 (P387) -- Innocent bystander (talk) (The user previously known as Lavallen) 15:38, 29 April 2014 (UTC)
- I think P438 (P438) is more suitable than P387 (P387) (left a note on the talk page).
- applies to part (P518) may actually be the best fit. catalog (P972) would in part be implicit of the kulturarvsdata property itself whereas applies to part (P518) clarifies which of the individual datasets it comes from. What would then be needed would be the opposite property (i.e. X is a dataset in kulturarvsdata). /André Costa (WMSE) (talk) 07:40, 30 April 2014 (UTC)
- I now also tested to use RAÄ number (P1262) as qualifier when fmis is used. I also tested an unorthodox way of using P387 (P387) -- Innocent bystander (talk) (The user previously known as Lavallen) 15:38, 29 April 2014 (UTC)
- I tested catalog (P972) now in Uppland Runic Inscription 932 (Q7899135). I have doubts if it is a correct use of that property, but maybe we can propose a new property for this. @Paperoastro, Zolo: applies to part (P518) may fit when there is several database-items for the same item. Like when both fmis (cultural heritage) and bbr (protected buildings) have an item for the same object. -- Innocent bystander (talk) (The user previously known as Lavallen) 15:29, 29 April 2014 (UTC)
- Thanks. Ping me if you need more info on the constraints. Which would the suitable property be for the dataset/service qualifier? Also would the value for this qualifier best be an object in it's own right which in turn has a claim stating that it is a subset/dataset of kulturarvsdata.? /André Costa (WMSE) (talk) 15:07, 29 April 2014 (UTC)
- Done as Swedish Open Cultural Heritage URI (P1260) @André Costa (WMSE), Laddo: I ask Laddo to review the constraints here. -- Innocent bystander (talk) (The user previously known as Lavallen) 17:01, 28 April 2014 (UTC)
Rundata
Description | Rundata (Q492230) is a database about runestones, mainly in Sweden, but stones in all of Europe, Greenland and U.S. can be found here. |
---|---|
Data type | String |
Template parameter | signum in sv:Mall:Runinskriftsfakta |
Domain | Runestones |
Example | U 932 -> Uppland Runic Inscription 932 (Q7899135), Ög ATA4905/48 -> Östergötlands runinskrifter ATA4905/48 (Q10727999) |
Robot and gadget jobs | yes |
Proposed by | Lavallen (talk) |
- Discussion
Widely used database. Lavallen (talk) 14:09, 6 March 2014 (UTC)
- Support Although the correct name for this would be "Signum" or "Samnordisk runtextdatabas signum". This property would only include the first two parts of this (which is what is commonly used). /André Costa (WMSE) (talk) 17:09, 6 March 2014 (UTC)
- I propose that this is created per the definition above. Additionally a filter can be set up to requre that the id follows the pattern
"<place> <*>"
where <place> is(Bo|D|G|Gs|Hs|J|Lp|M|Nä|Sm|Sö|U|Vg|Vr|Vs|Ög|Öl|BR|DR|FR|GR|IR|IS|N|X)
and <*> can be any alphanumeric string including the characters ";/-()". /André Costa (WMSE) (talk) 15:09, 28 April 2014 (UTC)- @André Costa (WMSE), Laddo: Done as Scandinavian Runic-text Database ID (P1261). Can you assist with the constraints, Laddo? -- Innocent bystander (talk) (The user previously known as Lavallen) 17:08, 28 April 2014 (UTC)
- I propose that this is created per the definition above. Additionally a filter can be set up to requre that the id follows the pattern
RAÄ-nummer
Description | Fornminnesregistret (Q10498015) is a database of the cultural heritage in Sweden. The links in that database can be provided by the proposed kulturarvsdata -property above, but the name of each item in this database is a code based on the name of the civil parish or city followed by a serial number. |
---|---|
Data type | String |
Template parameter | sv:Mall:RAÄ-nummer and commons:Template:Fornminne |
Domain | cultural heritage in Sweden |
Example | Uppsala 1:1 -> Uppland Runic Inscription 932 (Q7899135) |
Robot and gadget jobs | yes |
Proposed by | Lavallen (talk) |
- Discussion
Widely used database. Lavallen (talk) 14:09, 6 March 2014 (UTC)
- Support These are the de facto codes for the objects. /André Costa (WMSE) (talk) 17:00, 6 March 2014 (UTC)
- Done as RAÄ number (P1262) @André Costa (WMSE): -- Innocent bystander (talk) (The user previously known as Lavallen) 17:10, 28 April 2014 (UTC)
Norway Database for Statistics on Higher education (DBH) periodical ID
Description | Norwegian identifier for academic journals |
---|---|
Data type | String |
Template parameter | no:Mal:Infoboks_forskningstidsskrift param DBH |
Domain | creative work |
Allowed values | items of periodical (Q1092563) |
Example | The American Economic Review (Q1740221) => 422543; The Southern Review (Q3522794) => 447679 |
Format and edit filter validation | [1-9][0-9]{5} |
Source | http://bibsys.no ; https://dbh.nsd.uib.no/publiseringskanaler/Forside?sok.avansert=true&request_locale=en |
Robot and gadget jobs | USer:JVbot will populate |
Proposed by | John Vandenberg (talk) |
- Discussion
DBH is the Norwegian Database for Statistics on Higher education (DBH). This is the equivalent of the ERA Journal ID (P1058) for Norway. It sources records from other systems, including ITAR (see below).
It is included in the Norwegian Wikipedia infobox for journals. John Vandenberg (talk) 04:49, 7 March 2014 (UTC)
- Support -- SERutherford (talk) 20:48, 6 April 2014 (UTC)
- Support--Micru (talk) 12:34, 30 April 2014 (UTC)
- @John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 14:14, 30 April 2014 (UTC)
Norway Database for Statistics on Higher education (DBH) publisher ID
Description | Norwegian identifier for academic publishers |
---|---|
Data type | String |
Domain | creative work |
Allowed values | items of publishing company (Q2085381) |
Example | De Gruyter (Q98818) => 18493 |
Format and edit filter validation | [1-9][0-9]{3,4} |
Source | http://bibsys.no ; https://dbh.nsd.uib.no/publiseringskanaler/Forside?sok.avansert=true&request_locale=en |
Robot and gadget jobs | USer:JVbot will populate |
Proposed by | John Vandenberg (talk) |
- Discussion
DBH is the Norwegian Database for Statistics on Higher education (DBH). It sources records from other systems, primarily ITAR (see below) which doesnt have an accessible web presence. It includes 1,551 publishers, with ISBN prefixes, country, website, and a list of journals it publishes. The cross linking of publisher and journal is very useful to populate publisher (P123) for academic journals. John Vandenberg (talk) 04:49, 7 March 2014 (UTC)
- Support -- SERutherford (talk) 20:51, 6 April 2014 (UTC)
- Support --Micru (talk) 12:35, 30 April 2014 (UTC)
- @John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 14:21, 30 April 2014 (UTC)
Norway Import Service and Registration Authority (ITAR) periodical code
Description | Norwegian identifier for academic journals |
---|---|
Data type | String |
Template parameter | no:Mal:Infoboks_forskningstidsskrift param ITAR_kode |
Domain | creative work |
Allowed values | items of periodical (Q1092563) |
Example | The Southern Review (Q3522794) => 355 (see DBH Journal ID 447679) |
Format and edit filter validation | 7 digit number |
Source | http://bibsys.no ; https://dbh.nsd.uib.no/publiseringskanaler/Forside?sok.avansert=true&request_locale=en |
Robot and gadget jobs | USer:JVbot will populate |
Proposed by | John Vandenberg (talk) |
- Discussion
ITAR is "a national public service to help to increase the quality of data about scientific publications in the existing systems for research documentation and the Database for Statistics on Higher education (DBH). ITAR contains authority records for scientific publication channels (journals, series, publishers). Only publications published in a publication channel found in ITAR will count as scientific. ITAR contains also data about scientific publications (ITAR-publications) provided by ISI and Norart. These publications will automatically count as scientific. ITAR is administered by the en:Norwegian Social Science Data Services (NSD)." [10]
It is included in the Norwegian Wikipedia infobox for journals. John Vandenberg (talk) 04:49, 7 March 2014 (UTC)
- Support -- SERutherford (talk) 21:00, 6 April 2014 (UTC)
- Support --Micru (talk) 12:36, 30 April 2014 (UTC)
- @John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 14:24, 30 April 2014 (UTC)
Norway Import Service and Registration Authority (ITAR) publisher code
Description | Norwegian identifier for academic publishers |
---|---|
Data type | String |
Domain | creative work |
Allowed values | items of publishing company (Q2085381) |
Example | De Gruyter (Q98818) => 355 (see DBH Publisher ID 18493) |
Format and edit filter validation | 4 digit number |
Source | http://bibsys.no ; https://dbh.nsd.uib.no/publiseringskanaler/Forside?sok.avansert=true&request_locale=en |
Robot and gadget jobs | USer:JVbot will populate |
Proposed by | John Vandenberg (talk) |
- Discussion
In several countries, including Australia and Denmark, the government evaluation of research is just beginning to control the list of accepted publishers of books (& chapters). Norway has been doing it for a while, with this identifier. Also the Norwegian database contains links between publisher and academic journals, so having this ID in Wikidata will be useful to datamine and create the same relationships in Wikidata. John Vandenberg (talk) 04:49, 7 March 2014 (UTC)
- Support -- SERutherford (talk) 20:52, 6 April 2014 (UTC)
- Support --Micru (talk) 18:10, 30 April 2014 (UTC)
- @John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 18:24, 30 April 2014 (UTC)
ISFDB title ID
Description | Link to a title record, of a creative work, on Internet Speculative Fiction Database (Q2629164). Link format: http://www.isfdb.org/cgi-bin/title.cgi?FOO where FOO is the value. |
---|---|
Data type | String |
Template parameter | {{isfdb title}} |
Domain | work (Q386724) |
Allowed values | numerics |
Example | Red Nails (Q4134557) => 68494 |
Proposed by | AdamBMorgan (talk) |
- Discussion
To complement the above. - AdamBMorgan (talk) 23:47, 19 March 2014 (UTC)
- Support -- SERutherford (talk) 21:06, 6 April 2014 (UTC)
- Support--Micru (talk) 17:23, 30 April 2014 (UTC)
- @AdamBMorgan, SERutherford, Micru: Done --Jakob (talk) 18:08, 30 April 2014 (UTC)
Notable Names Database ID
Description | NNDB (Q1373513) is a notable biographical database with more than 40,000 entries, so I think that it will be quite useful to have an NNDB id as a property. |
---|---|
Data type | String |
Domain | human (Q5) |
Example | Per Teodor Cleve (Q377822) --> 143/000213501 |
Source | http://nndb.com/people/$1 |
Robot and gadget jobs | import from en:Template:NNDB |
Proposed by | --Jakob (talk) |
- Discussion
- Support - Kolja21 01:19, 25 March 2014 (UTC)
- Support - AdamBMorgan (talk) 12:58, 25 March 2014 (UTC)
- Support - SERutherford (talk) 20:05, 5 April 2014 (UTC)
- @Kolja21, AdamBMorgan, SERutherford: Done Even though I participated, there seems to be sufficient consensus here. --Jakob (talk) 18:15, 28 April 2014 (UTC)
Legal Entity Identifier
Description | Legal Entity Identifier (Q6517388): 20-digit, alpha-numeric reference string to uniquely identify a legally distinct entity. Conforms to the ISO 17442 standard, “Financial Services - Legal Entity Identifier (LEI).” |
---|---|
Data type | String |
Domain | corporation (Q167037) and/or company (Q783794) |
Allowed values | 20-digit, alpha-numeric string, see: p-lei.org/faq and openleis.com for examples. See the Legal Entity Identifier Regulatory Oversight Committee at www.leiroc.org. |
Example | Microsoft (Q2283) => INR2EJN1ERAN0W5ZP974 (see also: openleis.com/legal_entities/INR2EJN1ERAN0W5ZP974 |
Source | openleis.com or p-lei.org |
Robot and gadget jobs | Bots could populate a great deal of LEIs for corporations/companies. |
Proposed by | SERutherford |
- Discussion
Legal Entity Identifiers would be a useful and highly authoritative international point of reference if attached to specific company/corporation profiles. SERutherford (talk) 18:40, 5 April 2014 (UTC)
- Support John Vandenberg (talk) 21:27, 26 April 2014 (UTC)
- Support --Micru (talk) 17:22, 30 April 2014 (UTC)
- @SERutherford, John Vandenberg, Micru: Done --Jakob (talk) 21:56, 30 April 2014 (UTC)
Jufo ID
Description | Finnish Publication Forum ID |
---|---|
Data type | String |
Domain | periodical (Q1092563) & publishing company (Q2085381) |
Allowed values | six digit number |
Example | Nature (Q180445) => 63759; Acta Clinica Croatica (Q15753866) => 77064 |
Source | CSVs at http://www.tsv.fi/julkaisufoorumi/haku.php |
Robot and gadget jobs | User:JVbot will populate |
Proposed by | John Vandenberg (talk) |
- Discussion
user:Fnielsen has informed me that the Finns have a controlled periodical/publisher list for their research evaluation framework. Their online database with 25,0000 records is linkable and has a lot of useful fields in it. It is reviewed every three years, with the first review currently underway now in 2014. The CSV files are dated 17 April 2014. These IDs are stable between the current CSVs and the previous published official list. John Vandenberg (talk) 09:06, 17 April 2014 (UTC)
- Support -- SERutherford (talk) 02:01, 18 April 2014 (UTC)
- Support --Micru (talk) 18:31, 30 April 2014 (UTC)
- @John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 18:35, 30 April 2014 (UTC)
Royal Aero Club Aviator's Certificate ID
Description | Royal Aero Club Aviator's Certificate ID |
---|---|
Data type | String |
Domain | Royal Aero Club (Q1149581) & aircraft pilot (Q2095549) |
Allowed values | numbers |
Example | Charles Gordon Bell (Q16546912): 1 |
Source | w:List of pilots awarded an Aviator's Certificate by the Royal Aero Club in 1910 |
Proposed by | Christoph Braun (talk) |
- Discussion
There are +1000 Royal Aero Club Aviator's Certificate IDs which could be attributed by creating this property. Christoph Braun (talk) 21:55, 22 April 2014 (UTC)
- Christoph beat me to it :-). There are actually 22000+ certificates issued before the RAC lost this responsibility, but they're mostly of interest for the very early years (pre-WWI), and are a very good way to track early figures in UK aviation. 58% of the people who got one in 1910 currently have articles on enwiki, and 29% of those who got one in 1911. Andrew Gray (talk) 22:02, 22 April 2014 (UTC)
- Support --Micru (talk) 11:56, 30 April 2014 (UTC)
- Support -- SERutherford (talk) 00:26, 3 May 2014 (UTC)
- @Christoph Braun, Andrew Gray, Micru, SERutherford: Done --Jakob (talk) 17:09, 5 May 2014 (UTC)
CONOR.SI
Description | Authority control number issued by the Information sciences institute of Slovenia |
---|---|
Data type | Number (not available yet) |
Template parameter | CONOR.SI in sl:Predloga:Normativna kontrola |
Domain | human (Q5), organizations |
Allowed values | numbers, no obvious rule |
Example | France Prešeren (Q1031) => 954467 |
Source | Cobiss.si, a few have been inserted manually, see sl:Kategorija:Wikipedijini članki z identifikatorji CONOR.SI |
Proposed by | — Yerpo Eh? |
- Discussion
National authority control file, useful for Slovene authors. — Yerpo Eh? 07:49, 24 April 2014 (UTC)
- Comment The concrete template parameter seems to be used in about 15 articles in sl:WP and at the target site there is no "added value", i.e. at the moment it is not possible to reach any content of cobiss.si or dlib.si related to the authority record (the articles in the category mentioned above use a template accessing content by name search, not identifiers). However I could verify that an ID presented by CONOR is actually used in records of the national library in Ljubljana and that integration into VIAF has been announced last year: Seems the identifiers are at least stable enough to consider them as such. -- Gymel (talk) 09:02, 24 April 2014 (UTC)
- Granted, the functionality of the CONOR.SI database is rather limited for now, but it's a relatively new thing that is being actively developed. However, it does list alternative author names which constitutes added value. And no, the :slwiki template doesn't access content by name search, where did you get that idea? — Yerpo Eh? 09:13, 24 April 2014 (UTC)
- Sorry, on first inspection I somehow have missed to recognize the authority entry for CONOR.SI at sl:Zofka Kveder and thought that {{Dlib|ime=Zofka Kveder}} would trigger the category listing. Indeed the category is filled by the Lua module and directly reflects usaage of the CONOR.SI parameter (I got my number above indirectly by sl:Posebno:LinkSearch). BTW do you know if there is a relation at all between Digitalna knjižnica Slovenije and Virtualna knjižnica Slovenije and especially whether there are plans to make the digital content accessible via CONOR identifiers? -- Gymel (talk) 12:08, 24 April 2014 (UTC)
- Granted, the functionality of the CONOR.SI database is rather limited for now, but it's a relatively new thing that is being actively developed. However, it does list alternative author names which constitutes added value. And no, the :slwiki template doesn't access content by name search, where did you get that idea? — Yerpo Eh? 09:13, 24 April 2014 (UTC)
- Digitalna knjižnica (dLib) is a digitalization project by the National and University Library of Slovenia (NUK). NUK is covered by the COBISS system, but I am not aware of any plans to integrate dLib entries with the CONOR database. At least not yet, but as I said, CONOR is still being developed, so it could be reasonably expected. Actually, Dlib doesn't have special author listings in the database at all, relying on name search instead (example). — Yerpo Eh? 14:16, 24 April 2014 (UTC)
- Support --Micru (talk) 11:54, 30 April 2014 (UTC)
- Support -- SERutherford (talk) 22:20, 2 May 2014 (UTC)
- @Gymel, Yerpo, Micru, SERutherford: Done as a String datatype. --Jakob (talk) 00:14, 3 May 2014 (UTC)
WOEID
Description | unique geographic location ID used by Yahoo! GeoPlanet |
---|---|
Data type | String |
Domain | geographic location (Q2221906) |
Allowed values | 32-bit value as a plain decimal integer: i.e. presumably a whole number between 1 and 4294967295 |
Example |
|
Format and edit filter validation | {{Constraint:Single value}} {{Constraint:Unique value}} {{Constraint:Format|pattern=<nowiki>[1-4]?\d{1,9} |
Source | w:en:WOEID; https://developer.yahoo.com/geo/geoplanet/guide/concepts.html#woeids (WOEID introduction); https://developer.yahoo.com/geo/geoplanet/guide/index.html (guide to Yahoo GeoPlanet, the authoritative database for the WOEID) |
List of violations of this constraint: Database reports/Constraint violations/Property proposal/Archive/21#Range
List of violations of this constraint: Database reports/Constraint violations/Property proposal/Archive/21#Type Q2221906, SPARQL
</nowiki>
|robot and gadget jobs = No current bots or gadgets as far as I know. Someone could do data collection: The Yahoo GeoPlanet API already contains support for English Wikipedia page ID concordance as value "wiki
" (as well as several other cross-reference values) in the /concordance data. Where the en.wiki page ID doesn't exist in the Yahoo data, a bot could be designed to add the WOEID to Wikidata items when there is high confidence: for example, if there is a located in the administrative territorial entity (P131) of type second-level administrative division (Q13220204) for the Wikidata item, and that matches exactly one name in Yahoo GeoPlanet with the same Admin2, and the name is not ambiguous on the native language Wikipedia (i.e. needs unusual qualifiers in the title), then the item on Wikidata would have a high-confidence match to that WOEID. Or a gadget could allow user-assisted matching.
|proposed by = Closeapple (talk)
}}
- Discussion
Q7953796 ("Where On Earth Identifier") is a numeric identifier assigned to individual places for the Yahoo GeoPlanet (formerly Yahoo! Internet Location Platform) location database, which includes major buildings, parks, neighborhoods, cities, states/provinces, countries, continents, and seas (see Response Data Elements for a list of place types, and Place Types for a subset used for regional divisions). It appears to be useful for Wikimedia purposes because:
- Its design standard is similar to other authority control numbers: The GeoPlanet "Key Concepts" page states that "WOEIDs are unique and non-repetitive, and are assigned to all entities within the system. A WOEID, once assigned, is never changed or recycled. If a WOEID is deprecated it is mapped to its successor or parent WOEID, so that requests to the service using a deprecated WOEID are served transparently."
- It's the authority control number for the place names on Flickr pages: click on the location on a Flickr page and you'll see it link to a WOEID. The API (if you have access) also allows one to find nearby place names. If someone wrote the right code on Commons, that would reduce errors in bot and upload autocategorization on Flickr, since the text description (and/or coordinates) could be compared to the Flickr location name, to make category guesses with more confidence and thus less annoyance; for example, if the place name from Flickr also matched a word in the description, it would be more likely that the proper category is the one with that ID.
- WOEIDs are assigned to neighborhoods and points of interest, not just legal administrative divisions.
- WOEIDs correspond to GeoPlanet database entries with extensive parent and child location information.
- The GeoPlaces database already has concordance to some English Wikipedia page IDs, and also contains several other concordance links.
A caveat, which probably isn't relevant to approval here: If a programmer were to use the Yahoo GeoPlanet API as a source for these, Yahoo seems to allow a single application user only a few tens of thousands of requests per day, equivalent to a request every 2 to 4 seconds. Closeapple (talk) 01:09, 25 April 2014 (UTC)
- Support in addition to accessing the structured metadata within GeoPlanet, it is used by APIs such as the flickr API, and it also provides a simple way to jump across to resources in other platforms (such as flickr) as demonstrated in the examples above. In addition, this value is being written into the prose of articles.[11] John Vandenberg (talk) 22:18, 26 April 2014 (UTC)
- Support -- SERutherford (talk) 16:27, 27 April 2014 (UTC)
- Support --Micru (talk) 11:52, 30 April 2014 (UTC)
- @Closeapple, John Vandenberg, SERutherford, Micru: Done --Jakob (talk) 00:21, 3 May 2014 (UTC)
AlloCiné
→ Property:P1266 → Property:P1267
Description | AlloCiné (Q31165) identifier for French cinema, especially centering on novelties' promotion with DVD information. |
---|---|
Data type | String |
Template parameter | AlloCiné is used in 4 wikis via Template:AlloCiné title (Q14957268), and used in more than 5000 pages in frwiki. |
Domain | film |
Allowed values | unique identifier |
Example | The Pianist (Q150804)=>28359 |
Proposed by | GZWDer (talk) |
- Discussion
Restart request archived in Wikidata:Property_proposal/Archive/20. It's useful to store AlloCiné data in Wikidata. GZWDer (talk) 09:59, 26 April 2014 (UTC)
- Support. John Vandenberg (talk) 21:48, 26 April 2014 (UTC)
- Support -- SERutherford (talk) 02:03, 27 April 2014 (UTC)
- Support --Micru (talk) 09:43, 27 April 2014 (UTC)
- Support. Mushroom (talk) 12:08, 27 April 2014 (UTC)
Done : AlloCiné film ID (P1265), AlloCiné person ID (P1266), AlloCiné series ID (P1267). — Ayack (talk) 12:17, 30 April 2014 (UTC)
CANTIC
Description | The Catàleg d’autoritats de noms i títols de Catalunya (CANTIC, Catalonia names and titles authority catalog) is an authority catalog done by Catàleg Col·lectiu de les Universitats de Catalunya (CCUC, colective catalog of Catalonia Universities) and managed by the National Library of Catalonia (Q1200925). |
---|---|
Data type | String |
Template parameter | used in the Catalan version of Template:Authority control (Q3907614) (experimental) |
Domain | creative work, persons |
Allowed values | string pattern ('http://cantic.bnc.cat/registres/CUCId/$1') |
Example | Joan Fuster Ortells (Q561147) => http://cantic.bnc.cat/registres/CUCId/a10640745 |
Source | National Library of Catalonia |
Robot and gadget jobs | can be imported from Viaf.org and from Plantilla:Autoritat |
Proposed by | Micru (talk) |
- Discussion
Motivation: After a meeting Amical Wikimedia volunteers with the National Library of Catalonia, there was a great interest of interlinking the catalogue with the Catalan Wikipedia via Wikidata. This property is necessary for this task.--Micru (talk) 13:30, 29 April 2014 (UTC)
- Support--Kippelboy (talk) 13:39, 29 April 2014 (UTC)
- Support--Pere prlpz (talk) 14:05, 29 April 2014 (UTC)
- Support It will be useful.-KRLS (talk) 14:12, 29 April 2014 (UTC)
- Support--Mafoso (talk) 14:57, 29 April 2014 (UTC)
- Support --Arnaugir (talk) 16:09, 29 April 2014 (UTC)
- Support --ESM (talk) 16:12, 29 April 2014 (UTC)
- Support --Docosong (talk) 21:57, 29 April 2014 (UTC)
- Support -- SERutherford (talk) 01:32, 30 April 2014 (UTC)
- Support -- Gymel (talk) 09:04, 30 April 2014 (UTC)
- @Micru, Kippelboy, Pere prlpz, KRLS, Mafoso: @Arnaugir, ESM, Docosong, SERutherford, Gymel: Done I know this is being closed way early, but it's got so much support that this is a UCS/SNOW case. --Jakob (talk) 14:37, 30 April 2014 (UTC)
political position
Description | the political position of the organization, person, etc. |
---|---|
Data type | Item |
Template parameter | "position" in en:template:infobox political party |
Domain | person, place, creative work |
Allowed values | political positions |
Example | Conservative Party (Q9626) => centre-right (Q844072) |
Source | infoboxes |
Proposed by | Danrok (talk) 20:18, 29 January 2014 (UTC) |
- Discussion
- Support Good idea also. Ajraddatz (Talk) 03:21, 30 January 2014 (UTC)
- Comment Unclear. "Position" is not a parameter in en:template:infobox political party. --Kolja21 (talk) 07:26, 4 February 2014 (UTC)
- Seems that is is, but not documented. It is present here: Conservative Party (UK). Danrok (talk) 16:06, 5 February 2014 (UTC)
- Question Isn't this a type that should be a "subclass of"-statement? @Emw: --Tobias1984 (talk) 18:05, 4 February 2014 (UTC)
- Don't we already have political ideology (P1142)? --Wylve (talk) 20:10, 12 February 2014 (UTC)
- You are asking and answering your question at the same time. Danrok (talk) 11:15, 15 February 2014 (UTC)
- I think User:Wylve was asking "What makes this different from political ideology (P1142)?". --Arctic.gnome (talk) 18:50, 24 February 2014 (UTC)
- To state the obvious, no it is not that same. Danrok (talk) 00:10, 3 April 2014 (UTC)
- @Danrok: It's not obvious to me. Can you explain how this is different from P1142? Filceolaire (talk) 15:07, 14 April 2014 (UTC)
- To state the obvious, no it is not that same. Danrok (talk) 00:10, 3 April 2014 (UTC)
- I think User:Wylve was asking "What makes this different from political ideology (P1142)?". --Arctic.gnome (talk) 18:50, 24 February 2014 (UTC)
- You are asking and answering your question at the same time. Danrok (talk) 11:15, 15 February 2014 (UTC)
- Don't we already have political ideology (P1142)? --Wylve (talk) 20:10, 12 February 2014 (UTC)
Not done Lack of consensus.--Micru (talk) 21:14, 25 April 2014 (UTC)
replaced/succeeded by (organization/regime)
Description | a separate property like both followed by (P156) / structure replaced by (P167). |
---|---|
Data type | Item |
Domain | organization |
Example | Ming dynasty (Q9903)=>Qing dynasty (Q8733) |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 16:24, 4 February 2014 (UTC)
- @GZWDer: Can you choose an example that shows why we need this property? --Tobias1984 (talk) 17:40, 4 February 2014 (UTC)
- Because of there're no Chinese word means both "replaced by" and "following item".--GZWDer (talk) 17:42, 4 February 2014 (UTC)
- @GZWDer: I still don't understand. There is a property called "succeeded by (p156)" and a property "replaced by (p167)", and because in Chinese there is no word for "replaced and following" of them you want to create another property that will get the English label "replaced/succeeded by"? --Tobias1984 (talk) 17:53, 4 February 2014 (UTC)
- @Tobias1984:followed by (P156) only for two items exists at same time; structure replaced by (P167) only for building and structure; this for organization/regime. see Ivan A. Krestinin's comment at "replaces" section at Wikidata:Property proposal/Place.--GZWDer (talk) 17:56, 4 February 2014 (UTC)
- @GZWDer: I don't understand what that has to do with this one? --Tobias1984 (talk) 18:02, 4 February 2014 (UTC)
- @Tobias1984:followed by (P156) only for two items exists at same time; structure replaced by (P167) only for building and structure; this for organization/regime. see Ivan A. Krestinin's comment at "replaces" section at Wikidata:Property proposal/Place.--GZWDer (talk) 17:56, 4 February 2014 (UTC)
- @GZWDer: I still don't understand. There is a property called "succeeded by (p156)" and a property "replaced by (p167)", and because in Chinese there is no word for "replaced and following" of them you want to create another property that will get the English label "replaced/succeeded by"? --Tobias1984 (talk) 17:53, 4 February 2014 (UTC)
- structure replaced by (P167) is for buildings (and similar) only. So, has no relevance to organizations. Also, in English succeeded is much the same as replaced in the context of positions of authority. Danrok (talk) 16:35, 7 February 2014 (UTC)
- followed by (P156) is used for series of books, albums, TV shows where an item is not replaced by a following item. This is a new property for cases where an organisation item is replaced by another item. I Oppose this proposal because I think that it should be combined with GZWDer's proposal for a 'replaced by' property for political offices. At the very least this needs to be expanded to cover successor states. Filceolaire (talk) 21:23, 24 February 2014 (UTC)
Not done--Micru (talk) 21:14, 25 April 2014 (UTC)
replaced/preceded by (organization/regime)
Description | a separate property like follows (P155). |
---|---|
Data type | Item |
Domain | organization |
Example | Qing dynasty (Q8733)=>Ming dynasty (Q9903) |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 16:24, 4 February 2014 (UTC)
- @GZWDer: Can you choose an example that shows why we need this property? --Tobias1984 (talk) 17:40, 4 February 2014 (UTC)
- Oppose proposal makes no sense. Danrok (talk) 20:05, 7 February 2014 (UTC)
- Oppose - what? --Jakob (talk) 22:07, 25 February 2014 (UTC)
Not done--Micru (talk) 21:14, 25 April 2014 (UTC)
Swiss Football Association Club Number
Description | official club number of the Swiss Football Association |
---|---|
Data type | String |
Domain | all Swiss football clubs being member of SFV |
Allowed values | numbers 1001 to 13999 |
Example | FC Aarau (Q603271) => 1001 |
Source | http://www.football.ch/fr/ASF/Service-ASF/Clubs/Clubs-ASF.aspx |
Proposed by | Pütz M. (talk) |
- Discussion
- @Pütz M.: changed to string. -- Lavallen (talk) 18:23, 6 April 2014 (UTC)
- Done as Property:P1241. -- Lavallen (talk) 12:36, 7 April 2014 (UTC)
league season
Description | The last completed competitive league season. i.e Not the current season. Its different from P118. (It comes together with my below proposal). |
---|---|
Data type | Item |
Template parameter | "season" in en:Template:Infobox football club |
Domain | sports team (Q12973014) |
Allowed values | text |
Example | Real Madrid CF (Q8682) => 2013–14 La Liga (Q6086248) |
Source | external reference, Wikipedia list article (either infobox or source) |
Robot and gadget jobs | collecting data |
Proposed by | Xaris333 (talk) |
- Discussion
Motivation. Xaris333 (talk) 17:44, 31 March 2014 (UTC)
- @Xaris333: The current paradigm of Wikidata is to make properties time independent. So instead of limiting the property to "last season" I would use "league season + time qualifier". In that case you can link to all seasons that have a Wikidata-item:
- Real Madrid CF (Q8682)
- league season: 2013–14 La Liga (Q6086248)
- Qualifier: Point in time: 2013-2014
- league season: 2012–13 La Liga (Q720018)
- Qualifier: Point in time: 2012-2013
- league season: 2013–14 La Liga (Q6086248)
- Real Madrid CF (Q8682)
- I generally think we need to store this information, but I also don't know if this information could also be queried in a different way. Or even stored in a different way. After all the season of a leuage is a subclass of the leauge itself. If a club played in that leauge it also participated in that season. But until we have that technical capability we might need to use a more direct approach. --Tobias1984 (talk) 20:57, 1 April 2014 (UTC)
- I agree. And the most recent completed competitive league season to be at the top of the list. Xaris333 (talk) 21:05, 1 April 2014 (UTC)
- Oppose. This is too specialised. We need a generic property for all athletes/sports teams/candidates competing in sports leagues/races/elections. Renames this as "Participated in" or "Competed in" and move it to Property Proposal/Event I will support. Filceolaire (talk) 15:04, 14 April 2014 (UTC)
- As you have season items like 2013–14 La Liga (Q6086248), just add "participant (P710) Real Madrid CF (Q8682)" and start time (P580)/end time (P582) to the them. The rest is deducible. — Felix Reimann (talk) 09:50, 19 April 2014 (UTC)
Not done--Micru (talk) 21:14, 25 April 2014 (UTC)
league season position
Description | The league and position to which season refers. (It comes together with my above proposal). |
---|---|
Data type | number (1st, 2nd, 3rd, ...)-invalid datatype (not in Module:i18n/datatype) |
Template parameter | "position" in en:Template:Infobox football club |
Domain | sports team (Q12973014) |
Allowed values | 1st, 2nd, 3rd, ..., 30th |
Example | Real Madrid CF (Q8682) => 2nd |
Source | external reference, Wikipedia list article (either infobox or source) |
Robot and gadget jobs | collecting data |
Proposed by | Xaris333 (talk) |
- Discussion
Motivation. Xaris333 (talk) 17:44, 31 March 2014 (UTC)
- @Xaris333: This also needs time qualifiers (start and end date). League position changes after each game day. But that is the resolution we need in order to make sense of this property. Things like "best position 2012", "worst position between 2000 and 2005" can then be queried. That sounds like a lot of data now but we will probably laugh about this once Wikidata reaches Giga- and TeraStatements. --Tobias1984 (talk) 21:02, 1 April 2014 (UTC)
- The idea (due to the template) was to have the final position of the last completed season. Xaris333 (talk) 21:04, 1 April 2014 (UTC)
- @Xaris333: It is of course difficult to talk about things that are still work in progress, but I am pretty sure we will be able to query the final position of the season with some Lua-code. In general it would be good to only gather the final position in the beginning until more complex data sets can be easily queried and implemented in the infoboxes. --Tobias1984 (talk) 21:23, 1 April 2014 (UTC)
- The idea (due to the template) was to have the final position of the last completed season. Xaris333 (talk) 21:04, 1 April 2014 (UTC)
- Oppose. Needs to me more generic so it can be used in all sorts or races and competitions. See Wikidata:Property_proposal/Person#performance. Filceolaire (talk) 15:30, 14 April 2014 (UTC)
Not done--Micru (talk) 21:14, 25 April 2014 (UTC)
godparent
Description | godparent(s) of person |
---|---|
Data type | Item |
Domain | person |
Example | Queen Victoria godparent was Alexander I of Russia |
Source | external reference |
Robot and gadget jobs | no |
Proposed by | EugeneZelenko (talk) |
- Discussion
Some persons have godparent/godchild relations. --EugeneZelenko (talk) 04:34, 18 February 2014 (UTC)
- I don't think we should list everyone who has Queen Victoria as a Godparent but I think we might list the inverse property - for notable persons say who they are Godchild of (aka has Godparent). Filceolaire (talk) 21:11, 24 February 2014 (UTC)
- Queen Victoria is godchild in example. Please don't misinterpret godparent with godchildren. I suggested first, sure lists of godchildren could be very long and hard to maintain. --EugeneZelenko (talk) 14:52, 25 February 2014 (UTC)
- Support — Ayack (talk) 20:35, 1 March 2014 (UTC)
- Comment Maybe it would be enough using relative (P1038) with qualifier kinship to subject (P1039)=>godparent (Q223973), which are already used for non-blood relationships (like adoptions).--Micru (talk) 18:02, 3 March 2014 (UTC)
- Support --- Jura 11:00, 3 May 2014 (UTC)
- @EugeneZelenko, Filceolaire, Ayack, Micru, Jura1: Done
filmography
Description | list of films the person worked on |
---|---|
Data type | Item |
Domain | person |
Allowed values | instance of (P31) => filmography (Q1371849), is a list of (P360) => film (Q11424) |
Example | Bruce Lee (Q16397) => Bruce Lee filmography (Q4977862) |
Proposed by | Mushroom (talk) |
- Discussion
We need a way to link the hundreds of filmography items to their subjects. Just like discography (P358). Mushroom (talk) 11:01, 7 April 2014 (UTC)
- Support —Wylve (talk) 18:37, 25 April 2014 (UTC)
- Support --- Jura 11:00, 3 May 2014 (UTC)
- @Mushroom, Wylve, Jura1: Done --Jakob (talk) 11:41, 3 May 2014 (UTC)
ADS
Description | identifier in database of contemporary writers of the Association Authors of Switzerland (AdS) |
---|---|
Data type | String |
Template parameter | Template:ADS |
Domain | Swiss writers |
Allowed values | see sample |
Example | Chessex: 331, Peter von Matt: 1165 |
Source | Template:ADS, beacon file, search fr.wikipedia |
- Discussion
Reference the database on modern writers. --- Jura 00:31, 13 April 2014 (UTC)
- Comment Similar to Property:P1253. --- Jura 18:24, 2 May 2014 (UTC)
- Support -- SERutherford (talk) 18:51, 3 May 2014 (UTC)
- Support -- Gymel (talk) 09:20, 4 May 2014 (UTC)
- @Jura1, SERutherford, Gymel: Done --Jakob (talk) 12:04, 4 May 2014 (UTC)
body height
Description | body height of a person |
---|---|
Data type | Number (not available yet) |
Template parameter | en:Template:Infobox person => "Height"; en:Template:Infobox boxer => "Height"; en:Template:Infobox spy => "Height") |
Domain | person (Q215627) |
Allowed values | decimal numbers |
Example | Rafael Nadal (Q10132) => 1.85 meters; Hermann Maier (Q1956) => 1.81 meters |
Source | en:Template:Infobox person |
Proposed by | Stiegenaufgang (talk) |
- Discussion
- Not done See Wikidata:Property proposal/Pending/2#Height of person.--GZWDer (talk) 12:25, 29 April 2014 (UTC)
Munzinger
→ Property:P1284 → Property:P1285 → Property:P1286 → Property:P1287 → Property:P1288 → Property:P1289
Description | ID of Munzinger Archiv website |
---|---|
Data type | String |
Domain | people and organizations (music bands) |
Allowed values | String with exactly 11 numerical characters (11 digit number including zeros at the beginning). A Wikidata item should be allowed to contain several Munzinger numbers. |
Example | Charles Noguès (Q2721164) -> 00000001432 -> http://www.munzinger.de/search/go/document.jsp?id=00000001432 |
Robot and gadget jobs | A bot could fill the property by importing data from
I could also provide a simpler csv format that only features GND (= P227) and Munzinger ID. |
Proposed by | AndreasPraefcke (talk) |
- Discussion
The (quite large) BEACON files already cover those people that also have a GND authority entry. Munzinger Archiv features many more, though (e. g. sportspeople or diplomats). The Munzinger Archiv products have been a well-known biographical source since way back in the pre-digital age, and the website is freely accessible to many public library users throughout Germany. Even without this possibility, the website features information as to dates and places of birth and death and the formation of the described persons within its free parts that are of some use to users. --AndreasPraefcke (talk) 15:16, 25 April 2014 (UTC)
Alternatively, there could be six different properties (each with only one entry per Wikidata item) for each of the products:
- Munzinger IBA
- Munzinger Sport
- Munzinger Pop
- KDG Komponisten der Gegenwart
- KLG Kritisches Lexikon der Gegenwartsliteratur
- KLFG Kritisches Lexikon der fremdsprachigen Gegenwartsliteratur
--AndreasPraefcke (talk) 15:20, 25 April 2014 (UTC)
- Question You mention "the Munzinger Archiv products": Should therefore (in the one-property variant) any value for this property be accompanied by a qualifier noting the Wikidata item of the specific product it applies to? Could that be part of (P361) or collection (P195) - I have no idea wether these are intended to use as qualifiers: It is not the item (i.e. person) which is part of the database or (sub-)collection but rather only the biographical essay referenced by the proposed property. Or would rather be stated in (P248) mandatory even it this might suggest the data here would acctually have been ingested directly rather than imported from intermediate lists? -- Gymel (talk) 22:13, 25 April 2014 (UTC)
- Actually, the first two digits of the ID stand for the "product". 00: IBA, 01: Sport, etc. Probably six different properties are best, for future use of Wikidata data within Wikipedia articles. I'd still rather like the whole 13 number ID in the database, regardless if it is somewhat redundant, since everything else is bound to cause difficulties. As to a "source" fields etc., I don't know much and I don't care at all, since I have never found any of those to be of any use before. --AndreasPraefcke (talk) 14:08, 27 April 2014 (UTC)
- I would like to Support the proposed approach of six different (and otherwise "unqualified") properties with "compatible" (i.e. complete) identifiers and the opportunity to impose an additional uniqueness constraint on the values.
- The sidebar of the Munzinger corporate home page lists "Munzinger Personen" (IBA?), "Munzinger Sport" and "Munzinger Pop" as one "Biography" Group and "KLG", "KLfG", "KdG" together with the famous KLL (Kindlers Literatur Lexikon, in contrast to the former not even a biographical sketch is shown, just a login prompt) and other more encyclopedia-like products in a different section: I would propose to decoupple at least KLG, KLfG and KdG to property proposals of their own. -- Gymel (talk) 16:06, 27 April 2014 (UTC)
- Support Frequently referenced in Wikipedia. --- Jura 11:00, 3 May 2014 (UTC)
- @AndreasPraefcke, Gymel, Jura1: Done as Munzinger person ID (P1284), Munzinger Sport number (P1285), Munzinger Pop ID (P1286), Komponisten der Gegenwart ID (P1287), Kritisches Lexikon der Gegenwartsliteratur ID (P1288), and Kritisches Lexikon zur fremdsprachigen Gegenwartsliteratur ID (P1289). --Jakob (talk) 12:07, 3 May 2014 (UTC)
Thank you. This is already very helpful for me. --89.247.155.144 14:36, 5 May 2014 (UTC)
Emissivity
Description | emissivity (Q899670) |
---|---|
Data type | Number (not available yet) |
Allowed values | 0-1 |
Example | cement (Q45190)=>0.54 |
Proposed by | GZWDer (talk) |
- Discussion
Motivation. GZWDer (talk) 10:06, 6 March 2014 (UTC) Support --Micru (talk) 15:34, 18 April 2014 (UTC)
- @GZWDer, Micru: Done No opposition for two months. --Jakob (talk) 13:56, 6 May 2014 (UTC)
number of elevators (lifts)
Description | total number of elevators (lifts) |
---|---|
Data type | Number (not available yet) |
Template parameter | "elevator_count" in en:template:infobox building |
Domain | geographic location (Q2221906) |
Allowed values | positive whole number |
Example | Tour First (Q1509747) => 28 |
Source | external reference, Wikipedia list article (either infobox or source) |
Proposed by | Danrok (talk) 15:26, 9 March 2014 (UTC) |
- Discussion
- Support--Micru (talk) 15:44, 9 March 2014 (UTC)
- Support. As used in infobox. ----- Jura 10:26, 10 May 2014 (UTC)
lostbridges.org ID
Description | lostbridges.org is a database of covered bridges in the United States ans Canada |
---|---|
Data type | String |
Domain | covered bridge |
Example | Josiah Hess Covered Bridge No. 122 (Q6290513) --> PA/38-19-10 |
Source | http://www.lostbridges.org/details.aspx?id=$1&loc=n |
Proposed by | --Jakob (talk) |
- Discussion
Large and comprehensive database. --Jakob (talk) 22:27, 6 April 2014 (UTC)
- Looks like a lovly database! -- Lavallen (talk) 16:04, 11 April 2014 (UTC)
- Support ----- Jura 10:26, 10 May 2014 (UTC)
- Support. Emw (talk) 02:30, 14 May 2014 (UTC)
- Support --Fralambert (talk) 00:53, 15 May 2014 (UTC)
- @Jakec, Jura1, Emw, Lavallen: Done --Fralambert (talk) 01:06, 15 May 2014 (UTC)
officeholder
Description | A person who is the holder of an office or position; inverse of position held (P39). |
---|---|
Data type | Item |
Template parameter | "mp" in en:template:Infobox UK constituency main |
Domain | position (Q4164871) |
Allowed values | person |
Example | Q16707840 => Joseph Hiley (Q6283995), Cyril Banks (Q5200628), … |
Source | Wikipedia articles infoboxes and list articles |
Proposed by | James F. (talk) |
- Discussion
We have a property position held (P39) to represent the person => office link but not the reverse, office => person, which means that we cannot represent the data entered on one side of the relationship the other way around. I believe this to be non-controversial. James F. (talk) 22:26, 26 April 2014 (UTC)
- Support --LydiaPintscher (talk) 22:24, 10 May 2014 (UTC)
- Oppose. Completely redundant, adding no new data not covered by P39. --Yair rand (talk) 01:24, 12 May 2014 (UTC)
- Support What is the harm in inverse properties? --Jakob (talk) 02:15, 12 May 2014 (UTC)
- Support this inverse property is very practical for linking information, which otherwise is lacking.--Oursana (talk) 15:48, 12 May 2014 (UTC)
- @Jdforrester, LydiaPintscher, Yair rand, Oursana: Done --Jakob (talk) 15:51, 12 May 2014 (UTC)
office held by the head of government
Data type | Item |
---|---|
Domain | ~ |
Allowed values | subclass of "political office" |
Example | exemple d'élément qui utiliserait cette propriété, avec une valeur proposée; par exemple : Universe (Q1) => Earth (Q2) |
Format and edit filter validation | (exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17) |
Robot and gadget jobs | Devrait-il y avoir ou existe-t-il des bots ou des gadgets qui effectueront des tâches avec cette propriété? Par exemple: vérifier les autres propriétés afin d'être cohérent, collecter des données, automatiser un lien externe, etc. |
Proposed by | Zolo (talk) |
@Yair rand, Innocent bystander: there has been discussion as to whether head of government (P6) should be used with the name of the person or with the exact title of the office (ie for the US, "Barack Obama" vs "President of the United States"). Though solution 2 seems to be favoured in discussions, solution 1 has been implemented in practice. So let's just be pragmatical and create a second property. Zolo (talk) 07:42, 8 May 2014 (UTC)
- Stöder Pragmatism is good. Maybe we should add this as a qualifier? Otherwise will it be difficult to solve the Swedish problem with several head of government (P6) at the same time in a municipality. See sv:Stockholms_politik#Nuvarande borgarråd with 12 coexisting borgarråd with 9 different titles. -- Innocent bystander (talk) (The user previously known as Lavallen) 08:09, 8 May 2014 (UTC)
- I'm not sure that this will work well for all cases, but it will probably be better than the current situation, in my opinion. Support. --Yair rand (talk) 01:22, 12 May 2014 (UTC)
- Support--Oursana (talk) 15:51, 12 May 2014 (UTC)
- @Zolo, Innocent bystander, Yair rand, Oursana: Done, although with United States of America (Q30), there were to many head of government (P6) statements to add office held by head of government (P1313) as a qualifier to all of them. --Jakob (talk) 12:10, 15 May 2014 (UTC)
- @Jakec, Innocent bystander:. Yes, I think it can be used as a qualifier when things are ambiguous. But I'd say that for cases like the US it should be used as a "main" property - or maybe both as a main property and as a qualifier of each head of government (P6) value ? --Zolo (talk) 13:22, 15 May 2014 (UTC)