Wikidata:Property proposal/Archive/44

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.

GOV-Kennung (de) – (Please translate this into English.)

Done: Historical Gazetteer (GOV) ID (P2503) (Talk and documentation)

Description	genealogical place index
Data type	String
Domain	geographical feature (Q618123)
Example	Jork (Q504279) → JORORKJO43UM
Source	GenWiki (Q650669)
Formatter URL	http://gov.genealogy.net/item/show/$1

Motivation

Genealogical place index for central europe. See here for details (German).--Kopiersperre (talk) 09:47, 29 November 2015 (UTC)

Discussion

Norwegian municipality number

Done: Norwegian municipality number (P2504) (Talk and documentation)

Description	unique identifier for municipalities of Norway
Data type	String
Template parameter	"kommunenummer" in no:Mal:Infoboks norsk kommune
Domain	municipality of Norway (Q755707)
Allowed values	[012]\d{3}
Example	Skiptvet Municipality (Q156420) → `0127`
Source	no:Liste over norske kommunenummer

Motivation

All Norwegian municipalities have these (all current and some former, see the linked list). They are used extensively by government agencies, and can be used for automatic linking to statistics, maps, etc. It doesn't make sense to use a formatter URL though, since there is no one place to link to. Jon Harald Søby (talk) 17:44, 12 December 2015 (UTC)

Discussion

carries

Done: carries (P2505) (Talk and documentation)

Template parameter	`\|carries=` in en:Template:Infobox bridge
Domain	bridges, viaducts, aqueducts
Allowed values	roads, railways, waterways, footpaths, etc
Source	Wikipedia infoboxes

Motivation

Common in infoboxes. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:07, 28 September 2015 (UTC)

Discussion

Support. I've used part of (P361) (e.g. Westminster Bridge (Q456960): part of (P361) A302 road (Q20971401) but that is inferior to this proper way of handling it. Thryduulf (talk: local | en.wp | en.wikt) 18:41, 30 September 2015 (UTC)
Support. Joe Filceolaire (talk) 18:18, 6 October 2015 (UTC)
Support Seems like a useful thing to represent, and I cannot find any good substitute property. Should probably clarify that it relates two landmarks, so would not be used to say that a cruise ship carries passengers. Bovlb (talk) 17:04, 28 October 2015 (UTC)
Support as a broader property not limited to bridges, but useful for other items that carry things. Josh Baumgartner (talk) 20:17, 28 October 2015 (UTC)
- @Pigsonthewing: Would broadening this property be okay with you? It seems there is support for this property, so I would like to go ahead and create it, but I wanted to get your feedback first. Thanks! 64.21.103.106 18:32, 18 November 2015 (UTC) -- That was me, it logged out on me while I wasn't looking! Josh Baumgartner (talk) 18:34, 18 November 2015 (UTC)
  - @Joshbaumgartner: Broadening it how? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:56, 18 November 2015 (UTC)
    - @Pigsonthewing: Other items such as thoroughfares, pipelines, vehicles, etc. all carry things. Josh Baumgartner (talk) 00:10, 19 November 2015 (UTC)
      - @Joshbaumgartner: I would object to the addition of vehicles, and pipelines, per Bovlb's comment, above. The sense of "carry" is not the same, and possibly named differently in other languages. What would a thoroughfare carry? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 00:20, 19 November 2015 (UTC)
        @Joshbaumgartner: Did you see this? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:17, 27 November 2015 (UTC)
I assume this would be more specific than "bridge carries road" since we can e.g. make the statement instance of (P31) road bridge (Q537127) to define a bridge's type. Is that the case? --Izno (talk) 15:45, 7 January 2016 (UTC)
- Yes. It would be e.g. Westminster Bridge (Q456960)carriesA302 road (Q20971401) or Golden Gate Bridge (Q44440)carriesU.S. Route 101 (Q410892)State Route 1 (Q550419). Thryduulf (talk: local | en.wp | en.wikt) 03:02, 10 January 2016 (UTC)

@Pigsonthewing, Thryduulf, Bovlb, Joshbaumgartner: The property is ready. --Fralambert (talk) 18:05, 17 January 2016 (UTC)

INSEE canton code

Done: INSEE canton code (P2506) (Talk and documentation)

Description	number sequence for the identification of canton in France
Data type	String
Template parameter	insee
Example	canton of Fontaine-lès-Dijon (Q18129) -> 21 14
Format and edit filter validation	2/3 character, space, 2 character (\d{1,2}[0-9AB] \d\d)
Source	Liste des cantons français avant 2015

Motivation

About 3800 french canton. Gzen92 ^[discuter] 07:32, 6 January 2016 (UTC)

Discussion

Comment @Gzen92: This proposal should be posted in Wikidata:Property proposal/Place, rather than here. This page is for properties used for references to statements, such as reference URL (P854) and retrieved (P813). Jon Harald Søby (talk) 08:52, 6 January 2016 (UTC)

it's done. Gzen92 ^[discuter] 12:30, 6 January 2016 (UTC)

Support Different of INSEE municipality code (P374). --Fralambert (talk) 04:12, 9 January 2016 (UTC)
Support, I feel like it's better to have a separate property from INSEE municipality code (P374) (same source and look alike but different format and different scope). See Property talk:P374 for some talks about it. VIGNERON (talk) 13:26, 9 January 2016 (UTC)
Done @Jon Harald Søby, Gzen92, VIGNERON: Property created by GZWDer. --Fralambert (talk) 17:51, 17 January 2016 (UTC)

property usage

Not done

Description	Technical description of the recommended usage of the property; meant to replace instructions provided in field description of `{{Property documentation}}`
Data type	Monolingual text
Template parameter	N/A
Domain	Wikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed values	String description in each language
Example	father (P22) ==> "For adoptive father, rather use relative (P1038), qualified with kinship to subject (P1039)=nominal kinship (Q11666901)"
Source	Initially from description of `{{Property documentation}}` on the talk page of each property
Proposed by	-- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

Discussion

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

I think the Description field (between label and aliases) can do this so I would Oppose this property. If that doesn't work then propose this again when we have a 'multilingual text' datatype. Filceolaire (talk) 15:54, 15 November 2014 (UTC)
Oppose the "description" field of properties is sufficient. --Paperoastro (talk) 21:35, 15 November 2014 (UTC)
Support as proposer. I believe we need a Usage property to provide usage instructions for Wikidatians, to formalize the description field of {{Property documentation}} on the talk page of each property; this would complete property Definition proposed further above. -- LaddΩ chat ;) 02:14, 27 November 2014 (UTC)
Support. I still struggle with choosing whether a chapel is "part of" a castle or "located in" a castle. More definitions and usage guidelines would help. - PKM (talk) 18:44, 27 November 2014 (UTC)
Oppose As Paperoastro. Snipre (talk) 19:15, 12 December 2014 (UTC)
I changed the datatype to "monolingual text" to match the proposal content. Given that the "description" field is the only one visible when editing an item, I think it should sometimes contain usage guidelines (like which values to use for sex or gender (P21). I agree that the "description" field is not always enough, mostly because it should be kept short (both for technical and practical reasons), and because it cannot be formatted in Wikitext. We would have the same issues if we had a new property, so I think we should rather keep things in the property documentation. -Zolo (talk) 08:03, 14 January 2015 (UTC)
Comment There is now the comment property: comment (DEPRECATED) (P2315). --- Jura 11:57, 18 November 2015 (UTC)
Oppose use comment (DEPRECATED) (P2315) --Pasleim (talk) 13:07, 29 November 2015 (UTC)

Not done Insufficiant support. Use comment (DEPRECATED) (P2315). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:44, 29 November 2015 (UTC)

Question this property could answer

Not done

Description	String should include $1. $1 would be the label of the property where the item is used.
Data type	specialized item. Label should include $1.-invalid datatype (not in Module:i18n/datatype)
Domain	property except external identifiers
Allowed values	questions including a $1
Example	sex or gender (P21) → "What is the gender of $1 ?"

Support --- Jura 16:14, 24 October 2015 (UTC)
Comment changed to item-datatype. Might work better that way. --- Jura 00:36, 31 October 2015 (UTC)
I'm against this property as an item. Multilingual text seems better off the cuff. --Izno (talk) 19:23, 24 November 2015 (UTC)
- Wouldn't the result be the same? The main difference seems to be that the question gets a QID as well. --- Jura 19:35, 24 November 2015 (UTC)
  - What purpose does having a QID for the question solve? The only case where that is sensible is having multiple questions asked in the same question i.e. all births in the United States. But the proposed property can't account for that case and even the minor modification of a $2 doesn't help (how do you tell the property page that this statement is made on whether it cares about the 1 or the 2?). --Izno (talk) 19:38, 24 November 2015 (UTC)
    - We have items, but we don't know when or if we get multilingual text. Some properties might turn out to answer several questions. Besides, the questions might turn out to have a benefit of their own. --- Jura 20:00, 24 November 2015 (UTC)

Not done Invalid data type; no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:19, 8 January 2016 (UTC)

Expected completeness

Done: expected completeness (P2429) (Talk and documentation)

Domain	Wikidata properties
Allowed values	One of always incomplete (Q21873886), eventually complete (Q21873974), and is complete (Q21874050)
Example	ISBN-13 (P212) -> always incomplete (Q21873886) ISO 639-2 code (P219) -> eventually complete (Q21873974) ISO 3166-1 numeric code (P299) -> is complete (Q21874050)
Robot and gadget jobs	none

Motivation

First proposed in this discussion by User:Andrew Gray.

For some properties, like ISO 3166-1 numeric code (P299), we should already have a complete set. For others, perhaps like ISO 639-2 code (P219), we want a complete set, but may not yet have one. And for some, like ISBN-13 (P212), we know that we never will.

This property will allow us to inform data users of our expectations in this regard.

Suggestions for a better property name, and better item labels, are invited. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:53, 9 November 2015 (UTC)

Discussion

Support --Jane023 (talk) 14:12, 9 November 2015 (UTC)
Support -- I think it's a great idea. Jheald (talk) 16:53, 9 November 2015 (UTC)

Digression: Recently I've been looking at UK scheduled monuments, listed buildings etc (see project page), so I was wondering whether this could be extended to work for a property like National Heritage List for England number (P1216), where we are aiming for near complete coverage -- but only for items falling into certain classes; so for example all buildings listed Grade I and Grade II*, but not the rest of Grade II. Could one use the new property, but with qualifiers applies to part (P518) Grade I listed building (Q15700818), applies to part (P518) Grade II* listed building (Q15700831), (values indicated by the heritage designation (P1435) property) ?

It would be nice if somebody could use this property to put a safety-catch on deletion tools, eg a pop-up confirmation warning if someone tries to delete either the subject or the object of a statement that includes a property marked in this way.

(While we're at it, it would be nice if somebody could also do something to mark classes in a similar way -- so that deletion would be discouraged for an item that was an instance of a class that was intended to be approaching completeness). Jheald (talk) 16:53, 9 November 2015 (UTC)

@Jheald: Your listed building example is interesting, We could use qualifiers, as you suggest, or create another item; say "Set of Wikidata items with a given property which is intended to be complete to a certain level"; or a mix of the two. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:28, 9 November 2015 (UTC)

Ideally one would want to specify something like heritage designation (P1435) = Grade I listed building (Q15700818) as a machine-interpretable condition to specify classes for which completeness was desirable. A simple condition like that could be recorded as a qualifier; but not on this property -- it would need to be a qualifier on a different new property that knew to expect qualifiers of that form. Otherwise one just could give up on machine interpretability, and go with P518 as suggested above. Jheald (talk) 17:36, 9 November 2015 (UTC)

Another way to do the listed building example might be to put a property-valued property on Grade I listed building (Q15700818), eg Grade I listed building (Q15700818) "object of" heritage designation (P1435), and then to give as a qualifier "expected completeness" = "aspire to complete". This could such indications for properties like position held (P39), where otherwise it would be horribly unwieldy to list all the offices one would hope to have complete values for on the P39 page itself. Using it for item "object of" instance of (P31) or "object of" subclass of (P279) would also allow classes to be marked for which we may be aspiring to a complete enumeration. The only downside is that a 'safety catch' would need to have cached quite an extensive search to make its list of types of statement that would throw a deletion warning -- but there may be no way round that, if we want to make possible such lists. A report could be compiled for each property to show for what values completeness was marked as aspired-to. Jheald (talk) 09:35, 12 November 2015 (UTC)

Support Looks good, though (as above) identifying exactly what values to use will be interesting. Andrew Gray (talk) 20:35, 9 November 2015 (UTC)
Support. Also support the use of this property on class items.Joe Filceolaire (talk) 08:48, 11 November 2015 (UTC)
Comment this looks ready to create - however, I'd like to suggest the values be given short labels with long descriptions, i.e. label "always incomplete" with description "Set of Wikidata items with this property will always be incomplete", and similarly "expected complete" and "complete" for the other two short labels. Or does somebody have something better to suggest? ArthurPSmith (talk) 20:09, 15 December 2015 (UTC)

@Andrew Gray, Jheald, Filceolaire, ArthurPSmith: Done expected completeness (P2429). See always incomplete (Q21873886), eventually complete (Q21873974), and is complete (Q21874050). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:33, 29 December 2015 (UTC)

Female form of label (string)

Done: female form of label (P2521) (Talk and documentation)

Description	female form of label
Data type	Monolingual text
Domain	terms
Example	pevec (Q177220) => pevka (sl), kantavtor (Q488205) => kantavtorica (sl). Samples from discussion linked below (no warranty).

Discussion

Adapted from Wikidata:Property_proposal/Sister_projects#Female_form.2Fequivalent_of

Oppose I would prefer having 3 items for the example: "female singer" and "male singer" should be a subclass of "singer (profession)". Wikipedia pages (and everybody should think about how to implement Wiktionary) can attach to the appropriate item. Tobias1984 (talk) 13:03, 18 November 2014 (UTC)
- Not sure if it's a good idea to split occupations by gender. P:P106 = Q177220 should be sufficient. --- Jura 18:35, 18 November 2014 (UTC)
  - Sorry Tobias1984 but I think that's a bad idea. en infoboxes would end up with "occupation:male singer" and "occupation:female singer" which they would not be pleased with. "occupation:male author" and "occupation:authoress" would be even less welcome. Filceolaire (talk) 22:27, 20 March 2015 (UTC)
Support ... I think it is a good idea ... although I and some other sl. Wikipedians will have to do some work in Wikidata and also update coding in our infoboxes for persons. But I think it is worth the effort. But I'm not really familiar with the Wikidata structure, therefore the proposal Tobias made may also work. --Pinky sl (talk) 13:14, 18 November 2014 (UTC)
Support Good idea. I can remember that absence of female form of label was presented as one of the reasons against deeper WD integration on cswiki. That can be similar for all Slavic wikis. --Jklamo (talk) 00:00, 23 February 2015 (UTC)
Support Per Jklamo. Matěj Suchánek (talk) 09:30, 23 February 2015 (UTC)
Shouldn't these be simply included as aliases? Seems a lot more productive. Pichpich (talk) 18:30, 6 March 2015 (UTC)
- If it was only one of the aliases, you couldn't select the correct one to display. Of course, it can also be an alias. --- Jura 11:09, 9 March 2015 (UTC)
Support very useful for Slavic languages --Smihael (talk) 08:40, 12 March 2015 (UTC)
Oppose. Jura, Jared Zimmerman See what I have done with Q177220. I have changed the sl label to "pevec/pevka" and added "pevec" as an alias. I think this is a better way of dealing with this as the sl label now reflects the scope of the item which it did not before. "pevec" is an inaccurate label for singer (Q177220) as that item refers to both male and female singers. How does "pevec/pevka" look in the "occupation" line of an sl infobox?

There is a solution. Propose "Male form of label" - another new property with monolingual text datatype. Label Q177220 as "pevec/pevka" in slovenian with statements "Male form:pevec (lang=sl)" and "Female form:pevka (lang=sl)". Each of these statements could have multiple values in different languages. We could also use multilingual datatype (if it ever becomes available) since these translations will be user generated and needn't have references. I guess I wouldn't oppose this solution but I would rather just tell slovenia to get over itself and accept "pevec/pevka" as an occupation.Filceolaire (talk) 22:13, 20 March 2015 (UTC)

This applies to other languages too. For instatnce German - Autor/Autorin --Smihael (talk) 18:11, 9 November 2015 (UTC)

Support --Pasleim (talk) 21:18, 29 March 2015 (UTC)

Jura, Jared Zimmerman, Tobias1984 Would my proposal above work? Filceolaire (talk) 23:46, 5 May 2015 (UTC)

@Filceolaire: I guess at this point we should just try it out, and see how it goes. --Tobias1984 (talk) 07:45, 6 May 2015 (UTC)

I don't mind another property, why not bother filling in the form as everybody else? --- Jura 11:00, 8 May 2015 (UTC)

But Jura do you agree that the label should be "pevec/pevka" instead of "pevec" since the item refers to both men and women? Not much point in proposing another property unless that happens. Filceolaire (talk) 19:00, 11 May 2015 (UTC)

You need to propose this for the relevant version of Help:Labels. I don't edit in that language.

Personally, I was merely trying to help a user who came for help to Wikidata. Maybe someone else should try to help them, but they probably already lost interest. It really makes this project not look that good. --- Jura 22:52, 11 May 2015 (UTC)

Support --Tchoř (talk) 16:59, 12 June 2015 (UTC)

Support. I think that it's easier for me actor/actress in the label than a new property. Juan Mayordomo (talk) 19:22, 19 June 2015 (UTC)

Support I think this could be useful for things like Reasonator too. I would also support a property for the masculine form so that it can be explicitly stated instead of assuming that the label will always be the masculine form. - Nikki (talk) 14:52, 26 June 2015 (UTC)

Comment it seems that everybody but Filceolaire agrees. Will this be created or do I have to withdraw it? --- Jura 12:45, 4 July 2015 (UTC)
Comment Well, I don't agree. I agree with Filceolaire. His proposal is easiest of doing. Juan Mayordomo (talk) 17:44, 5 July 2015 (UTC)
- Somehow the opposing votes of you guys leave me confused. --- Jura 08:08, 7 July 2015 (UTC)
  - In my first comment I thinked that the text was indented and that I was respondig the comment from Filceolaire "Jura, Jared Zimmerman See what I have done with...". I agree with him. Juan Mayordomo (talk) 22:00, 8 July 2015 (UTC)
Oppose I also prefer the method described by Filceolaire. It is easier to implement and it makes the Wikidata pages more readable than having a property with a value for each of the languages that apply gender difference to words. At least with the label we only see the languages we know, but with properties we see the labels for all the languages. Also, it would be incorrect to hide all the monolingual text properties that are not from our known languages to prevent the kilometric Wikidata pages, because other applications for that label type can make the property relevant even if we don't understand the language in which is written. -- Agabi10 (talk) 00:27, 29 September 2015 (UTC)
- Wikidata isn't really meant to be readable. Otherwise the interface wouldn't look in the way it does. Besides, I didn't come across many wikis using that type of label. Did you? --- Jura 11:15, 29 September 2015 (UTC)
  - Wikidata pages have to be minimally readable because the only way of checking if a property with a value is there is checking it in the Wikidata page. I know it doesn't have to be as readable as a Wikidata page, but adding this property will add a lot of noise to the Wikidata page. Related with the thing of the Wikipedias that takes into account that differences it seems that at least Swedish and Spanish Wikipedias takes this into account, but after adding the property we can't know how many users will create claims for that property even if they are not going to use it on infoboxes. Having, for example, 20 claims for the mail form and another 20 for the female form will create a lot of (for my point of view) irrelevant noise. -- Agabi10 (talk) 11:35, 29 September 2015 (UTC)
    - I understand your point of view. I guess you will just stop adding statements once there are 10 on a page. Personally, I don't think property proposals should attempt to impose linguistic choices to users of languages they ignore. --- Jura 11:43, 29 September 2015 (UTC)
Comment The main label should be gender neutral. This property can only be created simultaneously with the corresponding property for the male form. —putnik 20:54, 7 October 2015 (UTC)
Support We need in Spanish Gender-neutral language. – The preceding unsigned comment was added by ProtoplasmaKid (talk • contribs) at 19:35, 17 October 2015 (UTC).
Oppose. This is linguistic data, part of Wiktionary's domain. This makes no more sense than having properties for "plural", "accusative", or any other pile of grammatical cases. --Yair rand (talk) 13:41, 18 October 2015 (UTC)
Comment The ideal thing should be adding that kind of support into the software having the hability to specify one or more gender specific labels to the elements and being able to access the one we want through infoboxes. Maybe we should suggest that in Phabricator instead of this property here. -- Agabi10 (talk) 14:31, 18 October 2015 (UTC)
- Somewhere the labels will still need to be stored. Unfortunately, Wiktionary can't provide this in a structured way and is unknown to Wikibase. --- Jura 14:48, 18 October 2015 (UTC)
- @Jura1: Yes, I know. What I mean is asking to the developers to make a way to make this known to Wikibase. I think that it can be useful... -- Agabi10 (talk) 15:05, 18 October 2015 (UTC)
Comment Of course Yair rand this is linguistic data, but our infoboxes (most of them, others will follow) use this data and they look now realy unprofessionally. Wikidata is meant to be for all Wikipedias, and we want that our infoboxes look good. We are working hard to make the language in articles look grammatically correct, but would also like to maximize the benefits of Wikidata. The best way for us would be that each occupation (for example: Q177220) should have additonal gender_female property), all languages that use only neutral gender, should ignore this new property. By the way, there's a a lot of languages, that use gramatical genders. And we didn`t loss interests in this problem. We constantly get questions about this problem, and I do not want to exclude "occupation" parameter from our infoboxes. I still hope that somehow this can be solved. --Pinky sl (talk) 14:07, 9 November 2015 (UTC)
Support Currently articles about women on sl:wiki look sexist and very unprofessional. --M11rtinb (talk) 15:12, 9 November 2015 (UTC)
Question I was thinking about this and wouldn't my reasons to vote against this be invalid if the datatype is changed from Monolingual Text to Multilingual Text? I don't know how this new data type is going to be shown in the interface, but it probably is better than a tone of monolinguals text claims... -- Agabi10 (talk) 15:15, 9 November 2015 (UTC)
Weak oppose This is basically linguistic data, not semantic data. We need a more comprehensive solution rather than an awkward band-aid, especially if we ever want the Wikibase software to be able to support Wiktionary. (If we have to use a band-aid in the meantime, I would probably prefer Filceolaire's suggestion.) Kaldari (talk) 23:03, 10 November 2015 (UTC)
en:Gender neutrality in languages with grammatical gender discusses what different languages are doing about this. What comes out there is that there is a particular effort to use gender neutral language in recruitment. This means gender neutral language is particularly used in the names of occupations, often by suffixes - programador/a etc. I can well imagine that there are wikipedians in various languages who are passionately opposed to such linguistic innovations but we still have the option of using 'programador ou programadora' as a label which is surely acceptable. What is not acceptable is to use a label which excludes women when the item explicitly includes women. Such labels are wrong and should be changed. Joe Filceolaire (talk) 10:11, 11 November 2015 (UTC)
- Joe Filceolaire in Spanish Wikipedia we started doing that and what we do is to parse the label of Wikidata to get "programador" when the gender of the person is undefined or male in Wikidata and "programadora" when the gender is defined as female. The problem we have is that most of the changes in the labels to set them in the format "programador/a" were reverted using as an argument that "programador/a" isn't an existing word and that the male usage is the correct one for collectives. I think that without some politic or something about that we're not going to advance that way but the Spanish Wikidata Community is to small and most of people doesn't check the village pump, so what can we do in that situation? -- Agabi10 (talk) 11:45, 11 November 2015 (UTC)
  - Agabi10: So there is one group who wants to use the label as a job title in infoboxes and has a problem because the label is male and another group that insists that the label isn't male; it's collective. I think you best bet is to ammend Help:Label/es to make clear that the label is not collective, it should be singular and should be usable as a gender neutral job title in wikipedia infoboxes. Advertise this change where you can, including to the user who reverted it last time. See if anyone on es:wikipedia is interested in contributing to the discussion. This may even be worth creating a Wikidata:Requests for comment for - in Spanish even! Hope that works for you. Joe Filceolaire (talk) 14:43, 12 November 2015 (UTC)

Support a mixt of both proposal (gender neutral form if exists - as in latin ? - or masculine form/feminine form in the label, and two properties : one for the masculine form, one for the feminine form : Joe Filceolaire : I did what's you are proposing, but I was revert by Andreasmperu (see this discussion. As we didn't want to wait until the problem be fixed in Wikidata, a developer made a patch in French Wikipedia, to transform the masculine label into feminine label when a women is concerned, for occupations. We have to add same scripts for functions and others properties affected. Then for each element affected, we have to fill-in by hand a list with WD label and it's feminine matching form. Others linguistics versions of Wikipedia could do the same, but I think it's a stupid job that each linguistic Wikipedia spend so much times in developing patches to fix the point, and in inputing manually the datas. That's why I think your proposal to accept F/M forms in the label is OK as gender neutral, but as interfaces cannot guess which is the good alias, creating two properties (male and female forms) is convenient and necessary. --La femme de menage (talk) 09:17, 20 November 2015 (UTC)

Support In this discussion I see 3 points against this property. So I split my comment in 3 parts:
1. Adding gender marked items won't work. occupation (P106) should represent field of work and nothing more. Female programmer has exactly the same field of work as male programmer or transgender programmer. Duplicates would make editing Wikidata more difficult. I looked at top 50 items for occupation (P106). 26 of them are gender marked in Russian. All 50 have feminine form, but only 26 are suited for generic usage. Adding claims for other 24 items would require more attention from editor. Also it won't work for transgender people, because each Wikipedia should decide the correct label for infobox according to lexical rules of its language.
2. Building of feminine form should not be done with Lua. Wikipedia is not the only user of Wikidata. An example from real life: Reasonator for Celine Dion in Russian says something like: "feminine male singer, male actor, male sound actor, musician". Both gender and field of work are broken and I can't blame Magnus for that.
3. Integrating Wiktionary into Wikidata won't work either. The list of gender marked labels for usage in Wikipedia differs from what any dictionary provides, at least in Russian.
--Lockal (talk) 21:47, 18 January 2016 (UTC)

@Jura1, Pinky sl, Jklamo, La femme de menage: Done

Models.com ID

Done: Models.com person ID (P2471) (Talk and documentation)

Description	identifier of a model in the Models.com website
Represents	models.com (Q3859883)
Data type	String
Template parameter	Template:Models.com (Q21504459)
Domain	types of items that may bear this property
Allowed values	type of linked items (Q template or text), list or range of allowed values, string pattern...
Example	Alessandra Ambrosio (Q151859) → alessandra-ambrosio
Source	external reference, Wikipedia list article, etc.
Formatter URL	http://models.com/models/$1
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)

Motivation

Widely used--Edoardo88 (talk) 17:42, 18 November 2015 (UTC)

Support Joe Filceolaire (talk) 06:55, 24 November 2015 (UTC)

ACMA Register of Radiocommunications Licences Client Identifier

Done: ACMA Radiocommunications Client Number (P2472) (Talk and documentation)

Description	Identifier of an organisation or person who holds one or more radiocommunications licences within Australia
Data type	String
Domain	organization (Q43229) and human (Q5) where the entity resides within Australia (Q408)
Allowed values	string pattern: \d+
Example	Department of Defence (Q2981744) → 1138015
Source	Register of Radiocommunications Licences
Formatter URL	http://web.acma.gov.au/pls/radcom/client_search.client_lookup?pCLIENT_NO=$1
Robot and gadget jobs	Client IDs can be extracted from the downloadable version of this database and mix-and-match could then be used to allocate clients to Australian organisations and persons

Motivation

The Australian Communications and Media Authority manages radiocommunications licences for organisations and persons within Australia (Q408). This database is the authoritative source of information for the organisations and persons in Australia who hold radiocommunications licenses, the spectrum these entities use, the location of transmitters operated by these entities and further details. By adding this property, Wikidata will have a significantly enhanced understanding of radiocommunications usage and spectrum management within Australia. The link between Wikidata organisations and persons and the ACMA Register of Radiocommunications Licences allows for complex and novel queries to be executed against ACMA records. For example, it would be possible to determine which Australian companies formed between 1970 and 1975 hold a license to use spectrum in the 900-1000MHz range. Another example could be the listing of notable Australian persons who hold an amateur radio license. Dhx1 (talk) 12:27, 22 November 2015 (UTC)

Discussion: Support Joe Filceolaire (talk) 07:02, 24 November 2015 (UTC); Comment Datatype changed to String (from Number). Dhx1 (talk) 13:28, 29 November 2015 (UTC)

Asset of Local Relevance ID

Done: IGPCV ID (P2473) (Talk and documentation)

Description	Cultural property identifier for Property of Local Relevance (Q11910247) in Valencian Community
Represents	Property of Local Relevance (Q11910247)
Data type	String
Template parameter	field "identificador" in ca:Plantilla:Infotaula patrimoni cultural and field "bic" in ca:Plantilla:filera BIC Val
Domain	places: cultural properties in Valencian Community
Allowed values	monuments
Example	Antiguo convento de Nuestra Señora de los Ángeles (Q17621231) -> 46.20.011-006 (register number)
Format and edit filter validation	2 numbers, dot, 2 numbers, dot, 3 numbers, dash, 3 numbers
Source	ca:Portal:Wiki Loves Monuments (ca:Categoria:Llistes de monuments del País Valencià)
Proposed by	KRLS (talk)

Motivation

It would be used to store WLM data that at the moment is not on Wikidata. We want to import the information from ca:Plantilla:Infotaula patrimoni cultural. More examples in ca:Llista de monuments de la Ribera Alta. KRLS (talk) 19:13, 28 November 2015 (UTC)

Discussion

Comment @KRLS: Is there a formatter URL? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:56, 29 November 2015 (UTC)

@Pigsonthewing: There is an official catalogue web (Detalles_brl.asp?IdInmueble=1981, 03.28.043-006), but each "url Id" don't match with the official protection number. Do you recommend to create this property with "url id" and save protection number with inventory number (P217) or any similar property?--KRLS (talk) 23:02, 29 November 2015 (UTC)

Support--Pere prlpz (talk) 11:01, 9 December 2015 (UTC)

CDLI ID

Done: CDLI ID (P2474) (Talk and documentation)

Description	Unique identifier of an object in the Cuneiform Digital Library Initiative
Represents	Cuneiform Digital Library Initiative (Q5194236)
Data type	String
Domain	work of art (Q838948)
Allowed values	P+numbers (Regex: P\d+)
Example	Bassetki Statue (Q4868081) → P216558 Babylonian Map of the World (Q279559) → P365726
Source	http://cdli.ucla.edu/.
Formatter URL	http://cdli.ucla.edu/search/archival_view.php?ObjectID=$1

Motivation

CDLI is a metacatalog. It shows information about pieces of art from the ancient Middle East in several museums including British Museum, National Museum of Iraq, Louvre Mbch331 (talk) 17:56, 29 November 2015 (UTC)

Discussion

Support — Ayack (talk) 11:19, 1 December 2015 (UTC)
Support Runner1928 (talk) 16:02, 2 December 2015 (UTC)
Support. Joe Filceolaire (talk) 01:29, 23 December 2015 (UTC)

NAVA ID

Done: NAVA ID (P2475) (Talk and documentation)

Description	identifier of a work, in the National Audiovisual Archive of Hungary
Represents	National Audiovisual Archive of Hungary (Q1213600)
Data type	String
Template parameter	`\|NAVA=` in hu:Sablon:Film infobox
Domain	film (Q11424), broadcasting program (Q19968906)
Allowed values	\d+(_\d\d\d\d)?
Example	Dögkeselyű (Q987167) → 1472388
Source	http://nava.hu/
Formatter URL	http://nava.hu/id/$1

Motivation

Used in Hungarian Wikipedia. NAVA is a state-supported audiovisual archive with a large library of legal deposits of original content by terrestrial stations. Máté (talk) 05:57, 30 November 2015 (UTC)

Discussion

Support Runner1928 (talk) 16:02, 2 December 2015 (UTC)

HNI person identifier

Done: HNI person/institution ID (P2476) (Talk and documentation)

Description	identifier for a person or organization in the database of Het Nieuwe Instituut
Represents	Nieuwe Instituut (Q20888634)
Data type	String
Domain	humans
Example	Rem Koolhaas (Q232364) → 43397abb-0a7f-5fd7-b5af-995192519b19
Source	http://zoeken.hetnieuweinstituut.nl/en/persons/
Formatter URL	http://zoeken.hetnieuweinstituut.nl/en/persons/detail/$1
Robot and gadget jobs	mix'n'match

Motivation

12.000± persons, including a lot of (Dutch) architects. Organizations are in the same "namespace", but need a seperate property imo. Sjoerd de Bruin (talk) 10:40, 1 December 2015 (UTC)

Discussion

Support, but I think since organizations would use the same formatter URL, there is no point in separating the two properties (see AGORHA person/institution ID (P2342) - Máté (talk) 11:04, 1 December 2015 (UTC)
- It's only annoying when you want to use constraints. Sjoerd de Bruin (talk) 11:38, 2 December 2015 (UTC)
Support — Ayack (talk) 11:17, 1 December 2015 (UTC)
Support I'm with Máté on this one. It's anoying, but that's how they implemented it. Multichill (talk) 22:23, 4 December 2015 (UTC)
Comment Sjoerd de Bruin the Template:Constraint:Type template allows multiple classes in a constraint, so it could be for example human (Q5) and organization (Q43229) as the allowed types for items with this property. I don't see it as a problem; if there seems to be a consensus please update the property proposal label and domain to indicate it covers both. ArthurPSmith (talk) 19:17, 7 January 2016 (UTC)

TBRC Resource ID

Done: BDRC Resource ID (P2477) (Talk and documentation)

Description	Unique identifier from the Tibetan Buddhist Resource Center online database and digital library.
Represents	Buddhist Digital Resource Center (Q17033622)
Data type	String
Domain	Persons (authors and historical personages), Locations, Institutions, Works (publications or manuscripts) and Topics - particularly in or from Tibet and surrounding regions.
Allowed values	type of linked items (Q template or text), list or range of allowed values, string pattern...
Example	Tenzin Gyatso (Q17293) → P1649 Tsurphu Monastery (Q927302) → G33 Prajnaparamita (Q751147) → T2005
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	http://tbrc.org/public?query=index
Formatter URL	http://www.tbrc.org/#!rid=$1

Motivation

The Tibetan Buddhist Resource Center (TBRC) database has unique identifiers (RID) for persons, places, documents, and institutions - particularly in Tibet and surrounding regions (Bhutan, Neepal, Sikkim, Mongolia, Ladakh etc.) - an area poorly covered by other authority control resources. (Note: TBRC Public Data Interface gives details of many types of queries which can be done on the TBRC database.) – The preceding unsigned comment was added by CFynn (talk • contribs).

Discussion

Support Runner1928 (talk) 16:02, 2 December 2015 (UTC)

Railways Archive event ID

Done: Railways Archive event ID (P2478) (Talk and documentation)

Description	Event ID in the Railways Archive database
Data type	String
Template parameter	none known
Domain	occurrence (Q1190554) - specifically railway accidents and incidents (probably mainly signal passed at danger (Q2811650) and train wreck (Q1078765)) in the British Isles (UK, Ireland, Isle of Man, Channel Islands) or Channel Tunnel.
Example	Opening of the Liverpool and Manchester Railway (Q7096523) → 1 2015 Wootton Bassett rail incident (Q19815417) → 9130
Format and edit filter validation	1 or more digits, the current maximum is 4 digits (9163) but numbering is sequential so 5 digits will be used in future.
Source	external reference
Formatter URL	http://www.railwaysarchive.co.uk/eventsummary.php?eventID=$1
Robot and gadget jobs	unknown

Motivation

The Railways Archive is an online archive of primary source documents (e.g. accident reports) and news stories relating to railway accidents and incidents in the British Isles (it also covers things like legislation not relevant to events). The standard of inclusion is much lower than Wikipedia's so there is a guarantee that any notable event on Wikipedia will have an entry, although updates are sometimes periodic (circa monthly) rather than instantaneous. Thryduulf (talk: local | en.wp | en.wikt) 04:08, 3 December 2015 (UTC)

Discussion

Support. Joe Filceolaire (talk) 01:33, 23 December 2015 (UTC)

SPDX identifier

Done: SPDX license ID (P2479) (Talk and documentation)

Description	SPDX license identifier
Represents	Software Package Data Exchange (Q2297620)
Data type	String
Template parameter	license-name property of MediaWiki's extension.json
Domain	items representing different licenses
Allowed values	See list of identifiers at https://spdx.org/licenses/
Example	GNU General Public License, version 2.0 (Q10513450) → GPL-2.0 GNU General Public License, version 3.0 (Q10513445) → GPL-3.0
Source	external reference, Wikipedia list article, etc.
Formatter URL	https://spdx.org/licenses/$1.html
Robot and gadget jobs	Legobot will add this property when ready

Motivation

MediaWiki and quite a few other projects have adopted SPDX license identifiers (see e.g. Special:Version). This will make it easy to go from the machine readable identifier to the Wikidata item. Legoktm (talk) 05:55, 5 December 2015 (UTC)

Discussion

IHO Hydrographic Dictionary (S-32)

Done: IHO Hydrographic Dictionary (S-32) Number (P2480) (Talk and documentation)

Description	hydrographic dictionary issued by International Hydrographic Organization
Represents	IHO Hydrographic Dictionary S-32 (Q21683228)
Data type	String
Allowed values	4 digits
Example	lighthouse (Q39715) → 2822
Source	http://www.iho.int/iho_pubs/standard/S-32/S-32-eng.pdf

Motivation

Official hydrographic dictionary of the world.--Kopiersperre (talk) 19:56, 7 December 2015 (UTC)

Discussion

Comment Datatype changed to "string". Is there a formatter URL? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:13, 10 December 2015 (UTC)
- There doesn't seem to be one as I get the idea that the source in the template is the actual dictionary. Mbch331 (talk) 11:59, 11 December 2015 (UTC)

Eliteprospects.com player ID

Done: Elite Prospects player ID (P2481) (Talk and documentation)

Description	Ice hockey player ID assigned by Eliteprospects.com
Represents	Elite Prospects (Q15906271)
Data type	String
Domain	human (Q5)
Allowed values	numbers
Example	Sidney Crosby (Q311280) → 6146
Format and edit filter validation	[1-9][0-9]*
Source	Template:Eliteprospects and the template in other language Wikipedias
Formatter URL	http://www.eliteprospects.com/player.php?player=$1

Motivation

Motivation: To be used as a source for player information. In property name, "player" is needed, because there are IDs also for teams, stuff people (coaches etc.), which I'm not currently proposing. And eliteprospects ID template is one of most used sports external link templates (currently it's transcluded on more than 7200 pages). Edgars2007 (talk) 17:38, 10 December 2015 (UTC)

Discussion

SABR ID

Done: SABR person ID (P2482) (Talk and documentation)

Description	identifier of a person in the Society for American Baseball Research database
Represents	Society for American Baseball Research (Q1129964)
Data type	String
Domain	human (Q5)
Example	Babe Ruth (Q213812) → 9dcdd01c
Source	http://sabr.org/
Formatter URL	http://sabr.org/bioproj/person/$1
Robot and gadget jobs	We may be able to crawl and match
Proposed by	Richard Arthur Norton (1958- ) (talk) 04:31, 4 January 2016 (UTC)

Motivation

Baseball related biographies. This is the de facto biographical source of baseball related biographies sanctioned by the MLB. Richard Arthur Norton (1958- ) (talk) 23:54, 12 December 2015 (UTC)

Discussion

Support --Edgars2007 (talk) 18:51, 21 December 2015 (UTC)

NCES District ID

Done: NCES district ID (P2483) (Talk and documentation)

Description	Identifier for a school district in the United States
Data type	String
Domain	school district (Q398141)
Allowed values	numbers
Example	Los Angeles Unified School District (Q1320340) → 0622710
Source	National Center for Education Statistics: Common Core of Data
Formatter URL	https://nces.ed.gov/ccd/districtsearch/district_detail.asp?ID2=$1
Robot and gadget jobs	The dataset of district names, locations, and IDs is freely offered by the National Center for Education Statistics (Q1966994). Perhaps a Mix-N-Match job.

Motivation

What Integrated Postsecondary Education Data System ID (P1771) is for colleges and universities in the United States, this NCES District ID is for primary and secondary education school districts. Both are identifiers from the United States Department of Education and both are used widely to track and study educational institutions. Runner1928 (talk) 22:23, 15 December 2015 (UTC)

Discussion

Comment Datatype changed to "string". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:57, 19 December 2015 (UTC)
Support sounds useful ArthurPSmith (talk) 16:47, 21 December 2015 (UTC)

NCES School ID

Done: NCES school ID (P2484) (Talk and documentation)

Description	Identifier for a school in the United States
Data type	String
Domain	school (Q3914)
Allowed values	numbers
Example	Grafton High School (Q5592543) → 550561002248
Source	National Center for Education Statistics: Common Core of Data
Formatter URL	https://nces.ed.gov/ccd/schoolsearch/school_detail.asp?ID=$1
Robot and gadget jobs	The dataset of school names, locations, and IDs is freely offered by the National Center for Education Statistics (Q1966994). Perhaps a Mix-N-Match job.

Motivation

What Integrated Postsecondary Education Data System ID (P1771) is for colleges and universities in the United States, this NCES School ID is for primary and secondary schools. Both are identifiers from the United States Department of Education and both are used widely to track and study educational institutions. Though the school ID is technically some number prefixed by a school district ID (e.g., school 550561002248 is part of district 5505610), in order to get a formatter URL to work we need to store the full school ID including district ID. Runner1928 (talk) 22:23, 15 December 2015 (UTC)

Discussion

Comment Datatype changed to "string". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:58, 19 December 2015 (UTC)
Support - yes I've noticed that issue with formatter URL's, it would be nice to be able to pull an additional property besides the identifier from the given property into the formatter. Has anybody looked at that? Anyway, this definitely seems useful too thanks. ArthurPSmith (talk) 16:50, 21 December 2015 (UTC)

Fashion Model Directory photographer ID

Done: FMD photographer ID (P2485) (Talk and documentation)

Description	external link to a photographer's profile at the Fashion Model Directory (FMD) website
Represents	The Fashion Model Directory (FMD) (Q963517)
Data type	String
Example	Patrick Demarchelier (Q920752) → patrick-demarchelier
Formatter URL	http://www.fashionmodeldirectory.com/photographers/$1

Motivation

Discussion: Support - Mbch331 (talk) 20:14, 22 December 2015 (UTC)

Fashion Model Directory brand ID

Done: FMD brand ID (P2486) (Talk and documentation)

Description	external link to a brand's profile at the Fashion Model Directory (FMD) website
Represents	The Fashion Model Directory (FMD) (Q963517)
Data type	String
Example	Giorgio Armani (Q635484) → giorgio-armani
Formatter URL	http://www.fashionmodeldirectory.com/brands/$1

Motivation

Discussion: Support - Mbch331 (talk) 20:14, 22 December 2015 (UTC)

Код Дзяржкартгеацэнтра (be) – (Please translate this into English.)

Done: page at website of Belarus Geocenter (P2487) (Talk and documentation)

Description	Код старонкі геаграфічнага аб'екта на сайце Дзяржаўнага цэнтра картографа-геадэзічных матэрыялаў і даных Рэспублікі Беларусь (be) – (Please translate this into English.)
Data type	String
Domain	geographical feature (Q618123)
Allowed values	text
Example	Doŭhaje Lake (Q2493529) → viewfgo/1639 Vidzy (Q934318) → viewate/3035 Minsk-Paŭnočny (Q4295174) → viewrw/537 Minsk-1 Airport (Q1373238) → viewair/5
Source	http://maps.by
Formatter URL	http://maps.by/$1

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

Discussion: Support--Хомелка (talk) 11:11, 24 December 2015 (UTC)

Аб'ект на Глобусе Беларусі (be) – (Please translate this into English.)

Done: Belarus Globe URL (P2488) (Talk and documentation)

Description	ID
Data type	URL
Domain	geographical feature (Q618123)
Allowed values	text
Example	Minsk District (Q1636191) → http://globus.tut.by/_regs/minsk.htm Zaslaŭje (Q200917) → http://globus.tut.by/zaslavl/index.htm Cathedral of the Transfiguration in Zaslaŭje (Q1982859) → http://globus.tut.by/zaslavl/index.htm#church
Source	Template:Belarus Globe (Belarusian Wikipedia (Q877583))

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

Discussion: Support--Хомелка (talk) 11:12, 24 December 2015 (UTC)

Radzima.org ID

Done: Radzima.org ID (P2491) (Talk and documentation)

Description	identifier in the Radzima.org database of landmarks and tourist attractions of Belarus, Lithuania and the Podlasie region of Poland
Represents	radzima.org (Q13027945)
Data type	String
Domain	geographical feature (Q618123)
Allowed values	text
Example	Minsk District (Q1636191) → rayon/minski Zaslaŭje (Q200917) → gorad/zaslaue Cathedral of the Transfiguration in Zaslaŭje (Q1982859) → object/3004
Formatter URL	http://www.radzima.org/be/$1.html

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

Discussion: Support--Хомелка (talk) 11:12, 24 December 2015 (UTC); Comment Please provide a more detailed description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:25, 9 January 2016 (UTC)

Аб'ект на сайце Праваслаўная архітэктура Беларусі (be) – (Please translate this into English.)

Done: hram.by ID (P2489) (Talk and documentation)

Description	Аб'ект на сайце "hram.by" (be) – (Please translate this into English.)
Represents	hram.by (Q15020682)
Data type	String
Domain	temple (Q44539)
Allowed values	numbers
Example	Cathedral of the Transfiguration in Zaslaŭje (Q1982859) → 6
Formatter URL	http://hram.by/churches/view/$1/

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

Discussion: Support--Хомелка (talk) 11:13, 24 December 2015 (UTC)

Старонка на сайце OSTIS Belarus Wiki (be) – (Please translate this into English.)

Done: page at OSTIS Belarus Wiki (P2490) (Talk and documentation)

Description	Старонка аб'екта на сайце OSTIS Belarus Wiki (be) – (Please translate this into English.)
Data type	String
Domain	geographical feature (Q618123)
Allowed values	text
Example	Rakaŭ (Q2500789) → Раков_6220857156
Formatter URL	http://ostisbelarus.sourceforge.net/index.php/$1

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

Discussion: Support--Хомелка (talk) 11:14, 24 December 2015 (UTC)

MTMT author ID

Done: MTMT author ID (P2492) (Talk and documentation)

Description	author's identifier in the Hungarian Scientific Bibliography
Represents	Hungarian Scientific Bibliography (Q1162264)
Data type	String
Template parameter	`\|MTMT=` in hu:Sablon:Személy infobox
Domain	persons
Allowed values	[1-9]\d*
Example	Elemér Hankiss (Q957435) → 10007871
Source	https://vm.mtmt.hu/
Formatter URL	https://vm.mtmt.hu/search/slist.php?AuthorID=$1

Motivation

A rather large scientific bibliography maintained by the Hungarian Academy of Sciences (Q265058). Máté (talk) 22:58, 2 January 2016 (UTC)

Discussion

Support for useful bibliographical data. Josh Baumgartner (talk) 17:28, 11 January 2016 (UTC)

OM institution ID

Done: OM institution ID (P2493) (Talk and documentation)

Description	identifier of primary and secondary schools at the Hungarian Ministry of Education
Represents	Ministry of Human Capacities (Q989266)
Data type	String
Template parameter	`\|om=` in hu:Sablon:Iskola infobox
Domain	school (Q3914)
Allowed values	\d{6}
Example	Varga Katalin Secondary School (Q258909) → 035990
Formatter URL	http://www.oktatas.hu/hivatali_ugyek/kir_intezmenykereso/!Intezmenykereso/Intezmeny/Index/$1
Robot and gadget jobs	import from infobox

Motivation

Widely used ID for schools in Hungary. The linked page of the Education Office contains reliable data on the institutions and also scanned copies of important documents. Máté (talk) 07:26, 3 January 2016 (UTC)

Discussion

Support valid authority control. Josh Baumgartner (talk) 17:24, 11 January 2016 (UTC)

Theatricalia person ID

Done: Theatricalia person ID (P2469) (Talk and documentation)

Domain	people
Allowed values	valid Theatricalia person IDs
Robot and gadget jobs	Theatricalia is an open databse, and has links to Wikipedia, so it should be easy to extract IDs programmatically

Motivation

A sister property to Theatricalia play ID (P1242). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:07, 7 January 2016 (UTC)

Discussion

Done Theatricalia person ID (P2469) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:33, 15 January 2016 (UTC)

Latvian cultural heritage register identifier

Done: Latvian cultural heritage register ID (P2494) (Talk and documentation)

Description	ID of the cultural heritage on http://saraksts.mantojums.lv/
Data type	String
Domain	heritage site (Q358) (Wikidata property for authority control for cultural heritage (Q18618628))
Allowed values	numbers
Example	Cēsis Castle (Q2512369) => 392
Format and edit filter validation	[1-9][0-9]*
Source	http://saraksts.mantojums.lv/, lv:Veidne:Monument, lv:Veidne:VKPAI objekta infokaste
Formatter URL	http://saraksts.mantojums.lv/lv/piemineklu-saraksts/$1/

Motivation

The site http://saraksts.mantojums.lv/ is the official database of the cultural heritage of Latvia, maintained by National Heritage Board of Latvia (Q20566223). Identifiers from this database is actively used in WLM photo contest monuments lists and other places.

Discussion: Support - valid authority control. Voll (talk) 10:11, 13 January 2016 (UTC); Support - it was used in WLM 2015 in Latvia. Lots of pictures in Commons tagged with it. --Papuass (talk) 10:19, 13 January 2016 (UTC); Support. --Edgars2007 (talk) 21:18, 13 January 2016 (UTC)

Latvian toponymic names database identifier

Done: Latvian toponymic names database ID (P2496) (Talk and documentation)

Description	Latvian Geospatial Information Agency geographical names database identifier
Data type	String
Domain	toponym (Q7884789) (Wikidata property for authority control for places (Q19829908))
Allowed values	numbers
Example	Upesciems (Q15219939) → 2814
Format and edit filter validation	[1-9][0-9]*
Source	http://vietvardi.lgia.gov.lv/vv/to_www.sakt?
Formatter URL	http://vietvardi.lgia.gov.lv/vv/to_www_obj.objekts?p_id=$1

Motivation

We specifically need this property to link Latvian Wikipedia geographical objects to the government geographical names database.

Discussion: Support - valid authority control. Voll (talk) 10:12, 13 January 2016 (UTC); Support - used as a reference source for populated places in Latvia for multiple Wikipedias. --Papuass (talk) 10:20, 13 January 2016 (UTC); Support. --Edgars2007 (talk) 21:18, 13 January 2016 (UTC)

Latvian National Address Register identifier

Done: Latvian National Address Register ID (P2497) (Talk and documentation)

Description	National Address Register classifier code (State Land Service of the Republic of Latvia)
Data type	String
Domain	toponym (Q7884789) (Wikidata property for authority control for places (Q19829908))
Allowed values	numbers
Example	Alsunga (Q432829) → 100143987
Format and edit filter validation	\d{9}
Source	https://www.kadastrs.lv/
Formatter URL	https://www.kadastrs.lv/varis/$1

Motivation

We specifically need this property to link Latvian Wikipedia geographical objects to the National Address Register database.

Discussion: Support - valid authority control. Voll (talk) 10:12, 13 January 2016 (UTC); Support - will be useful for future projects. --Papuass (talk) 10:21, 13 January 2016 (UTC); Support. --Edgars2007 (talk) 21:18, 13 January 2016 (UTC)

UNESCO Biosphere Reserve URL

Done: UNESCO Biosphere Reserve URL (P2520) (Talk and documentation)

Description	...
Represents	biosphere reserve (Q158454)
Data type	URL
Domain	biosphere reserve (Q158454)
Allowed values	à déterminer
Example	Fundy Biosphere Reserve (Q3457142) -- > http://www.unesco.org/new/en/natural-sciences/environment/ecological-sciences/biosphere-reserves/europe-north-america/canada/fundy/
Format and edit filter validation	n/a
Source	http://www.unesco.org/mabdb/br/brdir/directory/
Robot and gadget jobs	à déterminer

Motivation

rien à rajouter, @John Cummings: --- Jura 10:58, 23 December 2015 (UTC)

Discussion

Support --- Jura 10:58, 23 December 2015 (UTC)
Oppose Il existe un id unique pour chaque réserve de biosphère? Il me semble qu'il en a pas à ma connaissance. (Ex: Mont Saint-Hilaire. --Fralambert (talk) 00:03, 5 January 2016 (UTC)
- There is according to "Man and the Biosphere reserves" on Meta:WikiProject UNESCO/Data, but https://tools.wmflabs.org/mix-n-match/?mode=catalog_details&catalog=133 uses the entire URL as Id. In that case we might want to go with URL datatype. @John Cummings: can you advise?
  --- Jura 14:04, 5 January 2016 (UTC)
  - Thanks @Jura:, to the best of my knowledge there are no ID numbers for the Biosphere Reserves, simply the name of the site is used, the same is true for other UNESCO programmes e.g Memory of the World Programme and Lists of Intangible Cultural Heritage. Leaving the ID field for the programmes on Meta:WikiProject UNESCO/Data was an error which I've now corrected, very sorry for the mistake. John Cummings (talk) 14:32, 5 January 2016 (UTC)
    - @John Cummings: I had noticed for the later two. We can include full URLs, but it would help if they were fairly stable. So the Geoparks ID below is ok?
      --- Jura 14:56, 5 January 2016 (UTC)
      - @Jura:, all the urls will be stable and the below request looks good to me, let me ping @NavinoEvans: who has done all the work so far on importing things into Mix n' Match and Quickstatements. John Cummings (talk) 15:09, 5 January 2016 (UTC)

@Jura1:, @John Cummings: Yes that's all correct about the biospheres on the MAB program having no ID numbers (although they definitely should!). I imported them into Mix'n'Match with 'fake id' numbers - each item in the catalogue does link to the UNESCO page though because we added individual urls for each item. All looks good with the Geoparks ID below except the formatter URL does seem to need a country included as mentioned in the comments. Will continue discussion there :) NavinoEvans (talk) 02:36, 6 January 2016 (UTC)

Thanks for your feedback. I changed the datatype accordingly.
--- Jura 14:27, 6 January 2016 (UTC)
For me, a property who is not different of reference URL (P854) is useless. If the MaB Program decide one day to create a ID, i would change my opinion. --Fralambert (talk) 01:39, 7 January 2016 (UTC)
- I suppose you mean "described at URL". With the new external identifier property, many string properties will generate an output similar to that. One of the differences between external identifier properties and URL properties will be the entry format. With properties of both types, one can easily select items. Besides, this one is already in use at Mix'n'match.
  --- Jura 10:03, 9 January 2016 (UTC)
Support @Jura1, NavinoEvans, John Cummings: Je viens juste de voir que AlgaeBase URL (P1348) est utilisé comme propriété avec un url. J'enlève donc mon opposition. et je la marque comme prête. Je vais la créer plus tard en soirée ou demain. --Fralambert (talk) 01:28, 19 January 2016 (UTC)
@Jura1, NavinoEvans, John Cummings: Done with UNESCO Biosphere Reserve URL (P2520).

Corrigendum/ Erratum

Done: corrigendum / erratum (P2507) (Talk and documentation)

Description	a published correction
Represents	erratum (Q1348305)
Data type	Item
Domain	article (Q191067)
Example	EVOLUTION IN MENDELIAN POPULATIONS (Q5418627) → Q20746731
Source	journals and repositories
Robot and gadget jobs	probably

Motivation

While most publications contain errors, only a small subset have published errata or corrigenda associated with them. To handle information of the latter kind, I see two main options:

going for a dedicated property specific for errata/ corrigenda
going for a more general property (e.g. "update") that could comprise other things (e.g. retractions) as well.

I have a slight preference for the first option, which also fits with existing rather specific properties like software version identifier (P348) or has edition or translation (P747) . --Daniel Mietchen (talk) 22:06, 2 August 2015 (UTC)

Discussion

Comment @Daniel Mietchen: The range seems to me semantically like a diff (Q300901)  

or a patch in computing, or an amendment in law. If the property is gerenalized I think it must be looked in that direction compared to generalize to "retractations" which seems semantically completely different (that's more like "unpublication") ...

To me a version is not specific to a software and is just an identifier for an edition, so I'm not sure I would agree with the specificity (wrt. domain) of the properties you mention.

I tend to

Support, although I would very well see the properties appliable also in the domain of law and software with a label like "correction" or modification, with a property range like "delta" (diffs, rectification law) ...

The rule would be apply "delta item content" on "an edition of a work" gives "another edition of a work", so I'll very well see a qualifier "resulting edition" on the statements built with this qualifier. That would give

⟨ EVOLUTION IN MENDELIAN POPULATIONS (Q5418627)  

 ⟩ corrected/amended by Search ⟨ Q20746731 ⟩
results in Search ⟨ Evolution in Mendelian Populations (corrected). ⟩

for example. author TomT0m / talk page 09:03, 3 August 2015 (UTC)

I would certainly prefer a diff-based system for consuming information about corrections, but publishers are not there yet, and certainly have not been in the past. So for corrections already published, we'll have to stick with what is proposed above. --Daniel Mietchen (talk) 03:54, 8 August 2015 (UTC)

Daniel any idea about how we could qualify the nature of a specific correction? I remember some cases where a basionym page was not cited or a spelling error was corrected. --Succu (talk) 19:39, 7 August 2015 (UTC)

Haven't made up my mind about this yet, but dug a little deeper and found nothing useful in the Citation Ontology but a few useful pointers in this paper and these guidelines. --Daniel Mietchen (talk) 03:54, 8 August 2015 (UTC)

@Succu: perhaps use main subject (P921) on the corrigenda items, with values like typographical error (Q734832) or fraud (Q28813)? Still looking for a suitable controlled vocabulary but found "As of November 2014 the types of update that are accepted as CrossMark status updates are limited to: addendum, clarification, correction, corrigendum, erratum, expression_of_concern, new_edition, new_version, partial_retraction, removal, retraction, withdrawal" at CrossMark", which seems like a useful basis for discussing which terms we might need here. --Daniel Mietchen (talk) 06:55, 16 August 2015 (UTC)

OK, let's try it.

Support --Succu (talk) 22:05, 22 November 2015 (UTC)

The Source MetaData WikiProject does not exist. Please correct the name. --Daniel Mietchen (talk) 23:03, 19 August 2015 (UTC)

Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:37, 22 November 2015 (UTC)

allcinema film identifier

Done: Allcinema film ID (P2465) (Talk and documentation)

Description	films' IDs on allcinema Movie Database (Q11190174)
Represents	Allcinema (Q11190174)
Data type	Number (not available yet)
Domain	creative work
Allowed values	5 or 6 digit number
Example	Seven Samurai (Q189540) → 87913 Godzilla (Q860461) → 86049 Spirited Away (Q155653) → 163027
Source	Allcinema (Q11190174), http://www.allcinema.net/prog/index2.php, Template:FilmLinks (Q18932457) only when the type parameter is 'allcinema' or '1'.
Formatter URL	http://www.allcinema.net/prog/show_c.php?num_c=$1
Robot and gadget jobs	Sample URL: http://www.allcinema.net/prog/show_c.php?num_c=87913, the id parameter of Template:FilmLinks (Q18932457) only when the type parameter is 'allcinema' or '1'.
Proposed by	ワーナー成増 (talk) 08:22, 12 October 2015 (UTC)

Motivation

About 13,000 movie pages in the Japanese Wikipedia use the allcinema Movie Database using the Template:FilmLinks (Q18932457).ワーナー成増 (talk) 08:22, 12 October 2015 (UTC)

Discussion

Support. Joe Filceolaire (talk) 09:50, 8 November 2015 (UTC)

KINENOTE film ID

Done: KINENOTE film ID (P2508) (Talk and documentation)

Description	identifier of a film, in the KINENOTE movie database
Represents	KINENOTE movie database (Q11296881)
Data type	Number (not available yet)
Domain	creative work
Allowed values	3 - 5 digit number
Example	Seven Samurai (Q189540) → 23967 Godzilla (Q860461) → 24170 Spirited Away (Q155653) → 32651
Source	KINENOTE movie database (Q11296881), http://www.kinenote.com/main/public/home/, Template:FilmLinks (Q18932457) only when the type parameter is 'kinejun' or '2' or '5'.
Formatter URL	http://www.kinenote.com/main/public/cinema/detail.aspx?cinema_id=$1
Robot and gadget jobs	Sample http://www.kinenote.com/main/public/cinema/detail.aspx?cinema_id=23967, the id parameter of Template:FilmLinks (Q18932457) only when the type parameter is 'kinejun' or '2' or '5'.
Proposed by	ワーナー成増 (talk) 15:12, 12 October 2015 (UTC)

Motivation

About 10,000 movie pages in the Japanese Wikipedia use the KINENOTE Movie Database using the Template:FilmLinks (Q18932457).ワーナー成増 (talk) 15:12, 12 October 2015 (UTC)

Discussion

Movie Walker film ID

Done: Movie Walker Press film ID (P2509) (Talk and documentation)

Description	identifier of a films, in the Movie Walker Database
Represents	Movie Walker (Q21093280)
Data type	String
Domain	creative work
Allowed values	prefix(mv) and 5 digit number
Example	Seven Samurai (Q189540) → mv23786 Godzilla (Q860461) → mv23989 Spirited Away (Q155653) → mv32115
Source	http://movie.walkerplus.com/, Template:FilmLinks (Q18932457) only when the type parameter is 'walker' or '8'.
Formatter URL	http://movie.walkerplus.com/$1/
Robot and gadget jobs	Sample http://movie.walkerplus.com/mv23786/, the id parameter of Template:FilmLinks (Q18932457) only when the type parameter is 'walker' or '8'.
Proposed by	ワーナー成増 (talk) 06:11, 13 October 2015 (UTC)

Motivation

About 300 movie pages in the Japanese Wikipedia use the Movie Walker Database using the Template:FilmLinks (Q18932457).ワーナー成増 (talk) 06:11, 13 October 2015 (UTC)

Discussion

Comment I made items for Movie Walker (Q21093280), Japanese Cinema Database (Q21093526) and goo Eiga (Q21093430). --- Jura 16:51, 13 October 2015 (UTC)
- Comment I added properties and values to them a little bit.--ワーナー成増 (talk) 05:05, 23 October 2015 (UTC)
Support. --Marek Koudelka (talk) 17:06, 22 November 2015 (UTC)

National Discography of Italian Song ID

Done: National Discography of Italian Song artist/group ID (P2510) (Talk and documentation)

Description	Artist or music group identity code on the National Discography of Italian Song website
Data type	String
Domain	musical ensemble (Q2088357), musician (Q639669)
Allowed values	numbers
Example	Elio e le Storie Tese (Q988867) → 732
Formatter URL	http://discografia.dds.it/scheda_artista.php?ida=$1

Motivation

Musical website from Ministry of Culture (Q1347047) --★ → A ir on 90 16:31, 13 October 2015 (UTC)

Discussion

Support. Joe Filceolaire (talk) 09:52, 8 November 2015 (UTC)

MSK Gent work PID

Done: MSK Gent work PID (P2511) (Talk and documentation)

Description	Persistent identifier for an artwork from the collection of the Museum of Fine Arts Ghent (MSK) (Q2365880) in Ghent, Belgium
Data type	String
Domain	work (Q386724) and its subclasses
Allowed values	combination of numbers, letters, dashes / example: 1982-E
Example	Fountain with Kneeling Youths (Q21011370) → 1982-E
Source	will be mass imported / added in November 2015 in the context of the project Flemish art collections, Wikidata and Linked Open Data
Formatter URL	http://mskgent.be/collection/work/id/$1
Robot and gadget jobs	will be mass imported / added in November 2015 in the context of the project Flemish art collections, Wikidata and Linked Open Data

Motivation

Unique and persistent identifiers for these artworks. Corresponding URLs provide persistent links to 1) the description page of the artwork on the museum's own website and 2) its image, if available. Several thousands will be mass imported / added to Wikidata in November 2015 in the context of the project Flemish art collections, Wikidata and Linked Open Data -- Spinster (talk) 11:52, 19 October 2015 (UTC)

Discussion

Support. Joe Filceolaire (talk) 09:53, 8 November 2015 (UTC)

spin-offs

Done: has spin-off (P2512) (Talk and documentation)

Description	series' spin-offs
Represents	spin-off (Q1186399)
Data type	Item
Example	All in the Family (Q1048856) → Maude (Q1247562)

Motivation

Useful info. --AmaryllisGardener ^talk 19:32, 30 November 2015 (UTC)

Discussion

Comment This seems to be the inverse of based on (P144). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:20, 5 December 2015 (UTC)
- No I don't think they're related. Based-on is more for a movie based on a book and similar relations, no? Spin-offs are more an extension. --LydiaPintscher (talk) 22:58, 16 January 2016 (UTC)
Support Was looking for this to indicate that NCIS LA is a spin-off of NCIS. --LydiaPintscher (talk) 22:58, 16 January 2016 (UTC)

Jamendo album ID

Done: Jamendo album ID (P2513) (Talk and documentation)

Description	identifier for an album per the Jamendo website
Data type	String
Domain	musical release (Q2031291)
Example	Est! (Q3341139) → 10104
Formatter URL	http://www.jamendo.com/album/$1

Motivation

Jamendo (Q1132897) is a famous repository of open music. ★ → A ir on 90 18:35, 3 December 2015 (UTC)

Discussion

Jamendo artist ID

Done: Jamendo artist ID (P2514) (Talk and documentation)

Description	identifier for an artist per the Jamendo website
Data type	String
Domain	musical release (Q2031291)
Example	Rein (Q1814063) → 336855
Formatter URL	http://www.jamendo.com/artist/$1

Motivation

Jamendo (Q1132897) is a famous repository of open music. ★ → A ir on 90 18:35, 3 December 2015 (UTC)

Discussion

costume designer

Done: costume designer (P2515) (Talk and documentation)

Description	person or organisation who designed the costumes for a film, television programme, etc
Represents	costume designer (Q1323191)
Data type	Item
Template parameter	`\|kostýmy=` in cs:Template:Infobox - film `\|Vestuario=` in es:Template:Ficha de película `\|vestuari=` in ca:Template:infotaula pel·lícula `\|kostiumy=` in pl:Template:Film infobox `\|jelmeztervező=` in hu:Sablon:Film infobox
Domain	film (Q11424), television program (Q15416)
Allowed values	human (Q5)
Example	The Great Gatsby (Q892735) → Catherine Martin (Q436031)
Source	~~infotaula,~~ infoboxes
Proposed by	Jura 07:49, 5 January 2016 (UTC)

Discussion

Comment I filled out some of the missing parts of the proposal and added television program (Q15416) to the domain at 17:17,‎ 5 January 2016 (UTC). – Máté (talk) 18:49, 5 January 2016 (UTC)
Support - Mbch331 (talk) 17:56, 5 January 2016 (UTC)
Support – Máté (talk) 18:44, 5 January 2016 (UTC)
Comment (1) What does "infotaula" mean? (2) Allowed values should include organisations or teams, as well as individuals. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:12, 5 January 2016 (UTC)
- @Pigsonthewing: (1) It means "infobox". Jon Harald Søby (talk) 19:26, 5 January 2016 (UTC)
  - Thank you. Fixed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:43, 5 January 2016 (UTC)
    - Reverted. Don't remove non-English language content. This is not an English language only project.
      --- Jura 07:04, 7 January 2016 (UTC)
      - No Jura1, you haven't reverted my edit. Nor did I remove non-English content. It should also be apparent to anyone that Wikidata uses English as its primary language for community discussions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:16, 7 January 2016 (UTC)
- @Pigsonthewing: (2) Unlike e.g. visual effects, organisations aren't usually credited as the costume designer even if the (lead) costume designer may have an organisation working for them. – Máté (talk) 20:03, 5 January 2016 (UTC)
  - Usually - but not exclusively. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:08, 5 January 2016 (UTC)
    - Can you show me an example? (Blame my choice of words on my English.) The subject item also says it's a person. – Máté (talk) 20:19, 5 January 2016 (UTC)
Don't films have all sorts of production staff that would be useful to have data on? Are we going to have properties for every single type? I think it might make more sense to have a more generic property for these kinds of things. --Yair rand (talk) 19:53, 5 January 2016 (UTC)
- Such as "crew", with a qualifier? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:08, 5 January 2016 (UTC)
- Films have many sort of production staff, but some types are more important, and these more important deserve separate property.
- If costume design has its own item in multiple languages infoboxes and usually has its own film award (including Academy Award for Best Costume Design (Q277536)), it clearly deserves separate property. --Jklamo (talk) 03:13, 6 January 2016 (UTC)
  - I think there is a need for a system in any case. Preferably those with a main billing (Q4911899) receiving their own properties, and the rest of the crew (when notable) listed with the crew property. – Máté (talk) 06:23, 6 January 2016 (UTC)
  So this would mean that since we have directors, screenwriters, producers, EPs, DoPs, editors, composers, and cast covered (along with production and distribution companies), all we need to add is this one for costume designers, one for production designer (Q2962070), one for visual effects supervisor (Q8311), one for casting directors, one for other film crew member (Q17291399), and possibly miscellaneous company credits (equipment, VFX, sound, logistics, etc.). – Máté (talk) 09:53, 14 January 2016 (UTC)
Support --Jklamo (talk) 03:13, 6 January 2016 (UTC)
Support --Kolja21 (talk) 04:04, 6 January 2016 (UTC)

Scope.dk film ID

Done: Scope.dk film ID (P2518) (Talk and documentation)

Template parameter	"scope" in da:Skabelon:Infoboks film; da:Skabelon:Scope titel
Domain	films
Source	da:Skabelon:Infoboks film, da:Skabelon:Scope titel
Robot and gadget jobs	My bot can import values from dawiki

Motivation

This is a big Danish film database for Danish and international films and film people, that is linked extensively in the Danish Wikipedia. Jon Harald Søby (talk) 15:30, 5 January 2016 (UTC)

Discussion

Support - Mbch331 (talk) 17:56, 5 January 2016 (UTC)

@Jon Harald Søby, Mbch331: Done Scope.dk film ID (P2518) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:20, 18 January 2016 (UTC)

Scope.dk person ID

Done: Scope.dk person ID (P2519) (Talk and documentation)

Template parameter	da:Skabelon:Scope navn
Domain	people
Source	da:Skabelon:Scope navn
Robot and gadget jobs	My bot can import values from dawiki

Motivation

This is a big Danish film database for Danish and international films and film people, that is linked extensively in the Danish Wikipedia. Jon Harald Søby (talk) 15:30, 5 January 2016 (UTC)

Discussion

Support - Mbch331 (talk) 17:57, 5 January 2016 (UTC)

@Jon Harald Søby, Mbch331: Done Scope.dk person ID (P2519) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:28, 18 January 2016 (UTC)

commentary on

Withdrawn

Description	...
Data type	Item
Domain	commentary (Q1749541)
Example	Rashi's commentary on Exodus (Q21955236) → Exodus (Q9190)

Motivation

We need a property to associate commentaries with the works that they're commentaries on. --Yair rand (talk) 23:26, 3 January 2016 (UTC)

Discussion

Question Let's try to give it some thought before posting here. How would that be different from the commnentaries main subject ?
--- Jura 05:56, 4 January 2016 (UTC)
@Jura1: So, after spending some time trying to think of commentaries that have a sufficiently different/more specific main subject than the target work, I've come to the conclusion that it doesn't make a difference. Main subject can have multiple values, and the one that's a work is pretty clearly the target of the commentary given instance of (P31) commentary (Q1749541), making the existing property adequate. Proposal Withdrawn. --Yair rand (talk) 22:53, 7 January 2016 (UTC)

ComLaw Identifier

Done: ComLaw ID (P2461) (Talk and documentation)

Domain	act of parliament (Q1076579), regulation (Q428148) and bill (Q686822) where the document is in relation to laws of the Commonwealth of Australia (Q408)
Robot and gadget jobs	The ComLaw website could be scraped for a list of all documents with a ComLaw Identifier, then mix-and-match used to match up with legislation (for example, legislation listed at en:Category:Acts_of_the_Parliament_of_Australia)

Motivation

ComLaw is the Australian-government operated website containing a database and full text of acts, bills, regulations and similar documents of the Commonwealth of Australia (federal government). This property would significantly enhance the ability to use Commonwealth of Australia legislation as references in other Wikidata items, and would significantly enhance Wikidata's coverage of Australian law (for example, by cross-referencing the votes of members of parliament with bills). Dhx1 (talk) 08:41, 22 November 2015 (UTC)

Discussion: Support --Pasleim (talk) 10:33, 26 November 2015 (UTC)

@Dhx1, Pasleim: Done ComLaw ID (P2461) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:00, 8 January 2016 (UTC)

judicial sentence

Done: no label (P2466) (Talk and documentation)

Description	prison sentence or other criminal penalty given to subject following criminal or civil conviction
Represents	sentence (Q1763090)
Data type	Item
Template parameter	"sentence" in en:template:infobox serial killer,
Domain	items with convicted of (P1399)
Allowed values	instance of (P31) or subclass of (P279) punishment (Q186361)
Example	Günter Schabowski (Q57445) → imprisonment (Q841236) qualifier "period of time" 3 year (Q577); Fred West (Q577052) → life imprisonment (Q68676); Trent Hotton (Q7838410) → fine (Q2842797) qualifier "amount" 5000 Australian dollar (Q259502)
Source	external reference, Wikipedia list article, etc.
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)

Motivation

This is necessary for completeness for any criminal or civil conviction. I'm not sure if the "period of time" or "quantity" qualifiers exist yet or if they need to be proposed separately. This will need English aliases "sentence", "criminal penalty", "prison sentence", "jail sentence", "jail time", "fined", and possibly others. The label I've chosen as the primary one may not be the best. Thryduulf (talk: local | en.wp | en.wikt) 15:51, 1 November 2015 (UTC)

It may also need to be applied to items about events which have a perpetrator property (but I can't immediately find one of them). Thryduulf (talk: local | en.wp | en.wikt) 15:55, 1 November 2015 (UTC)
Discussion

Support- Mbch331 (talk) 12:16, 11 December 2015 (UTC)

level above and level below

level above

Done: league level above (P2499) (Talk and documentation)

Description	the league above this sports league
Data type	Item
Template parameter	"hiérarchie+" in fr:Modèle:Infobox Compétition sportive, "κατώτερο_επίπεδο" in el:Πρότυπο:Κουτί πληροφοριών ποδοσφαιρικής περιόδου πρωταθλήματος
Domain	sports league (Q623109)
Allowed values	Q template
Example	Ligue 1 (Q13394) → Ligue 2 (Q217374)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article, etc.
Robot and gadget jobs	Yes

level below

Done: league level below (P2500) (Talk and documentation)

Description	the league below this sports league
Data type	Item
Template parameter	"hiérarchie-" in fr:Modèle:Infobox Compétition sportive, "ανώτερο_επίπεδο" in el:Πρότυπο:Κουτί πληροφοριών ποδοσφαιρικής περιόδου πρωταθλήματος
Domain	sports league (Q623109)
Allowed values	Q template
Example	Ligue 2 (Q217374) → Ligue 1 (Q13394)
Format and edit filter validation	(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source	external reference, Wikipedia list article, etc.
Robot and gadget jobs	Yes

Rewritten as discussion. Joe Filceolaire (talk) 03:19, 23 September 2015 (UTC)

Motivation

Hello. Most leagues in many sports have upper levels. For example, the upper level of Ligue 2 (Q217374) is Ligue 1 (Q13394). It is most useful in seasons. For example, the upper level of 2014–15 Ligue 2 (Q16537500) is 2014–15 Ligue 1 (Q16335962). I couldn't find a property that already exists to add these claims in wikidata pages. You can read Wikidata:Project chat#Properties for lower or upper level?.

Xaris333 (talk) 19:05, 16 August 2015 (UTC)

Discussion

We have participant (P710) to list every team in the league.

We have a bunch of properties to use as qualifiers for each of the columns in the league table - games played, won, drawn, lost; ranking; goals for, against; league points. I think there may be a case for a "promoted to" and a "relegated to" property to use as qualifiers to identify which teams were promoted (and where to). Is that what these properties are for? Can we rename your proposed properties? Joe Filceolaire (talk) 00:19, 26 August 2015 (UTC)

I think "promoted to" and "relegated to" would probably be better. Where regional leagues feed into national leagues there isn't a 1-1 correspondence between leagues, e.g. teams relegated from National League (Q58916) go to either National League North (Q20809656) or National League South (Q20809674) depending on geography. Thryduulf (talk: local | en.wp | en.wikt) 14:51, 27 August 2015 (UTC)

But we can't say that 2014–15 Ligue 2 (Q16537500) promoted to 2014–15 Ligue 1 (Q16335962). 2014–15 Ligue 2 (Q16537500) promoted to 2015–16 Ligue 1 (Q19820211). I want to have properties to show which is the upper and the lower level of a season. Xaris333 (talk) 15:39, 4 September 2015 (UTC)

Xaris333: Now I understand. This is a property to describe the league structure. I had a look at fr:Modèle:Infobox Compétition sportive and I see the info box has three parameters - 'hiérarchie', 'hiérarchie+', and 'hiérarchie-' or series ordinal (P1545), "level above" and "level below". 'Upper level' and 'Lower level' have a slightly different meaning from 'level above' and 'level below' and I think 'level above' and 'level below' are closer to what you are proposing. Can we change the names to that? Joe Filceolaire (talk) 02:49, 5 September 2015 (UTC)

Joe Filceolaire, of course. Xaris333 (talk) 00:02, 23 September 2015 (UTC)

Support as rewritten. Xaris333 can you check the new version matches what you intended. I have deleted the use of this property for league seasons as these are a group of events while this property is for describing leagues i.e. organisations. Joe Filceolaire (talk) 03:19, 23 September 2015 (UTC)

Joe Filceolaire, its ok. Xaris333 (talk) 05:17, 23 September 2015 (UTC)

Comment What we really need is a good way to do ordered sets in Wikidata. That way each league or division could be a part of the set of leagues or divisions, 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:16, 17 November 2015 (UTC)
Support --ComputerHotline (talk) 19:34, 20 November 2015 (UTC)

results

Done: results (P2501) (Talk and documentation)

Description	results
Data type	Item
Example	2015 Schaal Sels (Q19951555) → general classification of the 2015 Coupe Sels (Q20895314)

Motivation

In cycling, I am since few able to fit infoboxes like here and here. My project is now to fit classifications in the corpse of articles : the goal is easy, today contributors must make the same work in their Wikipedia, it is a very big loss of time. In the future, all classification will be entered on Wikidata ans will be displayed in the articles of different Wikipedia, we will truely work together.

I need this property and the property below, as twin properties, to make the link between a race and his classification. When it is a stage race, we have different classification, for the general, for teams, for the best young, for the best sprinter... Once I will get these new properties, I will be able to to on Wikidata the good work, I think I will must wait on Wikipedia to have the program to display a classification. Jérémy-Günther-Heinz Jähnick (talk) 09:24, 7 November 2015 (UTC)

Discussion

Why have a separate page for the results (classification)? Why not just put all this info into the page for the competition? I Oppose this property and I think we should merge the 2015 Schaal Sels (Q19951555) and general classification of the 2015 Coupe Sels (Q20895314) items instead. You can still have an infobox on the wikipedia article with some of the wikidata info and a results table in the same wikipedia article with other info from wikidata. Joe Filceolaire (talk) 16:55, 9 November 2015 (UTC)

Filceolaire : for most races, we have different classification, as you can see here. So we need different pages to do the classifications, it is written in my motivations : When it is a stage race, we have different classification, for the general, for teams, for the best young, for the best sprinter.... I need an unique system, that will must be very easy to fit by lambda users. Few monthes ago, properties for different classification have been refused, and some people says me to have on item by classification, and it is interresting when we have 200 cyclists. I see you use number of points/goals/set scored (P1351), another contributor, Casper Tinan, says me to use points for (P1358). So you should discuss. Jérémy-Günther-Heinz Jähnick (talk) 11:26, 10 November 2015 (UTC)

Jérémy-Günther-Heinz Jähnick. First You use the word "Classification". I think you mean "results". In English 'classification' is about dividing things into classes - youth/sprinters/overall - and since you are discussing both concepts there is a lot of scope for confusion if you use 'classification' when you mean 'results'.

Second: the advantage of putting all the results on one page is that you have the complete results for each participant once so it is possible for other searches - e.g. on a rider - to produce other statistical tables, It's not just usable for this race.

Having said that it is difficult to give the ranking for a competitor in the General competition and their ranking in the youth competition on the same page. I will have a think about that and see if I can suggest a way to do that on one page. Joe Filceolaire (talk) 01:46, 11 November 2015 (UTC)

Filceolaire : I am French, and my English is not very good. I say classification because it is the word who appear on ProCyclingStats, the main website of cycling results. But you can change the word if you want.

On the second point, it must be very easy to fit informations by a lambda user. The use of a gadget and a page by result/classification is the most easy, like ProCyclingStats. Jérémy-Günther-Heinz Jähnick (talk) 09:37, 11 November 2015 (UTC)

'Classification' is a proper English term for what is being described here, and is used in a variety of racing types where results are broken down into a complex variety of stages, disciplines, qualifications, etc. Josh Baumgartner (talk) 23:56, 18 November 2015 (UTC)

Support usefull. A.BourgeoisP (talk) 21:56, 10 November 2015 (UTC)
Support. Jérémy-Günther-Heinz Jähnick I have thought about what you said and tried (and failed) to think of a way to do this on one page and, in the end, decided that separate results pages for each class of competitor is the way to go. I would ask that the English label for this property be changed to "Results". I think we also need a new property to specify what class of competitor each page refers to - men, women, youth, sprinters etc. Would "Class of competitor" work as a property name for that? Joe Filceolaire (talk) 15:34, 14 November 2015 (UTC)

Sorry for the late Filceolaire. For the class of competitors, it is possible to use instance of (P31) with values like classement général par équipe (for teams), classement général du meilleur jeune (for youth), classement général du meilleur sprinteur. The sex is not very important, because a stage race of woman has also classifications for youth, sprinter, climber... This property can be interesting to identify the cyclist who participate at a given races : for exemple, the Paris-Roubaix is for men, the Paris-Roubaix espoirs is for men under 23. Jérémy-Günther-Heinz Jähnick (talk) 11:03, 17 November 2015 (UTC)

Oppose Simply use
⟨ 2015 Schaal Sels (Q19951555)    ⟩ has part(s) (P527) ⟨ general classification of the 2015 Coupe Sels (Q20895314)    ⟩
. Josh Baumgartner (talk) 23:56, 18 November 2015 (UTC)
@Joshbaumgartner: : has part(s) (P527) is already use to list the stages when it is a stage race. Jérémy-Günther-Heinz Jähnick (talk) 18:48, 20 November 2015 (UTC)
- Support @Jérémy-Günther-Heinz Jähnick: Yeah, I see that. Josh Baumgartner (talk) 22:16, 7 December 2015 (UTC)
Support --ComputerHotline (talk) 19:34, 20 November 2015 (UTC)

classification of

Done: classification of race (P2502) (Talk and documentation)

Description	classification of
Data type	Item
Example	general classification of the 2015 Coupe Sels (Q20895314) → 2015 Schaal Sels (Q19951555)

Motivation

See above. Jérémy-Günther-Heinz Jähnick (talk) 09:24, 7 November 2015 (UTC)

Support usefull. A.BourgeoisP (talk) 21:55, 10 November 2015 (UTC)
Oppose ~~Use part of (P361) instead:~~

~~⟨ general classification of the 2015 Coupe Sels (Q20895314)    ⟩ part of (P361) ⟨ 2015 Schaal Sels (Q19951555)    ⟩~~

Josh Baumgartner (talk) 23:51, 18 November 2015 (UTC)

- - Per discussion above, part of (P361) is not ideal, but really this property is not needed. It is just an inverse of the results proposal above. Josh Baumgartner (talk) 22:19, 7 December 2015 (UTC)
    - Template:Pink : in fact, I think I will take another road : I already have general classification of race participants (P2321), then I will have a property for a stage result. So I think I will fill all the classification on the item of the race : if it is a single race classification, I will use general classification of race participants (P2321). If it is a stage race, I will use general classification of race participants (P2321) and the property for stage result on the item of the stage. It will be easier than having an item by classification. Jérémy-Günther-Heinz Jähnick (talk) 09:58, 8 December 2015 (UTC)
Support --ComputerHotline (talk) 19:34, 20 November 2015 (UTC)

victory

Done: victory (P2522) (Talk and documentation)

Description	event(s) won by the subject
Data type	Item
Domain	human (Q5), musical ensemble (Q2088357), sports team (Q12973014), etc.
Allowed values	competition (Q476300)
Example	Verandas Willems 2015 (Q19516702) → 2015 Internationale Wielertrofee Jong Maar Moedig (Q20015948) → 2015 Grand Prix de la ville de Pérenchies (Q20724111) Lance Mackey (Q943556) → 2005 Yukon Quest (Q18579430) ...
Robot and gadget jobs	inverse of winner (P1346)

Motivation

If we are able to list on Wikidata the roster of a cycling team (like other sports), we are not again able to list the victories of a team. It is possible to count thanks to number of wins (P1355), or to define a winner thanks to winner (P1346), we don't have a property that permits to list events that a team wins. The goal is to display a table like in the article Saison 2015 de l'équipe cycliste Verandas Willems, and it will be easy, because dates, countries and winners are entered in the item of the cycling race. I will be the case for the class. road bicycle racing (Q3609), track cycling (Q221635) and cyclo-cross (Q335638) are mentionned in the items of races, so it is OK to make at maximum three tables by article, according to the speciality. Jérémy-Günther-Heinz Jähnick (talk) 10:57, 7 November 2015 (UTC)

Support usefull. A.BourgeoisP (talk) 21:54, 10 November 2015 (UTC)
Oppose Simply an inverse of winner (P1346), no need to have the same data in two places. Josh Baumgartner (talk) 23:59, 18 November 2015 (UTC)
Support --ComputerHotline (talk) 19:34, 20 November 2015 (UTC)
Support I so needed this one that I proposed the same exact property. --Harmonia Amanda (talk) 22:39, 22 December 2015 (UTC)
Support --Ash Crow (talk) 22:41, 22 December 2015 (UTC)
Oppose, per Josh Baumgartner. --Yair rand (talk) 01:15, 23 December 2015 (UTC)
@Jérémy-Günther-Heinz Jähnick, A.BourgeoisP, ComputerHotline, Harmonia Amanda, Ash Crow: Done --Fralambert (talk) 03:31, 20 January 2016 (UTC)

category for recipients of this award

Done: category for recipients of this award (P2517) (Talk and documentation)

Description	link to Wikimedia category for receipients of this award
Data type	Item
Allowed values	Wikimedia category (Q4167836)
Example	Nobel Prize in Physics (Q38104) → Category:Nobel laureates in Physics (Q5838087)
Format and edit filter validation	—
Robot and gadget jobs	—
Proposed by	--ԱշոտՏՆՂ (talk) 11:33, 2 January 2016 (UTC)

Discussion

need for autocategorization--ԱշոտՏՆՂ (talk) 11:33, 2 January 2016 (UTC)

Support Paweł Ziemian (talk) 11:49, 2 January 2016 (UTC)

Theatricalia theatre ID

Done: Theatricalia theatre ID (P2468) (Talk and documentation)

Domain	people
Allowed values	valid Theatricalia theatreIDs
Robot and gadget jobs	Theatricalia is an open databse, and has links to Wikipedia, so it should be easy to extract IDs programmatically

Motivation

A sister property to Theatricalia play ID (P1242). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:37, 7 January 2016 (UTC)

Discussion

Done Theatricalia theatre ID (P2468) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:31, 15 January 2016 (UTC)

Biographical Dictionary of Women

Done: Catalan Biographical Dictionary of Women ID (P2498) (Talk and documentation)

Description	biographical dictionary of Catalan women
Data type	String
Template parameter	`\|id=` in ca:Template:Diccionari Biogràfic de Dones
Domain	see template
Allowed values	see template
Example	Maria Anna Josepha Althann (Q1895642) → 2034
Source	template
Formatter URL	http://dbd.cat/fitxa_biografies.php?id=$1

Motivation

Support --- Jura 08:26, 5 November 2015 (UTC)
- Please provide a valid formatter URL and English-language label and description. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:27, 6 November 2015 (UTC)
  - formatter URL is now provided. English label and description should not be a requirement in a multilinugal project in which everyone - even non english native speakers - are invited to participate. --Pasleim (talk) 00:22, 19 November 2015 (UTC)
    - They are indeed invited, and rightly so; nonetheless, the language in which this page - indeed, this project - is conducted is English. It is clear that Jura possesses workable English skills. Furthermore, the language he used in the proposal submission and his comments on it is English. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:57, 19 November 2015 (UTC)
Comment, for further information, please see the version of the proposal before someone removed content. --- Jura 20:03, 6 November 2015 (UTC)
- No information has been removed from the proposal; however I did fix your formatting errors. I also asked you, above, to provide some missing information. Will you now do so? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:23, 8 November 2015 (UTC)
Comment I moved this to the usual "format of proposal" section. --- Jura 09:02, 18 November 2015 (UTC)
- Not "usual"; usual sections restored. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:12, 18 November 2015 (UTC)
It seems you inserted a section header above my comment. Correcting. --- Jura 18:21, 18 November 2015 (UTC)
- Stop dicking around with the formatting Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:52, 18 November 2015 (UTC)

Discussion

Support --Pasleim (talk) 09:24, 11 November 2015 (UTC)
Oppose due to incomplete proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:50, 17 November 2015 (UTC)

I've added an English label. Will you support now? and Andy please assume good faith.

Jura I have added a description in English. I was surprised there was none in Catalan. Could you create an item for this institution/database - there doesn't seem to be any article about it, not even in the Catalan Wikipedia.

Support. Joe Filceolaire (talk) 00:07, 9 December 2015 (UTC)

As they say on en.Wikipedia, "AGF is not a suicide pact". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:46, 9 December 2015 (UTC)

@Filceolaire:: There was a crossreference there to the template, but someone was trying to be helpful by removing it. (Mais arrêtons de tirer sur l'ambulance). I'm not sure if it's appropriate to the translate the title of the work. Besides, it might not even need one, as fallback should work. --- Jura 13:50, 13 December 2015 (UTC)

Comment The label is unacceptably vague. Now that we have an English-language description, we can see that it should include the word "Catalan". It should also be suffixed "ID". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:46, 9 December 2015 (UTC)

Talouselämän vaikuttajat ID

Done: Talouselämän vaikuttajat ID (P2470) (Talk and documentation)

Template parameter	fi:Malline:Talouselämän vaikuttajat
Domain	people
Allowed values	numbers

Motivation

Used as a source, especially in Finnish Wikipedia; part of the new donation program of Finnish Wikipedia Library branch. Olimar (talk) 12:36, 30 November 2015 (UTC)

Discussion

Datatype changed to "string". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:22, 23 December 2015 (UTC)

@Olimar: Done Talouselämän vaikuttajat ID (P2470) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:51, 17 January 2016 (UTC)

Thank you!--Olimar (talk) 18:28, 17 January 2016 (UTC)

Label in feminine form

Withdrawn

Description	Feminine form for items with gender marked labels (e. g. profession) for infoboxes and descriptions
Data type	Monolingual text
Domain	items with property instance of (P31) with class occupation (Q13516667) or winner (Q18560095) or its subclasses
Example	actor (Q33999) → Русский: актриса , Français : actrice , English: actress

Motivation

Currently it is not possible to correctly use occupation (P106) in Russian and other languages with strongly marked grammatical gender. According to en:Gender neutrality in languages with grammatical gender, a single property for feminine form should be enough to cover most (if not all) of natural languages. --Lockal (talk) 14:55, 18 January 2016 (UTC)

Discussion

This one needs broader community discussion than this location as it broaches on Wiktionary topics as well as general prior disagreement in the community. Consider starting a discussion at WD:PC. --Izno (talk) 17:35, 18 January 2016 (UTC)
It's actually a duplicate of a proposal for which there is already a consensus here. Short term workaround (and probably a simpler solution) is to build the list of labels locally in LUA.
--- Jura 18:34, 18 January 2016 (UTC)

Huh, I expected this to be a duplicate of something, and naming of this property makes it difficult to search for. Setting status to "withdrawn". --Lockal (talk) 20:14, 18 January 2016 (UTC)

Australian Wetlands Database Australian Ramsar site number

Done: Australian Ramsar site ID (P2516) (Talk and documentation)

Description	Identifier of a Ramsar wetland listed in the Australian Wetlands Database managed by the Australian Government Department of the Environment
Represents	wetland (Q170321)
Data type	String
Template parameter	No existing property is known to exist, and no wetland infobox is known to exist. Perhaps en:template:Designation list could be updated
Domain	wetland (Q170321) where located in/on physical feature (P706) = Australian continent (Q3960) (approximation only)
Allowed values	string pattern: \d+
Example	Ginini Flats Wetlands Ramsar Site (Q5563129) → 45
Source	Australian Wetlands Database » Australian Ramsar Wetlands
Formatter URL	http://www.environment.gov.au/cgi-bin/wetlands/ramsardetails.pl?refcode=$1
Robot and gadget jobs	It may be possible to scrape IDs from the database and then import into Wikidata using mix-and-match

Motivation

The Australian Wetlands Database Directory is the authoritative reference managed by the Australian Government Department of the Environment listing important wetland (Q170321)s within Australia (Q408). Numerous Australian wetlands are listed by the Ramsar Convention (Q170170), and this proposed property identifies each Ramsar wetland within Australia. The database contains numerous fields of additional data exist such as location, area, elevation, wetland type, various descriptions and justification for categorisation as an important wetland. Approval of this property would significantly enhance Wikidata's understanding of Australian wetlands (natural environment), and increase understanding of the Ramsar Convention (Q170170). Dhx1 (talk) 11:29, 22 November 2015 (UTC)

Discussion: Support Thryduulf (talk: local | en.wp | en.wikt) 21:34, 22 November 2015 (UTC); Comment Datatype changed from Number to String. Dhx1 (talk) 13:15, 29 November 2015 (UTC)

BugGuide ID

Done: BugGuide taxon ID (P2464) (Talk and documentation)

Represents	BugGuide (Q4986057)
Data type	Number (not available yet)
Domain	Arthropoda (Q1360)
Example	Hermetia illucens (Q285029) → 7646
Format and edit filter validation	4 digits
Formatter URL	http://bugguide.net/node/view/$1

Motivation

American insect enthusiasts database Kopiersperre (talk) 09:23, 14 September 2015 (UTC)

Discussion

Oppose - See Archive. --Succu (talk) 09:50, 14 September 2015 (UTC)
- Succu: I couldn't find an old proposal for this property on that page or anywhere else. I really did look. Have you got a better link? Joe Filceolaire (talk) 23:40, 3 November 2015 (UTC)
  - Look for bugguide ID in Archive/24. --Succu (talk) 07:54, 4 November 2015 (UTC)
    - Found it Wikidata:Property_proposal/Archive/24#bugguide_ID. Don't see what your problem is with this property. Support. Joe Filceolaire (talk) 19:44, 2 December 2015 (UTC)
Support Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:47, 20 November 2015 (UTC)

Done @Kopiersperre, Pigsonthewing: Created as BugGuide taxon ID (P2464). Jon Harald Søby (talk) 12:05, 10 January 2016 (UTC)

personal protective measure against chemical exposure

Not done

Description	appropriate first aid protocol to employ when exposed to a chemical through a certain exposure route
Represents	safety precaution (Q21010924)
Data type	Item
Domain	chemicals or other things that are hazardous to health
Allowed values	subclasses of safety precaution (Q21010924) such as changing clothing daily prior to leaving work (Q21012353)
Example	hafnium (Q1119) → prevention of skin contact with chemical (Q21012344); prevention of eye contact with chemical (Q21012346); skin wash upon contamination (Q21012348); daily skin wash (Q21012349); removal of contaminated clothing (Q21012350); changing clothing daily prior to leaving work (Q21012353); providing eyewash fountains (Q21012354); providing quick drench facilities (Q21012355)
Source	Pocket Guide to Chemical Hazards, published by National Institute for Occupational Safety and Health (Q60346)
Robot and gadget jobs	Part of future mass importation of the Pocket Guide to Chemical Hazards into Wikidata.

Motivation

This is part of a mass importation of data from the Pocket Guide to Chemical Hazards into Wikidata. James Hare (NIOSH) (talk) 19:16, 25 September 2015 (UTC)

Discussion

Weak oppose We already have P940 (P940). Snipre (talk) 01:09, 26 September 2015 (UTC)

Support I think it would be good to have statements like this in addition to P940 (P940). The code is practical information, but we also have to work on Wikidata's ontology. --Tobias1984 (talk) 23:22, 7 October 2015 (UTC)

@Tobias1984, James Hare (NIOSH): My problem with this proposal is the anonymous label of the property: we should be coherent and use one generic property like the one proposed above and delete P940 (P940) or we create specific properties and the one above should include the name of the classification system beside P940 (P940).

Then we have another problem which come in my mind only now: most of the time we have several values from the same source for this kind of properties. Currently this is no link between the different values added as isolated value and when new values are added (new source or updated values) we need external parameters like date or source to be able to group relevant values. Snipre (talk) 11:26, 22 October 2015 (UTC)

The proposal to delete P940 (P940) sounds like a bad joke to me, sorry.

What should be done IMHO is that the text corresponding to a P phrase is displayed. Example: P244 – Keep valves and fittings free from oil and grease.

The newest official version of the texts is available on the UNECE website (PDF). --Leyo 21:05, 3 November 2015 (UTC)

James Is this just P940 (P940) but with item datatype? 'Cause I

Support that. If this information is different from P940 (P940) then which is most up to date/most authoritative (Your hafnium example doesn't have a P940 claim). Joe Filceolaire (talk) 01:30, 4 November 2015 (UTC)

Filceolaire, the publication I have been generating these Wikidata items with does not express personal protective measures in terms of GHS codes. I understand if the preference is to use GHS codes instead. James Hare (NIOSH) (talk) 16:03, 5 November 2015 (UTC)

James What is the status of the NIOSH "pocket guide"? I've had a look at it's web site and it obviously has lots more than just the recommended protective measures but on the bare question of protective measures it obviously overlaps the GHS statments. I'm sure some of the recommended personal protective measures align with GHS codes but has any thought been given to formally aligning these? I assume, from your username, that you are employed by or embedded with the US NIOSH so there must be someone there who knows the answer to these questions. You never know the measures may already be completely harmonised!

There is no reason why we cannot list the protective measures recommended by the 'NIOSH guide' as well as those recommended by the GHS for each chemical. The question is should we list both using this property? That could be messy, especially where one or the other has multiple recommendations, as you would have to check a qualifier to know which recommendation came from which guide. If we use separate properties then the property names would have to make clear which is which - the name proposed above wouldn't do for a NIOSH guide. That would be more appropriate for the GHS recommendations property (i.e. the GHS statement expressed as a series of wikidata statements) as that is backed by international standards, a UN agency and multiple different countries, Or have I misunderstood? Joe Filceolaire (talk) 04:30, 6 November 2015 (UTC)

Joe Filceolaire, I had previously asked the point of contact for the Pocket Guide about its harmonization with the GHS. He was too busy to respond at the time but I have asked him again. James Hare (NIOSH) (talk) 15:40, 6 November 2015 (UTC)

Thanks James. I went looking for a GHS statement for hafnium (Q1119) and found this page [1]. This seems very different from the example above. Are the measures for Hafnium listed above really what is reccommended by the NIOSH guide or are they just typical measures?

Sorry if this discussion seems excessive for one property. Changes I think are appropriate before this property is approved:

Change the name to "personal protective measure against chemical exposure recommended by the NIOSH Pocket guide"
Mark the items for the procedures as <instance of:Personal Protection and Safety code from the NIOSH Pocket Guide to Chemical Hazards> as well as <instance of:personal protection measure> or <instance of:safety measure> as appropriate.

That would be enough for me to vote for approval. Joe Filceolaire (talk) 08:51, 7 November 2015 (UTC)

I support the proposition of Joe Filceolaire for a dedicated property but the property name seems to me a bit too long better something like "NIOSH personal protective measure" and put "personal protective measure against chemical exposure recommended by the NIOSH Pocket guide" as description. All values for this property should be instances of the same class and not shared with other classification values. I am ready to support the creation of the property in these conditions. Snipre (talk) 15:14, 7 November 2015 (UTC)

I guess that works. James Hare (NIOSH) do you agree? Will you do the changes to the proposal above? Joe Filceolaire (talk) 00:22, 8 November 2015 (UTC)

I am not sure branding this as a NIOSH-specific property is useful. We can entertain recommendations from other OSH and industrial hygiene bodies as well. The only aspect specific to NIOSH is the source of information, but we can include that in the references. I understand the tension between this proposed property and the GHS precautionary code field, which documents the same thing but in two different ways (reference to other Wikidata items vs. reference to an external database). If the tension can't be reconciled then I am fine with deferring to the GHS codes, since they represent a global standard. James Hare (NIOSH) (talk) 15:06, 18 November 2015 (UTC)

This is not a problem to have different systems and even for each system different values from different sources. The main problem is to know which system is used: for GHS there is a really clear connection between the H phrases and the P phrases and the P phrases are clearly identified from a predefined list. Normally if you recommend some protective measures you should identify the risks so the question to know if NIOSH has this kind of relation and if this is documented somewhere. If this is not the case, then we have a problem: without a system, you can have different phrases for the same measure and this leads to dozens of items describing the same measures but with minor differences (typically "wash with water", "rince with water", "wash with water and soap", "wash with hot/cold water"). Snipre (talk) 15:42, 18 November 2015 (UTC)

@Tobias1984, James Hare (NIOSH), Filceolaire: Without any new contribution for this proposal, I propose to close it. I think we need a clear system with a predefined list of measures. Without that we will get a list of statements which can't be compared or used from a database point of view. Snipre (talk) 09:59, 14 January 2016 (UTC)

Unit of

Withdrawn

Description	Type of quantity of which the subject is a unit of measure
Represents	unit of measurement (Q47574)
Data type	Item
Domain	Units of measurement
Allowed values	Types of measured quantities, e.g. time (Q11471), length (Q36253), mass (Q11423), etc.
Example	furlong (Q494083) → length (Q36253) fortnight (Q2993680) → time (Q11471)

Motivation

Generally missing property. Especially useful for items with {{Constraint:Units}}. Currently, one must specify all possible units when setting this constraint; with this property, {{Constraint:Units}} could be modified to allow all units with "unit of"=[the desired type of quantity]. Swpb (talk) 17:43, 13 January 2016 (UTC)

Discussion

@Swpb: Sorry but why can't you use instance of (P31):unit of length (Q1978718) to retrieve all units of the same class ? I think your proposal is not clear especially your examples. Snipre (talk) 09:47, 14 January 2016 (UTC)

You could, it's just more awkward. What's wrong with the examples? Furlong is a unit of length, fortnight is a unit of time. Swpb (talk) 13:56, 14 January 2016 (UTC)

@Snipre: This make a direct link beetween the physical quantity (Q107715) and the unit.

Support. author TomT0m / talk page 17:57, 21 January 2016 (UTC)
Comment This is partially covered by measured physical quantity (P111).
--- Jura 13:50, 27 January 2016 (UTC)
Withdrawing per Jura, and adding "unit of" as an alias of measured physical quantity (P111). Swpb (talk) 14:15, 28 January 2016 (UTC)

machine readable notation

Not done

Description	the machine readable notation of a formula
Data type	String
Template parameter	machine readable notation
Domain	formulas
Allowed values	string containing all numbers [0-9], all english letters [a-z][A-Z], simple operators [+,-,*,/] and brackets ()
Example	p = 1/2 v**2 rho for dynamic pressure (Q949674)
Source	science. I'm sure there is a standard for this somewhere.
Robot and gadget jobs	read only, I think

Motivation

I want a field for copy pastable information for formulas somewhere, this gets relevant for formulas like bernoulli's principle which is tedious to copy by hand from the wikipage or for more complicated formulas. 78.52.128.119 10:51, 3 January 2016 (UTC)

Discussion: The problem is that there is many many notations ... usually to parse with a machine we need a grammar or a specification, which one do you intend to use ? author TomT0m / talk page 13:13, 11 January 2016 (UTC); This is a duplicate proposal of Wikidata:Property proposal/Generic#Mathematical formula. (TomT0m (talk • contribs • logs)) --Izno (talk) 13:16, 12 January 2016 (UTC); Not done, duplicate. Snipre (talk) 09:49, 14 January 2016 (UTC)

SEED number

Done: SEED number (P2524) (Talk and documentation)

Domain	Schools in Scotland
Allowed values	numbers
Source	http://www.educationscotland.gov.uk/parentzone/myschool/findaschool/index.asp http://www.gov.scot/Topics/Statistics/Browse/School-Education/Datasets/contactdetails
Robot and gadget jobs	Mixn'Match

Motivation

We have DfE URN (P2253), operated by the UK government but only applied to English/Welsh schools. This is the equivalent for Scotland. Schools in OpenStreetMap colleagues are currently tagging schools with this ID, so having it in Wikidata will allow us to identify matches and tag the OSM objects with their Wikidata ID also. I have not been able to identify a formatter URL. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:31, 11 January 2016 (UTC)

Discussion

Done SEED number (P2524) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:19, 23 January 2016 (UTC)

Ramsar Sites Information Service ID

Done: Ramsar Sites Information Service ID (P2525) (Talk and documentation)

Description	The id ont the Ramsar Sites Information Service of a Ramsar site
Represents	Ramsar site (Q20905436)
Data type	String
Domain	places
Allowed values	/d+
Example	Lake Saint Pierre (Q842881) → 949
Source	référence externe, article de liste de Wikipédia, etc.
Formatter URL	https://rsis.ramsar.org/ris/$1

Motivation

Since we are talk about the Biosphere Reserve and Geopark... Fralambert (talk) 01:31, 7 January 2016 (UTC)

Discussion

Support Dhx1 (talk) 15:13, 19 January 2016 (UTC)
@Dhx1: Done --Fralambert (talk) 22:47, 23 January 2016 (UTC)

National Historic Sites of Canada ID

Done: National Historic Sites of Canada ID (P2526) (Talk and documentation)

Description	the unique identificatoir of a National Historic Sites of Canada on the Directory of Federal Heritage Designations
Represents	national historic site of Canada (Q1568567)
Data type	String
Allowed values	/d+
Example	Rideau Canal (Q651323) → 503
Source	http://www.pc.gc.ca/apps/dfhd/search-recherche_eng.aspx
Formatter URL	http://www.pc.gc.ca/apps/dfhd/page_nhs_eng.aspx?id=$1

Motivation

Not all the national historic site of Canada (Q1568567) are listed on Canadian Register of Historic Places ID (P477). It could be usefull for some place like Canadian National Vimy Memorial (Q2561040) who not seem to be allowed to be on the Canadian Register of Historic Places (Q3456275) Fralambert (talk) 04:25, 12 January 2016 (UTC)

Discussion

Support Dhx1 (talk) 15:14, 19 January 2016 (UTC)

World Database of Protected Areas ID (WDPA ID)

Not done

Description	The ID number used for the site in the World Database of Protected Areas
Data type	String
Domain	Natural sites
Allowed values	Numbers
Example	Loch Maree (Q1310646) → 555541652
Source	Joint UNEP and IUCN project datasets http://www.protectedplanet.net/

Motivation

Protected Planet is a joint project of the UNEP World Conservation Monitoring Centre and IUCN to create a database of all the world's protected natural sites. This property will allow natural sites on Wikidata to be indexed to this database. John Cummings (talk) 11:21, 3 February 2016 (UTC)

Discussion

Question @John Cummings: Loch Maree has three ids 555541652, 95294 and 135095. What's the difference between them? --Succu (talk) 11:43, 3 February 2016 (UTC)

@Succu: Its because the site has three designations, Special Protection Area (Birds Directive), Ramsar Site, Wetland of International Importance and Site of Special Scientific Interest (GB). This would mean that the property would have multiple values on each item each linking to the relevant web page as a reference John Cummings (talk) 13:16, 3 February 2016 (UTC)

@John Cummings: Does protectedplanet use the OpenStreetMap relation ID (P402) for the map?--Kopiersperre (talk) 13:48, 3 February 2016 (UTC)

@Kopiersperre:, no I don't think so (I've looked at several datasets) John Cummings (talk) 14:00, 3 February 2016 (UTC)

But they are using OSM as basemap. How do they mark the right object?--Kopiersperre (talk) 14:24, 3 February 2016 (UTC)

@Kopiersperre: I don't know, I've looked in the spreadsheets and the guidance documents, it would be really really good to link these two things up. It looks like from this Twitter exchange something happened. I can't pretend I know very much about OpenStreetMap, is there some way of getting the list from OSM its self? John Cummings (talk) 17:03, 3 February 2016 (UTC)

Oppose Duplicate of WDPA ID (P809). --Fralambert (talk) 01:24, 4 February 2016 (UTC)

Thanks. John Cummings (talk) 08:57, 4 February 2016 (UTC)

IUCN Protected Areas Category

Not done

Description	protected area management categories classifying protected areas according to their management objectives
Data type	String
Domain	Places
Allowed values	Ia, Ib, II, III, IV, V, VI
Example	Q22569690 → Ia
Source	a number of sources including http://www.iucn.org/about/work/programmes/gpap_home/gpap_quality/gpap_pacategories/ and http://www.protectedplanet.net/
Robot and gadget jobs	Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)

Motivation

An international system for categorising protected areas recognised by national governments and the UN John Cummings (talk) 13:41, 3 February 2016 (UTC)

Discussion: Oppose @John Cummings:: It already covered by IUCN protected areas category (P814). --Fralambert (talk) 01:23, 4 February 2016 (UTC)

Thanks for spotting this, not sure how to withdraw my proposal, does it just get refused or should I delete it? John Cummings (talk) 08:55, 4 February 2016 (UTC)

ČSFD film ID

Done: ČSFD film ID (P2529) (Talk and documentation)

Description	Identifier for a film on the website csfd.cz
Represents	Česko-Slovenská filmová databáze (Q3561957)
Data type	String
Template parameter	Template:CSFD film (Q13361214), Template:Infobox film (Q6171351)
Domain	film (Q11424)
Example	Amélie (Q484048) → 29221
Format and edit filter validation	\d+
Source	http://csfd.cz
Formatter URL	http://www.csfd.cz/film/$1
Robot and gadget jobs	Open task.

Motivation

Add information defined in Template:CSFD film (Q13361214) to wikidata.
Add reference identifier. For Czech films is important source.
Improve film references graph.

Discussion: Support - Mbch331 (talk) 11:53, 25 January 2016 (UTC); Support Matěj Suchánek (talk) 14:25, 25 January 2016 (UTC); Support – Máté (talk) 15:22, 25 January 2016 (UTC); Support --Edgars2007 (talk) 08:15, 3 February 2016 (UTC)

Moment magnitude scale

Done: earthquake magnitude on the moment magnitude scale (P2527) (Talk and documentation)

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

Motivation

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

Support Usefull property. --Fralambert (talk) 23:14, 18 January 2016 (UTC); Support. Thryduulf (talk: local | en.wp | en.wikt) 03:08, 19 January 2016 (UTC); Support Aude (talk) 21:42, 3 February 2016 (UTC)
Discussion

@Simon Villeneuve, Fralambert, Thryduulf, Aude: Done! ArthurPSmith (talk) 21:31, 5 February 2016 (UTC)

Thank you! :) Aude (talk) 22:14, 5 February 2016 (UTC)

Richter magnitude scale

Done: earthquake magnitude on the Richter magnitude scale (P2528) (Talk and documentation)

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

Motivation

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

Support Usefull property. --Fralambert (talk) 23:15, 18 January 2016 (UTC)

Support magnitude is pretty fundamental to earthquakes. Thryduulf (talk: local | en.wp | en.wikt) 03:09, 19 January 2016 (UTC)

General support for having a property for earthquake magnitude, but oppose restricting this to Richter scale measurements. The en:Moment magnitude scale is more commonly and generally used now to measure earthquakes. The scale used could be indicated perhaps with the unit? or a qualifier. Aude (talk) 23:43, 23 January 2016 (UTC)

OK, duh. I see the proposal above for Moment magnitude scale as a separate property. I am ok with two separate properties for each. Aude (talk) 23:44, 23 January 2016 (UTC)

Support Snipre (talk) 21:37, 2 February 2016 (UTC)

Discussion

@Simon Villeneuve, Fralambert, Thryduulf, Aude, Snipre: Done! Wasn't sure how to implement the example with a '<' value though, so I picked a different example. ArthurPSmith (talk) 21:51, 5 February 2016 (UTC)

(Lowest) atmospheric pressure / Niedrigster Atmosphärendruck

Done: lowest atmospheric pressure (P2532) (Talk and documentation)

Description	Lowest atmospheric pressure in millibars (mbar)
Data type	Quantity
Template parameter	See en:Template:Infobox_hurricane: Pressure
Domain	Term — hurricanes/tropical cyclones, winter storms, European windstorms (think Freie Universität Berlin), etc.
Allowed values	Numeric — two-digit, three-digit
Example	Q264, Q187621, Q2110774, Q3045816
Source	HURDAT
Robot and gadget jobs	Manual to avoid human error.
Proposed by	Hurricanefan24 (talk) 13:50, 18 March 2013 (UTC)

Support --Goldzahn (talk) 19:11, 18 March 2013 (UTC)

Wrong data type. Should be deferred until QuantityValue implemented. --EugeneZelenko (talk) 13:41, 19 March 2013 (UTC)

Oppose A property proposal for pressure is proposed seeWikidata:Property_proposal/Term#Pressure. Merge with this one and use qualifier to indicate upper or lower. Snipre (talk) 14:07, 29 April 2013 (UTC)

Support Lowest atmospheric pressure is a measurement of hurricane strength, and so I support having it as a separate property specifically for hurricanes. Sven Manguard Wha? 20:21, 15 June 2013 (UTC)

Support per Sven Manguard. Macadamia1472 (talk) 09:38, 16 October 2013 (UTC)

Support Thryduulf (talk: local | en.wp | en.wikt) 14:33, 13 January 2016 (UTC)

Support needed for en:Template:Infobox_storm etc. and representing such info. Aude (talk) 00:54, 24 January 2016 (UTC)

Seems to be a general consensus on this now and we have the right datatype - @Hurricanefan24, Goldzahn, Sven Manguard, Macadamia1472, Thryduulf, Aude: - Done! ArthurPSmith (talk) 16:38, 8 February 2016 (UTC)

bowling style

Done: bowling style (P2545) (Talk and documentation)

Description	type of bowling employed by a cricketer
Represents	Types of bowlers in cricket (Q7860947)
Data type	Item
Template parameter	"bowling" in en:Template:Infobox cricketer
Domain	cricketers (occupation (P106):cricketer (Q12299841)
Allowed values	instance of (P31) or subclass of (P279):Types of bowlers in cricket (Q7860947)
Example	Sanath Jayasuriya (Q378810) → left-arm orthodox spin (Q1520158)
Source	external reference, Wikipedia list article, etc.
Robot and gadget jobs	import from infoboxes

Motivation

This is the key defining characteristic for cricket bowlers. Not all types have items yet and those that do don't seem well developed, but I will work on this. Thryduulf (talk: local | en.wp | en.wikt) 15:50, 10 November 2015 (UTC)

Discussion

Question Would
⟨ Sanath Jayasuriya (Q378810)    ⟩ position played on team / speciality (P413) ⟨ bowler (Q21479668)    ⟩
uses (P2283) ⟨ left-arm orthodox spin (Q1520158)    ⟩
work? I would be hesitant to have to create numerous 'x style/method' properties for all of the different sports and specialties. Josh Baumgartner (talk) 21:21, 13 November 2015 (UTC)
- That would reflect the "role" parameter in en:Template:Infobox cricketer (which would be one of bowler (Q21479668), "batsman", "wicket-keeper", "all-rounder" or "fielder" - I can't find entries for them immediately), not the type of bowler they are, so I don't think it is adequate here (as having a bowling style is not exclusive to those whose primary role is as a bowler). I can understand the reluctance to have countless properties for all sports but I don't think that will be necessary. I certainly can't think of an equivalent "type/style/method" property required for motorsport, football (soccer), rugby (union or league), archery, or (with lesser confidence) netball, volleyball, basketball, tennis, badminton or table tennis. It wouldn't surprise me if there was something similar with pitchers in baseball, but I don't know that sport well enough to be certain. Thryduulf (talk: local | en.wp | en.wikt) 22:41, 13 November 2015 (UTC)
  - @Thryduulf: Good point, so it seems a 'style' property is needed. I do know that there are baseball pitcher equivalents, as there are for chess players, just to name a couple I am familiar with. What about broadening this to be a general property ('style') that can cover all of these (and any others that come up)? Josh Baumgartner (talk) 22:48, 13 November 2015 (UTC)
    - Hmm, that's not a bad thought. It would need a good label and description crafting, if we want to avoid it being used for things like music genres, artistic movements, etc. "playing style" is my first thought, but I'm not sure I'm happy with that. Thryduulf (talk: local | en.wp | en.wikt) 00:49, 14 November 2015 (UTC)
support Something for which there is a need as it is a basic and standard component of cricket books (eg. Wisden bible) and commentary to describe someone who bowls accordingly. How well it is transportable to other components should not unreasonably delay its creation. — billinghurst sDrewth 06:15, 21 November 2015 (UTC)

sidekick of

Done: sidekick of (P2546) (Talk and documentation)

Description	close companions of fictional character
Represents	sidekick (Q281525)
Data type	Item
Example	Miles "Tails" Prower (Q194135) → Sonic the Hedgehog (Q191626)
Source	external reference

Motivation

I know some will say it's fancruft, but I say it would be nice to list this info. --AmaryllisGardener ^talk 22:55, 8 December 2015 (UTC)

Discussion

I would prefer if it was the other way round, i.e "sidekick of". Some main characters have had a lot of sidekicks and there can be some discussion as to whether a particular minor character was ever acknowledged as a sidekick. Joe Filceolaire (talk) 01:36, 9 December 2015 (UTC)

Good point. I changed it to reflect this. --AmaryllisGardener ^talk 16:31, 10 December 2015 (UTC)

perimeter

Done: perimeter (P2547) (Talk and documentation)

Description	linear distance around the outside of a closed polygon-shaped object
Represents	circumference (Q843905)
Data type	Number (not available yet)
Template parameter	"circumference" in en:Template:Infobox building
Domain	polygon-shaped objects, etc. e.g. buildings, lakes
Allowed values	positive numbers with units of length
Example	Sun (Q525) → 4379000 kilometre (Q828224) Lake Vyrnwy (Q2248798) → 11 mile (Q253276)
Source	external reference, Wikipedia list article, etc.
Robot and gadget jobs	import from infoboxes

Motivation

Although calculable from radius (P2120) for regularly shaped objects this is not always the case and seems to be a key missing property. Thryduulf (talk: local | en.wp | en.wikt) 16:47, 17 November 2015 (UTC)

Discussion

"Perimeter" is a more general term for the length of the edge of a shape. Some definitions restrict "circumference" to circles. Jc3s5h (talk) 21:33, 17 November 2015 (UTC)

@Jc3s5h: That's a good point. I'm happy with this being relabelled as "perimeter" - will it break anything if it is changed above? Thryduulf (talk: local | en.wp | en.wikt) 01:03, 23 November 2015 (UTC)

No; done, and other values adjusted accordingly. For 3D objects like planets, diameter would be more appropriate. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:45, 23 November 2015 (UTC)

Possibly re planets, but I note that en:Sun has separate infobox statements for equatorial radius and equatorial circumference, en:Moon has separate statements for mean radius, equatorial radius, polar radius and circumference. It's outside my area of expertise, but I don't know whether one is simply calculated from the other or whether they are separately measured properties. Diameter is proposed separately above anyway. Thryduulf (talk: local | en.wp | en.wikt) 22:16, 23 November 2015 (UTC)

@Thryduulf: Exactly what is your final objective with this one? It's just that the examples given are ambiguous. Buildings can have various perimeters and lakes change shape. Danrok (talk) 12:44, 24 November 2015 (UTC)

@Danrok: My aim is to be able to represent in wikidata what authors of encyclopaedia articles have decided is the key factual information about article subjects by inclusion in infoboxes. The infoboxes for planets, buildings, lakes and probably other subjects contain a parameter for the perimeter/circumference and as far as I have been able to tell it is not possible currently to represent this in Wikidata. Thryduulf (talk: local | en.wp | en.wikt) 14:32, 24 November 2015 (UTC)

@Thryduulf: The aim of Wikidata is not to simply reproduce what already exists in Wikipedia infoboxes. Why? Because some of the information that exists there is garbage and of no real use. We should be trying to fix that, as has already been done with interwiki links which was a stupendous mess pre-Wikidata. Complex objects can be measured in many different ways. Any property needs to make clear exactly what is being measured and how. For example, look at Eiffel Tower (Q243) and height (P2048) = 324m. This is meaningless and useless as it is. Begs the question, the height of what exactly? Now look here [2] and it all starts to become clear. We need a height to tip property, and others. Otherwise how do we compare heights of buildings? Danrok (talk) 15:25, 24 November 2015 (UTC)

@Danrok: some information may be incorrect, but that does not mean that all of it is or that it is never useful. Where objects have multiple perimeters then qualifiers can be used, e.g. applies to part (P518), and I'm really not sure whhy the absence of a specific height property/qualifier is at all relevant here? Thryduulf (talk: local | en.wp | en.wikt) 15:53, 26 November 2015 (UTC)

Comment to specify how it was calculated, the qualifier "criterion used" could work. --- Jura 11:49, 26 November 2015 (UTC)
Support Wikidata should by no means be trying to calculate this number, but for cases where source material specifies a perimeter value, this is a valid property. When available, a qualifier indicating method of determination would be valuable. Josh Baumgartner (talk) 20:40, 6 January 2016 (UTC)

Strand Orientation

Done: strand orientation (P2548) (Talk and documentation)

Description	Orientation of gene on double stranded DNA molecule
Data type	Item
Domain	gene (Q7187) and sequence annotation (Q19753314)
Allowed values	forward strand (Q22809680) or reverse strand (Q22809711)
Example	type III secretion system chaperone CT_043 (Q21173613) = forward strand (Q22809680)
Source	http://www.ncbi.nlm.nih.gov/gene

Motivation

Wikidata contains genomic start genomic start (P644) and genomic stop genomic end (P645) properties indicating the position of a gene on a DNA molecule (i.e. chromosome/plasmid). To give this statement more context it is import to denote which strand the gene is located on forward strand (Q22809680) or reverse strand (Q22809711). This context will allow gene annotations stored in Wikidata to be displayed accurately on a genome browser. Putmantime (talk) 22:38, 5 February 2016 (UTC) WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

Discussion

Support --Andrawaag (talk) 17:14, 10 February 2016 (UTC)

Tobias1984 I have adjusted the property value to item, created those items, and changed the label to reflect the fact that this applies to any double stranded DNA molecule (i.e. chromosome, plasmid etc...), and genomic was not accurate. Putmantime (talk) 18:56, 16 February 2016 (UTC)

Support Looks good in my opinion. And it is easy to improve on the items once the scope becomes clearer. --Tobias1984 (talk) 21:43, 18 February 2016 (UTC)

Support Obivously. Unless it's already existing in a different way. —Tinm (d) 03:56, 19 February 2016 (UTC)

WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. - Will create tomorrow if no one has any further suggestions. --Tobias1984 (talk) 21:43, 18 February 2016 (UTC)

Done --Tobias1984 (talk) 14:45, 21 February 2016 (UTC)

Italian Senate of the Republic ID

Done: Italian Senate of the Republic ID (P2549) (Talk and documentation)

Description	identifier for incumbent and former senators from the Italian Senate of the Republic
Represents	member of the Senate of the Italian Republic (Q13653224)
Data type	External identifier
Domain	politician (Q82955)
Allowed values	\d+
Example	Emilio Colombo (Q312058) → 638
Source	Senate of the Republic (Q633872)
Formatter URL	http://dati.senato.it/senatore/$1
Robot and gadget jobs	bot updloading

Motivation

See P1341. Epìdosis 19:35, 15 February 2016 (UTC)

Support it seems coherent with previous choices.--Alexmar983 (talk) 02:15, 22 February 2016 (UTC)

Discussion

Recording or performance of

Done: recording or performance of (P2550) (Talk and documentation)

Description	item is a recording or release of this composition
Data type	Item
Domain	items with instance of (P31) of musical release (Q2031291) or its subclasses
Allowed values	items with instance of (P31) of composed musical work (Q207628) or musical form (Q862597) or their subclasses
Example	O Holy Night (Q7073262) => O Holy Night (Q128008)
Proposed by	Sweet kate (talk)

Discussion

In trying to standardize data for Wikidata:WikiProject_Music I'm realizing there needs to be a music equivalent of edition or translation of (P629) in the way Wikidata:WikiProject_Books uses that property. For instance, MusicBrainz distinguishes between the composition itself (at the work level, like O Holy Night here and an individual recorded performance of it, like the single O Holy Night (Q7073262) performed by Ladywell Primary School (Q6470821). Rather than add the composer and lyricist for every single recording of this, they should just link to the primary original composition. Sweet kate (talk) 04:35, 9 December 2014 (UTC)

Comment I´d like to use it more general also for performances or live shows: "recording or performance of". Support--Giftzwerg 88 (talk) 11:29, 9 December 2014 (UTC)

That change is fine with me. Sweet kate (talk) 21:00, 23 December 2014 (UTC)

Support. Filceolaire (talk) 20:35, 7 March 2015 (UTC)
Comment I am in support of a "recording of" property, but how exactly is musical release (Q2031291) being defined here? It seems to be a different usage than what MusicBrainz has. Given that the proposed analogy is to edition or translation of (P629), which apparently mixes text translations with book printings, perhaps in that sense it is appropriate to mix recordings with releases. My preference, though, would be to differentiate a derivative creative/intellectual work from a product issuing. Perhaps this is beyond the scope of this discussion, though. Dancter (talk) 20:14, 11 March 2015 (UTC)
- Dancter an edition or translation of (P629) is not a reprinting of the same text. It is a new derivative work with changes from the previous edition. In the same way the recording of a performance of a piece of music or a play is different from other performances. It has a different arrangement (and arranger) and producer and director. In most cases a theatrical run of a play will be one item and this will be a 'performance' of the play item but sometimes the London and New York productions of the play will be different enough to count as different productions with separate wikidata items. In most cases a series of concerts will be a single item but in some cases (e.g. the Amnesty International series of concerts around the world with different lineups in each country) separate items may be justified. Filceolaire (talk) 22:31, 18 June 2015 (UTC)
  - Perhaps I was mistaking the approved usage of edition or translation of (P629) based on some erroneous instances, but again, in practice there doesn't generally seem to be clear delineations between issuings/publications and works/texts on Wikidata. Using "edition" in yet another sense: although a recorded performance is also a derivative work, it is not an edition of the original piece, nor does it in itself establish a new one. There are many cases in which a different recording or performance of a song is of the same arrangement.

I am somewhat wary of generalizing "recording" to "recording or performance," as in "audio production, regardless of whether a recording was made." Expressing "audio performance of" through a separate property does not add that much complexity, yet would provide for a much cleaner exchange with more mature systems, such as Music Ontology, or even just the MusicBrainz schema. I am definitely not in favor of diluting "performance" in this case beyond "individual audio performance" or even performance (Q35140) in general to other concepts that are performance-related, but not technically performances themselves. Just by the grammar of it, a run of a theatrical production is not the same as a performance of a play, and a leg of a concert tour is not the same as a performance of a concert. Dancter (talk) 01:05, 22 June 2015 (UTC)

@Sweet kate, Giftzwerg 88: any comment on the above? MSGJ (talk) 21:25, 10 June 2015 (UTC)
Comment, Why not to use edition or translation of (P629) for musical albums too? --Infovarius (talk) 09:58, 9 August 2015 (UTC)
- Because a recording of a work is quite significantly different in meaning from an edition of a book... —Tom Morris (talk) 16:18, 27 November 2015 (UTC)
Comment It may be useful to use FRBR terminology, at least for comparison. Literally speaking, "Recording or performance of" seems synonim to "embodiment of" (a manifestation "embodies" an expression). edition or translation of (P629) could be made more general (and precise) by renaming it to "realization of" and then it could be used for music too. Federico Leva (BEIC) (talk) 12:15, 31 December 2015 (UTC)
- A comparison may be useful to the extent that we would be dealing with outside sources and systems that are informed by FRBR, but I think it's a mistake to restrict our vocabulary to WEMI. FRBR, and WEMI in particular, is fairly abstract, and tends to be interpreted in very different ways across different fields. This makes it hard to use it for a well-defined property with a clear domain type and value type. Dancter (talk) 18:45, 5 January 2016 (UTC)

used metre

Done: used metre (P2551) (Talk and documentation)

Description	rhythmic structure of the poetic text
Represents	metre (Q192624)
Data type	Item
Domain	poetic texts
Example	Punica (Q1219433) → dactylic hexameter (Q5254470)

Motivation

Knowing in which meter a poem is written is a useful information! Epìdosis 21:09, 13 December 2015 (UTC)

Discussion

Comment I don't know whether this is adequately treated in other properties, but let me float the idea of thinking about a poem's versification along 2 axes -- literally -- horizontal and vertical. Horizontal being (if I read you correctly) what you're talking about here: meter. Vertical being (usually) rhyme scheme. As an example, the horizontal verse form of a Shakespearean sonnet is "iambic pentameter" ... the vertical verse form is "ABAB CDCD EFEF GG". Why not just have 1 property that says "Shakespearean sonnet"? Because too many poems will not have such a convenient label, but can still be easily described along these 2 axes. Even "Petrarchan sonnet" fails to describe specifically what the rhyme scheme of the sestet is. This 2-axis system may also help discourage editors from saying e.g. "meter=sonnet" (a sonnet is not a meter).
A counter-example might be in lyrics with complex versification, where it might make more sense to think of a stanza as (say) an integrated "A3 B2 B3 A4 C4 D5 C2 D4" rather than horizontal = "3.2.3.4.4.5.2.4" + vertical = "ABBACDCD". (Here, my numerals might mean "feet" or "stresses"; others count syllables -- this would all have to be worked out.)
But a counter-counter to this might be the ease with which it can be seen that (A) horizontal = "XAXA" + vertical = 4.3.4.3" and (B) horizontal = "ABAB" + vertical = 4.3.4.3" can be sung to the same tune (exactly the same meter), even though their rhyme schemes differ.
Finally, I would hesitate to call the vertical property "rhyme scheme", even though this would usually be correct. This is because, for example, sestinas and elegiac couplets have vertical structure, but not rhymes; on the other end, "unrhymed" or "blank" (which would necessarily be legitimate values) are not strictly rhyme schemes. Food for thought. Phil wink (talk) 07:23, 28 December 2015 (UTC)
Support such a property, with English description "poetic metre" or "poetic meter" to avoid ambiguity with other forms of measure. Swpb (talk) 15:17, 1 February 2016 (UTC)

quantitative metrical pattern

Done: quantitative metrical pattern (P2552) (Talk and documentation)

Description	description of a quantitative verse's metric
Represents	metrical pattern (Q3951891)
Data type	String
Domain	items in Category:Metrical feet (Q8622640), in Category:Versus (Q6327904) and Category:Types of verses (Q9165785) (not all)
Allowed values	use only some features (—; ∪; X; \|), each spaced by a blank; starting a new line must be possible
Example	pyrrhic (Q2120090) → ∪ ∪
Source	list of feet (Q18816397) for feet; the single articles for verses

Motivation

Metrical pattern of a feet or a verse is a standard information which might be included in a database. Epìdosis 19:05, 14 December 2015 (UTC)

Discussion

Comment I think this property in insteresting and worthwhile to consider. I suppose that the indication of the metric can be in various ways. In the Danish Wikipedia I have seen the notation "9.9.9.9" for Den yndigste rose er funden (Q21065160), see da:Den yndigste rose er funden. This notation misses the stresses. Is the suggestion for "allowed values" a standard way of defining metric? The vertical bar usually indicates bars in musical notation. — Finn Årup Nielsen (fnielsen) (talk) 12:58, 26 December 2015 (UTC)

@Fnielsen: I intended "|" for caesura (Q247417). About the notation of da.wiki: probably that is not based on quantitative metrics (Q3855709), which was the one I considered ... possibly we could create two properties, one for quantitative metrics and one for accentuate metrics. --Epìdosis 13:25, 26 December 2015 (UTC)

Comment Just to be explicit, I'd call this "quantitative metrical pattern" which, if I'm reading you correctly, is the limited topic you're addressing here. I fear "metrical pattern" will elicit doomed attempts to describe stress, syllable-stress, tonal, and even free verse using your symbols for short, long, anceps, and caesura! Whereas (hopefully) "quantitative metrical pattern" will tell some editors that this property just isn't germane for these types of verse. Other notes (that I'm not an expert on): Do you intend that this property should indicate (A) the underlying meter of a work (or even a line), e.g. "this is written in dactylic hexameter" -- or (B) the rhythmic character of an individual realized line? (I suspect 1 property should not be used for both.) For example, if (A), then the whole Aeneid would have 1 value for this property -- but it would need to include additional symbols (e.g. ∪ ∪ with a single macron over them -- don't know how you'd actually do that). Also if (A) would it be appropriate to have distinct symbols for "anceps" and "brevis in longo"? for required, preferred, allowed, and forbidden caesurae? Whereas if (B) each line would have its own value, 1 of dozens possible, but each position would be certainly defined (e.g. a final syllable would be well and truly either a long or short, despite it occupying a "brevis in longo" position). Finally, my sense is that, even though this appears to be optimized for Greek/Latin verse, this system, once worked out, would probably succeed with other quantitative prosodies, e.g. Sanskrit, Persian, Arabic. Cheers. Phil wink (talk) 06:28, 28 December 2015 (UTC)

@Phil wink: OK for "quantitative metrical pattern". Then, I meant (A), the underlying meter of a work. About additional symbols I found an useful catalogue here. For caesurae, do you have any suggestions? --Epìdosis 18:20, 29 December 2015 (UTC)

Support. I have written up extensive notes at User:Phil wink/Quantitative scansion notes which I hope will lead to productive discussion on how to implement this property. If so, I suggest that such discussion take place on its associated Talk page: User talk:Phil wink/Quantitative scansion notes. Cheers. Phil wink (talk) 05:01, 6 January 2016 (UTC)

in work

Done: in work (P2553) (Talk and documentation)

Description	qualifier of award received (P166) and nominated for (P1411) to specify in which creative work the awarded or nominated creative work appeared causing the nomination/award win
Data type	Item
Allowed values	creative works
Example	For Writing's on the Wall (Q20962306), that was nominated for the Academy Award for Best Original Song (Q112243), this award would be qualified nominee (P2453) => Sam Smith (Q15123969) and in work => Spectre (Q18602670) For Sam Smith (Q15123969), who was nominated for the Academy Award for Best Original Song (Q112243), this award would be qualified for work (P1686) => Writing's on the Wall (Q20962306) and in work => Spectre (Q18602670)
Proposed by	Jobu0101 (talk) 12:20, 15 January 2016 (UTC)

Motivation

When I entered all the nominations of 88th Academy Awards (Q20022969) I stuck at the category Academy Award for Best Original Song (Q112243). Here people are nominated for a song within a film. So for example Sam Smith (Q15123969) was nominated for his work Academy Award for Best Original Song (Q112243) which was played in Spectre (Q18602670). In my opinion it's important to capture in the nomination claim also the film Spectre (Q18602670) but we don't have a qualifier property to do so. It's not enough to enter in Writing's on the Wall (Q20962306) that this song is played in Spectre (Q18602670) because a song could be played in several films. So we really have to put this fact in a qualifier for the nomination. --Jobu0101 (talk) 12:20, 15 January 2016 (UTC)

Discussion

Support. As I pointed already out in the motivation I support my own proposal. --Jobu0101 (talk) 12:27, 15 January 2016 (UTC)
Support. I support the property proposal due to the fact, there is no way to relate a nominated work to the work it is used in by now, although there is a strong relation between that items, for what Writing's on the Wall (Q20962306)/Spectre (Q18602670) is a good example. Queryzo (talk) 17:55, 8 February 2016 (UTC)
Support --LydiaPintscher (talk) 19:11, 23 February 2016 (UTC)