Wikidata:Property proposal/Archive/47

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

Please restrict each archive page to at most 80 proposals, to avoid the Lua error: too many expensive function calls issue that messes up previous archive pages.


implements programming language

   Not done
DescriptionProgramming language implemented by this software
Representsimplementation of a programming language (Q4117406)
Data typeItem
Domaincompilers and/or interpreters (possibly including VMs?): implementation of a programming language (Q4117406)
Allowed valuesprogramming languages: programming language (Q9143)
ExampleCPython (Q599384) => Python (Q28865)
Oracle Database (Q185524) => PL/SQL (Q41574)
Category:Fortran compilers (Q7799956): instance of (P31) => compiler (Q47506) with qualifier <implements> Fortran (Q83303)
Discussion

Motivation:

Proposed by: SamB (talk)

Well, it'd be nice to be able to tie the items for programming languages and the items for the relevant implementations together somehow; this seems a straightforward, appropriate way. SamB (talk) 20:31, 23 April 2015 (UTC)

Could we make this more generic? Say have a property that specifies the standards that the output files comply with like writable file format (P1073) (or extend P1073 so it can be used for this? Filceolaire (talk) 01:47, 24 April 2015 (UTC)
@SamB: Is this indented for query language (Q845739) (e. g. SQL (Q47607), regular expression (Q185612)), or only for programming language (Q9143)? -- Sergey kudryavtsev (talk) 08:18, 24 April 2015 (UTC)
May be better generize: implements the syntax? -- Sergey kudryavtsev (talk) 08:22, 24 April 2015 (UTC)
@SamB: any further response? MSGJ (talk) 21:39, 10 June 2015 (UTC)
@MSGJ: uh, yeah, generalizing this enough to include query languages like SQL or XPath whatever would't be a terrible idea; perhaps it should be "implements computer language"? That could even work for programs that implement the JVM or .NET's CLI. (By the way, any ideas about how to represent the output language(s) of a compiler? Should every ISA also count as a computer language?)
[Oops, I forgot to sign this last night! SamB (talk) 14:25, 11 June 2015 (UTC)]
I would even further generalize and also include emulators or VMs. Rename the property implements, with software as domains, and programming languages, specifications and computer architectures as ranges. But we would need maybe to sort out the compilation/emulation stuff. It's pretty clear that a compiler produces programs in output and that emulators or virtual machines just executes ... That's too kind of implementation TomT0m (talk) 10:48, 11 June 2015 (UTC)

 CommentProperty proposals about computing should have their own section, currectly some are also done in Natural sciences ...

 Not done No support.--Micru (talk) 22:34, 20 March 2016 (UTC)

running time

   Not done
DescriptionThe duration of a film, episode, song, album, etc.
Data typequantity with unit seconds/minutes/hours-invalid datatype (not in Module:i18n/datatype)
Template parameter
Domainwork (Q386724)
Example
  • Gravity (Q2579784) => 91m <=> 1h 31m
  • Felina (Q15015184) => 55m
  • Baby Blue (Q4838206) => 217s <=> 3m 37s
  • American Tragedy (Q1933180) => 50m 41s
    • Format and edit filter validationItems need to have instance of (P31) => film (Q11424) or episode (Q1983062).
    SourceWikipedia articles might already have the duration listed. duration (P2047)
    Robot and gadget jobsYes! Bots can update this tag automatically from Wikipedia articles itself (that have a infobox film with runtime parameter) or fetch them from the IMDb API if IMDb ID (P345) is present.
    Explanation
    Discussion
    •  Support --- Jura 10:57, 5 December 2015 (UTC)
      • As noted more than once previously, as the opponent you don't need to support your own proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:18, 5 December 2015 (UTC)
        • Can you provide a reference for this affirmation? I don't think you had provided a reference for your affirmation last either. As usual. --- Jura 13:53, 5 December 2015 (UTC)
          • @Jura1: Obviously you support your own proposal. You would not propose something you don't agree with. So I don't think we should write a statement against self-support because it is implicit in the proposal itself. --★ → Airon 90 15:46, 6 December 2015 (UTC)
            • Sometimes I merely formulate proposals for other people. Some of them I support as well. I noticed others doing the same. We do have a statement requiring people to check existing property before making proposal, but it seems people don't read that either. What do you think? --- Jura 15:57, 6 December 2015 (UTC)
    •  Oppose. duration (P2047) is sufficient. I also note that the edit filter suggested does not match the examples and that the datatype is not listed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:18, 5 December 2015 (UTC)
    •  Oppose I don't get why you should separate this property from duration (P2047). --★ → Airon 90 15:28, 6 December 2015 (UTC)
      • Just to clarify: In English, your statement would display "Oppose I don't get why you should separate this property from running time (P2047)", but as P2047 gets changed, it should read "from duration (P2047)". --- Jura 16:00, 6 December 2015 (UTC)
    •  Oppose. P2047 has nearly a thousand uses, and only 9 of them are for "duration". The rest are all for running time, an entirely separate concept, and one that actually deserves a property. "Duration" does not. The broken uses of P2047 should be removed, and the label/description/constraints should be changed back to running time. --Yair rand (talk) 21:54, 17 January 2016 (UTC)
      • @Yair rand: Can you explain how "duration" and "running time" are different concepts? Thryduulf (talk: local | en.wp | en.wikt) 02:04, 19 January 2016 (UTC)
        • As far as I can tell, a "running time" is a specific type of duration. If I saw "duration" without qualifier on an item describing a creative work, I would assume it meant precisely "running time". There is unquestionably a need for the general "duration" property; the lack of items using it that way reflects the fact that, until last week, it wasn't worded that way. I've been working to remedy that, applying the property to items with duration, such as Qantas Flights 7 and 8 (Q16177169) and human pregnancy (Q11995). Swpb (talk) 17:55, 19 January 2016 (UTC)
        • @Thryduulf: An event/span of time has a "duration", which is the amount of time between the beginning of the event and the end of the event. A recorded work has a "running time", which is the intended duration (same sense) of any particular showing/use of the recording. The work itself is not an event, or span of time, or a class of events or spans of time. It has no duration. A light-year might always take a year for light to run through, but that doesn't mean the length itself has a duration of one year. Even more so, a recording intended to be viewed by means of a player over the course of one hour does not have a duration of one hour. --Yair rand (talk) 02:44, 21 January 2016 (UTC)
          • That's a dubious distinction, and one not adhered to by other schemas. I'm fine with a separate "running time" property, but it ought to be considered a subproperty of duration. Swpb (talk) 14:25, 21 January 2016 (UTC)
            • @Swpb: Looking at schema.org's description of duration, it doesn't look like it overlaps with duration of a span of time at all. It's just running time, extended to similar situations (length of time to cook a dish, do an exercise, have a flight from point a to point b, etc). --Yair rand (talk) 16:54, 21 January 2016 (UTC)
      • I agree with the practical considerations in Yair rand's opinion, but the problem is that the definition of the existing property varies across languages. The label in English is much more specific than the ones in other languages even if the descriptions were more restrictive in various languages. Given the somewhat limited use of the existing property, a new one could avoid such issues.
        --- Jura 06:28, 21 January 2016 (UTC)
    •  Oppose duration (P2047) is surely enough. -- VlSergey (трёп) 10:29, 11 February 2016 (UTC)

     Not done Use duration (P2047) instead.--Micru (talk) 22:36, 20 March 2016 (UTC)

    Model

       Done: model (P2634) (Talk and documentation)
    Domainartworks
    Allowed valuesitems representing people; possibly animals
    Motivation

    No other suitable property seems to be available. depicts (P180) would be confused with the person the image is intended to represent. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:27, 4 January 2016 (UTC)

    Discussion

    ✓ Done @Pigsonthewing, Милан Јелисавчић, Máté, Thryduulf: --Micru (talk) 22:46, 20 March 2016 (UTC)

    frame rate

       Not done
    Descriptionthe frame rate of audiovisual work at which its duration was measured
    Representsframe rate (Q119565)
    Data typeNumber (not available yet)
    Domainqualifier of duration (P2047) on audiovisual work (Q2431196)
    Allowed valuestypically between 12 and 300 (most often but not exclusively 16, 18, 23.976±0.001, 24, 25, 50, 59.94±0.001 or 60) with unit "frame per second" (to be created)
    Example → 24 fps
    Motivation

    There can be several minutes of difference between the running time of a movie depending on the different frame rates in which it is shown. E.g. the length of Star Wars VII. is 135:27 at 24 fps (theatrical) but 130:02 at 25 fps (PAL, European et al. TV standard) [1]. Máté (talk) 07:17, 27 January 2016 (UTC)

    Discussion
    {{Oppose}} this is very technical property, and it describes not the movie itself, but intermediate media used to transfer such creative work, another property may be proposed -- original media, to describe how movie was filmed. -- Vlsergey (talk) 06:47, 2 February 2016 (UTC)
    @Vlsergey: please read the proposal again. I do not propose it as a property for creative works, but as a qualifier for their running time. – Máté (talk) 07:09, 2 February 2016 (UTC)
    I've read proposal and studied example in proposal and would say that "135 minutes" will not depends on media used to transfer Star Wars Episode VII: The Force Awakens (Q6074). It doesn't have a lot of sense with movies with sound. Frame rate just does not define duration for such movies -- one can't speed up or slow down movie by changing frame rate. It may have sense for soundless movies, but then scope of property (and example) should be redefined. -- Vlsergey (talk) 07:58, 2 February 2016 (UTC)
    @Vlsergey: but it is common practice. To begin with neither NTSC or PAL is capable of the transmission of the 35 mm native 24 fps (for NTSC it is always slowed down to ~23.976 fps, for PAL it is always sped up to 25 fps, the sound along with it). This changes the running time by several minutes. Moreover, TV shows are often sped up for reruns to allow more time for ads, especially in the US. Many old films were somewhat sped up to fit the requirements of 21st century digital containers. There are differences in running time even between theatrical screening methods. – Máté (talk) 08:13, 2 February 2016 (UTC)
    (The change in the speed of the sound is also normally indicated by the change in fps. – Máté (talk) 08:16, 2 February 2016 (UTC))
    It's the first time i'm reading about changing sound of published movie. Okay, would you mind to provide example for Star Wars Episode VII: The Force Awakens (Q6074)? I.e. reliable sources that provides tables of different duration and fps? -- Vlsergey (talk) 05:55, 3 February 2016 (UTC)
    See the link in the proposal to the certificate by Freiwillige Selbstkontrolle der Filmwirtschaft (Q329126): [2]. Also, the British Board of Film Classification (Q861670) lists it at different running times for 70 mm IMAX and IMAX 3D: [3] (bottom of the page, open "Features" menu). – Máté (talk) 06:22, 3 February 2016 (UTC)
    ohhhh... It really happens. Thank you for links! -- Vlsergey (talk) 08:09, 3 February 2016 (UTC)
    No problem. :) – Máté (talk) 08:14, 3 February 2016 (UTC)

     Not done No support.--Micru (talk) 22:48, 20 March 2016 (UTC)

    ID in Russian public register of films

    Descriptionwork ID in the Russian Ministry of culture's public register of films
    Data typeString
    Domainaudiovisual work (Q2431196)
    Allowed values\d+
    ExampleStar Wars Episode VII: The Force Awakens (Q6074) → 172805401
    SourceRussian public register of films
    Formatter URLhttp://mkrf.ru/registr/detail.php?ID=$1

    It's a big official database maintained by the Russian Ministry of culture. —putnik 15:04, 31 January 2016 (UTC)

    Discussion

    ✓ Done @putnik, Máté, Vlsergey: --Micru (talk) 23:05, 20 March 2016 (UTC)

    RARS rating

       Done: RARS rating (P2637) (Talk and documentation)
    DescriptionRussian Age Rating System rating of work
    RepresentsRARS rating system (Q4114937)
    Data typeItem
    Domainaudiovisual work (Q2431196)
    Allowed values0+, 6+, 12+, 16+, 18+
    ExampleStar Wars Episode VII: The Force Awakens (Q6074) → 12+
    SourceRussian public register of films

    Like NMHH film rating (P2363) and FSK film rating (P1981). —putnik 15:04, 31 January 2016 (UTC)

    Discussion

    ✓ Done @putnik, Vlsergey, Máté:--Micru (talk) 23:07, 20 March 2016 (UTC)

    Credit line

       Not done
    Descriptionline used by museums per inventory item to describe the method of donation/acquisition. For Wikimedia commons, the original uploader
    Data typeString
    Template parameterWikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
    DomainInventory number (P217), Image (P18)
    Allowed values"uploaded by XXX", "bequest of XXX on behalf of ZZZ", etc.
    ExamplePortrait of Sir Robert Phelips (Q22570179) → P217 = NPG 3790, "Given by Charles E. Russell, 1951" [4]
    Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    Sourceexternal reference, Wikipedia list article, etc.
    Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
    Motivation

    Part of an ongoing effort to model copyright status. Jane023 (talk) 15:17, 4 February 2016 (UTC)

    Discussion

    Aside from the GLAM use-case (e.g. The bequest statement that is a formal part of the attribution to many artworks, as displayed on the walls in museums), this could be particularly useful when we eventually start handling Commons metadata in Wikidata (the Structured Data) project. Without an appropriate free-text field for attribution information it would require that we create a Wikidata item for every single uploader to Commons. Also, because the "image" property is already a direct link to the file on Commons, the "credit line" property could be a Qualifier to it. Wittylama (talk) 15:30, 4 February 2016 (UTC)

    Yes, so this property is a part of common image metadata currently used by GLAMs and Wikimedia projects, but not yet documented. See en:Credit line as an example of how metadata fields of artworks such as this one still have a long way to go. --Jane023 (talk) 15:35, 4 February 2016 (UTC)
    We already have author (P50), creator (P170) and others. I don't think that adding another property like this would help anything. Can't we just make an existing property slightly more generic to cover any possible attribution target? Nemo 15:56, 4 February 2016 (UTC)
    Turning "creator" into a free-text field would solve the problem I identify in my comment, but would also create further problems by breaking the structure of the property as it was originally created - to create the structured data relationship between works and authors. Also, it would not solve the question addressed by the proposal - of being able to incorporate GLAM metadata for their artworks for the bequest information (which is different to the authorship information). Wittylama (talk) 16:38, 4 February 2016 (UTC)

    This property is not to be confused with the attribution. This property has to do with provenance only. --Jane023 (talk) 18:29, 4 February 2016 (UTC)

    In the current form the proposal says "For Wikimedia commons, the original uploader"? What? Can you give an example of that? I also wonder what this has to do with copyright. Credit line is just a friendly way of providing provenance, it doesn't have to do anything with copyright. Multichill (talk) 17:21, 5 February 2016 (UTC)
    An example of a credit line being the original uploader rather than the Commons uploader is here: File:Flickr - USCapitol - Library of Congress.jpg --Jane023 (talk) 22:21, 17 February 2016 (UTC)

     Not done No support.--Micru (talk) 23:09, 20 March 2016 (UTC)

    number of parts of a work of art

    Descriptionthe number of parts of a work of art, such as the number of movements in a composition
    Data typeNumber (not available yet)
    Domainwork of art (Q838948)
    Exampleclassical music: Divertimento for Orchestra (Q1230598) → 7; Symphony No. 9 (Q11989) → 4; The Well-Tempered Clavier (Q211971) → 96
    dance: Swan Lake (Q199786) → 29
    painting: The Four Apostles (Q829270) → 2
    Format and edit filter validationnone
    Robot and gadget jobsunknown
    Motivation

    Hi, I think it might be valuable to have a property for the number of parts in a work of art, e.g. the number of pieces in a composition such as a symphony that has three, four or five movements. Maybe limiting this property to music is a better idea, maybe it's better to expand it to all types of art. Maybe such a property already exists and I just could not find it. Thanks, Gnom (talk) 10:19, 25 February 2016 (UTC)

    Discussion
     Support. If you expand this to all forms of art. This will be useful to store the number of chapters of a book, of acts of a play, etc. Thierry Caro (talk) 10:47, 27 February 2016 (UTC)
     Support. A user just asked about a method to get this kind of count automatically on ptwiki (for TV anime episodes). Helder 22:06, 20 March 2016 (UTC)

    ✓ Done @Gnom, Thierry Caro, Swpb, He7d3r: --Micru (talk) 22:53, 20 March 2016 (UTC)

    BBFC rating

       Done: BBFC rating (P2629) (Talk and documentation)
    Domainfilm (Q11424), television program (Q15416), video game (Q7889)
    Allowed valuesU, PG, 12A, 12, 15, 18 certificate (Q4557532), R18 certificate (Q7274429), and maybe E certificate (Q5324831)
    ExampleEx Machina (Q16635326) → 15
    Motivation

    See MPA film rating (P1657), FSK film rating (P1981), and NMHH film rating (P2363). Máté (talk) 21:12, 11 March 2016 (UTC)

    Discussion

    @Máté: ✓ Done BBFC rating (P2629). Please complete the list of permitted items, then add your example to the property documentation. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:01, 19 March 2016 (UTC)


    Type locality or co-type localities (geology)

    Descriptionlocation of the first occurrence(s) of a valid mineral
    Representstype locality (Q1973416)
    Data typeItem
    Examplecarboborite (Q3658269) → Da Qaidam Hu (Q23498113)
    Sourcemindat.org, mineralienatlas.de, Handbook of Mineralogy (MSA), reference search ([5]), IMA-CNMNC Newsletters
    Motivation
    Valid minerals need a type locality (geology). --Chris.urs-o (talk) 12:20, 24 March 2016 (UTC)
    Discussion
    I see I was wrong, and that the zoological Code does give formal status to "type locality", in that it defines it. As far as I can see the zoological Code does not use "type locality", beyond this defining of it. - Brya (talk) 05:27, 1 April 2016 (UTC)


    ✓ Done --Tobias1984 (talk) 18:14, 2 April 2016 (UTC)

    Davis Cup player ID

    Descriptionidentifier for a tennis player, in the Davis Cup database
    RepresentsDavis Cup (Q132377)
    Data typeExternal identifier
    Template parameterTemplate:DavisCup player
    DomainQ5
    ExampleRod Laver (Q105550) → 10002749
    Sourcehttp://www.daviscup.com/
    Formatter URLhttp://www.daviscup.com/en/players/player/profile.aspx?playerid=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Last(?) two (with FedCup player) IDs to improve tennis player reference graph. Used widely in several Wikipedias. Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    Discussion
    ✓ Done @Edgars2007, NavinoEvans, Løken, Pigsonthewing: --Pasleim (talk) 09:52, 23 March 2016 (UTC)

    FedCup player ID

    Descriptionidentifier for a tennis player, in the Fed Cup database
    RepresentsBillie Jean King Cup (Q206984)
    Data typeExternal identifier
    Template parameterTemplate:FedCup player
    DomainQ5
    ExampleLindsay Davenport (Q11677) → 20001736
    Sourcehttp://www.fedcup.com/
    Formatter URLhttp://www.fedcup.com/en/players/player/profile.aspx?playerid=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Last(?) two (with Davis Cup player) IDs to improve tennis player reference graph. Used widely in several Wikipedias. Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    Discussion
    ✓ Done @Edgars2007, NavinoEvans, Løken, Pigsonthewing: --Pasleim (talk) 09:57, 23 March 2016 (UTC)

    applies to aspect

       Not done
    Descriptionaspect of the item for which the claim is valid; synonyms: "in relation to", "with respect to", "relates to"
    Data typeItem
    Domainthis would be a qualifier on statements
    Allowed valuestype of linked items (Q template or text), list or range of allowed values, string pattern...
    ExampleNorth Lincolnshire (Q175945) located in the administrative territorial entity (P131) Lincolnshire (Q20989059) "with respect to" ceremonial county of England (Q180673),
    Lancashire (Q23077) shares border with (P47) Cheshire (Q23064) "with respect to" historic county of England (Q1138494)
    Motivation

    This would be a generalisation of applies to part (P518) to cover cases where the statement-value applies not to part of the subject, but in connection with an aspect of it.

    For example, with located in the administrative territorial entity (P131), one could indicate that some area was a subdivision of one area in respect of one scheme (eg current administration), but a subdivision of a different area in respect of a different scheme (eg a scheme of traditional subdivisions), or another area again in respect of further schemes (eg police areas, ambulance areas, fire service areas).

    This is a different thing to P518, which would would indicate that the statement only applied to part of a geographical area.

    Also, where we have an item that is covering multiple roles, it can be useful to indicate which role for that item a statement applies to -- for example if the same item is covering two different types of administrative areas that cover the same ground, there may be different values of head of government (P6) in relation to the different roles.

    This is not to preclude the items later being split into different items for the different roles; or more specific properties later being invented to cover particular types of relationships. But I think it is useful, at the very least, to have a generic property to allow information to be untangled in the structures we have, while discussions as to how those structures might be refined may be ongoing. Jheald (talk) 11:11, 28 October 2015 (UTC)

    Discussion
    •  Comment normally, the value of P31 wouldn't be repeated systematically as qualifier when an item is being used. If handeling two parallel hierarchies in P131 is difficult, maybe it's worth creating a distinct property for ceremonial counties. BTW there is a generic qualifier P794 (P794). --- Jura 10:11, 31 October 2015 (UTC)
    It's not just a P131 problem, and it's not just ceremonial counties. For example, this could equally arise with identifiers, where different contexts of the same item might have different identifiers, sometimes even in the same database. This may occur where an item has more than one P31 -- there needs to be a way to say which one which identifier applies to.
    But even for the P131 case, it's not just the present ceremonial counties. There are other old administrative structures, and one would want to record in relation to which structure the hierarchical relationship existed. Jheald (talk) 18:26, 31 October 2015 (UTC)
    In general, I think this suggests you'd need separate items. We would really need samples to discuss this. --- Jura 23:43, 31 October 2015 (UTC)
    I agree. I'd say if an administrative unit is replaced by a new one we also should use "replaced by" to link the items old/new unit. author  TomT0m / talk page 09:55, 1 November 2015 (UTC)
    At Poplar and Limehouse (Q1032451) there is the statement replaces (P1365) → Bethnal Green and Bow (Q3134130), but it only replaced parts of Bethnal Green and Bow (Q3134130), which still exists as a current constituency but with different borders (Poplar and Limehouse (Q1032451) is the majority of the previous Poplar and Canning Town (Q3403573) but unlike Bethnal Green and Bow it changed names and so got a new article/item. Other than listing wards (which don't have items afaict) with applies to part (P518) how do we reflect this? It seems like something this might work for. Thryduulf (talk: local | en.wp | en.wikt) 11:41, 1 November 2015 (UTC)
    @Thryduulf: I'd use separated from (P807) View with SQID for this.
    I think we should have a property like "located in the (exact) same territory" to link an administrative unit to the main (by convention) teritory of the administration of the country. author  TomT0m / talk page 12:42, 2 November 2015 (UTC)
    "Contains, Contained by, Contains major portion of, Primarily contained by, Partially contains, Partially contains, Partially contained by" might work better than P131.
    In any case, I'm not sure if this or P131 is ideal to model gerrymandering (Q476310). --- Jura 13:12, 2 November 2015 (UTC)
    located in the administrative territorial entity (P131) is ill defined, if defined at all :) There is a least two things countained in it, locality and political organisation : american states depends on the general state who define some federal rules, and they are geographically contained (and they covers taken together) in the US territory/. More than Partially contains / Partially contained by I'd use a single symmetric property geographically overlaps with. I'd tend to be OK with Contains / Contained by, but we lack the covers property This is a similar case with class covering by subclasses in Invalid topic given
       Under discussion
    DescriptionMISSING
    Data typeMISSING
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    , I'd propose a similar solution, for the same reason. Yet we would have to solve the political hierarchies/relationships beetween entities. author  TomT0m / talk page 14:10, 2 November 2015 (UTC)
    Oh, and I still think we need a property to say the territory is shared because there might be several division (state, religious or whatever) with different administration but who aligns with state administration division for convenience. author  TomT0m / talk page 14:13, 2 November 2015 (UTC)
    Comment. I have mostly held off from creating new items so far working on administrative entities in the UK. User:Danrok originally raised the concern that we were sometimes combining onto one item various different aspects of an entity, that were regarded as different things by the Ordnance Survey. He raised the case of Aberdeen (Q36405), which we have as both a city and a unitary authority. I haven't looked at the Scottish structures yet, but I think an analogue is eg Cambridge (Q350) which on WIkidata (and Wikipedia) we currently have as both a city and a non-metropolitan district. The OS has two records, one for the administrative district and one as a named place. In this case I think we probably are right to keep one record, as Cambridge the place for most purposes equals Cambridge the city, the boundaries of which are currently defined by the boundaries of the district. But as one gets down to the 'Civil Parish' level there may be questions when we have ABCD as both a village and a civil parish, does a stated area correspond to the area of the parish, or the area of the core settlement. The "co-classes" links at Wikidata:WikiProject_UK_and_Ireland/adm/England#Items_by_subdivision_type give counts of what other classes the administrative entities are also listed as instances of. On the other hand, until we have properties we want to hang off these items, I am loath to break them up -- for one thing, which item would the en-wiki article link to, and how would its infobox also find and extract statistics from the related item?
    One set of items I have started to break up is Ceremonial Counties, where the area administered by the County Council is now smaller than the full ceremonial county. So I have started creating the new items returned by this query. But even here, where we do have two different areas on the ground, I am wondering whether this is the right thing. The infobox for en:Lancashire or en:County Durham currently lists both (but not eg any of the other unitary authorities that are part of County Durham). Is it right to split the item? Or should one have area relating to the Ceremonial County and area relating to the Unitary Authority on the same item?
    For counties, I think there may be a case to split. For civil parishes there may be a case to keep together. Either way, I think there is a case to have the functional ability to be able to model the data both ways, whether for long-term purposes, or whether for short-term purposes, to clarify the data in the immediate term, while the long-term structure is being debated/discussed.
    (And this is without prejudice to other cases where one might want to make suitable qualifications -- eg the entities bordering the ceremonial county of Lancashire now, as opposed to the entities bordering its historical form. Yes, one can sometimes denote historic data with start & end dates; but it's nice also to be able to identify it with a particular structural arrangement, that may have been revised at different times in different places). Jheald (talk) 17:22, 1 November 2015 (UTC)
    I don't think you need to model items symmetric to enwiki articles. If one article includes two concepts, they can draw data with random access from two items. --- Jura 13:13, 2 November 2015 (UTC)
    The usual approach I use is to split things which contain multiple things (e.g. Lincolnshire (the ceremonial county) versus Lincolnshire (the administrative county)) but not split things which don't contain multiple things (e.g. a civil parish which contains only one settlement). Basically, if they didn't have the same name, what would we do? In the former case, it would be a ridiculous idea to merge two things with different names which contain different things (imagine merging England with the UK!). In the latter case, they're not clearly distinct items even with different names (I could imagine having different items, but I could also imagine having one item and saying "the village is called X but the civil parish is officially called Y").
    Another way to look at it: When you want to use the item, if you merge the items in the former case, it becomes far more awkward to link to the item, e.g. how do you distinguish someone born in the ceremonial county of Lincolnshire from the administrative county? You would need to keep adding qualifiers to the statements linking to the item to clarify which of the two you mean and it would be more sensible to just have separate items. On the other hand, if the civil parish only contains one settlement, it's far less of a problem, villages often don't have well-defined borders, so even if we know the exact coordinates of something, we might still have no idea whether it counts as being in the village or not, so for those it's easier to have a single item.
    - Nikki (talk) 13:51, 2 November 2015 (UTC)
    •  Oppose as duplicate to criterion used (P1013). Swpb (talk) 21:01, 7 January 2016 (UTC)
    • @Jheald: Would you also use this for cases where it's an aspect of the item itself, rather than an aspect of the target item in a statement? E.g. there are a lot of items which have multiple GeoNames and/or GNIS IDs where each ID applies to a different P31 statement on the item. - Nikki (talk) 11:01, 17 March 2016 (UTC)
    •  Oppose Because it's general but really vague. Only one example, for which I'd tend to propose the creation of an item for the old entity to avoid a real mess and a really badly scoped item. Think outside data usage, label of the old administrative division ... plus there is already a need of a item for the aspect, it is more simple to put the data in this item. Overall the aspect notion seems totally ill defined. author  TomT0m / talk page

     Not done no concensus --Srittau (talk) 01:44, 25 March 2016 (UTC)

    product / sum / power / function application

       Not done
    Descriptionthis [unit / mathematical expression] is the product of that [unit / mathematical expression] resp.
    Representsproduct (Q901718)
    Data typeNumber (not available yet)
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesunits / mathematical expressions / numbers ...
    Example
    ⟨ kilowatt hour (Q182098)  View with Reasonator View with SQID ⟩ product Search unknown value Help
    of (P642) View with SQID ⟨ watt (Q25236)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ 1000 (Q43016)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ hour (Q25235)  View with Reasonator View with SQID ⟩
     ;
       Not done
    Description[unit / mathematical expression / number] is n-th power of
    Representsexponent (Q2233915)
    Data typeItem
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesnumbers
    Example
    ⟨ square root of 2 (Q389813)  View with Reasonator View with SQID ⟩ power of Search ⟨ Q200 ⟩
    power Search ⟨ 0.5 ⟩
    /
    ⟨ square root of 2 (Q389813)  View with Reasonator View with SQID ⟩ power of Search ⟨ Q200 ⟩
    power Search ⟨ Q2114394 ⟩
     ;
       Not done
    Descriptionthis [unit / mathematical expression] is the result of the application of that function with those paramters (ordered).
    Data typeItem
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesmathematical functions (qualified by parameters value)
    Example
    ⟨ pi/4 ⟩ application of Search ⟨ https://www.wikidata.org/wiki/Q2257242 ⟩
    to value Search ⟨  1 ⟩
     ;  ;

    ADDED LATER

       Not done
    Descriptionthis [unit / mathematical expression] is the division of that [unit / mathematical expression] with the ("with" qualifier)
    Representsproduct (Q901718)
    Data typeNumber (not available yet)
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesunits / mathematical expressions / numbers ... qualified with "with" units / mathematical expressions / numbers ...
    Example
    ⟨ kilowatt hour (Q182098)  View with Reasonator View with SQID ⟩ product Search unknown value Help
    of (P642) View with SQID ⟨ watt (Q25236)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ 1000 (Q43016)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ hour (Q25235)  View with Reasonator View with SQID ⟩
     ;
       Not done
    Descriptionthis [unit / mathematical expression] is the sum of that [unit / mathematical expression] resp.
    Representsproduct (Q901718)
    Data typeNumber (not available yet)
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesunits / mathematical expressions / numbers ...
    Example
    ⟨ kilowatt hour (Q182098)  View with Reasonator View with SQID ⟩ sum Search unknown value Help
    of (P642) View with SQID ⟨ watt (Q25236)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ 1000 (Q43016)  View with Reasonator View with SQID ⟩
    of (P642) View with SQID ⟨ hour (Q25235)  View with Reasonator View with SQID ⟩
     ;
    ring/field/type of structure
       Not done
    Descriptionmathematical structure
    Representsmathematical structure (Q748349)
    Data typeItem
    Domainunits / mathematical expressions / numbers ...
    Allowed valuesmathematical structure (Q748349)
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING

    The qualifiers "of/power/to/with" would maybe need their counterpart with the number datatype because expressions might be either power of raw numbers or of number items or expression items.

    Motivation

    {{TranslateThis |en= Express mathematical expression in Wikidata. This will allow to express units in terms of other units, to define mathematical constants, ... |fr= Exprimer dans Wikidata des expressions mathématique permet de stocker des formules, de définir les constances mathématiques ou les unités les unes par rapport aux autres, ...

    Notified participants of WikiProject Mathematics /

    Notified participants of WikiProject Physics /

    Notified participants of WikiProject Chemistry

    author  TomT0m / talk page 21:47, 23 November 2015 (UTC)

    Discussion
    •  Support, but I think the problem with the units of measurement is far more complex. Imagine for example that the height of a mountain is declared in "feet" and the user has a preference for metric system, we need to somehow these data are converted and displayed according to the preference of each user. But also I see no point in stating the same information in different possible units. I just do not really know how it can be done, perhaps through some tool. --Almondega (talk) 23:32, 23 November 2015 (UTC)
      That's why in earlier proposal, we suggested to restrict to SI units. But this proposal is at least a proposal to store the correspondance beetween units in a generic way, for example with a statement
      ⟨ feet ⟩ product Search unknown value Help
      of value Search ⟨  0.3048 ⟩
      of (P642) View with SQID ⟨ meter ⟩
      . Then an infobox or a gadget can analyse this to compute the result in meters / in feet). We could write constraints such that the measures physical quantity (Q107715) are compatible. author  TomT0m / talk page 11:36, 24 November 2015 (UTC)
    •  Weak support - it feels somehow wrong to me that you are doing this primarily through qualifiers, but the only alternative I can think of given wikidata's current structure is to use several claims rather than one and that can't be right either given how claims are generally independent of each other. I think what we really need is a "list" datatype in wikidata, so that you could have a claim of the sort 'item <product of> [number, item1, item2, ...]' as a single claim (without qualifiers). Is there any prospect for getting a list datatype supported? Other than that, I think a "division" or "ratio" property would be helpful too, when it's a product involving an inverse. ArthurPSmith (talk) 22:08, 24 November 2015 (UTC)
    •  Weak oppose Mainly because of the value of the claim is set to unknown value. We don't have now a proper way to create this kind of relation. Snipre (talk) 08:08, 25 November 2015 (UTC)
    •  Comment @Snipre, ArthurPSmith: Qualifiers precise the meaning of the claim, and are "closed" or can be considered as closed, cf. Markus Krötzsch on this mail https://www.mail-archive.com/wikidata-l@lists.wikimedia.org/msg05880.html , as opposed to a list of claims that we can't assume to be complete, a claim and it qualifiers are assumed to be complete. If we have a list of qualifiers, there is no missing qualifier. As Here the order is not important, we do not need more to express a close list. The encoding is the one suggested by Markus on the "(Disjoint) union of" proposal upper. Overall I did not see a discussion about a list datatype and I think if we can do without it we don't have to add this to the already pretty loaded plate of the development team. author  TomT0m / talk page 15:02, 25 November 2015 (UTC)
      • @TomT0m: I hadn't read the above discussion on the Union proposal; that does make it seem more reasonable. In fact, I think that gives us a way to implement list values in a de facto manner through the use of qualifiers. Instead of using "unknown value", make the target of the product claim an item representing the data type, maybe list (Q12148816) or set (Q36161), and then list the elements via specific qualifiers (we don't seem to have an "has element" property, so maybe that should be proposed also? ArthurPSmith (talk) 15:17, 25 November 2015 (UTC)
        • @ArthurPSmith: I don't really know why saying it is a list is useful, as we already know it's a list by definition of the property. It's something to express on the property item, I guess, no real need to make this redundant claim in every statement with this property. Maybe the type of the elements of the list, or their number, or a dummy labelled item with a comment/statements about the list (the number of elements) ? would be more useful. author  TomT0m / talk page 15:32, 25 November 2015 (UTC)
    • @TomT0m, Almondega:  Comment what is the status of this proposal now that we have a mathematical expression datatype? It seems to me that there ought to be a way to combine "mathematical expression" with some variable substitution process via qualifiers (as the suggestion above incorporates qualifiers) to allow this to work. But I don't know technically quite how to do that. In any case, I don't think a separate property should be needed for each type of combination (product, ratio, etc). ArthurPSmith (talk) 14:23, 11 February 2016 (UTC)
    •  Oppose When you are taking a product, it is really only useful to consider multiple terms. So having a single mathematical expression as the input to the "product" property is not useful. Also, we have to be clear about what ring or field we are working over when considering products and powers.--Jasper Deng (talk) 06:23, 17 March 2016 (UTC)
      • @Jasper Deng: We can just create items for other terms of the formula. I'll just note that the existing "formula" datatype is not clear about the meaning of the operators. I completed the proposal according to your comment, please update your comment/vote. author  TomT0m / talk page 11:06, 24 March 2016 (UTC)
    •  Oppose For me this seems to be an abuse of qualifiers and unknownvalue to get multivalued claims. The use of unknownvalue is also counterintuitive and so I think many users will not use these properties in the intended way. --Pasleim (talk) 10:29, 24 March 2016 (UTC)
      @Pasleim: It's not an abuse if we decide it's a legitimate way. Please don't stop stuffs just because of a vague feeling. The intended way can be corrected, it's just a matter of a correct constraint and a message on the use page with a few usage instruction or a pointer to the property page. Plus Markus above gave the idea that any item could actually be used instead of "some value". author  TomT0m / talk page 11:02, 24 March 2016 (UTC)
      @Pasleim: could you also comment on the "union of" proposal higher up on this page which uses the same technique? I didn't see a lot of opposition to it there although I originally had the same concern. Perhaps an item specifically for collections rather than unknown value would be better? Or a Null (or collection!) datatype perhaps? ArthurPSmith (talk) 13:37, 24 March 2016 (UTC)

    @TomT0m:  Not done, no consensus. --Srittau (talk) 02:09, 30 March 2016 (UTC)

    interest

       Done: interested in (P2650) (Talk and documentation)
    Descriptionitem of special or vested interest to the subject
    RepresentsInterest (Q3153794)
    Data typeItem
    Domainorganizations or people
    Allowed valuesitems
    Example
    Sourcestatements should be sourced, with varied sources applicable
    Robot and gadget jobspossible
    is of interest to
       Not done
    Descriptionthe item is interesting to a project, community or organization
    Data typeItem
    Domainany
    Example
    Motivation

    Allows a community or project to make a list of items that are of interest to them. This opens WD as a data integration/editing platform to such projects: a prerequisite is to be able to get all relevant items back in a reliable way. I participate in 2 projects (see example values) that can use that, and in the process can contribute important info to the items of interest. Checked in "Generic" properties, and IMHO there's nothing appropriate. Vladimir Alexiev (talk) 14:09, 17 December 2015 (UTC)

    Discussion

    Josh Baumgartner (talk) 20:10, 6 January 2016 (UTC)

    Motivation

    @Vladimir Alexiev, Pigsonthewing, Izno: This proposal is the result of a previous proposal which was not done, but the inverse of it was favored. Discussion on that proposal is included in the expandable section above. Josh Baumgartner (talk) 20:10, 6 January 2016 (UTC)

    Discussion
    •  Comment Better, but the examples seem overly precise. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:55, 7 January 2016 (UTC)
    • Agreed with Andy in that the examples are overly precise. The concepts that should be the targets of those groups would and should only be the most general classess or instances possible. In the first example, "Holocaust", and in the second, "food" as well as "drink". There doesn't seem to be a way to regulate that automatically.

      I'm also vaguely concerned about the use of this property on Q5 items to specify e.g. "soccer". Is the query "all women interested in soccer who aren't soccer players" an interesting one, for example? --Izno (talk) 17:29, 19 January 2016 (UTC)

    ✓ Done @Vladimir Alexiev, Pigsonthewing, Izno: Consensus for inverted property in previous discussion, created with broadened examples. --Srittau (talk) 02:04, 25 March 2016 (UTC)

    discontinued date

    Descriptiondate that the availability of a product was discontinued
    Data typePoint in time
    Template parameter"discontinued" in en:template:Infobox information appliance, "discontinued" in en:Template:Infobox OS, "discontinued" in en:Template:Infobox software, "discontinued" in en:Template:Infobox web browser
    Domainany commercial product whose availability is limited over time, such as computer hardware, proprietary computer software, individual models of motor vehicles or aircraft
    Allowed valuesany date (whether a year, year-month, or year-month-day)
    ExampleMosaic (Q381047) → 7 January 1997; Daihatsu Sonica (Q763994) → April 2009; Oberheim OB-X (Q3347942) → 1981; preladenant (Q7240024) → May 2013
    Motivation

    With any kind of commercial product, in particular individual models of computer hardware, or computer software packages, there is generally both a release date (the date the product becomes commercially available) and a discontinued date (the date the product ceases to be commercially available.) After the discontinued date, instances of the item are usually still in existence, but they can no longer be commercially acquired in new condition. While I was principally looking for this property for use for computer models and computer software, I can see it being applicable to any commercial product, e.g. individual models of cars or aircraft. This property would mark the end period of which Property:P577 (release date) is the beginning. SJK (talk) 05:49, 13 February 2016 (UTC)

    Addendum: I don't think the property is even unique to commercial products per se. An open source project, even if never a "commercial product", can be taken to be discontinued on the date at which all of its developers cease actively working on it. SJK (talk) 06:05, 13 February 2016 (UTC)
    Further addendum: note that service retirement is similar but not quite the same. If we look at the lifecycle of most products, it could be summarised as: (1) announcement date (announced but not yet available to be ordered) (2) available for order date (date on which orders will first be accepted, but not yet shipped) (3) first customer ship date (date first unit ships to customer) (4) withdrawal from marketing date (new orders will no longer be accepted after this date) (5) last customer ship date (date last unit manufactured ships to customer) (6) end of service (post-sales service/support/maintenance ends at this date). I know for computer software, (6) is often distinct from (4)/(5). P730 might be interpreted as (6) instead of (4)/(5). It looks like P730 was created for aircraft, but I dare suggest the lifecycle is actually quite similar for both aircraft and computer hardware/software - there are many models of aircraft which you can no longer order new from the manufacturer, but the manufacturer still provides field service for, which demonstrates the distinction between (6) and (4)/(5).SJK (talk) 09:13, 13 February 2016 (UTC)
    Discussion

    @SJK, Thryduulf, TomT0m, Pasleim, Nikki, Brya: ✓ Done. All comments and objections have been resolved. There is a clear difference between when something ceases to exist/to be true (end time (P582)) and when something was discontinued, but still continues to exist (this property). --Srittau (talk) 23:07, 26 March 2016 (UTC)

    has part of the type

    DescriptionThis token is made of elements of that type
    Data typeItem
    Domainobjects, events
    Allowed valuesclasses
    ExampleUniverse (Q1) → star (Q523) (whereas
    ⟨ star (Q523)  View with Reasonator View with SQID ⟩ has part(s) (P527) View with SQID ⟨ Sun (Q525)  View with Reasonator View with SQID ⟩
    ⟨ Universe (Q1)  View with Reasonator View with SQID ⟩ has part(s) (P527) View with SQID ⟨ Sun (Q525)  View with Reasonator View with SQID ⟩
    )
    Robot and gadget jobsDevrait-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.
    Motivation

    There is an ambiguity about part of this property is aimed to partially solve (Ajoutez ici vos motivations pour la création de cette propriété) author  TomT0m / talk page 19:56, 18 February 2016 (UTC)

    Discussion
    "(whereas
    ⟨ star (Q523)  View with Reasonator View with SQID ⟩ has part(s) (P527) View with SQID ⟨ Sun (Q525)  View with Reasonator View with SQID ⟩
    )" is an incorrect statement. Universe (Q1) → star (Q523) is a statement which can be made with "has part(s) (P527)". What is the concern here? --Izno (talk) 21:14, 18 February 2016 (UTC)
    has part is tricky. We don't know for sure if our subject item is an individual star, in which case we could enumerate the star, or a class of object (the star class represents all the stars). There is a difference here : we should have to qualify the statements to say that the universe has stars (in general) with the number of stars it actually has, whereas there is only one sun and we're sure of it. I often see the two mixed up and I don't really like that. I'd like to have a non ambiguous property that we for sure use to link individual to their kind of classes, that we know can correctly be qualified by a number, whereas the other can't by design and links instances to instances. I think this is a potential improvement for quality management. Overall, per Refining "part of" there is conceptually work to be done with this property. author  TomT0m / talk page 21:34, 18 February 2016 (UTC)
    •  Support I agree "has part" is ambiguous as to whether its target is an instance (token) or a class (type). One suggestion I have, is maybe we should label this "has part of the class" instead of "has part of the type". The current (English) wikidata terminology seems to be "class" not "type", since we have an "subclass of" property not "subtype of", so we should try to stay consistent with that terminology in this property also. SJK (talk) 09:32, 26 March 2016 (UTC)

    @TomT0m, Izno, SJK: ✓ Done. I used the terms "class" and "item" as used on Wikidata. --Srittau (talk) 11:42, 27 March 2016 (UTC)

    Google Knowledge Graph identifier

    Descriptionidentifier for Google Knowledge Graph API
    Data typeExternal identifier
    Domaingeneric
    Allowed values\/g\/[0-9a-zA-Z]+
    ExampleAlphabet Inc. (Q20800404) → /g/11bwcf511s
    SourceGoogle Knowledge Graph API
    Formatter URLhttps://kgsearch.googleapis.com/v1/entities:search?ids=$1&key=<API-KEY>
    Motivation

    Identity assurance for Wikidata items created since Freebase became read-only and allows for cross referencing between Wikidata and the new Google Knowledge Graph API  – The preceding unsigned comment was added by Domswaine (talk • contribs).

    Discussion

    Can one access the data without owning a API-KEY? --Pasleim (talk) 15:33, 22 February 2016 (UTC)

    Not as far as I am aware, however an API key can be obtained for free by visiting https://console.developers.google.com/ . There is a basic allowance of 100,000 queries/day, which can be increased upon request. User:Domswaine 22:06, 22 February 2016 (UTC)
    In 2015 Google started requiring all API requests to be signed with a key tied to a Google Account. I assume its "to stop rogue apps" and force legal agreements. This is also why a bunch of YouTube players stopped working after April 2015 (e.g. Apple TV 2nd gen). But, yes it would be nice to link to an open viewer. Dispenser (talk) 22:40, 22 February 2016 (UTC)

    @Domswaine, Dispenser: ✓ Done, no objections. --Srittau (talk) 11:49, 27 March 2016 (UTC)

    @Srittau: I am uninvolved, have no plans for importing for this property, and was only replying to the API key question. Dispenser (talk) 20:51, 28 March 2016 (UTC)
    @Dispenser: I was not trying to imply that. Just informing people who might be interested in this property. If you have no further interest, that is perfectly fine. --Srittau (talk) 21:11, 28 March 2016 (UTC)

    is a period in the history of

       Not done
    Descriptionthis item is about a temporary form of this value
    Data typeItem
    Domainformer entity (Q15893266)
    Allowed valuesparent item about the entire history of the subject
    ExampleSecond Republic of South Korea (Q233263) → South Korea (Q884)
    Dominion of New Zealand (Q2594990) → New Zealand (Q664)
    Motivation

    I'd like a property to link series of historic versions of an entity with the parent item about the entity. I mostly want it for countries, but it could probably be used for other kinds of entities. For example, we could have series of items about former countries that all replaced each other:

    1. indigenous Foobar
    2. Colony of Foobar
    3. self-governing dependency of Foobar
    4. Independent Republic of Foobar

    These four items should all link to each other using replaced by (P1366) and replaces (P1365), and they should all contain "is a period in the history of → Foobar". --Arctic.gnome (talk) 00:17, 25 February 2016 (UTC)

    Discussion

    @Arctic.gnome, Thryduulf, TomT0m:  Not done for now. I like the idea in general, but there are unanswered concerns and User:TomT0m showed a way to link those items together. Would need a larger discussion to address these concerns. (Maybe on the Project chat, since these pages are not frequented very well.) --Srittau (talk) 11:57, 27 March 2016 (UTC)

    SOATO ID

       Done: SOATO ID (P2672) (Talk and documentation)
    DescriptionIdentifier for the Belarusian Code System for Administrative-territory Division Objects and Settlements
    RepresentsCode System for Administrative-territory Division Objects and Settlements (Q6538410)
    Data typeString
    Domaingeographical feature (Q618123)
    Allowed valuesnumbers
    ExampleRakaŭ (Q2500789) → 6220857156
    Sourcehttp://ostisbelarus.sourceforge.net/ ...and others

    --Чаховіч Уладзіслаў (talk) 19:18, 23 December 2015 (UTC)

    Discussion

    @Чаховіч Уладзіслаў, Voll: ✓ Done with type "external identificator", no objections. --Srittau (talk) 12:19, 27 March 2016 (UTC)

    OpenStreetMap Nominatim Place Identifier

       Not done
    DescriptionIdentifies places within Nominatim, OSM's reverse geocoding lookup service
    Data typeString
    Domainplaces
    Example10 Downing Street (Q169101) → 144831814
    Format and edit filter validation\d+
    Sourcehttp://nominatim.openstreetmap.org/
    Formatter URLhttp://nominatim.openstreetmap.org/details.php?place_id=$1
    Robot and gadget jobsThere is the potential to reverse geocode Wikidata items that have geo information
    Motivation

    OSM is the most complete open source of places, being able to cross reference to other place systems would be extremely valuable. Thinkcontext (talk) 16:12, 30 January 2016 (UTC)

    Discussion
     Question According to Wikidata:OpenStreetMap OSM identifiers are unstable. May this also apply for the Nominatim Place Identifier? --Pasleim (talk) 15:19, 22 March 2016 (UTC)
    @Thinkcontext: Did you see this? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:49, 25 March 2016 (UTC)

    @Thinkcontext, Pasleim, Pigsonthewing:  Not done, according to [8], these IDs don't seem particularly stable. This is a principle problem with OSM, since it is very easy (and sometimes necessary) to delete and recreate an object, so there is no stable way to link to them. --Srittau (talk) 12:24, 27 March 2016 (UTC)

    True. The solution is to add the Wikidata ID to the object (node, way or relation) in OSM. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:41, 27 March 2016 (UTC)

    next crossing

    DescriptionNext crossing of a river with a qulaifier for "upstream" or "downstream". (Alternatively, have separate properties for each)
    Data typeItem
    Template parameterSuccession boxes on en.Wikipedia, for example on en:Westminster Bridge
    DomainBridges, aqueducts, railways, roads, pipelines, powerlines, cable car lines
    ExampleWestminster Bridge (Q456960) => Lambeth Bridge (Q1130666) (upstream); Jubilee line (Q961290) (downstream)
    Data typeItem
    Discussion

    Motivation:

    Proposed by: Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:58, 14 March 2015 (UTC)

    •  Comment It's needed specify crossing type to eliminate the ambiguity (next automobile bridge, next railway bridge, next powerline and so forth). -- Sergey kudryavtsev (talk) 08:05, 25 March 2015 (UTC)
    •  Comment I think it would be better to have a "next crossing [up|down]stream" property for the next crossing of any type, and a "next crossing of type [up|downstream]" with a mandatory qualifier of "bridge", "pedestrian tunnel", etc. to handle the specific types. Thryduulf (talk: local | en.wp | en.wikt) 09:25, 18 April 2015 (UTC)
    •  Support --- Jura 12:11, 30 April 2015 (UTC)
    •  Comment What we really need is a good way to do ordered sets in Wikidata. That way each crossing could be a part of the set of crossings, and the order could be defined as part of that set. Sets can be ordered numerically, temporally, spatially, administratively, etc. and an item could be part of any number of sets. Attaching something like 'next crossing' directly to the bridge item or 'next higher league' to a sport league assumes a lots of particular perspective in how one is looking at the crossing and the set. That means for every different kind of ordered set, it would have to have its own set of properties, with their own set of constraints, etc. Having a general structure set up for ordered sets would, on the other hand, allow us to use the same structure and properties whether we are defining the order of crossings down a river, intersections along a road, leagues or organizations within a hierarchy, etc. Josh Baumgartner (talk) 22:15, 17 November 2015 (UTC)

    @Pigsonthewing, Thryduulf: ✓ Done as two properties. If we get the ability to do ordered sets in Wikidata at some point, we need to refine. --Srittau (talk) 13:21, 27 March 2016 (UTC)

    The discussion of these proposals is sorted to place from unsorted. Josh Baumgartner (talk) 21:33, 6 November 2015 (UTC)

    proportion of population

       Not done
    Descriptionnumber between 0.00 and 1.00 (displayed as %) representing the proportion of a population; used with qualifier sex or gender (P21) or religion or worldview (P140) or ethnic group (P172) or applies to part (P518) to indicate which population this applies to
    Representsdemographic balance (Q15911027)
    Data typeQuantity
    Allowed values0 < n <100
    ExampleFryšták (Q1471150) → 51.4477 - units % (sex or gender (P21):female (Q6581072)); (point in time:2015)
    Alternative to the properties above

    I think that the female ratio property is too narrow and we a need a more general property which can be used for other things besides gender and which can be used for other genders besides male and female. Joe Filceolaire (talk) 17:27, 22 August 2015 (UTC)

    Discussion

    @Jura, Josh Baumgartner, Kopiersperre, Antrocent:

    How would you use it ? As I understand it, the property would already be used as a qualifier, and you cannot set a qualifier to a qualifier... -Ash Crow (talk) 22:07, 23 August 2015 (UTC)
    Ash Crow: I wouldn't use it as a qualifier. I would use it as a claim about an organization or census area and add a qualifier to say which proportion we were talking about - see the example. Joe Filceolaire (talk) 21:06, 12 September 2015 (UTC)

    @Jura, Josh Baumgartner, Kopiersperre, Antrocent, Ash Crow: I have changed this so the data type is number with units. Since any item can be used as a unit this would mean we don't need a qualifier; we can just say Fryšták (Q1471150) → 0.514477 - units female (Q6581072); (point in time:2015). OK? Joe Filceolaire (talk) 03:40, 23 September 2015 (UTC)

    I think a qualifier of some sort was the right approach and I think this is the wrong way to use unit support.
    There is no way for a machine to know that the number here does not mean "0.514477 measured in females" (just over half of one female person) but should instead be interpreted as "51.4477% are female". Doing it this way creates multiple ways to interpret the data type which I don't think is a good idea. Percentages/ratios do not have units (which is another reason it seems like the wrong approach), but I think the best way we have for entering percentages is to enter a number between 0 and 100 and use "percent" as the unit, so that you can tell from the unit that the number does not represent a concrete number but rather a percentage. That would also mean that it displays much better for humans, because (as far as I'm aware) we don't have a way to have numbers between 0 and 1 displayed as a percentage. - Nikki (talk) 09:36, 23 September 2015 (UTC)

    @Filceolaire:  Not done, no concensus and a very haphazard way to properties not intended as qualifiers as such. --Srittau (talk) 13:28, 27 March 2016 (UTC)

    geography

    DescriptionStores the item that deals with the geography of the subject
    Representsgeography (Q1071)
    Data typeItem
    DomainMostly places but not only.
    Example
    Motivation

    We already have history of topic (P2184) to connect such thing as Paraguay (Q733) and history of Paraguay (Q1121772). So I think we may also have the equivalent for geography (Q1071). Of course, the use of the latter may be more limited. It will be found mostly on items about places important enough to have their own geographical subpage. But it could also be used on items such as transport (Q7590), to connect them to items like transport geography (Q795612). Thierry Caro (talk) 02:10, 12 March 2016 (UTC)

    Discussion

    ✓ Done @Thierry Caro, Pigsonthewing, Thryduulf: --Micru (talk) 21:17, 20 March 2016 (UTC)

    Indonesian Administrative Division (district) ID

       Withdrawn
    DescriptionUnique identification code for a district of the Republic of Indonesia
    Data typeExternal identifier
    Domainsettlements in Indonesia
    Allowed valuesthree numbers separated by decimal point
    ExampleBarus (Q2886206) → 12.01.01
    Sourcehttp://www.kemendagri.go.id/pages/data-wilayah
    Motivation

    Volunteers from Wikipedia Indonesia plan to add all list of identifiers, creating new item when necessary. Beeyan (talk) 06:01, 21 March 2016 (UTC)

    Discussion


    Dear, @Pigsonthewing:, @Pasleim:, and @Snipre: actually there is one property that use the same data with this one, but the value is different, 00.00.00.000, 00.00.00, 00.00, and 00. Should we combine all of this into one property or separate? Thanks --Beeyan (talk) 04:42, 23 March 2016 (UTC)

    I recommend to combine all to one property. It would be the same as for China administrative division code (P442) or Thailand central administrative unit code (P1067) --Pasleim (talk) 09:35, 23 March 2016 (UTC)
    Thank you @Pasleim:, can you please reject my request? I'll add more descriptions in P2588 --Beeyan (talk) 05:53, 24 March 2016 (UTC)
    I've edited the regular expression in Property:P2588 Beeyan (talk) 06:17, 24 March 2016 (UTC)
    Marked as withdrawn. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:26, 24 March 2016 (UTC)

    Indonesian Administrative Division (regency) ID

       Withdrawn
    DescriptionUnique identification code for a regency of the Republic of Indonesia
    Data typeExternal identifier
    Domainsettlements in Indonesia
    Allowed valuestwo numbers separated by decimal point
    ExampleCentral Tapanuli (Q5800) → 12.01
    Sourcehttp://www.kemendagri.go.id/pages/data-wilayah
    Motivation

    Volunteers from Wikipedia Indonesia plan to add all list of identifiers, creating new item when necessary. Beeyan (talk) 06:04, 21 March 2016 (UTC)

    Discussion

    Marked as "withdrawn" per the above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:27, 24 March 2016 (UTC)

    Indonesian Administrative Division (province) ID

       Withdrawn
    DescriptionUnique identification code for a province of the Republic of Indonesia
    Data typeExternal identifier
    Domainsettlements in Indonesia
    Allowed valuestwo-digit number
    ExampleNorth Sumatra (Q2140) → 12
    Sourcehttp://www.kemendagri.go.id/pages/data-wilayah
    Motivation

    Volunteers from Wikipedia Indonesia plan to add all list of identifiers, creating new item when necessary. Beeyan (talk) 06:07, 21 March 2016 (UTC)

    Discussion

    Marked as "withdrawn" per the above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:28, 24 March 2016 (UTC)

    runner-up

       Not done
    Descriptionperson or team that received 2nd place in an event
    Representsrunner-up (Q3275569)
    Data typeItem
    Template parameter"runner" in en:template:Infobox tennis tournament event, "second" in en:Template:Infobox international football competition
    Allowed valuespeople/teams
    Example2015 Wimbledon Championships – women's singles (Q20084166) → Garbiñe Muguruza (Q34276), 2014 FIFA World Cup (Q79859) → Argentina national association football team (Q79800)
    Second (original proposal as archived)
       Not done
    Descriptionsecond
    Data typeItem
    Template parameterThis property would be used to store the name of the second runner (or silver medalist) and then generate tables directly in the body of the Wikipedia article concerned.
    Domainsport cyclist (Q2309784)  View with Reasonator View with SQID
    Allowed valuesArnaud Démare (Q552724) for exemple
    ExampleFour Days of Dunkirk (Q513691)

    has part(s) (P527) => 2015 Four Days of Dunkirk (Q18589873)
    winner (P1346) => Ignatas Konovalovas (Q381409)
    second => Bryan Coquard (Q994991)

    third => Alo Jakin (Q4734082)
    Sourcefr:Quatre jours de Dunkerque#Palmarès
    Robot and gadget jobsyes
    Motivation

    Je prévois dans le cyclisme d'utiliser massivement les données de Wikidata pour centraliser ici le maximum de données possibles, l'objectif étant d'une part de laisser du temps aux contributeurs des petites versions linguistiques, de leur laisser la possibilité de générer des articles très rapidement, de sorte à ce qu'il ne leur reste plus qu'à rédiger, et d'autre part de centraliser au maximum la maintenance et la mise à jour. Ce chantier va être étalé tout au long de l'année 2015.
    Sur les articles concernant les courses cyclistes, nous associons à chaque édition le vainqueur, le deuxième et le troisième, c'est-à-dire les coureurs qui montent sur le podium. Il existe actuellement une propriété winner (P1346), déjà utilisée dans Four Days of Dunkirk (Q513691) et Paris-Arras Tour (Q3365097), mais il nous manque une propriété pour indiquer le deuxième et une autre pour le troisième. L'objectif étant à terme de générer les tableaux présents dans chaque article de course cycliste, comme fr:Quatre jours de Dunkerque#Palmarès, depuis Wikidata. Le coureur arrivé deuxième et celui arrivé troisième sont également demandés dans les infobox d'étapes de courses cyclistes, telles que la 20e étape du Tour de France 2014. Cette demande pourrait permettre de faciliter le travail sur un grand nombre d'articles et dans de nombreuses langues.

    [Google Translate] I plan in the cycling massively used to centralize data Wikidata here the maximum possible data, with the aim firstly to allow time to contributors small versions language, they leave open the possibility of generating products rapidly, so that it does not just have to write them, and also centralize maximum maintenance and update. This project will be spread throughout the year 2015.
    Of the articles about cycling races, we associate with each edition the winner, the second and the third, that is to say the riders on the podium. There is currently a winner (P1346) property already used in Four Days of Dunkirk (Q513691) and Paris-Arras Tour (Q3365097), but we lack a property to indicate the second and one for third. The objective is ultimately to generate the tables present in all cycling races article, like fr:Quatre jours de Dunkerque#Palmarès, since Wikidata. The second runner arrived and the third are also requested in the infobox stages of cycling races, such as 20e étape du Tour de France 2014. This application could help facilitate the work on a large number of articles and in many languages​​. Jérémy-Günther-Heinz Jähnick (talk) 14:16, 15 May 2015 (UTC)

    Discussion
    •  Support. I think you should record this with ranking (P1352) as well, as a qualifier to each cyclist, so the position of every cyclist in the race can be recorded and included in the results table. Filceolaire (talk) 23:49, 17 May 2015 (UTC)
    •  Support. Filceolaire : utiliser la propriété ranking (P1352) est déjà prévu en qualificatif lorsque la propriété classement général demandée ci-dessus aura été créée. C'est même un élément clé de la réalisation des classements sur Wikidata. Dans cette demande que je mets en œuvre actuellement, les propriétés deuxième et troisième ont pour vocation d'être utilisées dans les infoboxes et dans le tableau du palmarès. Plus globalement ces deux propriétés serviront à indiquer les podiums dans toutes les compétitions. Jérémy-Günther-Heinz Jähnick (talk) 11:25, 18 May 2015 (UTC)
     Support A.BourgeoisP (talk) 15:47, 20 May 2015 (UTC)
     Oppose use --Pasleim (talk) 21:26, 20 May 2015 (UTC)
    @Pasleim: You don't read the use I want : fr:Quatre jours de Dunkerque#Palmarès : I need these properties as qualifiers to list the palmarès. Jérémy-Günther-Heinz Jähnick (talk) 11:20, 21 May 2015 (UTC)
    You can create the palmarès with participant (P710) and ranking (P1352). No need to store the information two times. / Tu peux créer le palmarès avec participant (P710) et ranking (P1352). Pas nécessaire de enregistrer les informations deux fois. --Pasleim (talk) 11:58, 21 May 2015 (UTC)
    @Pasleim: Are you sure that Four Days of Dunkirk (Q513691) will permit to find the infos on 2015 Four Days of Dunkirk (Q18589873) and all of the previous editions ? Jérémy-Günther-Heinz Jähnick (talk) 12:29, 21 May 2015 (UTC)
    Yes. Not now, but in a couple of weeks, see Wikidata:Arbitrary access. --Pasleim (talk) 13:17, 21 May 2015 (UTC)
    Thank you, I am sure now I take a good direction

     Not done Opposed (=withdrawn?) by proponent. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:53, 27 June 2015 (UTC)

    Motivation

    We have winner (P1346), so why not runner-up? --AmaryllisGardener talk 16:25, 10 November 2015 (UTC)

    Discussion

    I asked this property few month ago, it was refused. I must now use qualifiers. Jérémy-Günther-Heinz Jähnick (talk) 16:33, 10 November 2015 (UTC)

    @Jérémy-Günther-Heinz Jähnick:  Not done, use participant (P710) with ranking (P1352) as qualifier. Otherwise we have two ways to model the same thing. Additionally we would need further properties to model further ranks. All this makes querying harder, not easier. --Srittau (talk) 18:38, 26 March 2016 (UTC)

    @Srittau: : it is not me that I ask this property, I use specific qualifiers. Jérémy-Günther-Heinz Jähnick (talk) 08:40, 27 March 2016 (UTC)
    Oops, thank you for pointing this out. @AmaryllisGardener: --Srittau (talk) 08:49, 27 March 2016 (UTC)

    Cycling Quotient identifier (race) (men)

    DescriptionCycling Quotient identifier (race)
    Data typeExternal identifier
    Domaincycle sport (Q2215841)
    Example2015 Grand Prix de Fourmies (Q20872499) → ...
    Sourcehttp://www.cqranking.com/men/asp/gen/race.asp?raceid=28943
    Robot and gadget jobsyes
    Motivation

    See above. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

    Discussion
    I see the 'Giro dell'Emilia' has 2 codes. http://www.cqranking.com/men/asp/gen/race.asp?raceid=28341 and http://www.cqranking.com/women/asp/gen/race.asp?raceid=10712 - for the mens and womens races. It looks like you need two separate properties - one for men and one for women - to make sense of these CQranking codes. Are you going to propose that or will we just do the mens? Joe Filceolaire (talk) 15:37, 12 November 2015 (UTC)
    I just work on men cycling races, but it is not impossible to create another property for women. Jérémy-Günther-Heinz Jähnick (talk) 17:06, 14 November 2015 (UTC)
     Support provided the property name is changed to make it clear it is only to be used for men's races. Joe Filceolaire (talk) 22:20, 21 November 2015 (UTC)

    @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, ComputerHotline, Thryduulf: ✓ Done with CQ Ranking men's race ID (P2648) --Fralambert (talk) 22:10, 24 March 2016 (UTC)

    Cycling Quotient URL (team, men)

    DescriptionCycling Quotient identifier (team)
    Data typeURL
    Domaincycle sport (Q2215841)
    ExampleTopsport Vlaanderen-Baloise 2015 (Q18746658) → TSV
    Sourcehttp://www.cqranking.com/men/asp/gen/team.asp?year=2015&teamcode=M13
    Robot and gadget jobsyes
    Motivation

    See above. Jérémy-Günther-Heinz Jähnick (talk) 15:41, 11 November 2015 (UTC)

    Discussion
    •  Support usefull. A.BourgeoisP (talk) 20:51, 11 November 2015 (UTC)
    • Topsport Vlaanderen-Baloise 2015 (Q18746658) has got 9 entries on this site - one each for every year from 2008 to 2016 though all of these have the teamcode 'TSV' so I have added that to your example. (Search for team with no year selected and code = TSV) The search function uses asp so the search string isn't in the url so we can't use the 'formatter property' to construct a search to get the list of 9 entries.
    Womens teams have a different url (change 'men' to 'women' in the url above).
    all this means that we can't use the CQranking team code to generate a link to the team page on CQranking.com unless we have separate mens and womens properties and we give the value as "year=2015&teamcode=TSV" instead of just "TSV" then each team has as many entries for this property as it has entries on CQranking. Is that how you want to do this or do you just want the team code but don't need to link to the team CQranking page? Joe Filceolaire (talk) 15:24, 12 November 2015 (UTC)
    I don't know, in fact, I want to use the entry in the template fr:Modèle:Cqranking at the bottom of articles. My goal is also to translate the template and permit to other Wikipedians to uses these datas in their language, like ProCyclingStats. Jérémy-Günther-Heinz Jähnick (talk) 11:07, 17 November 2015 (UTC)
     Support. The existing property CQ Ranking male cyclist ID (P1541) only works for male riders. Similarly this property only works for male teams but it will do that as well as P1541. I think you need to rename this property and P1541 and then create matching properties for CQrankings for women riders and teams. Joe Filceolaire (talk) 22:19, 21 November 2015 (UTC)

    @Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, ComputerHotline: done with CQ Ranking men's team URL (P2649) --Fralambert (talk) 22:27, 24 March 2016 (UTC)

    Merci @Fralambert:. J'ai vu que tu as classé ces nouvelles propriétés comme des identifiants, est-ce que tu pourrais en faire de même avec ProCyclingStats race ID (P2327) et Cycling Archives race ID (P2330) en situation sur 2016 Tour de Normandie (Q23534938). J'avais contacté un employé de WMF il y a quelques semaines, mais je n'avais pas eu de réponse bien précise. Jérémy-Günther-Heinz Jähnick (talk) 12:52, 25 March 2016 (UTC)
    J'ai regardé User:Addshore/Identifiers/2 et les deux propriétés ont été mis dans la case à convertir en identifiant externe le 22 mars. Que j'imagine que ce sera fait dans les prochains jours. --Fralambert (talk) 03:00, 26 March 2016 (UTC)


    minimal lethal concentration

    DescriptionLowest concentration of a toxic substance in an environmental medium that kills individual organisms or test species under a defined set of conditions.
    Representsminimal lethal concentration (Q21346369)
    Data typeNumber (not available yet)
    Template parameterLCLo
    Domainchemicals
    Allowed valuesnumbers with units mg/m3 or ppm over a time period, in a specific animal through a defined route of administration (time period, route of administration and animal should be qualifiers)
    Exampledichlorine (Q1904422): 800 ppm, applies to taxon (P2352): Canidae (Q25324), route of administration (P636): inhalation (Q840343), duration (P2047): 30 minutes
    SourceExternal references
    Motivation

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

    Discussion

    @Snipre, Jtuom, Pigsonthewing: ✓ Done: minimal lethal concentration (P2710). --Almondega (talk) 12:52, 6 April 2016 (UTC)

    elected in

       Done: elected in (P2715) (Talk and documentation)
    Descriptionthe election a person gained a position from, used as qualifier
    Data typeItem
    Domainelected officials
    Allowed valueshumans who have been elected to a role
    ExampleTed Strickland (Q465295)position held (P39) -> Governor of Ohio (Q20644070) ( elected in - > 2006 Ohio gubernatorial election (Q7081047) )
    Motivation

    Antrocent (talk) 23:21, 27 November 2015 (UTC)

    Discussion
    •  Support if we really do not have this already. I can't find anything but I'd be surprised if there wasn't something. Thryduulf (talk: local | en.wp | en.wikt) 23:58, 27 November 2015 (UTC)
    •  Support Actually, there is an inverse property successful candidate (P991), but it's used is not clear enough; the most often (mis)use of this property is a making a link between parlamentary elections and one person (prime minister? leader of the strongest party? who knows...) My question on the talkpage doesn't seem to bother anybody. Anyway, the proposed property seems to bring a more error-proof and less clarification-demanding solution. --Shlomo (talk) 18:50, 28 November 2015 (UTC)
    •  Comment from the English label, I thought this was a duplicate of electoral district (P768). Not sure what to suggest though. I suppose it should also link every re-election. --- Jura 09:42, 4 December 2015 (UTC)
      I had the same impression until I saw the example. Maybe the English name of this property should be reconsidered. I leave this for the native speakers, though.
      About the re-election: Supposed we have one statement of position held (P39) for several consecutive periods, there certainly should be qualifiers linking to all the re-elections. But maybe a separate position held (P39) statement for every period (with a single link to [re-]election) would be a better choice. On the other hand, how will we use the replaces (P1365) and replaced by (P1366) qualifiers in the case of re-election? Could an item link to itself?--Shlomo (talk) 12:55, 6 December 2015 (UTC)
    • from the name of the property, I thought it was a date property. from the provided example, I would suggest elected during (in is such a catch-all term) --Hsarrazin (talk) 10:02, 24 December 2015 (UTC)
      "During" seems also ambiguous (even if probably less ambiguous than "in") - it can also refer to time or to event that takes place at the same time as the election does. What about "elected through"? Or maybe just "election"? (Just proposals, I'm not a native speaker of English and I can't feel the slight differences between the options so well...)--Shlomo (talk) 16:42, 24 December 2015 (UTC)
      To me (a native English speaker) "elected during" is at least as likely to be a time field than "elected in". My first thought would be to expect things like "elected during 2015 (Q2002)" or "elected during 43rd Parliament of the United Kingdom (Q21084460)" and less likely to refer to an election. "Elected at" is the best short name I can come up with, "elected as a result of" is longer but not necessarily better. It also implies that has cause (P828) as a qualifier to their position would work. Thryduulf (talk: local | en.wp | en.wikt) 23:08, 24 December 2015 (UTC)
    •  Comment I still do not know how to handle cases, when people get their "position held", not by getting more votes than anybody else, but by replacing somebody who temporarly or for the rest of the period cannot "hold their position" any longer. Parental leave, retirement and death also affects MPs. An example: Börje Vestlund (Q512590) is since 2015-10-01 an MP of the Swedish parlaiment, not because he was elected as such, but as a replacement for Stefan Löfvén, who holds the position as Prime Minister. -- Innocent bystander (talk) 17:34, 24 December 2015 (UTC)
      As for MPs' replacements, they are not just anybody who comes and is ready to continue the job; usually they took part in the same election and on the same list as the replaced MP, they just ended "below the line" according to the number of seats gained by that particular list. But the legitimacy for becoming an MP is their election result. (I asked in another discussion, if such candidates can be included in successful candidate (P991) statements...) Anyway I assume, that their position can be described as "elected at/through/whatever" the election even if there was a considerable time span between the election and obtaining the position.--Shlomo (talk) 09:22, 4 January 2016 (UTC)
      A more serious problem are the MPs (or any other "elected" body), that are not elected at all. In some parliaments (councils a.s.o.) there are several seats reserved for representatives of some particular groups or regions. Such MPs are not always elected, but nominated by another body, or their MP-ship is connected with another function a.s.o. Surely they shouldn't be described as "elected at", but with another property (if there is one...) That could cause problems with constraints, scripts that use this data for infoboxes etc. What about a more general property, something like "legitimated by", which usually will link to the election, but can refer to another facticity as well if needed.--Shlomo (talk) 09:22, 4 January 2016 (UTC)
    • successful candidate (P991) is currently vague, but the solution is not to start making duplicate or near-duplicate properties.  Oppose. --Yair rand (talk) 20:41, 29 February 2016 (UTC)
    •  Support This may be a way to catch more easily start time (P580) and end time (P582) in most cases of a very large number of MPs. Kumkum (talk) 18:34, 12 March 2016 (UTC)

    median lethal concentration

    DescriptionStatistically derived median concentration of a substance in an environmental medium expected to kill 50% of organisms in a given population under a defined set of conditions.
    Data typeNumber (not available yet)
    Template parameterLC50
    Domainchemicals
    Allowed valuesnumbers with units in amount per volume for a specific animal over a certain time through a defined route of administration (time duration, animal, route of adminsitration should be qualifiers)
    Exampledichlorine (Q1904422): 137 ppm, applies to taxon (P2352): house mouse (Q83310), route of administration (P636): inhalation (Q840343), duration (P2047): 1 hour
    SourceExternal references
    Motivation

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

    Discussion

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

    @Snipre, Jtuom, Pigsonthewing: ✓ Done: median lethal concentration (LC50) (P2712). --Almondega (talk) 13:44, 6 April 2016 (UTC)

    Wiktionary

    •  Oppose all of these. Wikidata has items, each of which has labels in many languages, all referring to the same item. Wiktionary has words, each of which has translations into many languages, all of which are different words with separate entries in wiktionary. The properties below are properties for words; not for wikidata items so they don't have much use here on wikidata.
    Try omegawiki.org if you want to support a database crossed with a dictionary. They have 'concepts' linked to 'expressions' in multiple languages. I believe they are already looking at linking the 'concepts' to wikidata items. --Filceolaire (talk) 00:51, 19 June 2013 (UTC)

    anagrams (en)

       Not done
    Descriptionsee m:Wikidata/Notes/Future#Wiktionary
    Data typeItem
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Proposed byGZWDer (talk) 10:19, 18 June 2013 (UTC)
    Discussion

     Support This is currently the only non language-specific property in this list therefore it would be an easy enforceable proposal.--Bigbossfarin (talk) 18:46, 29 October 2013 (UTC)

    @GZWDer:  Not done, no consensus for Wiktionary items at the moment. --Srittau (talk) 02:19, 30 March 2016 (UTC)

    patronymic / Patronym / nom à suffixe patronymique / patronimico

       Not done
    DescriptionThe patronymic of a person. This only applies to persons who have a patronymic. This provides a machine readable version of the label for person items. For example, Leo Tolstoy will have value ("en:Nikolayevich", "de:Nikolajewitsch", "ru:Николаевич" ...) as the value of this property.
    Data typeMultilingual text (not available yet)
    DomainPerson
    Example
    ⟨ Leo Tolstoy (Q7243)  View with Reasonator View with SQID ⟩ patronym Search ⟨  Nikolayevich ⟩
    Proposed byŠlomo (talk)
    Discussion

    If there is an agreement on properties for family name and given name, there should be also a property for patronymic which differs from both of them.--Šlomo (talk) 10:20, 25 February 2013 (UTC)

    • And matronymics... and clan names, nisbats, teknonyms, cognomens... --Yair rand (talk) 22:35, 18 March 2013 (UTC)
       Oppose. --Yair rand (talk) 00:46, 7 June 2013 (UTC)
    •  Support plus the other properties listed by Yair, though they can probably wait for now. Filceolaire (talk) 19:11, 14 May 2013 (UTC)
    •  Support --Odejea (talk) 13:14, 5 June 2013 (UTC)
    •  Support Additional question: How one should indicate that (Icelandic) names do not have a family part? לערי ריינהארט (talk) 06:14, 15 October 2013 (UTC)
    •  Support But this is not consistent with first name which has the Item data type. --DixonD (talk) 09:25, 8 November 2014 (UTC)
    •  Oppose as proposed, but  Support is item datatype to be consistent with other name properties. I also support the other types of names, though also a generic name property because what exact class a name is in a particular usage is not always specified in the source, but we still ought to have a way to add the claim. Josh Baumgartner (talk) 20:46, 20 October 2015 (UTC)
       Question @Joshbaumgartner: Can you point me at an explanation for why first and family name have item datatype? It seems like an extra burden on contributors to reify names, and probably leads to great under-population of these properties. And it doesn't seem ontologically sound to link items as siblings simply because they share a name. It's as if we make homonyms siblings under a word simply because of a lexical coincidence. Thanks, Bovlb (talk) 17:40, 17 November 2015 (UTC)
      @Bovlb: No, I am not well versed in exactly why it was set up that way and personally I agree with you that it is a burden to have to learn the whole system of adding items for names, and then sub-items for specific name applications, even having separate items by gender for some of them, and then go create new items and sometimes additional structure every time you just want to identify someone's name. I certainly have shied away from putting in names that don't already have items because it is tangential to what I am putting in and I want to stay focused on my main objective...for example I may be updating player-to-team links and wouldn't mind filling in player first, last, etc. names, while I'm there, but if it takes going down a side road and having to create new items, it isn't always worth the time. However, the reason I listed my recommendation to change to 'item' is because we should be consistent in what system we use, and unless we are going to re-visit how we do first and last names, then it is the system that is in place right now. Josh Baumgartner (talk) 18:33, 17 November 2015 (UTC)
      @Joshbaumgartner: I can see one advantage, which is that it gives you name translations for free, although I'm not aware of any attempt to exploit that. The fact that it discourages addition of names seems like a major drawback. Bovlb (talk) 16:55, 25 November 2015 (UTC)
    •  Oppose when applied to person with patronymic, but  Support when applied to that person's father's given name from which the patronymic is derived. Ideally, the patronymic for a person should be retrievable wherever needed by looking at the person's father (P22)'s given name (P735) with preferred rank and grabbing its value for this proposed property. This arrangement also allows the patronymic to be adjusted by the person's ethnic group (P172); if the same name item has different patronymics assigned to it in different languages, people with different values for ethnic group (P172) can have different patronymics shown when needed. ––– For those people whose fathers are not on Wikidata, there could be a sister property 'patronymic from' that takes a name item, so that the patronymic can be generated from that name alone. Mahir256 (talk) 06:44, 13 December 2015 (UTC)

    @Šlomo:  Not done, no consensus for Wiktionary items at the moment. --Srittau (talk) 02:19, 30 March 2016 (UTC)

    Commons category

       Not done
    DescriptionA replacement of current Commons category (P373)
    Data typeItem
    Template parameterCommons cat-templates
    Domainall
    Allowed valuesitems related to categories on Commons
    ExampleWikidata (Q2013):Category:Wikidata technical administration (Q14565196)
    Sourcecurrent use of P373
    Robot and gadget jobsyes
    Proposed byLavallen (talk)
    Discussion

    P373 are from the old ages in Wikidatas history when Commons wasn't connected to Wikidata. Now it is, and I think we should rethink how we technically connect ourself with Commons. I here propose the idea that the current Property for Commonscat: Commons category (P373) who has datatype:string should be replaced with an item who has item as datatype. If this proposal is successfull, maybe the same thing should happen with Commons gallery (P935)? Lavallen (talk) 18:42, 17 March 2014 (UTC)

     Comment Is there some difference from topic's main category (P910)? Another thing: bugzilla:47930 does not allow to query data from non-directly connected item. Third thing: there is idea merge category item and article item to single item. — Ivan A. Krestinin (talk) 21:21, 18 March 2014 (UTC)
    Exactly Ivan. No difference, and no action until bugzilla:47930 is fixed. So we just have to wait.
    And category and article in the same item is not going to happen. Multichill (talk) 21:49, 18 March 2014 (UTC)
    What is the benefit of P373 if there is topic's main category (P910) having an item that links to Commons? As of now this looks like duplication to me, or worse storing correct and outdated information at the same time, e.g. Aveiro District (Q210527) and Category:Aveiro District (Q8280642) which are linked twice with each other (P310/P910) and where the category item links to commons:Category:Aveiro District both link to commons:Category:Aveiro (district) via P373. The longer P373 stays, the more outdated information will be created. Tamawashi (talk) 05:13, 27 June 2014 (UTC)
     Comment Commons Galleries can be linked via sitelink on the topic item, as Commons Categories can be linked from topic's main category item. Please show what extra benefit Commons gallery (P935) and Commons category (P373) can have with respect to having connections between things, i.e. apart from different visualization. Tamawashi (talk) 05:51, 27 June 2014 (UTC)
     Not done no support --Pasleim (talk) 13:56, 22 March 2016 (UTC)

    collage image

       Done: montage image (P2716) (Talk and documentation)
    Descriptionimage file that assembles two or more other images of item
    Data typeCommons media file
    Domainany
    Allowed valuesimages from category:montages etc
    ExampleBerlin → Collage Berlin2.jpg
    Proposed by
    --- Jura 08:58, 1 March 2016 (UTC)


    sectional view

       Done: sectional view (P2713) (Talk and documentation)
    Descriptionfichier image montrant une vue en coupe de l'élément
    Data typeCommons media file
    Domainany
    Allowed valuessectional views
    Examplehuman eye (Q430024) → File:Human eye cross-sectional view grayscale.png, Ligne de Cerdagne (Q2164826) → Train Jaune profil.png
    Proposed byThierry Caro (talk) 20:42, 19 March 2016 (UTC)
    Discussion

    Most of the world is in 3D and we need to get a sectional view of things to fully understand how it works in there! But image (P18), it's natural, mostly stores external views of stuff. A property dedicated to sectional views would be useful for things as different as an organ (Q712378), a building (Q41176) or a machine (Q11019), but also to store the altimetric diagram of a cycling race (Q15091377), for instance. Thierry Caro (talk) 20:42, 19 March 2016 (UTC)

    Wikimedia import status

       Not done
    Descriptionstatus of the import of the list, template or category from Wikipedia or any other Wikimedia site to Wikidata
    Data typeItem
    Domainlists, templates, categories
    Allowed valuesspecific status items (per wiki or import step)
    ExampleCategory:Governors of West Virginia (Q8497371) → all incumbents imported (item deleted)
    SourceWikidata contributors
    Robot and gadget jobscould be set automatically after import by bot

     Not done, no consensus. --Srittau (talk) 02:25, 30 March 2016 (UTC)

    no-observed-adverse-effect level (NOAEL)

    DescriptionGreatest concentration or amount of a substance, found by experiment or observation, which causes no detectable adverse alteration of morphology, functional capacity, growth, development, or life span of the target organism under defined conditions of exposure.
    Representsno observable adverse effect level (Q1755926)
    Data typeNumber (not available yet)
    Domainchemicals
    Allowed valuesnumbers with units in amount per kilo per day for a specific animal using a specific administration route during a defined duration (administration route, animal and duration should be qualifiers)
    Examplechlorobenzene (Q407768): 27.25 mg/kg bw/day, applies to taxon (P2352): dog, route of administration (P636): oral exposure, duration (P2047): 13 weeks
    SourceExternal references like toxnet
    Motivation

    Provide full set of toxicological data. Snipre (talk) 00:42, 8 March 2016 (UTC)

    Discussion
     Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)
     Support Interesting information. Will be useful to Open Food Facts, which is also linked to Wikidata--Teolemon (talk) 14:52, 7 March 2016 (UTC)

    @Snipre, Jtuom, Teolemon: ✓ Done: no-observed-adverse-effect level (P2717). --Almondega (talk) 14:28, 6 April 2016 (UTC)

    embed URL

    Descriptionformatter URL for embeddable content
    Data typeString
    DomainRFC 3986
    Allowed valuesSame as formatter URL
    Example
    Motivation

    P1651 (YouTube video identifier) only lists non-embeddable URLs, removing users from their current viewing point. In mobile environments doing so may require launching a separate application, losing previous application state. Beyond video: Web comics can be embedded (XKCD encourages this), photographs, 360 panoramas, podcasts, legislation (text), and even emulators.

    Which is preferable? A formatter URL qualifier (embed=Document/Image/Audio/Video/Web) or another property (embed URL) to indicate this?

    Challenges:
    <iframe>s requires a fixed width and height. They do not scale like <img> (automatic height with given width), hopefully this will be fixed. Media type information (document, picture, sound, video, or JavaScript) might be useful. Audio containers should have non-zero width/height (for buttons). Dispenser (talk) 20:19, 21 January 2016 (UTC)

    Discussion

    Given that the Youtube ID is shared between the direct URL and the URL for embedding, and given that the ID itself is stored for YouTube video ID (P1651), I don't quite see what purpose that would serve. Alphos (talk) 12:10, 22 January 2016 (UTC)

    The idea is programs can embed the video instead of launching a new browser window. The alternative is every program special casing every service. Dispenser (talk) 23:58, 22 January 2016 (UTC)
    this proposal makes only sense to me if we use it as property on property pages, . But is there beside YouTube video ID (P1651) another property on which we could use it? --Pasleim (talk) 15:02, 22 March 2016 (UTC)
    The commercial service Embed.ly lists 300+ providers, but most of those are proxied snippets (e.g. New York Times article). I have added 3 more example properties to the list. Dispenser (talk) 13:25, 23 March 2016 (UTC)
     Oppose Can be algorithmically determined from YouTube video ID (P1651). --Srittau (talk) 02:13, 25 March 2016 (UTC)
    Where should it be stored instead? How do you extended it to other properties? Dispenser (talk) 03:38, 25 March 2016 (UTC)
    Sorry, I was for some reason thinking of another property proposal. --Srittau (talk) 03:51, 25 March 2016 (UTC)
     Support Seems useful to me, similar to formatter URL (P1630). It should be called "formatter embed URL", though. --Srittau (talk) 03:51, 25 March 2016 (UTC)
    If this is implemented, the data type should be string like formatter URL (P1630), not URL. The value of the property is not designed to be a URL itself. - Nikki (talk) 18:39, 25 March 2016 (UTC)
    Agreed. I changed it in the proposal. --Srittau (talk) 18:44, 25 March 2016 (UTC)
    @LydiaPintscher: Can we get your opinion? I'm still undecided if it should be a standalone property or a qualifier of formatter URL (like regexes on IMDb). Dispenser (talk) 22:02, 30 March 2016 (UTC)
    It seems to me that in spirit this is very similar to the distinction we already make for formatter URI and formatter URI for RDF resource (P1921). So imho it is best done as a separate property. --LydiaPintscher (talk) 07:27, 31 March 2016 (UTC)

    Hungarian-style transcription

    Descriptiontranscription of a monolingual text value in a non-latin script according to the guidelines of the Hungarian Research Centre for Linguistics (Q7315098), Helyesírás (Q1035212), and Hungarian Wikipedia (Q53464)
    Data typeString
    Domainqualifier of monolingual text values
    Example
    ⟨ Isaac Asimov (Q34981)  View with Reasonator View with SQID ⟩ birth name (P1477) View with SQID ⟨ "Исаак Юдович Озимов" [ru] ⟩
    → "Iszaak Judovics Ozimov"
    ⟨ Seven Samurai (Q189540)  View with Reasonator View with SQID ⟩ title (P1476) View with SQID ⟨ "七人の侍" [ja] ⟩
    → "Sicsinin no szamurai"
    Motivation

    A sub-property of transliteration or transcription (P2440). The Hungarian Wikipedia (and all Hungarian publications that can afford a copy-editor and a proofreader) use Hungarian-style (popular) transcriptions instead of international or scientific ones. For larger languages the Hungarian Academy of Sciences have published detailed transcription tables (also included and refined in Helyesírás), while for others only guidelines, based on which the editors of Hungarian Wikipedia have created transcription tables for several further languages written in non-latin scripts, available at w:hu:WP:ÁTÍR. Máté (talk) 15:18, 23 March 2016 (UTC)

    Discussion
     Support --Pasleim (talk) 07:48, 30 March 2016 (UTC)

    lowest-observed-adverse-effect level (LOAEL)

    DescriptionLowest concentration or amount of a substance (dose), found by experiment or observation, which causes an adverse effect on morphology, functional capacity, growth, development, or life span of a target organism distinguishable from normal (control) organisms of the same species and strain under defined conditions of exposure.
    Representslowest-observed-adverse-effect-level (Q2446987)
    Data typeNumber (not available yet)
    Domainchemicals
    Allowed valuesnumbers with units in amount per kilo per day for a specific animal using a specific administration route during a defined duration (administration route, animal and duration should be qualifiers)
    Examplechlorobenzene (Q407768): 54.5 mg/kg/day, applies to taxon (P2352): dog, route of administration (P636): oral exposure, duration (P2047): 13 weeks
    SourceExternal references like toxnet
    Motivation

    Provide full set of toxicological data. Snipre (talk) 12:52, 11 February 2016 (UTC)

    Discussion
     Support Basic toxicological properties such as this should be added to Wikidata. It would bring more health-relevant information to chemical properties. It would also make easier to find and compare toxicity of different chemicals. --Jtuom (talk) 14:52, 29 January 2016 (UTC)
     Support Interesting information. Will be useful to Open Food Facts, which is also linked to Wikidata--Teolemon (talk) 14:52, 7 March 2016 (UTC)

    @Snipre, Jtuom, Teolemon: ✓ Done: lowest-observed-adverse-effect level (P2718). --Almondega (talk) 17:32, 6 April 2016 (UTC)

    Swimrankings.net swimmer ID

    Descriptionidentifier for a swimmer, in the Swimrankings.net database
    Data typeExternal identifier
    Template parameterTemplate:Swimrankings
    Domainhuman (Q5)
    Allowed values[1-9][0-9]*
    ExampleRyan Lochte (Q201517) → 4038679
    Sourcehttps://www.swimrankings.net/
    Formatter URLhttps://www.swimrankings.net/index.php?page=athleteDetail&athleteId=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Major database for swimmer biographies referencing. Used in several Wikipedias. Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    Discussion
    ✓ Done @Edgars2007, Tubezlob, Løken, Thierry Caro: --Pasleim (talk) 09:40, 23 March 2016 (UTC)

    Basketball-Reference.com male player ID

    DescriptionIdentifier for a male basketball player on the Basketball Reference website
    Data typeExternal identifier
    Template parameterTemplate:Basketballstats (Q6712643)
    Domainhuman (Q5)
    ExampleKareem Abdul-Jabbar (Q179051) => a/abdulka01
    Format and edit filter validation[a-z]/[a-z]{4,7}\d{2}
    Sourcehttp://www.basketball-reference.com/
    Formatter URLhttp://www.basketball-reference.com/players/$1.html
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    To be used as a source for player information. See also: Baseball-Reference.com major league player ID (P1825), Baseball-Reference.com minor & foreign league player ID (P1826), Sports-Reference.com Olympic athlete ID (archived) (P1447). --Edgars2007 (talk) 13:17, 27 January 2016 (UTC)

    Discussion
    •  Support Jon Harald Søby (talk) 21:02, 27 January 2016 (UTC)
    •  Comment Why not adding player (males) to the property-name for differentiating from other possible ID's from the same database like: player (female), teams, basketballmatches, referees, coaches and so on. See the database for other possibilities. Regards Migrant (talk) 23:59, 27 January 2016 (UTC)
      • @Migrant: Sorry for late response. So... a) I was just following other sportsperson-related IDs b) Label isn't written in stone, we can always change it, if there are more related properties, we can adjust labels. c) OK, I agree that basketball-reference database has some other good properties (for coaches, WNBA players, referees), but some of them (basketball matches) are ... I hope you understand, what is my point. Even association football (Q2736) hasn't gone in such detail yet, but it most probably have tens of such databases :) Yes, I don't have any real objections to adjust label (feel free to do that yourself, if you think it's needed), but I think that should also be done for other sports IDs at least. --Edgars2007 (talk) 15:37, 29 January 2016 (UTC)
    •  Support --- Løken (talk) 12:18, 19 March 2016 (UTC)

    @Edgars2007, Jon Harald Søby, Migrant, Løken: ✓ Done, without the "male" part. I don't see a reason not to allow female players, since they use the same formatter URL. I also added a female example. --Srittau (talk) 01:32, 30 March 2016 (UTC)

    Opensecrets Identifier

    DescriptionIdentifier used by Opensecrets for people and organizations involved in US elections
    Data typeExternal identifier
    Domainpeople, organizations
    Allowed valuestype of linked items (Q template or text), list or range of allowed values, string pattern...
    ExamplePaul Ryan (Q203966) → N00004357
    Sourcehttp://opensecrets.org
    Formatter URLhttp://www.opensecrets.org/politicians/summary.php?cid=$1
    Robot and gadget jobsCongressional members info can be imported from https://github.com/unitedstates/congress-legislators
    Motivation

    The Opensecrets API is one of the most popular and authorative 3rd party information sources for US election data. Thinkcontext (talk) 20:26, 29 January 2016 (UTC)

    Discussion

    @Thinkcontext, Runner1928, NavinoEvans: ✓ Done --Srittau (talk) 01:46, 30 March 2016 (UTC)

    NDL JPNO

       Done: JPNO (P2687) (Talk and documentation)
    DescriptionJapanese National Bibliography Number (Q3873059) per the National Diet Library (Q477675)
    RepresentsNational Bibliography Number (Q3873059)
    Data typeExternal identifier
    Template parameternone
    Domainversion, edition or translation (Q3331189) (see Wikidata:Books task force#Edition item properties)
    Allowed values\d{8}
    ExampleThe Master of Go (1973) (Q15231929) → 22015095
    1975 講談社 (Kodansha) edition of 妖星伝 1 (鬼道の巻) (Yōseiden 1: Kidō no maki) by 半村良 (Ryō Hanmura) in Japanese → 75001537
    Format and edit filter validation8 digits
    Sourcehttp://ndl.go.jp/
    Motivation

    This is currently used by Template:JPNO (Q14398398) and is an eight digit string assigned by National Diet Library (Q477675) to catalog all editions of works published in Japan and/or in the Japanese language (as opposed to NDL Bib ID (P1054) which is an identifier for editions held in NDL and cataloged via OPAC). It is mentioned in English in these places (among others):

    It can also be used to index into Webcat Plus (NACSIS-CAT (Q11234325) a service of National Institute of Informatics (Q4346622)). For example for the same edition (JPNO 75001537) mentioned in the example: http://webcatplus.nii.ac.jp/webcatplus/details/book/nbn/75001537.html (where it is referred to as "nbn/75001537" ) Uzume (talk) 02:16, 4 February 2016 (UTC)

    Discussion

    @Uzume, Pigsonthewing: ✓ Done --Srittau (talk) 02:43, 30 March 2016 (UTC)

    Box Office Mojo person ID

    Descriptionidentifier of a person in the Box Office Mojo database
    RepresentsBox Office Mojo (Q223142)
    Data typeExternal identifier
    Template parameterTemplate:Mojo name (Q21481323)
    Domainhuman (Q5)
    Allowed values[a-z0-9]+
    ExampleMatt Damon (Q175535) → mattdamon
    Formatter URLhttp://www.boxofficemojo.com/people/chart/?id=$1.htm
    Motivation

    See also Box Office Mojo film ID (former scheme) (P1237), Box Office Mojo franchise ID (former scheme) (P2530), , Box Office Mojo studio ID (P2531) Edoardo88 (talk) 16:32, 8 February 2016 (UTC)

    Discussion
     Support - Mbch331 (talk) 18:01, 8 February 2016 (UTC)
     Support, probably this would've been my next :)… – Máté (talk) 18:36, 8 February 2016 (UTC)
     Support --Edgars2007 (talk) 22:43, 8 February 2016 (UTC)

    @Edoardo88, Mbch331, Máté, Edgars2007, Pigsonthewing: ✓ Done, mostly support, only dissent was not further substantiated. --Srittau (talk) 19:01, 30 March 2016 (UTC)

    BARTOC ID

       Done: BARTOC ID (P2689) (Talk and documentation)
    DescriptionIdentifier in BARTOC Terminology Registry
    RepresentsBasic Register of Thesauri, Ontologies & Classifications owned by Esquiress Lyndsey Watson Copyright © (Q22279816)
    Data typeExternal identifier
    Domainknowledge organization system (Q6423319) and subclasses such as classification scheme (Q5962346)
    Allowed values[1-9][0-9]*
    ExampleDewey Decimal Classification (Q48460) → 241
    Sourcehttp://bartoc.org/
    Formatter URLhttp://bartoc.org/en/node/$1
    Robot and gadget jobsthere are backlinks to Wikidata in BARTOC for reuse
    Motivation

    The BARTOC Terminology Registry contains almost 1.800 thesauri, classification, ontologies etc. Last month 163 of them had been found in Wikidata (see https://github.com/gbv/bartoc2wikidata/blob/master/bartoc2wikidata.csv). The scope of BARTOC is very broad, so all instances of Basic Register of Thesauri, Ontologies & Classifications owned by Esquiress Lyndsey Watson Copyright © (Q22279816) can be described in BARTOC as well. -- JakobVoss (talk) 10:30, 11 February 2016 (UTC)

    Discussion

    @JakobVoss, Pigsonthewing: ✓ Done, no objections. --Srittau (talk) 19:10, 30 March 2016 (UTC)

    FIG gymnast identifier

    DescriptionGymnast's identifier at the database of International Federation of Gymnastics
    RepresentsInternational Gymnastics Federation (Q379079)
    Data typeExternal identifier
    Template parameterTemplate:FIG |id=
    Domainhuman (Q5)
    Allowed values[1-9][0-9]*
    ExampleAly Raisman (Q238663) → 13822
    Sourcehttps://database.fig-gymnastics.com/
    Formatter URLhttps://database.fig-gymnastics.com/public/gymnasts/biography/$1/true?backUrl=
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    International Gymnastics Federation (Q379079) is the governing body for the Olympic sport of gymnastics (Q43450). Used in many Wikipedias, which uses information from website as primary source, as it contains a lot of useful information. Edgars2007 (talk) 10:17, 5 March 2016 (UTC)

    Discussion

    @Edgars2007, Løken, Pigsonthewing: ✓ Done --Srittau (talk) 12:37, 3 April 2016 (UTC)

    ISU figure skater identifier

    Descriptionidentifier for a figure skater, in the International Skating Union database
    RepresentsInternational Skating Union (Q543115)
    Data typeExternal identifier
    Template parameterTemplate:ISU name |id=
    Domainhuman (Q5)
    Allowed values[0-9]*
    ExampleAlexei Yagudin (Q316861) → 00000254
    Sourcehttp://www.isuresults.com/bios/
    Formatter URLhttp://www.isuresults.com/bios/isufs$1.htm
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    International Skating Union (Q543115) is the governing body for the Olympic sport of figure skating (Q38108). Used in many Wikipedias, which uses information from website as primary source, as it contains a lot of useful information. Edgars2007 (talk) 10:17, 5 March 2016 (UTC)

    Discussion

    ESPNcricinfo player ID

    DescriptionID for a cricketer in ESPNcricinfo's database
    RepresentsESPNcricinfo (Q2118845)
    Data typeExternal identifier
    Template parameter|id= in Template:Cricinfo
    DomainQ5
    Allowed values[0-9]+
    ExampleAbdul Aziz (Q4665270) → 39343
    Sourcehttp://www.espncricinfo.com/
    Formatter URLhttp://www.espncricinfo.com/ci/content/player/$1.html
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Major database for cricket players. Used widely in several Wikipedias. Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    Discussion

    @Edgars2007, Thryduulf, Pigsonthewing: ✓ Done --Srittau (talk) 12:48, 3 April 2016 (UTC)

    CricketArchive player ID

    Descriptionidentifier for a person in the CricketArchive.com database
    RepresentsCricketArchive (Q2117742)
    Data typeExternal identifier
    Template parameterTemplate:Cricketarchive
    DomainQ5
    ExampleAbdul Aziz (Q4665270) → 41464
    Sourcehttp://www.cricketarchive.com/
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Major, compherensive database for cricket players. Used widely in several Wikipedias. Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    Discussion

    English Wikipedia uses template with such input: |1=41464, and just gets first two digits for URL, but I think, we can do this in other way like I proposed. --Edgars2007 (talk) 11:54, 9 March 2016 (UTC)

    OK, I wasn't pleased with this "solution" so I changed it to normal ID. I hope it's OK, that we won't have formatter URL for now, but simply string. Of course, it the property gets approved --Edgars2007 (talk) 10:28, 11 March 2016 (UTC)
    •  Support --- Løken (talk) 12:19, 19 March 2016 (UTC)
    •  Support, but this should still be datatype=external-id. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:46, 21 March 2016 (UTC)
    •  Neutral I'm not very happy with this approach, unless there exists some kind of notation of how this identifier is supposed to be used which can be used programmatically, preferrably from Lua. Maybe there should be some kind of pseudocode allowed in the formatter URL's? If not, the ID should be something the formatter URL can use. The way it's noted now, you can't use it unless you have "the key" which isn't present here. Stigmj (talk) 22:52, 1 April 2016 (UTC)
      • Most probably I won't answer your question, Stigmj, but I'll give a try. So if you provide local formatter URL at Wikipedia, then you can use this property in such URL (this is in wikitext, which of course will be very easy convertable to Lua): http://www.cricketarchive.com/Archive/Players/{{#expr:trunc({{{id}}}/1000)}}/{{{id}}}/{{{id}}}.html. Having correct formatter URL at Wikidata, so everything is pretty, isn't possible at current stage. The ID at Wikidata itself will be clickable, I assume, as we have a gadget for that. Why not having "normal" ID for working URL generation? Well, one of most important reasons is to not have possible problems in future, if website admins decide to change URL format. And "41/41464/41464" isn't ID, "41464" is :) IMHO, not having working URL for an ID is not good enough reason not to store values themselves at Wikidata. At least, not in this case. --Edgars2007 (talk) 11:58, 2 April 2016 (UTC)
        • Edgars2007: Is it possible to use the ID on the site somehow without knowing the exact "encoding" in the URL? If so, I'm all for it. What I don't like is a collection of purely internal ID's which can't be used or referenced in any way without knowing how to use them. In this exact case, it's possible to "encode" the URL correctly on wikipedia if you know how it's constructed, but this information is *not* present in the wikidata-entry and would possibly prevent the usage from other parties not privy to this information. As a minimum, the property should be marked as such. Stigmj (talk) 17:44, 2 April 2016 (UTC)
        • Edgars2007: And to add to this, Freebase, Metacritic and Rotten Tomatoes uses "multipart" values which has direct mapping to URL's in their systems. I'm pretty sure they have some kind of internal ID as well, which we can't see or know about. I can't see the rationale for having this ID be any different. Yes, enwiki may have done it differently for this exact ID, but that's not a good enough reason for me. Local formatter URL's are not "user friendly" and I would like to avoid them when possible. The only reason I can see is if the ID is actually usable for any other purpose than the lookup via a direct URL. Stigmj (talk) 23:02, 2 April 2016 (UTC)

    @Edgars2007, Løken, Pigsonthewing: ✓ Done. It is certainly useful to record an ID, even if our simple URL formatter approach can not create a link from that. But links can be derived programatically, for example in templates. --Srittau (talk) 13:09, 3 April 2016 (UTC)

    @Edgars2007, Srittau, Løken, Pigsonthewing: I'm am questioning what the real ID is in this case. Why is the ID "41464" in this case and not "41/41464/41464"? Is there some corroborating information to this effect other than the simple programmatically possibility of constructing the URL knowing only the "last part" of the "long ID"? As I have asked before, is there any way of finding or using this ID in the website other than constructing the URL needed to access the information? Edgars2007 alleges the URL could possibly be changed in the future and an ID with "41/41464/41464" may not be valid anymore. This is true, but then the ID could also change altogether unless we have some kind of assurance of the stability of the said structure. All signs points to the "41464"-part being the "ID" as noted, but unless this can be corroborated and possible to use in some way other than constructing the URL's, I can't see the problem with using a "41/41464/41464"-notation as the ID. We already have precedence for this in many other identifiers. Stigmj (talk) 14:18, 3 April 2016 (UTC)
    @Stigmj: Please continue this discussion of the property talk page.

    UIPM ID

    Descriptionidentifier for a athlete, in the Union Internationale de Pentathlon Moderne database
    RepresentsUnion Internationale de Pentathlon Moderne (Q1347281)
    Data typeExternal identifier
    Template parameterit:Template:SchedaUIPM
    Domainhuman (Q5)
    Allowed values[1-9][0-9]+
    ExampleLaura Asadauskaitė (Q260438) → 4232
    Sourcehttp://www.pentathlon.org/
    Formatter URLhttp://www.pentathlon.org/athletes/athlete-bio/?id=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Union Internationale de Pentathlon Moderne (Q1347281) is the governing body for the Olympic sport of modern pentathlon (Q32485). Database contains detailed statistical information. ID will be used in Template:Sports links (Q22674492). Edgars2007 (talk) 09:16, 25 March 2016 (UTC)

    Discussion

    @Edgars2007, Thierry Caro, Pigsonthewing: ✓ Done --Srittau (talk) 21:54, 6 April 2016 (UTC)

    United World Wrestling ID

    Descriptionidentifier for an athlete, in the United World Wrestling database
    RepresentsUnited World Wrestling (Q688489)
    Data typeExternal identifier
    Template parameteren:Template:FILA
    Domainhuman (Q5)
    Allowed values[A-Z1-9][A-Z0-9]+
    ExampleAnastasija Grigorjeva (Q465714) → 5283C4DFAF6E45DF8879B7934AB9E111
    Sourcehttps://www.iat.uni-leipzig.de/
    Formatter URLhttps://www.iat.uni-leipzig.de/datenbanken/dbfoeldeak/daten.php?spid=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    United World Wrestling (Q688489) is the governing body for the Olympic sport of wrestling (Q42486). Database contains detailed statistical information. ID will be used in Template:Sports links (Q22674492). Edgars2007 (talk) 09:16, 25 March 2016 (UTC)

    Discussion

    @Edgars2007, Løken, Pigsonthewing, Thierry Caro: ✓ Done --Srittau (talk) 22:02, 6 April 2016 (UTC)

    Badminton World Federation ID

    Descriptionidentifier for a badminton player, in the Badminton World Federation database
    RepresentsBadminton World Federation (Q126638)
    Data typeExternal identifier
    Template parameterde:Vorlage:BWF
    Domainhuman (Q5)
    Allowed values[A-Z0-9-]+
    ExampleChen Long (Q715563) → 8F42FC23-89C1-40CF-8F20-8519DE2BE4EF
    Sourcebwfcontent.tournamentsoftware.com
    Formatter URLhttp://bwfcontent.tournamentsoftware.com/profile/default.aspx?id=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    Badminton World Federation (Q126638) is the governing body for the Olympic sport of badminton (Q7291). Database contains detailed statistical information, that is useful for players referencing. ID will be used in Template:Sports links (Q22674492). Edgars2007 (talk) 10:09, 28 March 2016 (UTC)

    Discussion

    @Edgars2007, Løken, Thierry Caro, Pigsonthewing: ✓ Done --Srittau (talk) 22:26, 6 April 2016 (UTC)

    ISSF ID

    Descriptionidentifier for an athlete, in the International Shooting Sport Federation database
    RepresentsInternational Shooting Sport Federation (Q708793)
    Data typeExternal identifier
    Template parameteren:Template:ISSF name
    Domainhuman (Q5)
    Allowed values[A-Z0-9]+
    ExampleJoshua Richmond (Q6290155) → SHUSAM1912198501
    Sourcehttp://www.issf-sports.org
    Formatter URLhttp://bwfcontent.tournamentsoftware.com/profile/default.aspx?id=$1
    Robot and gadget jobsMy bot can import values from Wikipedias
    Motivation

    International Shooting Sport Federation (Q708793) is the governing body for the Olympic sport of shooting sport (Q206989). Database contains detailed statistical information, that is useful for athletes referencing. ID will be used in Template:Sports links (Q22674492). Edgars2007 (talk) 10:09, 28 March 2016 (UTC)

    Discussion

    @Edgars2007, Løken, Thierry Caro, Pigsonthewing: ✓ Done --Srittau (talk) 22:35, 6 April 2016 (UTC)

    New York Times Semantic Concept proposals

    New York Times Semantic Concept: Person

       Done: no label (P2690) (Talk and documentation)
    DescriptionThe New York Times associates Semantic Concepts with articles, these concepts are exposed both through metadata embedded in the HTML of articles as well as through its Semantic API. This property identifies people, others identify places, organizations and descriptors.
    Data typeString
    Template parameternone
    Domainpeople
    ExampleBarack Obama (Q76) → "Obama, Barack"
    Sourcehttp://developer.nytimes.com/docs/semantic_api
    Formatter URLhttp://api.nytimes.com/svc/semantic/v2/concept/name/nytd_per/$1?api-key=your-API-key
    Robot and gadget jobsThe Semantic API contains incomplete links to Wikipedia, Freebase and DBPedia, these could be imported on an ongoing basis. Additional unmaintained data is available from data.nytimes.com which could be done as a one time load.
    Motivation

    Being able to associate New York Times articles with semantic concepts opens up an avenue for many third party applications to interact with their data. The Times has already associated a subset of their controlled vocabulary with Wikipedia items, so part of the work is already done.

    This submission is further to discussion with Thryduulf and Runner1928 from a previous submission Thinkcontext (talk) 18:49, 24 February 2016 (UTC)

    Discussion

    New York Times Semantic Concept: Location

       Done: no label (P2692) (Talk and documentation)
    DescriptionThe New York Times associates Semantic Concepts with articles, these concepts are exposed both through metadata embedded in the HTML of articles as well as through its Semantic API. This property identifies locations, others identify people, organizations and descriptors.
    Data typeString
    Template parameternone
    Domainlocations
    ExampleAcapulco (Q81398) → "Acapulco (Mexico)"
    Sourcehttp://developer.nytimes.com/docs/semantic_api
    Formatter URLhttp://api.nytimes.com/svc/semantic/v2/concept/name/nytd_geo/$1?api-key=your-API-key
    Robot and gadget jobsThe Semantic API contains incomplete links to Wikipedia, Freebase and DBPedia, these could be imported on an ongoing basis. Additional unmaintained data is available from data.nytimes.com which could be done as a one time load.
    Motivation

    Being able to associate New York Times articles with semantic concepts opens up an avenue for many third party applications to interact with their data. The Times has already associated a subset of their controlled vocabulary with Wikipedia items, so part of the work is already done.

    This submission is further to discussion with Thryduulf and Runner1928 from a previous submission Thinkcontext (talk) 18:49, 24 February 2016 (UTC)

    Discussion

    New York Times Semantic Concept: Organization

       Done: no label (P2691) (Talk and documentation)
    DescriptionThe New York Times associates Semantic Concepts with articles, these concepts are exposed both through metadata embedded in the HTML of articles as well as through its Semantic API. This property identifies organizations, others identify places, people and descriptors.
    Data typeString
    Template parameternone
    DomainOrganization
    Example3M (Q159433) → "3M Company"
    Sourcehttp://developer.nytimes.com/docs/semantic_api
    Formatter URLhttp://api.nytimes.com/svc/semantic/v2/concept/name/nytd_org/$1?api-key=your-API-key
    Robot and gadget jobsThe Semantic API contains incomplete links to Wikipedia, Freebase and DBPedia, these could be imported on an ongoing basis. Additional unmaintained data is available from data.nytimes.com which could be done as a one time load.
    Motivation

    Being able to associate New York Times articles with semantic concepts opens up an avenue for many third party applications to interact with their data. The Times has already associated a subset of their controlled vocabulary with Wikipedia items, so part of the work is already done.

    This submission is further to discussion with Thryduulf and Runner1928 from a previous submission Thinkcontext (talk) 18:49, 24 February 2016 (UTC)

    Discussion

    New York Times Semantic Concept: Descriptor

       Done: no label (P2693) (Talk and documentation)
    DescriptionThe New York Times associates Semantic Concepts with articles, these concepts are exposed both through metadata embedded in the HTML of articles as well as through its Semantic API. This property identifies descriptors, others identify places, organizations and people.
    Data typeString
    Template parameternone
    Domaindescriptor
    Exampleabsenteeism (Q332278) → "Absenteeism"
    Sourcehttp://developer.nytimes.com/docs/semantic_api
    Formatter URLhttp://api.nytimes.com/svc/semantic/v2/concept/name/nytd_des/$1?api-key=your-API-key
    Robot and gadget jobsThe Semantic API contains incomplete links to Wikipedia, Freebase and DBPedia, these could be imported on an ongoing basis. Additional unmaintained data is available from data.nytimes.com which could be done as a one time load.
    Motivation

    Being able to associate New York Times articles with semantic concepts opens up an avenue for many third party applications to interact with their data. The Times has already associated a subset of their controlled vocabulary with Wikipedia items, so part of the work is already done.

    This submission is further to discussion with Thryduulf and Runner1928 from a previous submission Thinkcontext (talk) 18:49, 24 February 2016 (UTC)

    Discussion
    •  Support all three New York Times semantic concept proposals. Thryduulf (talk: local | en.wp | en.wikt) 19:22, 24 February 2016 (UTC)
    •  Strong support for all four NYT proposals. http://data.nytimes.com/ has all data available in one file per semantic concept type. Those files have multiple ways to auto-match records, including geonames, dbpedia, freebase, and more. I'd love to hear more from @Thinkcontext: about ways to automatically populate this information. Runner1928 (talk) 16:16, 25 February 2016 (UTC)
      • @Runner1928: topics.nytimes.com has what I believe is a complete listing of the topics which correspond to the concepts. It should be a simple matter to scrape the topic text and do a lookup against the API to get Wikipedia, Freebase or DBPedia reference. data.nytimes.com contains RDF dumps which have all the information so it would be best to do a mass import of that first and then setup a bot to monitor the topic listing.
    •  Comment These "formatter URL" values will NOT work with wikidata - it requires a developer API key - the "your-API-key" piece. When you follow the links as given it returns an error page ("Inactive developer"). Unless we can find a URL link for these concepts that does not have that dependency on personal API keys, I am uncomfortable with adding these identifiers to wikidata. ArthurPSmith (talk) 20:27, 29 February 2016 (UTC)
    • @ArthurPSmith: I see, thanks for the comment. As you can tell I've been having difficulty figuring out how and where this information would best fit into wikidata. I think there's considerable value to having it in wikidata, do you have any suggestion as to where it would best fit? As a generic property? Thinkcontext (talk) 14:56, 1 March 2016 (UTC)
      • @Thinkcontext: I agree it would be nice to include this data somehow in wikidata. But I don't think you have the right data format here. Looking at their "about" page the ID's should be numbers, not the words you list, and the formatter should be simply http://data.nytimes.com/$1 - as that about page says, "For instance our subject heading for "Park Slope, Brooklyn" is associated with the URI http://data.nytimes.com/60694995023816375851. " So I think the ONLY thing wikidata should have is those numbers (represented as external identifiers) linked to the associated wikidata items via something like a "NY Times Semantic Concept ID". We definitely don't want to have some dependence on a developer API - they provide open linked data, we should use that. ArthurPSmith (talk) 15:04, 1 March 2016 (UTC)
      • Hmm, I just noticed this issue was brought up previously (earlier proposal still on this page). However, I think your argument is wrong. If NY Times is not providing this data without restricting it (via developer API) then it should not be in wikidata. We should take what they give us as open, even if it hasn't been kept up to date. There are English text labels associated with each concept at data.nytimes.com (the skos:prefLabel value) and there is also a search API link provided, so I don't think your concerns about being unable to look things up from the number are valid. And I think the number is the only reasonable thing we can use here. ArthurPSmith (talk) 15:19, 1 March 2016 (UTC)
        • @ArthurPSmith: The text labels are not only exposed by the API. In fact the reason I feel the text labels have great value for linked data applications is that they are exposed within the HTML of articles as metadata. Example from todays paper, What to Watch For on Super Tuesday has <meta name="per" content="Clinton, Hillary Rodham" /> (as well as a variety of other tags for other people and subjects) which NYT lets us know corresponds to http://dbpedia.org/resource/Hillary_Rodham_Clinton. Its extremely rare for a major news organization to connect their own internal processes to the linked data cloud in this way, we would potentially be giving up a great deal of value in not recording this information. As for the numerical ids, I personally don't see the value of them and feel having obsolete ids is confusing clutter. Thinkcontext (talk) 16:01, 1 March 2016 (UTC)
          • @Thinkcontext: Can you give a reference for why you think the numerical ids are obsolete? There is no sign of it on the NY Times web pages, including the one you linked to - the Semantic API page explicitly says: "As part of its work on linked data New York Times R&D created http://data.nytimes.com, a site where we publish the vocabulary used to index concepts. The site assigns a unique URI to each concept, and in the form of http://data.nytimes.com/concept_uri. This "concept_uri" is a mandatory parameter for accessing the Semantic API with a linked data reference." and that "concept_ui" is the numerical id we are talking about here. The REASON it is important to have a numerical id instead of a name is - suppose you have an article tagged with "Clinton, Hillary Rodham" - and then she gets divorced and changes her name back to "Rodham, Hillary". Suddenly all your old semantic concept id's are invalid. But the numerical id refers to the same person and is still good. It doesn't look to me like the NY Times is providing a strong guarantee regarding the permanence of the concept labels, and the concept_uri values are being promoted. Unless you can provide some more evidence on why you think the data.nytimes.com stuff is really abandoned it seems to me the numerical ids are the ones we need here. Or perhaps you can give a more complete use case describing an instance where the labels would be helpful to have in wikidata and a numerical id would not? I'm not seeing the problem right now. ArthurPSmith (talk) 16:42, 1 March 2016 (UTC)
            • @ArthurPSmith: I feel that the numerical id is obsolete because data.nytimes.com has not been updated for around 5 years.This snapshot from archive.org in 2011 has the exact same number of entities listed as today, so no new items have entered that data set. I have examined the SKOS data dumps and verified that they contain the same number. The individual record for Hillary Clinton on that site lists a last used time in 2010. I'd definitely prefer to have a permanent id but if they have abandoned it I don't think it would be good for wikidata to use it, especially because they are over 20,000 items short now. Your point about changing names is a good one, I think these would be better as generic properties rather than authority control ids, I guess I'll resubmit. Thinkcontext (talk) 19:37, 1 March 2016 (UTC)
              • well the snapshot you point to says exactly the same thing as the current page about the total too, so apparently the 20,000 missing hasn't changed since 2011: "The New York Times uses approximately 30,000 tags to power our Times Topics Pages. It is our intention to publish all of these tags as linked open data." Is there any third-party discussion on what the NY Times is doing on this, or a more recent quote from them? Also, how would you source the full dataset if it's not available from data.nytimes.com? ArthurPSmith (talk) 21:10, 1 March 2016 (UTC)
                • @ArthurPSmith: topics.nytimes.com contains most of the additional labels, scraping them is a simple matter. I'm not aware of any more recent statement from them about their open data plans. Thinkcontext (talk) 22:25, 2 March 2016 (UTC)
                  • @Thinkcontext: Well, I'm not sure this is going anywhere between just the two of us; this will be my last comment here on this, I just don't feel I can support this proposal at this time though in principle I would like to see NY Times semantic concepts linked. Looking at topics.nytimes.com the list seems at least as out of date as whatever is on data.nytimes.com. Not a single one of the 2016 presidential contenders is listed on the "People" topics page, for example, not even Trump or Clinton. Maybe the best way forward would be to email NY Times and try to convince them to use wikidata ID's as semantic concepts, if they are having trouble maintaining their own database. ArthurPSmith (talk) 14:20, 3 March 2016 (UTC)
    • I'm not sure why this has been posted as a new proposal; but please see my comments in the previous discussion, which this proposal does not address. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:57, 3 March 2016 (UTC)

    @Thinkcontext, Thryduulf, Runner1928: ✓ Done. This was a hard one. Frankly speaking, the linked data initiative of the New York Times is a mess. On the one hand you have an open, non-restricted API, using surrogate keys, with data under a CC license. This has seemingly been abandoned five years ago. On the other hand, you have a restricted, registration-required, unfree API, using natural keys, for which we have no stability guarantee, but which seems to be kept fairly up-to-date. (I registered and got an API key. I checked two items. Zaha Hadid (Q47780), who died today and has an obituary on www.nytimes.com had not been updated. On the other hand, the entry for Bernie Sanders was last updated in February.) Both APIs have no references to each other. Nevertheless I think there is inherent value in linking our concepts to that of the New York Times as a major news outlet. The outdated data is no options, so we have to use the current API, despite its problems. Let's hope their data becomes more open in the future. --Srittau (talk) 20:08, 31 March 2016 (UTC)

    is verso of

       Done: is verso of (P2682) (Talk and documentation)
    DescriptionA property to indicate the two-dimensional artwork (usually drawing or painting) that is on the front (recto) side of this artwork
    Data typeItem
    Domaintwo-dimensional (flat) work of art (Q838948)
    ExampleCroy family shield (Q21614521) → Portrait of Philippe de Croy (Q22970535)
    Sourceusually museums' online collections
    Motivation

    I've encountered several artworks already for which we'd need this property. This is different from pendant of (P1639), which refers to two artworks on different carriers that were created to complement each other. I also propose the reverse property. Both must be named clearly (or get several crystal clear aliases) so that they don't get mixed up with their reverse. Spinster (talk) 15:22, 29 February 2016 (UTC)

    Discussion

    @Spinster, Jane023, Husky, Pigsonthewing: ✓ Done --Srittau (talk) 23:51, 28 March 2016 (UTC)


    Typeface/font

    DescriptionTypeface/font which is used in a work/book
    Representstypeface (Q17451)
    Data typeItem
    Template parameter(noone known)
    Domainbook (Q571) and similar
    Allowed valuesInstances of typeface (Q17451) or font (Q4868296)
    ExampleSamlede Digte (Q21996304) -> Janson (Q716102)
    Robot and gadget jobs(probably not necessary)
    Motivation

    Books are usually produced with one or a few distinct typefaces. Examples of typefaces are Times Roman (Q1321181), Janson (Q716102) or Palatino (Q1093499). Newer books often state the typeface in the frontal matter. Together with the number of pages, ISBN, title, author, etc., it is what characterizes an edition of a book. — Finn Årup Nielsen (fnielsen) (talk) 19:02, 30 March 2016 (UTC)

    Discussion


    Bekker Number

       Done: Bekker Number (P2683) (Talk and documentation)
    Descriptionreference to works in the Corpus Aristotelicum
    RepresentsBekker numbering (Q20065339)
    Data typeExternal identifier
    Domainworks by Aristotle
    ExampleDe divinatione per somnum (Q3481620) → 462b
    SourceWikipedia
    Proposed by
    --- Jura 18:55, 6 March 2016 (UTC)
    Discussion

    @Jura1: ✓ Done, no objections. --Srittau (talk) 00:03, 29 March 2016 (UTC)


    mean lifetime

       Done: mean lifetime (P2645) (Talk and documentation)
    Descriptioninverse of decay rate for an elementary particle; half-life is ln(2) times this value
    Representsmean lifetime (Q1758559)
    Data typeNumber (not available yet)
    Template parameter"mean_lifetime" in w:en:Template:Infobox particle
    Domainparticle physics (Q18334)
    Allowed valuesany positive floating number
    Exampleneutron (Q2348) → 880,3 ± 1,1 seconds
    Motivation

    See this discussion. Pamputt (talk) 17:02, 11 March 2016 (UTC)

    Discussion
    1.  Weak support - this is closely related to half-life (P2114) but 'mean lifetime' is more commonly used for elementary particles, while 'half life' for nuclides. For some items we might have both values - is there a way to constrain them to indicate they should be numerically related? ArthurPSmith (talk) 19:34, 11 March 2016 (UTC)
    2.  Weak support Agreed with ArthurPSmith. Pamputt (talk) 22:55, 19 March 2016 (UTC)
    ✓ Done @Pamputt, ArthurPSmith: --Pasleim (talk) 23:47, 23 March 2016 (UTC)

    Extinct

       Not done
    Descriptionstatus of a taxon of which no living examples remain
    Representsextinction (Q123509)
    Data typeString
    Template parameterExtinct in Template:Taxonomy/Tyrannosaurus
    DomainAll taxa
    Allowed valuesYes/No
    ExampleTyrannosaurus (Q14332) → Yes
    Motivation

    As proposed here there's not a way to know if a taxon is extinct when we create a Wikidata list of, let's say, Mammals families. With a simple yes/no definition we can change this, as we can generate a list with only extant or extinct groups. Theklan (talk) 12:53, 3 March 2016 (UTC)

    Discussion

     Support but it should not be a String datatype; I don't believe we have boolean datatypes in wikidata, but you can do the equivalent with an item datatype with allowed values true (Q16751793) and false (Q5432619) perhaps? ArthurPSmith (talk) 21:28, 3 March 2016 (UTC)

     Oppose I now don't believe this is necessary, instance of (P31) with an appropriate item should suffice. ArthurPSmith (talk) 17:50, 22 March 2016 (UTC)
    It can also be done changing taxon (Q16521) with extinction (Q123509) -Theklan (talk) 22:31, 3 March 2016 (UTC)
    What about a more generic property like "status"? --Micru (talk) 22:35, 3 March 2016 (UTC)
    Sounds good. What kind of statuses did you had in mind? Of course IUCN is one good source but for this it should perhaps be something more general? --Averater (talk) 08:57, 5 March 2016 (UTC)
    A better term would be „extinction status” which takes the values extant and extinct. The default value extant should only be used if there are contradicting claims. --Succu (talk) 15:24, 7 March 2016 (UTC)
    I'd totally oppose a meaningless "status" property. It would be totally empty. author  TomT0m / talk page 16:43, 8 March 2016 (UTC)

    WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --Succu (talk) 22:41, 3 March 2016 (UTC)

    Can this not be done with IUCN conservation status (P141) extinct species (Q237350)? Thryduulf (talk: local | en.wp | en.wikt) 23:46, 3 March 2016 (UTC)
    The IUCN Red List did not include taxa that went extinct before 1500 AD. --Succu (talk) 11:50, 4 March 2016 (UTC)
    And it doesn't include taxa other than species, as genus, families or whole phylla. -Theklan (talk) 20:37, 4 March 2016 (UTC)
     Comment I am not happy with this: Tyrannosaurus rex is not "extinct" but is know to us only from fossils (bones and perhaps eggs). I would rather see a property "fossil". Or "instance of fossil". - Brya (talk) 05:26, 4 March 2016 (UTC)
    If a taxon is not extant, then it is extinct. It can be known from fossils or not, that's the evidence for us to know that it was extant when it lived. -Theklan (talk) 20:37, 4 March 2016 (UTC)
    The point is that these are two different things: "only known from fossils" and "extinct". And for Tyrannosaurus rex the label "extinct" is not a meaningful one.
            And "extant" is here and now (it is plain silly to say "to those dinosaurs that were taxonomists T. rex was an extant species", as we don't know of any dinosaurs that were taxonomists; in fact even the idea that there might have been dinosaurs that could read will be regarded as far-fetched by the scientific community). - Brya (talk) 11:02, 5 March 2016 (UTC)
    I don't think is silly to say that Tyrannosaurus rex or Homo habilis are extinct species, nor Australopithecus an extinct genus. -Theklan (talk) 23:33, 6 March 2016 (UTC)
    Whoever said that was silly? But to say that Tyrannosaurus rex is extinct is quite uninformative. The dodo is "extinct", there are quite a few species that are "presumed extinct" (they might still be found alive) and there are species that are "extinct in the wild" (there are some in zoos or gardens). But Tyrannosaurus rex is in a quite different category and "only known from fossils". - Brya (talk) 05:49, 7 March 2016 (UTC)
    An interesting discussion. I guess that the extinction status (basically true/false) should be supplemented with an estimated time (date) of extinction (eg. 68,000,000 MY). That would allow us to somewhat categorize the extinct species. There is a grey zone between "fossil only" and "extinct" and I would be afraid of drawing a clear line between those two. As for "extinct in the wild", we already have such information in the IUCN categories, don't we (E vs. EW categories) - extinction in the wild vs. individuals in ZOO only applies to year>1500 species and that's covered by IUCN quite well.--Vojtěch Dostál (talk) 07:26, 7 March 2016 (UTC)
    Indeed, IUCN covers most of the cases of "extinct" (in the narrow sense), but not the dodo. Nor the moa, which is more of a grey area. In many cases, age will work, but its presence would have to be made a requirement. Also, there are lot of fossils, and these are not necessarily well documented (or defined). In those cases there is nothing like an estimated time of extinction. - Brya (talk) 11:43, 7 March 2016 (UTC)
    As far as I know when a mass extinction occurs (as in the Permian) there is an extinction. So if there's an extinction then those taxa are now extinct. They were alive. Then all of them died. And now they're extinct. -Theklan (talk) 12:20, 7 March 2016 (UTC)
    The organisms that went extinct then can be subdivided in two groups: 1) those that are known to us (at least in part) by fossils and 2) those that are not known to us at all. - Brya (talk) 17:43, 7 March 2016 (UTC)
    Those that are not known to us at all, is to say, the unknowns unknown are not eligible for Wikidata. -Theklan (talk) 22:40, 7 March 2016 (UTC)
    Fossilworks and PaleoDB make no distinction (dodo at Fossilworks) between „real fossils” and taxa that became extinct in the holocene (another example woolly mammoth (Q3699044)). --Succu (talk) 15:24, 7 March 2016 (UTC)
    Fossilworks looks at this from the other end: everything in Fossilworks is fossil. - Brya (talk) 17:43, 7 March 2016 (UTC)
    Yes, both have a field extant. --Succu (talk) 21:54, 7 March 2016 (UTC)
    Because there are fossils of extant species and taxa. For example Homo sapiens is known by fossils and we are here. -Theklan (talk) 22:40, 7 March 2016 (UTC)
    I'd  Weak oppose as it's a case of classification which can be handled with instance of (P31). It's clearly doable with a class extinct taxon, like a lot of properties wich could use the boolean datatype. author  TomT0m / talk page 16:43, 8 March 2016 (UTC)
    Yes, we could have "instance of fossil taxon", with "fossil taxon" a subclass of "taxon". - Brya (talk) 18:31, 8 March 2016 (UTC)
    I'll add that this has the additional features of the classical handling on classes, we can add has characteristic (P1552), properties for this type and so on. author  TomT0m / talk page 10:14, 10 March 2016 (UTC)
     Not done --Pasleim (talk) 23:50, 23 March 2016 (UTC)

    Micro-organism respiration

       Not done
    DescriptionRequirement respiration for micro-organisms
    Data typeItem
    Domaintaxon (Q16521) AND strain (Q855769)
    Allowed valuesanaerobic organism (Q189790) OR aerobic organism (Q193124) OR microaerophile (Q548321) OR facultative anaerobic organism (Q1091848) OR microaerophile (Q548321) OR obligate aerobe (Q7075150) OR obligate anaerobe (Q2915932)
    ExamplePseudomonas putida KT2440 (Q21079489) → aerobic organism (Q193124)
    Robot and gadget jobsWe are planning this to use in bots that add phenotypic characterisations
    Motivation

    /Micro-organisms can grow under various oxygen conditions. Some can grow only with oxygen while others can only grow without. Between these two there is a range in which organisms can grow partially with or without oxygen. These phenotypic characterisations are of utmost interest for further characterising bacteria. --jjkoehorst (talk) 07:15, 9 March 2016 (UTC)

    Discussion
    Andrew Su
    Boghog
    Emw
    Dan Bolser
    Daniel Mietchen
    Gtsulab
    Andra Waagmeester
    Sebotic
    Elvira Mitraka
    Konrad U. Förstner (talk)
    Kristina Hettne
    Hardwigg
    i9606
    Putmantime
    Jasper Koehorst
    Comamonas
    Muhammad Elhossary
    Netha Hussain
    Fractaler
    Layla Michán
    SCIdude
    Therealjoesmith
    TiagoLubiana
    Tris T7 TT me
    Juliansteinb
    Leptospira
    L.C.Reimer
    Charlie Pauvert (talk)

    Notified participants of WikiProject Microbiology

     Comment The "Facultative (Q5428855)" seems to be an error? From a glance at the two proposals, I am not convinced we would need two separate properties, we might get by with just one property for micro-organisms? - Brya (talk) 06:46, 10 March 2016 (UTC)

    You mean a more generic phenotype property? Which could encapsulate, oxygen requirement, temperature range among other to be defined properties? --jjkoehorst (talk) 09:08, 12 March 2016 (UTC)

    Yes. - Brya (talk) 10:38, 12 March 2016 (UTC)

    Indeed Q5428855 was a mistake as this is a too generic feature. Has been removed. --jjkoehorst (talk) 09:38, 12 March 2016 (UTC)

     Comment @jjkoehorst: I propose you to chenge the label of the property by bacteria or micro-organism respiration. Oxygen requirement is not really adapted. Snipre (talk) 12:01, 12 March 2016 (UTC)
     Comment @Snipre: I have modified the title and working on the addition of the other values. --jjkoehorst (talk) 15:51, 12 March 2016 (UTC)

    mirTarBase ID

       Done: mirTarBase ID (P2646) (Talk and documentation)
    DescriptionThe identifier for the mirTarBase database, a database for microRNAs and their targets.
    RepresentsMiRTarBase (Q6826951)
    Data typeExternal identifier
    DomainMolecular biology
    Allowed values'MIRT' as a prefix followed by six digits, e.g. MIRT000057
    Examplehsa-mir-143 (Q6871657) → MIRT000312
    Sourcehttp://mirtarbase.mbc.nctu.edu.tw/php/download.php
    Formatter URLhttp://mirtarbase.mbc.nctu.edu.tw/php/detail.php?mirtid=$1
    Robot and gadget jobsProteinBoxBot will add and maintain these items from their original source
    Motivation

    This property would hold the identifier for the microRNA target database mirTarBase (http://mirtarbase.mbc.nctu.edu.tw/index.php) and would allow to properly represent microRNAs in Wikidata and also represent their targets in Wikidata with the 'regulates' property (P128). I consider this as a very valuable resource in Wikidata, as this data only is available on the mirTarBase project website or as an MS Excel sheet. Integrating this data into Wikidata would add a great resource for understanding gene expression and also will allow to enrich the Wikipedia articles on microRNAs with a reliable resource on microRNA targets. Sebotic (talk) 00:29, 12 March 2016 (UTC)

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

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

    Notified participants of WikiProject Medicine

     Support --I9606 (talk) 04:07, 14 March 2016 (UTC)

     Support MicrobeBot (talk) 18:38, 17 March 2016 (UTC)

    Discussion

    @Sebotic, I9606, MicrobeBot: ✓ Done --Pasleim (talk) 00:01, 24 March 2016 (UTC)

    median lethal dose

       Not done
    DescriptionStatistically derived median dose of a chemical or physical agent (radiation) expected to kill 50% of organisms in a given population under a defined set of conditions.
    Representsmedian lethal dose (Q711849)
    Data typeNumber (not available yet)
    Template parameterLD50
    Domainchemicals
    Allowed valuesnumbers with units in amount per kilo for a specific animal using a specific administration route (administration route and animal should be qualifiers)
    Examplemethanol (Q14982): 4710 mg/kg, applies to taxon (P2352): house mouse (Q83310), route of administration (P636): intravenous injection (Q1369403)
    SourceExternal references
    Motivation

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

    Discussion

    Biographical Directory of Federal Judges id

    Descriptionidentifier for a judge in the Biographical Directory of Federal Judges
    Data typeExternal identifier
    Template parameter1 in en:Template:FJC Bio and other language versions
    DomainQ5
    Allowed values\d+
    ExampleRobert Gibson (Q7344755) → 851 -> [10]
    Sourcefrom the website, or wikipedia templates.
    Formatter URLhttp://www.fjc.gov/servlet/nGetInfo?jid=$1&cid=999&ctype=na&instate=na
    Robot and gadget jobsimport from enwiki
    Motivation

    The Biographical Directory of Federal Judges (Q4914870) is an directory of information about US Federal Judges. It is in the public domain, it is a useful source of information, as well as a unique identifier. Silverfish (talk) 19:03, 18 November 2015 (UTC)

    Proposal format
    Discussion
    • Closed this as not done, because the request has been open for about a month and it lacks a proper motivation and description and the example is unclear. This makes it impossible to create the property. Mbch331 (talk) 11:40, 8 November 2015 (UTC)
      • Mbch331: Rationale is "implement Wikidata phase 2". Additional details are available by clicking on the template link for full details. I took the liberty to structure the discussion above. --- Jura 12:26, 8 November 2015 (UTC)
        • We shouldn't guess what it's meant for, we shouldn't go to other projects to see why a proposal has been done. The example doesn't match the allowed values, so the example is invalid. When asked for more information by 2 opposes, no information is provided. When I mark the proposal as not done, additional information is provided. The information needed to create a property should be provided upon the moment of proposing the property. And still not all information is provided. A link to a template isn't a property title. If you still want this property, place a proper request that doesn't make others guessing at what you want. Mbch331 (talk) 14:30, 8 November 2015 (UTC)
          • It's not clear if all opposes actually read the proposal, so I'd rather not get involved. IMHO the template needs to be checked in detail to assess the proposal. Obviously, it can help to re-state the project goal each time and, yes, including "en:Template:" in the label isn't needed, but we wouldn't have done that anyways. --- Jura 15:50, 8 November 2015 (UTC)
            • I assure you I read the proposal in full. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:54, 13 November 2015 (UTC)
            • I assure the same. The description is "..." and the motivation is "(Add your motivation for this property here.)". I've gone further and read the linked template, but it is a WP template and doesn't say anything about Wikidata implementation. If we don't have that information, then there really isn't anything to work with here and thus my opposition until the proposal is fleshed out to actually explain what the property is, what it is meant to do, and how it should be implemented. Josh Baumgartner (talk) 00:43, 18 November 2015 (UTC)
              • At least one of you had a look at the template. I wonder if there are several ways to implement this. Personally, I think there would be just one. Josh, could you list the variants? --- Jura 09:12, 18 November 2015 (UTC)
    • I have added what I think is the necessary information for the property, as I think it seems useful. I invite Jura1 to check it, and everyone else to see if they support now we have the information filled in. Silverfish (talk) 19:03, 18 November 2015 (UTC)
    •  Support @Silverfish, Jura1: This proposal looks good now. Josh Baumgartner (talk) 19:58, 19 November 2015 (UTC)

    @Silverfish, Joshbaumgartner: ✓ Done. The only opposing votes were for formal reasons, which have been resolved since. --Srittau (talk) 18:26, 8 April 2016 (UTC)

    Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Archive/47&oldid=413900705"