Wikidata

Wikidata:Property proposal/Archive/41

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


This archive page is full. Use Archive/42 or subsequent ones.


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



Wikidata property sample

Descriptionif the sample entity is a property, not an item
Data typeProperty
Domainproperties with datatype property
Examplerelated property (P1659) → father (P22) mother (P25)

Metadata properties

Read this first

If Semantic Web concepts like "range", "domain", "type", "Class", "subClassOf", "Property" and "subPropertyOf" are Chinese to you, I highly recommend reading:

The OWL 2 Primer explains those basic Semantic Web concepts. Once you've read that, use http://www.w3.org/TR/rdf-schema/#ch_properties as a reference for the definitions of "range", "domain", etc.

  • rdf:type and rdfs:subClassOf are probably not very relevant for statements on properties.
  • Range, domain and subproperty of are exceedingly relevant.

There are several more pieces of vocabulary relevant for statements on properties -- e.g. inverse of (owl:inverseOf) -- but I recommend understanding the basic properties first. Familiarity with them is essential for anyone discussing statements on properties. Emw (talk) 13:11, 14 November 2014 (UTC)

Status of metadata support

Statements on properties are now live.

Properties for property domains

Properties used for:

  1. Specifying which items may bear a given property ("property domain")
  2. Specifying which values a given property may be assigned ("property value domain")

Originally proposed

These properties are currently in Wikidata:Property_proposal/Pending/4#Metadata properties, originating from Wikidata:Project_chat/Archive/2013/10#Property_Metadata:

domain

   Not done
Descriptionany resource that has this property is an instance of one or more of those classes. Implements rdfs:domain. Replaces (with slightly different semantics) {{Property documentation}} and {{Constraint:Type}}.
Data typeItem
Template parameterN/A
DomainWikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed valuesitem(s) (or query??) By default, each value assumes relation instance of (P31) to the specified item type or to a subclass of (P279) of it. For other relations, to that class or to a subclass thereof, should be qualified with the sought property, like subclass of (P279).
Examplefather (P22) ==> person (Q215627)
SourceInitially from domain of {{Property documentation}} on the talk page of each property
Robot and gadget jobsInitial creation to be performed by bots using {{Constraint:Type}}.
Proposed byWikidata:Project_chat/Archive/2013/10#Domain
Discussion

Originally requested by User:Filceolaire at Wikidata:Project_chat/Archive/2013/10#Domain: "links to a class-item (an item which subclass of and instance of properties link to)." -- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

Original discussion (Oct 2013)
datatype item
links to a class-item (an item which subclass of and instance of properties link to). The property should (mostly) only be used on items which are an instance of (P31) of items which are subclasses of the class-item specified by this property.
matches the rdfs:domain property Filceolaire (talk) 18:06, 8 October 2013 (UTC)
  Conditional support. I would support storing domain claims only if the semantics matched those of rdfs:domain. This implies constraints that can be leveraged by semantic reasoners to do type inference, as summarized in http://www.ksl.stanford.edu/software/jtp/doc/owl-reasoning.html. These are "strong" constraints. User:Silver_hr made some informative comments on this in W3C standards for property "domain" and "allowed values". Emw (talk) 15:56, 14 October 2013 (UTC)
@Emw : I doubt we can seriously align the semantics to those of owl like that, as we would have to ckeck the consistency of the whole wiki and of the database all the time. I'm pretty sure considering the size and perimeter of the database it would be kind of really hard, and that it would be all the time inconsistent, so anything could be logically deduced ... We need something weaker, and try to achive all ontology consistency and zero constraint violation with the tools we have. TomT0m (talk) 18:05, 14 October 2013 (UTC)
Having the definition of 'domain' match rdfs:domain is independent of how we ensure consistency in the knowledgebase. It simply means that for a property P that has the domain C, "resources denoted by the subjects of triples whose predicate is P are instances of the class C." Whether we want to prevent inconsistent statements though measures in the UI or simply detect inconsistent statements after the fact as we currently do is an independent matter -- we can still use rdfs:domain as the formal definition of 'domain'. Emw (talk) 19:36, 14 October 2013 (UTC)
Formal definitions in owl is useful if we want to prove that the onlogy is consistent and the datas are consistent. If there is inconsistencies, then by en:explosion principle then anything becomes virtually inferable, that makes inferences pretty useless, so we lose the advantages of having strong and well defined semantics. If a kitten can become a mayor, then we can't decently say the range of the mayor property is a subclass of human in those conditions. Or we need to make a special case in the ontology just for that, or to weaken the constraint insanely. That means if we do a owl export of that, the database will have to be badly curated before we actually can use it in a reasoner. TomT0m (talk) 20:23, 14 October 2013 (UTC)
Using rdfs:domain as the definition of domain does not in itself prove that the ontology is consistent. It simply provides one of multiple criteria to show that. Consistency enforcement is a distinct, independent matter, as explained above.
Furthermore, citing exceedingly rare counterexamples as a reason to abandon the idea of property domain and range constraints is in my opinion a red herring. First, we should ask ourselves if such counterexamples are actually valid. Can a kitten be a mayor, or can a horse be a senator? No, they can't -- by default, considering such things to be invalid subjects of properties conventionally restricted to humans is entirely reasonable. It is completely sensible to assert that kittens cannot be mayors. Second, if there is a compelling reason to expand the domain or range of properties beyond their conventional values, then we have a viable option in the case of crazy office holders or other subjects of properties conventionally restricted to humans: expand the domain from human (Q5) to person (Q215627). As described in the Wikipedia article Person, that term is quite the catch-all. Third, the fact that some properties might have unintuitively broad domains and ranges does not negate the fact that other properties actually do have well-defined domains and ranges. The domain of encodes (P688) is subclasses of gene (Q7187), and its range is subclasses of protein (Q8054) or RNA (Q11053). The statement BRCA1 (Q14862218) encodes (P688) kitten (Q147) is always wrong. Emw (talk) 22:05, 14 October 2013 (UTC)
More discussion

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

  Conditional support. As @Emw: mentions, encodes (P688) should have domain gene (Q7187) and range protein (Q8054). But there are hundreds of Wikipedia articles (and therefore Wikidata items) about both the gene (Q7187) and the protein (Q8054), for example BRCA2 DNA repair associated (Q421651). Therefore the property encodes (P688) points to the same item. This happens for many other items where the domain and range are conflated in common language (and in Wikipedia articles). I support Domain, but are we prepared make items on Wikidata separate, even when the domain and range are conflated in Wikipedia (or invent a new semantics of Domain for these cases)? Jefft0 (talk) 13:17, 29 November 2014 (UTC)
Jefft0, we should not diverge from the standard semantics of domain, i.e. rdfs:domain. This property will be an important basis for inference, like instance of (P31) having the semantics of rdf:type and subclass of (P279) having the semantics of rdfs:subClassOf. More specifically, Wikidata's domain property should take the semantics as used in OWL 2 DL, the reference ontology language of the Semantic Web.
Your concern about conflation among relata is warranted. The folks at WikiProject Molecular biology have fortunately already split Wikidata's items about genes from items about their products; see Wikidata_talk:WikiProject_Molecular_biology#Distinguishing_between_genes_and_proteins. But conflation affects other swaths of knowledge -- e.g. infectious diseases are often conflated with their pathogen, and other effects with their causes.
Having a domain property will standard semantics will help reveal these logical issues. It will also make Wikidata more interoperable with the rest of the Semantic Web. Emw (talk) 03:06, 4 December 2014 (UTC)
  •   Comment. Filceolaire, Laddo, TomT0m, Paperoastro, Jefft0, I have changed the proposed property's description from "type(s) of items that may bear this property" to an extremely close paraphrasing of the definition of rdfs:domain: "any resource that has this property is an instance of one or more of those classes". The former definition was vague and could be interpreted as having non-W3C semantics. It's important to align our definitions with the W3C standards to ensure interoperability with the rest of the Semantic Web. Emw (talk) 05:04, 19 December 2014 (UTC)
Ivan, could you please link to where {{Constraint:Type|class=Q8054|relation=subclass}} is used? I am inclined to answer "yes" to your question, but I want to verify that example. Thanks, Emw (talk) 05:38, 19 December 2014 (UTC)
Property talk:P375, Property talk:P121, Property talk:P128, Property talk:P186, ... — Ivan A. Krestinin (talk) 13:00, 21 December 2014 (UTC)
  •   Support the second definition. Paperoastro (talk) 12:15, 21 December 2014 (UTC)
  •   Oppose  Oppose Ontotext's experience with large LOD datasets shows that the semantics of rdfs:domain and rdfs:range are often useless and even dangerous, because they propagate wrongly applied properties into wrong types.
    • The "infer" semantics of these properties is surprising to most people (anyone with an OO background), who expect a "constraint" semantics.
    • That's the reason why schema.org has NOT adopted rdfs:domain and rdfs:range but weaker schema:domainIncludes and schema:rangeIncludes. Please read "The decision to allow multiple domains and ranges was purely pragmatic" on that page and reflect upon it! schema.org is a large ontology, supported by all search engines, and has a good class hierarchy and good props.
    • Wikidata has good props (due to strong editorial process) but horrible class hierarchy. Don't exacerbate this problem by inferring types from property assertions! Let's first look at how can we fix the class hierarchy.
    • "is an instance of one or more of those classes" doesn't work with rdfs:domain&range, because rdfs:domain=class1,class2 infers both classes as type of object. Eg on dbpedia mapping wiki, someone said that the domain of firstAscentYear is Peak,Volcano (meaning either peak or volcano). But now every ascended thing becomes BOTH a peak and a volcano :-(
    • The DBpedia ObjectProperty extractor doesn't pay attention to declared domain/range of properties (so on DBpedia these are "wishful thinking" really). So if you apply domain/range reasoning, you'll mis-type all kinds of objects.
    • @Emw: in conclusion, don't use rdfs:domain and rdfs:range, use the weaker schema:domainIncludes and schema:rangeIncludes. --Vladimir Alexiev (talk)
  •   Support Sorry but can we put the philosophical discussion for later ? Right now we need a way to look for set od properties useful to describe one item and we can't do that: specific projects handles lists of properties with all update problems. I want to be able to filter properties tables like this one using one or several domains criteria. So let's go with this property. Snipre (talk) 11:45, 23 December 2014 (UTC)
  •   Oppose if this property does not support constructions like class1 or class2. We have too many multitype properties like IMDb ID (P345) already. — Ivan A. Krestinin (talk) 19:37, 23 December 2014 (UTC)
  • I still   Support this proerty but I agree with Vladimir Alexiev that it should be based on the schema:DomainIncludes rather than rdfs:domian. Filceolaire (talk) 23:47, 28 December 2014 (UTC)
  • I would support starting with a "weak" property meaning "only items that are instances of at least one of the classes indicated here can have this property". So really a straightforward replacement for Template:Constraint:Type|relation=instance (not sure for |relation = subclass).
    As for rdfs domain, am not opposed to creating it as a second, separate property, but I am not convinced it is really enforceable in Wikidata.
    I am inclined to think those properties would be mostly useful as maintenance tools (sanity checks, add missing p31..) than for inferrence. "property:father domain:person" might tell us that everything with a father is a person, but I do not quite see the point of knowing that given that anyhow any item with a father statement should also be marked as an instance of person through P31 and P279.--Zolo (talk) 22:22, 29 December 2014 (UTC)

range

   Not done
Descriptionthe values of this property are instances of one or more of those classes. Implements W3C rdfs:range. Replaces (and uses different semantics from) allowed values of {{Property documentation}} and {{Constraint:Value type}}.
Data typeitem (or query?)-invalid datatype (not in Module:i18n/datatype)
Template parameterN/A
DomainWikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed valuesitem(s) (or query??). By default, each value assumes relation instance of (P31) to the specified item type or to a subclass of (P279) of it. For other relations, to that class or to a subclass thereof, should be qualified with the sought property, like subclass of (P279).
Examplefather (P22) ==> human (Q5) qualified with sex or gender (P21)==>male (Q6581097)
SourceInitially from allowed values of {{Property documentation}} on the talk page of each property
Robot and gadget jobsInitial creation to be performed by bots using {{Constraint:Value type}} and {{Constraint:One of}}.
Proposed by-- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)
Discussion

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

Name changed from Value Item Domain because this is defining the Range of Items this property can link to. Wording changed so this can only be used to link to a class from which corresponds to the items which are acceptable values for this Property, as rdf:range. Filceolaire (talk) 22:23, 17 November 2014 (UTC)
  • I have changed this proposed property's label from 'Item Value Range' to 'range', for simplicity, parallelism with domain, and emphasis of grounding in standard Semantic Web vocabulary. Emw (talk) 03:13, 4 December 2014 (UTC)
I have now also changed the property's description to align with that from the W3C's definition of rdfs:range. This is the definition the rest of the Semantic Web uses; we should do the same. LaddΩ, please let me know if you disagree. Emw (talk) 02:26, 19 December 2014 (UTC)
@Emw: Fair with me, you guys know way better how to best describe these concepts. -- LaddΩ chat ;) 03:24, 19 December 2014 (UTC)
I've tweaked the description again to use an extremely close paraphrasing of the definition of rdfs:range: "the values of this property are instances of one or more of those classes". This change is purely syntactic and intended to make for easier reading and interpretation, while retaining the semantics of rdfs:range. Emw (talk) 05:08, 19 December 2014 (UTC)
Constraints declared in statements on properties will not be enforced in Wikibase. I think that's wise; hard constraints are not a good idea at this phase in Wikidata's development. Domain and range are fundamental properties used throughout the Semantic Web. Bots and other tools can be built as we make statements about domain and range. Let's not wait another 6 months, let's create this property soon. Emw (talk) 19:41, 7 December 2014 (UTC)
We don't need to have these constraints used in the Wikibase system but I don't want to use template in the talk page and statements to define constraints: only one place should be used to describe the constraints and to feed the constraint checking bots. Snipre (talk) 15:05, 9 December 2014 (UTC)
Snipre, I agree. Statements on properties involving metaproperties like range, domain, inverse of, etc. would be the sole place for such constraints. In time, they would replace the system of templates currently used in property talk pages. But we need to create these properties first. Emw (talk) 01:21, 10 December 2014 (UTC)
@Snipre: Could you provide link to the system discussion, definition, roadmap or something else? — Ivan A. Krestinin (talk) 20:25, 12 December 2014 (UTC)
@Ivan A. Krestinin: Better ask for Lydia. The only thing I have is this comment from her.
Emw No. If there is no use, no creation. We should wait until we see the final system in order to create the correct and most appropriate properties. I don't want to have to modify and to delete an bunch of statements which were bad used. Snipre (talk) 07:41, 13 December 2014 (UTC)
Snipre, again, constraints declared in statements on properties will not be enforced in Wikibase, per the Wikidata development plan. The development plan comes from Lydia. The reason statements on properties exist is to replace the hackish Property Talk page templates with content on the Property page itself. Range is a fundamental property used throughout the Semantic Web in precisely the way it is being proposed here. This is "the correct and most appropriate" property for what is being proposed here. Bot implementers and third parties using RDF exports cannot being work with this property until it is created. Waiting "until we see the final system in order" is putting the horse before the cart. If you have some reason to object to using range as defined in W3C standards (which is what is being proposed here) then please outline that. Otherwise, we should move forward and create this property.
Ivan, Innocent bystander, Tobias, Zolo, others, could you please weigh in here, preferably including a concrete 'Support' or 'Oppose' vote with any explanation? I do not want to let this proposal languish for months. Let's decide to create it or not. If not, let's come up with things we need from the Wikidata development team in order to use this most basic of properties. I for one think we should get on with it and create this property for the reasons described above. Emw (talk) 02:38, 19 December 2014 (UTC)
As for me the property is useless without other properties described in #Originally proposed section below. Also current suggestion mixes different relations: {{Constraint:Value type|relation=instance}}, {{Constraint:Value type|relation=subclass}}, {{Constraint:One of}}. I think we need concertize the property meaning. — Ivan A. Krestinin (talk) 05:03, 19 December 2014 (UTC)
Emw If you read my comment you will see that I never speak about constraints enforced in Wikibase. Before any creation we have to have a good idea about what we will have at the end. First from the comment of Lydia I pointed it seems that a group of students is working on the constraints. Do you know that thing ? For me this is not clear so first we have to clarify that thing. Then if we create this property statements is it planned with the current bot to migrate from the current system using the talk page templates to the new statements system ? I am not against this property I just want a clear technical solution with the implication of all persons using these constraints. I want to avoid a mixture of systems, I want to be able to delete the talk page templates when I create the corresponding statements about the constraints. I don't want to see statements about constraints AND talk page templates at the same time because the next time we will have to change a constraint we have to know where we have to change it. Is my position clear now ? Snipre (talk) 10:03, 19 December 2014 (UTC)
I know about the student group, but I do not see any activity of this group, no planes, no declarations, no roadmaps. So I think about current system migration from templates on talk pages to properties. This migration requires a number of new properties. But I want to avoid properties duplication. So created properties must be usable for constraints checks too. Now we already have some duplication: allowed values of {{Property documentation}} is duplicate class parameter of {{Constraint:Value type}} and values of {{Constraint:One of}}. This duplication present because allowed values is not defined enough. Relation between it and property values can be instance, subclass, value list or another. Will new domain property be bad defined too? — Ivan A. Krestinin (talk) 22:19, 19 December 2014 (UTC)
  Support I see no harm in creating this and seeing where it leads us. Can't be more concrete at the moment, as I have not read up, on statements on properties yet. --Tobias1984 (talk) 08:13, 19 December 2014 (UTC)


numerical value range

   Not done
DescriptionRange of numerical values allowed to be associated with that property: meant to replace field allowed values of {{Property documentation}}.
Data typeNumerical range? List of numbers? Set?-invalid datatype (not in Module:i18n/datatype)
Template parameterN/A
DomainWikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed valuesSet of numerical values (how? dedicated items?)
Examplenumber of deaths (P1120) ==> integers, 0 or positive
SourceInitially from allowed values of {{Property documentation}} on the talk page of each property
Robot and gadget jobsInitial creation to be performed by bots
Proposed byWikidata:Project_chat/Archive/2013/10#Range
Discussion

Originally requested by User:Filceolaire at Wikidata:Project_chat/Archive/2013/10#Range. -- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

Original discussion (Oct 2013)
datatype item
links to a class-item (an item which subclass of and instance of properties link to). The property should (mostly) only only link to items which are an instance of (P31) of items which are subclasses of the class-item specified by this property.
matches the rdfs:range property Filceolaire (talk) 17:55, 8 October 2013 (UTC)
  Conditional support. I would support storing range claims only if the semantics matched those of rdfs:range. See comments in Domain section above. Emw (talk) 15:56, 14 October 2013 (UTC)
Struck per Filceolaire's comments. The proposal above this one has been changed to discuss range.
More discussion

Necessary to replace field allowed values of {{Property documentation}}.
A range implies... a minimum value and a maximum value? A domain? A set of allowed values? An item representing a numerical domain? -- LaddΩ chat ;) 03:45, 12 November 2014 (UTC)

User:Laddo, see rdfs:range and https://www.google.com/search?q=rdfs%3Arange. I recommend Googling "rdf rdfs owl (name of property)" if you're unsure of the meaning of these proposals. These properties of properties should all be based on properties in RDF, RDFS and OWL -- i.e. Semantic Web standards.
We should deprecate "allowed values" as soon as possible. It's unclear whether it refers to rdfs:range or owl:oneOf. Editors routinely use "allowed values" both ways, making the property quite ambiguous. Emw (talk) 12:38, 14 November 2014 (UTC)
I agree that "allowed values" is kind of a melting pot at the moment, and I'd gladly get rid of it, but it's hard to stop using it as long as the properties from this section cannot be implemented. -- LaddΩ chat ;) 00:30, 15 November 2014 (UTC)
Emw, LaddΩ If I am reading the definition you linked to properly it is saying that rdf:range should always link to a Class which in wikidata terms means it should always link to an item which has a subclass of statement. This means that rdf:range is not equivalent to this property. This property is for defining the acceptable values for date or number items which is quite different from rdf:range. Can you confirm that is your interpretation of rdfs:range ? Filceolaire (talk) 22:18, 17 November 2014 (UTC)
Filceolaire, you're right, thanks for the careful reading. I've struck my support. There are other way to encode this information in OWL, but range is not it. Emw (talk) 03:47, 19 December 2014 (UTC)
Name changed from 'Numeric value Domain. Wording of the description changed to make clear this property refers to the Range and not the Domain. The more I look at this the more it seems to me that Domain and Range should link both to Query entities. Queries will have functions like has statement:Instance of:human and more than:0. and has format:NNN??#. Anyone else see that? Filceolaire (talk) 22:44, 17 November 2014 (UTC)
@Filceolaire: I used "numerical domain" because I thought it might specify not only the min and max, but also the nature of acceptable values: real number (Q12916) (floats), integer (Q12503), natural number (Q21199), rational number (Q1244890)... I'm pretty sure a query is not adequate for a numerical domain/range, but since I haven't yet read rdfs:range, let me give a more informed opinion in a couple more days. -- LaddΩ chat ;) 02:18, 20 November 2014 (UTC)
LaddΩ, rdf:range links to a class of items so it will be of no use for properties with date, numeric or text datatype. It is only for Properties with Item datatype. My point was that the kinds of properties we need for defining the range of Date, numeric and text datatypes look more like queries and less like the properties we use with itemsFilceolaire (talk) 11:17, 20 November 2014 (UTC)
  •   Oppose Wait until a unique system for constraint definition is defined. We should sure to create properties which can be used in the future constraint check system.

Originally proposed

These properties are currently in Wikidata:Property_proposal/Pending/4#Metadata properties, originating from Wikidata:Project_chat/Archive/2013/10#Property_Metadata:

These two were later added at Wikidata:Property_proposal/Pending/4#Statements about properties:

  • License terms
  • Place of publication

definition

   Not done
DescriptionTextual description providing a clear & simple, unambiguous and non-technical description of what the property represents.
Representsdefinition (Q101072)
Data typemultilingual text ?-invalid datatype (not in Module:i18n/datatype)
Template parameterN/A
DomainWikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed valuesText definition in each language
Example
  • father (P22) ==> "Biological father of a person"
  • vessel class (P289) ==> "Group of ships of a similar design, generally from the same model of a given ship builder"
SourceInitially based on description of {{Property documentation}} on the talk page of each property, without the technical portion
Proposed by-- LaddΩ chat ;) 00:10, 28 November 2014 (UTC)
Discussion

  Support As the proposer, mainly because of statements like this excerpt from w:Wikipedia talk:WikiProject Ships#Fall back on Wikidata for Ship class:

<rant>This last point is one of my pet peeves about Wikidata. The reason that we use named parameters in our templates is so that humans can understand the purpose of the parameter. We have |Ship name= and |Ship commissioned= and |Ship length= and |Ship class= and a whole raft of other parameter names that convey meaning to humans. Not so with Wikidata. Without we have some sort of dictionary, P289 is meaningless and that is a barrier to its use that must, must be changed.</rant> (from User:Trappist the monk)
We absolutely need a more lengthy and explicit description of a property, that can be accessed remotely for tooltip pop-ups, for example. This description is intended for non-technical users, and shall be distinct from Property usage further below, that aims at clarifying its technical usage for Wikidata contributors.
-- LaddΩ chat ;) 00:10, 28 November 2014 (UTC)

comment: Editor Laddo has asked for my comments. I come here knowing nothing about Wikidata. That is my <rant />. I am very much in favor of the liberal use of descriptions that aid understanding so for that reason I am in favor of Description. In re-reading my <rant />, I think that I failed to get across the essence of what I wanted to say. If I am writing a template that uses some wikidata property, I can, I presume, troll wikidata until I find it and then I can include it in my template. Because I did the research, I know what that cryptic bit of text is and what it means (at least for the short term). Some time later another editor reading my template's code might be able to infer what {{#property:P289}} is and does, but without she researches it, she won't know. So, perhaps what it is that I'm looking for is some way to alias {{#property:P289}} to something that immediately conveys to a human reader what that property thing is / does without needing to look it up every time I see it (because I won't remember day to day what it means – I suspect that to be a common affliction, especially as we age).

Here is Editor Laddo's snippet of en:Template:Infobox ship characteristics/sandbox that uses {{#property:P289}}:

{{#if:{{{Ship class|}}}<!-- either -->{{#property:P289}}|<tr style="vertical-align:top;"><td>Class & type:</td><td>
{{#if:{{{Ship class|}}}|{{{Ship class|}}}|[[{{#property:P289}}]]}}</td></tr>
}}

When I first saw this it was a meaningless change because I couldn't attach meaning to {{#property:P289}}. After some study, I could infer that it might provide ship-class information if the template didn't already have it. If there were such a thing as {{#property_alias:ship_class}} then Editor Laddo's code would look like this and anyone reading it would have a much better chance of understanding the code at first reading without needing a dictionary:

{{#if:{{{Ship class|}}}<!-- either -->{{#property_alias:ship_class}}|<tr style="vertical-align:top;"><td>Class & type:</td><td>
{{#if:{{{Ship class|}}}|{{{Ship class|}}}|[[{{#property_alias:ship_class}}]]}}</td></tr>
}}

I am old enough to remember programming in BASIC on the first IBM PCs. In those days, variable names were one or two characters. It was great to move on to C where variable names could mean something. Wikidata properties that are just numbers seem like a throwback to those not-so-great days of BASIC. Am I making any sense?

I would add one other, unrelated comment. At enwiki, the use of tooltips is rather strongly discouraged for reasons of accessibility (see en:Wikipedia:Manual_of_Style/Accessibility#Text).

—Trappist the monk (talk) 00:53, 29 November 2014 (UTC)

Now using clearer {{#property:ship class}} in that infobox, since the "label" syntax is also supported (see mw:Wikibase/Notes/Inclusion syntax). -- LaddΩ chat ;) 02:39, 1 December 2014 (UTC)

recommended qualifier

   Not done
DescriptionQualifier(s) that should be associated to statements using this property.
Data typeProperty
Template parameterN/A
DomainWikidata property (Q18616576) - Wikidata:Glossary#Property
Allowed valuesAny Wikidata property (Q18616576) allowed to be used as qualifier
Exampleposition held (P39) recommended qualifiers electoral district (P768), replaces (P1365), end time (P582), replaced by (P1366), statement is subject of (P805) (see Property talk:P39)
SourceCan be initially based on {{Constraint:Qualifier}}
Proposed by-- LaddΩ chat ;) 17:43, 13 November 2014 (UTC)
Discussion

Such a property would be the basis for constraining the use of qualifiers. -- LaddΩ chat ;) 17:43, 13 November 2014 (UTC)

  • @Snipre: No they are not. This could mean this property is allowed here as a qualifier, so don't hesitate to use it. With a qualifier as a string descriptions, we could even give informations to the user on how it's supposed to be used in this context. TomT0m (talk) 20:27, 15 June 2015 (UTC)
@Snipre: I'm afraid i disagree about partial information. To take the example above. Giving the current office held by a politician is useful information, just by itself. Every additional datum added is useful but adding info to one politician does not make all other politician bios useless. Wikidata will not ever be complete or finished but it will, eventually, be better than all the alternatives. Filceolaire (talk) 21:23, 18 June 2015 (UTC)

en:Template:FJC Bio

   Not done
Description...
Data typeString
Template parametersee above
DomainQ5
Allowed values\d+
ExampleRobert Gibson (Q7344755) → {{FJC Bio|851}}
Sourceexternal reference, Wikipedia list article, etc.
Robot and gadget jobsimport from enwiki
Motivation

(Add your motivation for this property here.) --- Jura 08:13, 8 October 2015 (UTC)

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

Dictionary of Art Historians

Descriptionentry in the Dictionary of Art Historians
RepresentsDictionary of Art Historians (Q17166797)
Data typeString
Domainpersons
ExampleAby Warburg (Q60185) → warburga
Sourceexternal reference (for additions); mix'n'match list
Formatter URLhttps://dictionaryofarthistorians.org/$1.htm
Robot and gadget jobsyes
Motivation
Discussion

@Jura1, Spinster, Pasleim: Done. Jonathan Groß (talk) 09:55, 23 November 2015 (UTC)

Norwegian organization number

Descriptionthe organization's ID in the Norwegian Entity Registry
RepresentsNorwegian organization number (Q11994066)
Data typeString
Template parameterUsed in no:Mal:Infoboks organisasjon
DomainNorwegian organizations
Allowed values[0-9]{9}
ExampleWikimedia Norge (Q6985258) → 993101583
SourceThe Entity Registry
Formatter URLhttp://w2.brreg.no/enhet/sok/detalj.jsp?orgnr=$1
Robot and gadget jobsMy bot can import values from nowiki and nnwiki.


beam

   Done: beam (P2261) (Talk and documentation)
DescriptionThe beam of a ship is its width at the widest point as measured at the ship's nominal waterline.
Representsbeam (Q2376482)
Data typeNumber (not available yet)
Template parameter« maître-bau » dans fr:Modèle:Infobox Navire, "beam" in en:Template:Infobox ship career
Domainboats
Allowed valuesnumber with unit of distance
ExampleCMA CGM Bougainville (Q21008053) → 54 m
Sourcefr:Maître-bau en:Beam (nautical)
Motivation

Allow to describe the dimensions of boats on Wikidata. Tubezlob (🙋) 16:36, 6 October 2015 (UTC)

Discussion

draft

   Done: draft (P2262) (Talk and documentation)
DescriptionThe draft (American) or draught (British) of a ship's hull is the vertical distance between the waterline and the bottom of the hull (keel), with the thickness of the hull included; in the case of not being included the draft outline would be obtained.
Representsdraft (Q244777)
Data typeNumber (not available yet)
Template parameter« tirant d'eau » dans fr:Modèle:Infobox Navire, "draft" in en:Template:Infobox ship career
Domainboats
Allowed valuesnumber with unit of distance
ExampleCMA CGM Bougainville (Q21008053) → 16 m
Sourcefr:Tirant d'eau en:Draft (hull)
Motivation

Allow to describe the dimensions of boats on Wikidata. Tubezlob (🙋) 16:47, 6 October 2015 (UTC)

Discussion
Motivation

All organizations in Norway have an organization number, so having it in Wikidata would be great. Jon Harald Søby (talk) 16:31, 12 November 2015 (UTC)

Discussion

  Strong support --Almondega (talk) 21:30, 14 November 2015 (UTC)

  Support Runner1928 (talk) 22:28, 16 November 2015 (UTC)
  Support Already used in infoboxes on nowp. Would definitely be good to have. Danmichaelo (talk) 21:09, 17 November 2015 (UTC)
  Support Thryduulf (talk: local | en.wp | en.wikt) 21:33, 17 November 2015 (UTC)

@Jon Harald Søby, Almondega, Runner1928, Danmichaelo, Thryduulf: Done. Jonathan Groß (talk) 11:05, 23 November 2015 (UTC)

Track gauge

   Not done
DescriptionQ214519 (track gauge), use "track gauge" instead of "gauge" since other gauges exist, most notably Q904003 (loading gauge)
Data typeNumber (not available yet)
Template parameter"track_gauge" or "gauge" as in:
Domainrail network, rail line
Allowed values0.01 ... 10 000 (steps: 0.01 mm)
ExampleQ660895 (Tōkaidō Shinkansen) => 1435. Allow qualifiers "from" and "to", since some lines have been re-gauged.
Format and edit filter validation??? (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
Source...
Robot and gadget jobsData could be collected from different Wikipedias
Proposed byKwj2772 (talk) and HSRtrack (talk)
  • Kwj2772 (talk) 16:55, 6 April 2013 (UTC)
  • HSRtrack (talk) 02:30, 13 May 2013 (UTC)
    •   Support Joshbaumgartner (talk) 04:34, 9 May 2013 (UTC)
      Oppose the name, and that the value includes a unit - I would restrict input to metric and mm. There are too many systems otherwise, Imperial, Portuguese, Spanish, Swedish, Prussian ... support the general idea. Please see the proposal for #Track gauge below. HSRtrack (talk) 18:24, 14 May 2013 (UTC) Changed to   Support after merging the two proposals. HSRtrack (talk) 22:53, 23 May 2013 (UTC)
    Comments: I agree with HSRtrack that is should be numeric (in mm, without unit). en:wiki uses this list: en:Template:RailGauge/entry_check.
    Small gauges <100 mm: Note that small gauges are used too (say under 100 mm), mostly for toys and models. In [:en:Template:RailGauge], they are not separated. Now about precision: if we adhere to the generic safe 3 significant figures of precision, we'll need decimal places when the gauge is under 100 mm.
    Definition in inches: Some rail gauges are defined in imperial measures originally (inches). These may well be converted to mm, provided that re-converting to inches results in the same defined imperial measure. This is called a round-trip conversion check. It can be demonstrated that in this an integer value in mm (say >100mm) corresponds to 1⁄32 inch or larger. (That is: calculating back from mm to inch results in 1⁄32 inches or larger, so there is no overprecision since there are no gauges defined by 1⁄64.)
    For gauges <100mm (including to-scale models) one should/could use decimal inch values. An issue here could be: when the scale is defined like 1:1⁄32, typically imperial, the round trip check should work. en:User:DePiep= -DePiep (talk) 10:07, 16 May 2013 (UTC)
    I added a section about units at en:track gauge. Support two decimal digits as found in en:List of rail transport modelling scale standards HSRtrack (talk) 16:50, 22 May 2013 (UTC)
      Support Don't worry about the number of decimals - datatype number can support any number of decimal places and nothing here will influence that. Filceolaire (talk) 12:58, 26 May 2013 (UTC)
    Maybe restriction to two decimal places is wanted, since it disallows inputs like 1000.0000000001, 1000.000000001 (one zero less), 1000.0000000002 HSRtrack (talk) 13:16, 26 May 2013 (UTC)
    IMHO it should be of "number with unit" datatype. --Ricordisamoa 18:34, 28 May 2013 (UTC)
    Why do we need unit? It will be simplier if use one unit. And in infobox we can make units conversion.--Ahonc (talk) 20:54, 28 May 2013 (UTC)
    If the unit is always "mm" as proposed, then it is redundant. If the unit can be different from mm, then it will render lot of data useless to many people. What is 1 Prussian foot? HSRtrack (talk) 21:40, 28 May 2013 (UTC)

    Track gauge (merged)

    Some discussion below may be worth keeping.

    Source diff: http://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Unsorted&diff=prev&oldid=42173146

    Copied from Wikidata:Property_proposal/Unsorted#Track gauge
       merged
    Descriptiontrack gauge (Q214519)
    Data typeNumber (not available yet)
    Template parametermerged
    Domainrail network, rail line
    Allowed values0.01 ... 10 000 (steps: 0.01 mm)
    ExampleQ660895 (Tōkaidō Shinkansen) => 1435. Allow qualifiers "from" and "to", since some lines have been re-gauged.
    Format and edit filter validation??? (sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    Sourcew:en:T scale (3 mm), w:en:Ridable miniature railway (89 mm), w:en:List of track gauges by size (8200 mm)
    Robot and gadget jobsData could be collected from different Wikipedias
    Proposed byHSRtrack (talk)
    Discussion

    Currently values are distributed between different Wikipedia, sometimes a value is in the Portuguese and not any other, sometimes in Spanish and not any other, sometimes in German and not any other... HSRtrack (talk) 02:30, 13 May 2013 (UTC)

    Seems like a good idea. There needs to be flexibility to allow multiple values, e.g. w:South Tynedale railway (built as 1435mm, preserved as 610mm), w:Rail Transport in Victoria (there are 1600mm, 1435mm, 1067mm and 762mm gauge lines). I don't know how Wikidata works so I have no idea if this is a problem or not. Thryduulf (talk) 09:57, 13 May 2013 (UTC)
    Some gauges are defined in metric system, others in imperial system. -DePiep (talk) 10:42, 13 May 2013 (UTC)
    And even others in Portuguese, Spanish, Prussian or Swedish units. HSRtrack (talk) 22:05, 13 May 2013 (UTC)
    • How they are defined can be listed separately, also how they were in their history. This value here is just meant for mm-precision of what they are. Note also, that definitions can change and the UK rails are now defined as 1435 mm. Also, since almost all countries in the world beside the US, Liberia and Burma seem to have switched to metric, most current operated world wide track is probably operated in metric. Furthermore, all Wikipedias beside the English one seem to use metric categorization in mm. So, if one needs extra values for English Wikipedia, please create an extra field, but allow for coordination between the metric Wikipedias. HSRtrack (talk) 15:02, 13 May 2013 (UTC)

    This discussion seems to be duplicate of Wikidata:Property_proposal/Place#rail_gauge_.2F_.2F. Kwj2772 (talk) 17:23, 14 May 2013 (UTC)

    Then please merge into the earlier one. -DePiep (talk) 09:38, 16 May 2013 (UTC)
    If Kwj2772 allows me to do so or better reverse merge since the "Track gauge"-proposal is much better developed. HSRtrack (talk) 17:18, 22 May 2013 (UTC)
    Just merge them. Kwj2772 (talk) 03:24, 23 May 2013 (UTC)
    There is already track gauge (P1064) for this and I feel like there is a reason to continue using this: It would allow to more precisly specify specify the gauges, for example for finland and russia, where one has 1524 and the other 1520, but both are claimed in discussions on dewiki to result in the same range due to differing tolerances. --Nenntmichruhigip (talk) 17:56, 10 September 2015 (UTC)

    Not done - track gauge (P1064) already exists. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:38, 19 November 2015 (UTC)

    Indigenous to

       Done: indigenous to (P2341) (Talk and documentation)
    Descriptionarea or ethnic group that a language, folk dance, cooking style or other cultural expression is found (or was originally found)
    Data typeItem
    Template parameterput Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement
    Domainlanguages, dialects, folk dances, cooking styles, other cultural expressions
    Allowed valuesadministrative geographical areas, geographical features, ethnic groups.
    Exampledandiya raas (Q3629880) => Gujarat (Q1061)
    Sourceexternal reference, Wikipedia article
    Robot and gadget jobsShould or are bots or gadgets doing any task with this? probably not
    Proposed byFilceolaire (talk)
    Discussion

    This property would be similar to endemic to (P183) but for languages, dialects, folk dances, cooking styles and other regional cultural expressions instead of species Filceolaire (talk) 00:25, 7 November 2014 (UTC)

      Support I was looking for a way to link instruments to where they're from but couldn't find any suitable property. This seems to be what I was looking for.
    One thing I would say, though, is that culture is the result of a group of people behaving in a common way and many (if not most) cultural things are really linked to an ethnic group (Q41710) or human social group (Q874405) (including religious groups) and then to specific areas via the regions those groups of people live in, rather than directly to an area. Not all groups of people have a clearly defined area either.
    Some examples: haka (Q3595586) is a dance of the Māori (Q6122670) of New Zealand (Q664), Muong (Q3236789) is spoken by the Muong people (Q72805) of Vietnam (Q881), t'rưng (Q7667735) is an instrument used by the Jarai people (Q2467559) and Bahnar people (Q1347290) of Vietnam (Q881), Miao language (Q33813) is spoken by the Hmong people (Q219205) of southern People's Republic of China (Q148), Vietnam (Q881), Laos (Q819) and Thailand (Q869), Ainu cuisine (Q4697541) is the style of cooking of the Ainu people (Q101828) of northern Japan (Q17).
    How do you think things like that should be handled? - Nikki (talk) 02:25, 3 March 2015 (UTC)
    Nikki Description amended to add "ethnic group" as well as area. Filceolaire (talk) 21:22, 20 March 2015 (UTC)
    I don't think it makes sense to say that something is "indigenous to" an ethnic group. The adjective indigenous relates to places, not groups. It would make more sense to add ethnic group as a target for the property, i.e. "area that an ethnic group is found (or was originally found)". Kaldari (talk) 19:27, 13 November 2015 (UTC)
      Support Popcorndude (talk) 12:08, 15 September 2015 (UTC)
      Question Would this apply to foods as well? For example, could you say "tamales are indigenous to Mesoamerica"? Kaldari (talk) 23:13, 10 November 2015 (UTC)
    Yes Kaldari. This could be used for foods. Joe Filceolaire (talk) 09:52, 11 November 2015 (UTC)

    playing range image

    Descriptionimage showing the playing range of the instrument
    Representsrange (Q1042979)
    Data typeCommons media file
    Template parameter"range" in en:Template:Infobox instrument, "Tonumfang" in de:Template:Infobox Musikinstrument and the equivalents in other languages.
    Domainmusical instrument (Q34379)
    Allowed valuesCommons image files
    Exampledouble bass (Q80019) => commons:File:Range_contrabass.png, western concert flute (Q209554) => commons:File:Range_flute.png
    Sourceinfoboxes
    Robot and gadget jobsBots could import the values from infoboxes and check that the values are in commons:Category:Instrument_ranges or one of its subcategories
    Motivation

    image (P18) is normally used for an image of the instrument itself, which is completely different from the range of notes it can play. Nikki (talk) 12:01, 28 April 2015 (UTC)

    Discussion
    •   Oppose. The images you link to show the upper note and the lower note that the instrument can play. Wouldn't it be much better to have statements giving the upper and lower notes? That way we could not only automatically generate these images we could also use this info in other ways? You could use this for the range a singers voice could achieve too. I would suggest using datatype "item" for these "upper note" and "lower note" properties - we can have items for each note all the way up to the highest and lowest notes large organs can achieve. Filceolaire (talk) 12:50, 28 April 2015 (UTC)
    •   Support per Nikki's comment below. Filceolaire (talk) 19:34, 11 May 2015 (UTC)
      • Why not both? I would support adding properties and items for the upper and lower notes too, but I don't think that would replace the images. Generating the images automatically is a nice idea in theory, but it's not that simple to do. Both examples I linked have more than simply two notes, plus you have to deal with things like choosing the best clef to use. Even if you figure out all the properties needed to provide enough information and create all the necessary items, you then need something which is capable of bringing it all together and something to generate the image itself. It's a rather complicated process to generate an image, especially when the images already exist. - Nikki (talk) 15:37, 29 April 2015 (UTC)
    • Per Filceolaire, far better to have a property for the item representing the top note, and another for the bottom note. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:30, 30 April 2015 (UTC)
      The existing images are stored on Commons and references to the images are duplicated across Wikipedias (e.g. commons:File:Range_flute.png is used by 25 different Wikipedias). It would make sense if the infoboxes could access references to the images from a central data repository instead of having to duplicate them. Isn't that exactly one of the reasons Wikidata exists?
      Not having this property will not stop the images from being added, they will just end up being added using image (P18) instead (as has already happened for western concert flute (Q209554)), which seems rather suboptimal, since as I mentioned, image (P18) would normally be used for pictures of the instrument itself, not for its playing range. They are images of two completely different things, so it makes sense to keep them separated.
      - Nikki (talk) 09:57, 10 May 2015 (UTC)
    OK. Lets have both. I have changed my vote above and added proposals for the "highest note" and "lowest note" below.   Support. Filceolaire (talk) 21:55, 23 May 2015 (UTC)

    OpenBenchmarking entry

       Not done
    DescriptionEntry at the OpenBenchmarking.org database
    Data typeString
    Domainsoftware, hardware
    ExampleSuperTuxKart (Q971909) → http://openbenchmarking.org/test/pts/supertuxkart
    Sourceexternal reference, Wikipedia list article, etc.
    Formatter URLhttp://openbenchmarking.org/$1
    Motivation

    OpenBenchmarking.org keeps a comprehensive database of hardware and software performance. That could be of use to Wikidata as it allows a third party to machine-readably get performance results from a Wikidata item. Pikolas (talk) 22:55, 30 June 2015 (UTC)

    Discussion
    "pts/supertuxkart" seems to be a test suite rather than a product result. That is why it is in "http://openbenchmarking.org/test/" rather than "http://openbenchmarking.org/results/". Results seem to be generally for particular PC configurations or for a range of products compared rather than for a particular product with a wikidata item and the 'OpenBenchmarking.org/results/' references are for that series of tests rather than relating to a particular product.
    or have I misunderstood? Joe Filceolaire (talk) 20:19, 22 July 2015 (UTC)
      Oppose unless Pikolas has more info. Joe Filceolaire (talk) 23:54, 20 August 2015 (UTC)

    Not done - no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:06, 17 November 2015 (UTC)

    option for grammatical category

       Not done
    Descriptionsubject is one of the possible values for grammatical category object.
    Data typeItem
    Domaingrammeme (Q2374489)
    Allowed valuesgrammatical category (Q980357)
    Examplesubjunctive (Q473746) → grammatical mood (Q184932)
    Sourceexternal linguistics reference
    Robot and gadget jobsprobably not
    Motivation

    I wish to expand our coverage of linguistics (Q8162). Popcorndude (talk) 00:18, 6 July 2015 (UTC)

    Discussion

    or this could be called simply "grammatical category". Popcorndude (talk) 01:39, 6 July 2015 (UTC)

    A significant proportion of the uses of this can be found here. Popcorndude (talk) 16:53, 14 August 2015 (UTC)
    Would it be acceptable to have subjunctive (Q473746) be subclass of grammatical mood (Q184932) and instance of grammeme (Q2374489)?
    It also seems to me that a particular grammatical category is not really a "class", but I'm open to discussion. Popcorndude (talk) 00:57, 21 August 2015 (UTC)
    @Popcorndude: There is linguistic discussions on the enwiki article on type–token distinction (Q175928). So yes, I say it's modellable by classes. There is a class of sentences in which a special grammatical category appears. If a sentence is made of words of other linguistic entities, then each linguistic entity can be bound to fulfil a grammatical role ... subjonctive is bound to a class of particular forms of verbs ...
    If I say that the "subjonctive" concept is very closely related to all the sentenses (or sentences parts) that are written in the subjonctive mode, would make sense ? We could say "this is subjonctive" irl. Then "subjonctive" would be a subclass of sentences, or the precise relevant linguistic items. "Grammatical mode" would be the metaclass (see Help:Classification) of all the relevant classes of sentences relevant to model grammar. I think this would do the trick.author  TomT0m / talk page 07:19, 21 August 2015 (UTC)
    Sorry, I can't follow what is said here. I don't understand what this property is for too. :/ Could someone expand on this a bit? --SynConlanger (talk) 14:09, 21 August 2015 (UTC)
    User:SynConlanger, the idea was to link grammemes (past tense, subjunctive, perfect, dual, etc.) with the corresponding grammatical category (tense, mood, aspect, number, etc.). However, now that I think about it, User:TomT0m is right (so far as I understand him), and this could just as easily be modeled by having all the grammatical categories be subclasses of grammatical category, and then just have all the grammemes be subclasses of them and instances of grammeme. Is that what you meant TomT0m, or have I totally misunderstood your suggestion? Popcorndude (talk) 15:33, 21 August 2015 (UTC)
    @Popcorndude: I think we're on the same page :) I did not know the grammeme word. author  TomT0m / talk page 15:40, 21 August 2015 (UTC)
    Grammeme is a quite obsolete term for an emic grammatical entity. It was in vogue during the "tagmemic linguistic" era. But I'm a phonetician/phonologist not a morphosyntactician so I may be wrong! But I got the point! I agree in having "grammatical category" < "tense" < "past" and the like (where < means "contains the subclass" or whatever it may be metadata-ly speaking). --SynConlanger (talk) 17:17, 21 August 2015 (UTC)
    In that case I will retract this proposal. I would not be surprised to find that some other term is now prefered to "grammeme", but it was an item that already existed, so it seems like I might as well use it anyway. Popcorndude (talk) 17:45, 21 August 2015 (UTC)

    object spatial depth

       Not done
    Description3rd dimension, other than length, width, etc., where this dimension is named "depth"
    Data typeQuantity
    Domain3d objects, sample: cameras
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    Robot and gadget jobsimport from https://www.freebase.com/digicams/camera_dimensions/depth

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:33, 20 November 2015 (UTC)

    period

       Done: time period (P2348) (Talk and documentation)
    Template parameter"epochs" in en:template:Infobox ancient site, likely others
    Domainarchaeological and palaeontological sites and finds; historical events; geological sites
    Allowed valueshistorical eras, geological eras, cultural eras, regnal eras, etc.
    Sourceexternal reference, Wikipedia list article, etc.
    Motivation

    This is a key piece of information for geology, archaeology, palaeontology and history items. Thryduulf (talk: local | en.wp | en.wikt) 12:43, 4 November 2015 (UTC)

    Discussion

      Support, located in time zone (P421) is occasionally used to record this and I've wanted a way to correct it without getting rid of the data entirely. Popcorndude (talk) 13:22, 4 November 2015 (UTC)

    @Thryduulf, Popcorndude, Joshbaumgartner, Filceolaire, Jheald:   Done time period (P2348) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:24, 24 November 2015 (UTC)

    Statistical unit

    DescriptionThe statistical unit of the dataset (country, household, individual, etc)
    Representsstatistical unit (Q3409269)
    Data typeItem
    Template parameter« unité statistique » dans fr:Modèle:Infobox Jeu de données
    DomainJeu de données (dataset)
    Allowed valuesWikidata item (Q16222597), individual (Q795052), household (Q259059), country (Q6256)
    ExamplePenn World Table (Q7163352) → country (Q6256)
    Format and edit filter validation(exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
    Sourceréférence externe, article de liste de Wikipédia, etc.
    Robot and gadget jobsDevrait-il y avoir ou existe-t-il des bots ou des gadgets qui effectueront des tâches avec cette propriété? Par exemple: vérifier les autres propriétés afin d'être cohérent, collecter des données, automatiser un lien externe, etc.
    Motivation

    Je voudrais créer les propriétés sémantiques pour décrire un jeu de données. L'unité statistique permet de décrire l'élément représenté dans la base de données. Par exemple, ça peut être un pays dans le cadre des Penn World Tables, un individu dans la cadre d'un sondage, un ménage dans le cadre de l'Enquête Emploi, une voie ou une rue dans la cas du fichier FANTOIR de la DGFIP, un élément (Q16222597) pour Wikidata, etc.

    I would like to create semantic properties which describe a dataset. A statistical unit is the unit of the dataset. For instance, this can be a country for the Penn World Tables dataset, an item for Wikidata, an individual in a poll, an household in an official statistical survey such as Labor Force survey or even a street in datasets like FANTOIR.

    --PAC2 (talk) 15:34, 11 November 2015 (UTC)

    Voir aussi Wikidata:Property_proposal/Unsorted#Variables. --PAC2 (talk) 08:44, 18 November 2015 (UTC)

    Discussion
      Support Popcorndude (talk) 16:21, 11 November 2015 (UTC)
      Support. Thryduulf (talk: local | en.wp | en.wikt) 21:40, 11 November 2015 (UTC)
    to indicate, for example, that column 2 gives population sizes ? Jheald (talk) 16:23, 15 November 2015 (UTC)
    Of course, thats part of the plan. The "column" is only meaningful for tabular data. I think, we should have the property "contains variable" --PAC2 (talk) 10:51, 16 November 2015 (UTC)
    •   Comment While "statistical unit" is certainly an accurate term for this (cf en:statistical unit), it's also rather a confusing term, since it is quite specialist terminology, and most people unfamiliar with the phrase might assume the property was for a unit in the sense of a metre or a second. Is there a case for using some other synonym for the property's label ? -- eg perhaps "explanatory variable" (though that's still not quite right). Jheald (talk) 13:11, 25 November 2015 (UTC)
      It 's difficult to find another term. "explanatory variable" is wrong. The "statistical unit" is the base item of the dataset. It could be books for a bibliographic database, a place of OpenStreetMap, an item for Wikidata, an household for the British Household Panel Survey. An "Observation" would also be appropriate (See Hadley's Wickham data semantics in this article http://www.jstatsoft.org/article/view/v059i10, page 3); --PAC2 (talk) 14:19, 25 November 2015 (UTC)

    has list

       Done: has list (P2354) (Talk and documentation)
    DescriptionWikimedia list related to this subject
    Data typeItem
    Allowed valuesinstance of (P31): Wikimedia list article (Q13406463)
    ExampleSpain (Q29) → list of cities of Spain (Q189098) (with qualifier of (P642) → municipality (Q15284))
    Motivation

    In eswiki we want to link items of countries and municipalities to the list of municipalities for that country. I asked about it in the Project chat how to do it and they suggested the use of a generic property like "has list" that has to be created (because I found properties for specific lists but not a generic one to use for this use case). The idea is to put the list in the country element and get the list directly from the country element when needed and using arbitrary access from the municipality elements. Agabi10 (talk) 15:59, 15 November 2015 (UTC)

    Discussion

    intended public/target/designed for

    Descriptionthis work or product (or object) is intended to be read/watched by, or has been designed to that person or class of person, or animals, plants, …
    Data typeItem
    Domainclasses of human (at least of beings :) subclasses of being (Q203872)      human (Q5)     , specific humans, animals, …
    Allowed valuesworks or artworks, object, class of object.
    Example (could not fins an item for undergraduate person
    Discussion

    The subject item could be target market (Q198981)      but I think it is broader than a commercial buisiness concept, but if anybody has a better idea ...

    Proposed by: TomT0m (talk)

    Motivation: seems a pretty common stuff to add, and useful to use a class of people as intended target. Maybe an alternative intended to use for <education> would be a good complement.

    TomT0m (talk) 20:26, 1 April 2015 (UTC)

      Comment that would be audience (Q211198)? Have you something like e.g. young adult literature (Q1233720) in mind which has a tendency to overlap with genre (P136) or rather ratings like USK 16 (Q14920393) or with finer granularity subclasses of the population specified by interests like White Anglo-Saxon Protestant (Q256898) or male videogamers between 25 and 30, farmers from northern Kansas which I usually would not deem notable items in Wikidata? -- Gymel (talk) 18:41, 23 May 2015 (UTC)
    @Gymel: More like class of people as I said, and yes, if there is a need I'm ready to create such items. It's a good thing to be able to compress such complex statements with one item, maybe in the future a query. TomT0m (talk) 19:04, 23 May 2015 (UTC)
    How about a more general property like designed for or intended for? MSGJ (talk) 21:37, 10 June 2015 (UTC)
    @MSGJ: Agreed, I modified the proposal TomT0m (talk) 09:27, 12 July 2015 (UTC)

    online service

       Done: online service (P2361) (Talk and documentation)
    Descriptionthe online service/online service provider tied to an item
    Representsinternet service provider (Q11371)
    Data typeItem
    Template parameter"onlineservice" in Infobox VG
    DomainNumerous
    ExampleXbox 360 (Q48263) → Xbox network (Q170073)
    Motivation

    Per TomT0m's suggestion above ;) --George (Talk · Contribs · CentralAuth · Log) 19:17, 24 May 2015 (UTC)

    Discussion

    UN/LOCODE

       Not done
    Descriptiongeographic coding scheme by UNECE
    RepresentsUN/LOCODE (Q499348)
    Data typeString
    Domaincity (Q515), transport infrastructure (Q376799)
    Example

    with classifier: 

    1 = port (for any kind of waterborne transport)
2 = rail terminal
3 = road terminal
4 = airport
5 = postal exchange office
6 = Inland Clearance Depot – ICD or "Dry Port", "Inland Clearance Terminal", etc.
7 = fixed transport functions (e.g. oil platform)
B = Border crossing function
    0 = function not known, to be specified
    Sourcehttp://www.unece.org/cefact/locode/service/location.html
    Motivation

    Use is highly advised by IMO for the automatic identification system (Q787197).--Kopiersperre (talk) 10:18, 13 November 2015 (UTC)

    Discussion

    Not done - UN/LOCODE (P1937) already exists. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:23, 19 November 2015 (UTC)


    northwest coordinate of location map

       Not done
    Descriptionsee above. use as qualifier.
    Data typeGeographic coordinates
    Template parameterTemplate:Location map (Q5625881)
    Domainplace
    Examplesee above
    Robot and gadget jobsYes
    Proposed byGZWDer (talk)
    Discussion

    GZWDer (talk) 13:16, 6 January 2015 (UTC)

    I would rather have a "northernmost latitude" and a "westernmost longitude" property with type = number (decimal value). Parsing it from a coordinate-type property seems needlessly complicated.--Zolo (talk) 08:04, 9 January 2015 (UTC)
    Thinking of it, maybe it is best to wait until there is Wikibase on Commons so that we can store the data directly there. --Zolo (talk) 09:00, 17 January 2015 (UTC)
    I think this is a bad decision. Get the value of the coordinates is simple enough, but the coordinates are stored in the designated type. —putnik 18:31, 27 April 2015 (UTC)
    We already have coordinates of northernmost point (P1332), coordinates of southernmost point (P1333), coordinates of easternmost point (P1334), and coordinates of westernmost point (P1335). Can't we use those instead (as Zolo asked)? They are not specific to a particular map projection. I'm inclined to oppose unless someone can tell me why we need something else. Filceolaire (talk) 20:02, 19 March 2015 (UTC)
    Map not need all four. What a couple of them should we choose? I think it might be a good solution to add these two parameters: "northwest coordinate" and "westernmost coordinate" (not only for location maps, but for future uses too).   Weak support. —putnik 18:31, 27 April 2015 (UTC)
    I guess the idea is to create location maps with marks. If you have the coordinates of a city and a location map you still need to know which sector the location map is showing to put the mark for the city on the right place. --Pasleim (talk) 22:10, 20 May 2015 (UTC)
    Such qualifier is useful only for specific kind of map projection (Q186386) (usually small) in which latitude and longitude can be converted to x and y value in the picture of map using linear function (Q188597). However if you look at Antarctica.svg, the translation to x and y is rather complex. The general solution to the problem is creating function, which test whether the given coordinate is visible on the map, and converts it to pair of (x, y) in the picture. Paweł Ziemian (talk) 11:54, 13 June 2015 (UTC)
    @Filceolaire: A statement with coordinates of northernmost point (P1332) d:o 1333, 1334 and 1335 have all both latitude and longitude. Adding all four, therefor gives 4 longitudes + 4 latitudes = 8 numbers. That would give us an unsolvable system of linear equations (Q11203). We need exactly four numbers here to copy the functions of present templates like Template:Location map Andorra (Q12259). That is easiest accomplished by adding coordinates of the most NW and SE points of the map.
    @Paweł Ziemian: That also includes nations like Russia and Greenland. They are the exceptions, they cannot be solved in a simple way like most other nations and regions in the world. -- Innocent bystander (talk) 18:05, 6 July 2015 (UTC)
    Yes, I know. It was an example, where the problem is easiest to observe (I think). Paweł Ziemian (talk) 18:43, 6 July 2015 (UTC)
    Innocent bystander What if we take the 'northernmost' and 'southernmost' points and discard their longitude values and then take the 'easternmost' and 'westernmost' and discard the latitude. Now we have two latitude values and two longitude values and the problem of finding NW and SE coordinates from these is solvable. Greenland shouldn't be a problem nor should Russia since we specify which point is easternmost and which is westernmost. Antartica only has a 'northernmost' point, defining a circular map. Similarly for the Artic sea. Easy peasy.
    "Ah" you say "but that means the map of russia and of greenland is not square!" and I say that depends on which projection you are using. These maps are square if you use the Peters equal area projection for instance. This will, however, distort the shape of Russia and Greenland. You would be better to use a polar projection for the maps. The centre of this polar projection should be at a latitude half way between the 'northernmost' and 'southernmost' points and a longitude half way between the east and west extreme points. Not hard to calculate. The north south east and west limits of the maps should be at or beyond the NSEW extreme points. Sounds perfectly possible to me. Google earth does this all the time - draws a polar projection with a centre point wherever the centre of your screen is. I'm still Opposed to creating new properties. Filceolaire (talk) 00:27, 8 July 2015 (UTC)
    A map of Russia or Greenland with the same longitude in the left upper and left lower corner are possible to create, but they are aestheticly awkward. Maps with other kind of projections exists in these cases, so it is solvable. The problem is that somebody have to create these maps and templates. We are not flooded with such skilled users on Commons and the Wikipedias. -- Innocent bystander (talk) 05:05, 8 July 2015 (UTC)
    This guy got an individual engagement grant to do exactly these maps. You should talk to him. Filceolaire (talk) 22:33, 16 July 2015 (UTC)
    There are several use cases with map overlays, where the placement of the overlay object would be needed. I had thought of using the northernmost coordinate and it's companions, but they are coordinate points, consisting of both longitude and latitude. This means there has to be either a more suitable property (a corner point, such as presented here) or a more suitable datatype (lat or long only, and a corresponding property). I think the previous would be more lightweight. So, I   Support --Susannaanas (talk) 08:37, 14 September 2015 (UTC)

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:21, 19 November 2015 (UTC)

    southeast coordinate of location map

       Not done
    Descriptionsee above. use as qualifier.
    Data typeGeographic coordinates
    Template parameterTemplate:Location map (Q5625881)
    Domainplace
    Examplesee above
    Robot and gadget jobsYes
    Proposed byGZWDer (talk)
    Discussion

    GZWDer (talk) 13:16, 6 January 2015 (UTC)

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:22, 19 November 2015 (UTC)

    female ratio

       Not done
    Descriptionfemale part of the population/sample. Another way of entering data instead of using female population (P1539) and male population (P1540). Avoid using both.
    Data typeNumber (not available yet)
    Allowed values>=0 and <=1
    ExampleFryšták (Q1471150) → 0.514477 (in 2015); United States Senate (Q66096) → 0.20 (January 3, 2015)
    Motivaton
    Discussion
    •   Oppose. We should not be creating special 'female' properties. Why isn't there a 'male ratio' property? Remember the row over separate categories for 'women poets' on en:WP. Lets not do that.
    I would delete female population (P1539) and male population (P1540) as well. Just use population (P1082) with qualifier applies to part (P518) then it can be used for all the cross tabs in the census - sex, age, religion, race, etc. Filceolaire (talk) 16:50, 30 April 2015 (UTC)
    @Filceolaire: Is it the concept you don't like or the formulation? How about a gender neutrally formulated property for the gender ratio? There is en:List of countries by sex ratio, but I'd rather see a percentage of total. Male ratio could work as well, but focus is frequently on the female part. --- Jura 17:04, 30 April 2015 (UTC)
    @Filceolaire: care to explain? --- Jura 02:19, 3 May 2015 (UTC)
    Jura, Antrocent I have been thinking about how we can express this in a gender neutral way. I think I would prefer the property was called "Proportion of population". Examples:
    "Proportion of population:0.8(applies to part:male)", "Proportion of population:0.2(applies to part:female)", "Proportion of population:0.1(applies to part:Roman Catholic)", "Proportion of population:0.08(applies to part:HIV positive)". When the number of people who identify as neither male nor female goes above 0.005 we should include them in the info boxes. With this property we can do that. We won't need to redefine the property. OK? Filceolaire (talk) 23:36, 5 May 2015 (UTC)
    This is tempting indeed and could store the information:
    • Using a generic field mixing it with other information is always possible, but generally not preferred (the answer to the question asked by Filceolaire is here).
    • In this case, it would complicate things twice:
      1. once we have to check if the property actually contains information about the gender ratio,
      2. then if it's the male or the female part.
    I suppose it's still not gender neutral, as one would have to pick one or the other when adding the statement. --- Jura 10:54, 8 May 2015 (UTC)
    •   Comment I changed the proposal to use 0.20 instead of 20%. This is more consistent with the datatype. It could still be displayed as a percentage. --- Jura 18:23, 30 April 2015 (UTC)
    • Support gender ratio is a frequently referenced statistic. Antrocent (talk) 18:59, 30 April 2015 (UTC)
    •   Oppose: Sex ratio is a recognized statistic, but if we maintain it, is should be a single property ("sex ratio" or "gender ratio") with the method of computation detailed in the description. There should not be female and male properties. Personally, I think it would be even better to simply use population (P1082) with qualifiers to indicate actual population numbers of any identified genders and let the client calculate the ratio to meet their needs. However, I realize that in reality, the base numbers are not always available and only the derived value is made available for certain populations. Josh Baumgartner (talk) 16:57, 11 June 2015 (UTC)
      • Josh, as I said above I think this should made more general so it can be used for other population tabs besides gender. Rename as "Proportion of population" with qualifier "Applies to part:Catholics/men/women/natives/born overseas etc. " Filceolaire (talk) 23:35, 18 June 2015 (UTC)

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:15, 19 November 2015 (UTC)

    male ratio

       Not done
    Descriptionmale part of the population/sample. Another way of entering data instead of using female population (P1539) and male population (P1540). Avoid using both.
    Data typeNumber (not available yet)
    Allowed values>=0 and <=1
    ExampleFryšták (Q1471150) → 0.485533 (in 2015); United States Senate (Q66096) → 0.80 (January 3, 2015)
    Motivation
    Discussion

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:17, 19 November 2015 (UTC)

    gender ratio

       Not done
    Descriptiongender distribution of the population/sample. Method of computation: female population/total population
    Data typeNumber (not available yet)
    Allowed values>=0 and <=1
    ExampleFryšták (Q1471150) → 0.515477 (in 2015); United States Senate (Q66096) → 0.20 (January 3, 2015)
    Note

    reformulated proposal per suggestion above by Joshbaumgartner. @Kopiersperre, Antrocent: --- Jura 07:14, 23 June 2015 (UTC)

    Motivation
    Discussion
    •   Oppose if this is only used for the female population. This should be a general property "proportion of population" which is used with qualifier applies to part (P518) to indicate if the proportion quoted refers to male or female or transgender or unknown gender or african american or finnish speaking or Catholics or high school graduates or any other tab in a population census. Filceolaire (talk) 16:42, 28 June 2015 (UTC)

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:19, 19 November 2015 (UTC)

    Metadata properties


    Please complete discussions on Wikidata:Property proposal/Property metadata before implementing these new properties.

    -- LaddΩ chat ;) 04:26, 13 November 2014 (UTC)


    per This request, property metadata should be stored as statements. So I reopen these request:

    # Property Name datatype
    1 Dedicated item for property item Wikidata item of this property (P1629)
    2 Property ID string
    3 URL format string formatter URL (P1630)
    4 Constraint type item property constraint (P2302)
    5 Property used for constraint item property (P2306)
    6 Item used for constraint item item of property constraint (P2305)
    7 Format used for constraint item is pollinated by (P1703)
    8 Range used for constraint time+number maximum value (P2312), minimum value (P2313)
    9 Subproperty item subproperty of (P1647)
    10 Equivalent property url equivalent property (P1628)
    11 Example all Wikidata property example (P1855)
    12 Main item item Wikidata property (P1687)

    --GZWDer (talk) 14:03, 30 October 2013 (UTC)

    Just for your information: properties on properties can't currently be stored until we close bugzilla:49554. I currently can't give a date for that but it will not happen before the end of this year. --Lydia Pintscher (WMDE) (talk) 14:53, 23 November 2013 (UTC)

    Statements about properties

    A while ago there was a discussion about statements about properties. Since then WMF legal have published meta:Wikilegal/Database Rights which includes the advice that: 

    For EU databases, bots or other automated ways of extracting data should also be avoided
because of the Directive’s prohibition on “repeated and systematic extraction” of even insubstantial amounts of data.

    This suggests another couple of statements we need to be able to make about our authority control properties and other properties that refer to databases.

    • License terms
    • Place of publication

    Filceolaire (talk) 23:09, 22 November 2013 (UTC)

    Some time ago it was decided that the best place to store property metadata was on the property page itself with statements. License info also could go there (using copyright license (P275)). The thing is that property pages do not accept statements, that's why we haven't processed yet some other related properties (for instance these or this). Is there any difficulty in unlocking property pages for adding statements?--Micru (talk) 08:40, 23 November 2013 (UTC)
    According to Lydia, meta-properties depend on bugzilla:49554. I will copy this conversation to Wikidata:Property proposal/Pending/4 (properties depending on the bug) for future reference.--Micru (talk) 15:40, 23 November 2013 (UTC)
      Done all created during the last 12 months. --Pasleim (talk) 19:58, 27 November 2015 (UTC)

    Spatial extent

       Done
    DescriptionSpatial extent for the object along some axis, in positive direction perpendicular from a reference plane, what is most commonly referred to as its maximum width in some direction.
    Representsheight (Q208826)
    Data typeNumber (not available yet)
    Template parameterfor example "elevation" in w:en:template:infobox mountain above the geoid WGS84 (Note that "elevation" is interpreted as grade/slope in some languages.)
    DomainAny object with spatial extent
    Allowed valuesAll positive one-dimensional values with a length unit
    ExampleThe height of a mountain Glittertind (Q397876)
    Robot and gadget jobsBots would collect this from both articles in Wikipedia and use external datasets
    Proposed byJeblad (talk)
    Discussion

    This is a spatial extent for an object in some direction, going perpendicular on a plane, and unless otherwise specified it is the maximum length in any direction.

    • A qualifier instance of (height (Q208826) is this right?) would take whats given as subject item above and will specify what the extent measure. (For example the height of a mountain.)
    • A qualifier geoid (perhaps better called datum) which gives the interpretation of the items referenced, that is a height is according to the instance of. Default is WGS84 (World Geodetic System (Q215848)).
    • A qualifier reference item which would be interpreted according to the instance of and geoid if that is given. The measured length is by extension to the surface of this item. Could be an extended plane.
    • A qualifier extent coordinate system to specify the local coordinate system. Default is spherical coordinate system (Q203218).
    • A qualifier azimuth or orientation according to the instance of and geoide. Defaults to "unknown".
    • A qualifier inclination or polar angle according to the instance of and geoide. Defaults to "unknown".

    Tried to reformulate the spatial extents to be a single generic one. It seems that there is a problem whether the system is a local one when the reference system point back to itself or the geoid is undefined, or it is a global one references something else. One way around could be to drop geoid and only use reference item and infer geoid from this item. The item lives within some other system or is self referencing. No reference item would be interpreted as a self reference.

    Note that if the azimuth and/or inclination is set wrong the measurement axis my never touch the surface of the reference item. Jeblad (talk) 01:38, 30 October 2014 (UTC)

    Wait until we have the 'number with dimension' datatype, though I am really not clear how this is used and whether it would be better using a collection of specific properties such as 'Base' for mountains. Filceolaire (talk) 20:59, 31 October 2014 (UTC)
    Filceolaire can you point me to wherever a discussion about a 'number with dimension' datatype is going on? Getting a quantity datatype right is difficult, but rather easy compared to a dimension datatype. To make an example, a length dimension can exist and within that dimension there can be two length measures that can not be compared. Most of the time this situation arise because of lost knowledge about how base units relates, or becase there is (or was) conflicting definitions. My favorite example is the length measure "coffestops", see also m:Wikidata/Notes/Values. Another nice one is that "there are 4 stone throws (w:no:Steinkast) on one arrow shot (w:no:Pilskudd)", that is old Norse length measures. There is also "vika sjóvar" which is the distance you row a boat in two hours, which is calculated to be 11 112 meter on Wikipedia. :D In effect you have subdimensions within a dimension, but note that subdimensions in this case does not imply subclasses you can cast to a common baseclass (length is an abstract property and you can't cast a coffestop to a base class). Anyhow, I think it is better to create usable solutions and reprocess existing properties later when someone create the perfect solution. Jeblad (talk) 15:32, 5 November 2014 (UTC)
    See Wikidata:Requests_for_comment/Dimensions_and_units_for_the_quantity_datatype. Filceolaire (talk) 19:08, 5 November 2014 (UTC)
    I saw that page, didn't realize it was a proposed as an implementation. As it stands it is probably not a solution, in fact I think it will make it really hard to solve some real-world problems.
    Perhaps I should try to make a better explanation. That page describe the preferred units to use, it does not describe the role the measurement have. A property (predicate) describes the role a specific value (object) has in relation to an item (subject). An extent is such a property, and that will use a length measurement, possibly with units according to the given page. It is possible to use a length as a property, but then you must add qualifiers to say that this is in fact an extent. I think it is better to say what you measure with the property itself, and then add refinements to that, otherwise you need qualifiers about qualifiers (statements about reified statements about reified statements). An extent can have an orientation, but a length does not have one. It might not even be a measurement in a straight line. Jeblad (talk) 19:43, 5 November 2014 (UTC)
    In this case instance-of seems to be right as this would be a statement about a height, that is a height measurement. Usually it is wrong to use instance-of as a qualifier, that is rdf:type about a statement. Jeblad (talk) 02:32, 23 November 2014 (UTC)
      Comment. Jeblad, Filceolaire, how about using first-class properties like height (or spatial height) when applicable, and this property for more complex spatial extents? This approach works well for our kinship properties, where we have first-class properties like mother, father, brother, sister and child for basic relations, and relative with a type of kinship qualifier for more distant relations. Emw (talk) 01:11, 9 December 2014 (UTC)
    Emw There are 75 properties using this data type listed on Wikidata:Property_proposal/Pending/2 which have been approved and are waiting, pending the creation of this datatype. Check there and see if the property you are proposing is already approved. Filceolaire (talk) 23:25, 17 December 2014 (UTC)
    I believe property extent gives a more general solution than length in Wikidata:Property_proposal/Pending/2, and it will also cover minor axis. Remember, generalize! Jeblad (talk) 14:02, 28 February 2015 (UTC)
    I wonder if there should be no default for geoid, and the interpretation should be length along major axis. The next minor axis in following order will then give the reference system according to the right hand rule. Jeblad (talk) 14:11, 28 February 2015 (UTC)

      On hold pending data type. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:56, 22 March 2015 (UTC)

      Done elevation above sea level (P2044) and height (P2048) --Pasleim (talk) 20:03, 27 November 2015 (UTC)

    Australian Stratigraphic Units Database STRATNO

    Descriptionidentifier for a stratigraphic unit listed in the Australian Stratigraphic Units Database
    Representsstratigraphic unit (Q3694119)
    Data typeString
    Template parameterNo infobox parameter is known to currently exist, however a new parameter could be included within the template en:template:infobox rockunit
    Domainstratigraphic unit (Q3694119) where located in/on physical feature (P706) = Australian continent (Q3960) (approximation only)
    Allowed valuesstring pattern: \d+
    ExampleGascoyne Complex (Q5526405) → 7044
    Sourceexternal reference, Wikipedia list article, etc.
    Formatter URLhttp://dbforms.ga.gov.au/pls/www/geodx.strat_units.sch_full?wher=stratno=$1
    Robot and gadget jobsSTRATNO IDs could be scraped from the Australian Stratigraphic Units Database and then imported into Wikidata using mix-and-match
    Motivation

    Properties Litholex ID (P731), BGS Lexicon of Named Rock Units ID (P732) and DINOloket ID (P733) are examples of similar properties which exist for stratigraphic unit identification systems of other countries. This property proposal allows for Australian stratigraphic units to be linked to the authoritative catalogue (the Australian Stratigraphic Units Database) for such information on Australia.

    The Australian Stratigraphic Units Database (ASUD) originated as the National Register of Stratigraphic Names in 1949. The register was originally set up to help geoscientists adhere to the (then) newly created Australian Code of Stratigraphic Nomenclature (Lenz, et al, 1996). All information was held in a card file system until 1979 when the database was first developed electronically. The database now records information on all Australian stratigraphic units and their usage in literature, making it a centralised reference point for all Australian stratigraphic unit information. The database is also the repository for definition descriptions for these units. The database is maintained by Geoscience Australia in collaboration with the Geological Society of Australia's Australian Stratigraphy Commission. Dhx1 (talk) 10:22, 22 November 2015 (UTC)

    Discussion
      Support. Thryduulf (talk: local | en.wp | en.wikt) 21:30, 22 November 2015 (UTC)
      Comment Datatype needs to be string. Although the identifier is only a number we don't want any number formatting, or conversions. --Tobias1984 (talk) 08:58, 27 November 2015 (UTC)
      Comment Changed datatype to string, thanks Tobias1984. Dhx1 (talk) 13:08, 29 November 2015 (UTC)
      Done --Tobias1984 (talk) 13:17, 29 November 2015 (UTC)


    FAO status

    DescriptionFAO (united nation organisation about food) status of a race like abondance (Q322890)     
    Data typeItem
    Template parameter« statut FAO » dans fr:Modèle:Infobox Race (in progress)
    Domainbreed (Q38829)     
    Allowed valuesFAO statuses : C (critical) / D (endangered) / CM (critical-maintened) / DM ( endangered-maintened) / X (extinct) / NAR (not at risk) / - (not enough datas). Items to be created.
    Example
    ⟨ abondance (Q322890)      ⟩ FAO status Search ⟨ Not a risk ⟩
    Format and edit filter validation(exemple : 7 chiffres peuvent être validés avec le filtre d'édition Special:AbuseFilter/17)
    SourceHexasoft datas, FAO list
    Robot and gadget jobsdata import
    Motivation

    Is implemented into frwikis infobox, Wikidata usage on discussion. Datas from a United Nation organisation. author  TomT0m / talk page 16:03, 3 November 2015 (UTC)

    Discussion

      Support The name of the property should be FAO conservation status, in my opinion. Domain is wrong, and should be breed (Q38829). Allowed values should be the “FAO conservation status” item. C.f. Property_talk:P141. Tinm (talk) 18:12, 3 November 2015 (UTC)

      corrected author  TomT0m / talk page
      Support. Joe Filceolaire (talk) 23:43, 3 November 2015 (UTC)
      Support Mirgolth (talk) 08:49, 4 November 2015 (UTC)
      Support Very useful data at all levels. Little risk of error due to the name (there's no latin name for domestic breeds) --Tsaag Valren (talk) 17:20, 4 November 2015 (UTC)
      Support Jérémy-Günther-Heinz Jähnick (talk) 09:32, 21 November 2015 (UTC)

      Comment @TomT0m: This proposal looks well supported and I would like to create the property as my first experience at property creation :) However, a couple of things before I do that: (1) I think the name (en at least) should be "FAO risk status" - in the FAO documentation I looked at it seems to be referred to with that combination of terms most often, and I think that clarifies what it is for. (2) The target items need to be created - at the least the "not at risk" item for the example. I will go ahead and do that unless it's already been done. I'll probably work on this around 20 hours from now, so please make a note here if you have other ideas or want me to wait. Thanks! ArthurPSmith (talk) 22:02, 30 November 2015 (UTC)

      Done ArthurPSmith (talk) 20:34, 1 December 2015 (UTC)

    Musopen composer identifier

    DescriptionMusopen.org composer identifier
    RepresentsMusopen (Q2572292)
    Data typeString
    DomainPersons
    Allowed valuestext
    ExampleWolfgang Amadeus Mozart (Q254) => wolfgang-amadeus-mozart
    Sourcehttps://musopen.org/music/
    Formatter URLhttps://musopen.org/composer/$1/
    Robot and gadget jobscould be added by bot since the identifiers in urls are consistent
    Proposed byWesalius (talk)
    Discussion

    Musopen.org hosts PD lincensed rercordings and sheet music of classical composers. Wesalius (talk) 12:48, 30 January 2015 (UTC)

      Comment actually Mozart is known as composer of recorded music https://musopen.org/music/composer/wolfgang-amadeus-mozart/ and as composer of sheet music https://musopen.org/sheetmusic/composer/wolfgang-amadeus-mozart/ and fortunately(?) the biographical sketches indicate that someone is aware of the two being the same person. -- Gymel (talk) 17:36, 24 February 2015 (UTC)
    I just noticed https://musopen.org/composer/wolfgang-amadeus-mozart/ dedicated to both (listing "most popular" entries). Thus the name forms are identical by design. -- Gymel (talk) 18:01, 24 February 2015 (UTC)
    formatter URL added. Is that the best choice? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:49, 6 March 2015 (UTC)
    I've added a trailing slash to the formatter URL, since https://musopen.org/composer/wolfgang-amadeus-mozart just redirects to https://musopen.org/composer/wolfgang-amadeus-mozart/ for me and I don't see any point in linking to something which redirects if it can easily be avoided. - Nikki (talk) 13:05, 1 May 2015 (UTC)

    @Wesalius, Gymel, Nikki, Runner1928:   Done Musopen composer ID (P2338) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:45, 23 November 2015 (UTC)


    World of Shakespeare ID

       Not done
    Descriptionpage ID at World of Shakespeare website
    RepresentsElectronic Encyclopedia World of Shakespeare (Q19959941)
    Data typeString
    Template parameternone, will be supported by Template:Authority control (Q3907614) in ruwiki
    Domainany
    Allowed values[0-9]+
    ExampleVladimir Vysotsky (Q512) => 4284
    Format and edit filter validationshall be unique
    Sourceruwiki articles, site itself
    Formatter URLhttp://www.world-shake.ru/ru/Encyclopaedia/$1.html
    Robot and gadget jobswill be supported by "WEF: External Links" gadget
    Motivation

    Another good and reliable source. VlSergey (gab) 11:31, 21 May 2015 (UTC)

    Discussion
    •   Weak oppose To be clear, this is a (very) miniature version of what one may find on Wikipedia. I see a few issues with this specific website. 1. its title makes you think of everything about Shakespeare, but it's mainly where Russia intersects with Shakespeare, excluding most important information. 2. It still seems to be in its infancy and doesn't cover many topics, but does cover topics such as "Shakespeare in Russia." 3. The ID for the article in Russian is not the same ID for the article in English. For the example above, the English ID is 4360 (vs. 4284), so the URL is http://world-shake.ru/en/Encyclopaedia/4360.html. Nonetheless, if we only care about the Russian language section, this is moot. 4. I saw at least two likely copyright violations on the website, specifically with images. I only browsed a few pages so they may be the only ones. While it's not against policy as far as I know, it is still something we should keep in mind when linking to external sites. On the other hand, the site seems to be on the right track and has a plethora of references in each article, some inline, some not, so in some ways. Hazmat2 (talk) 22:47, 21 May 2015 (UTC)
    •   Oppose per above. Diego Grez-Cañete (talk) 05:16, 16 October 2015 (UTC)

      Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:48, 23 November 2015 (UTC)


    Swedish Film Database

    Swedish Film Database film ID

    DescriptionSwedish database of films
    RepresentsSwedish Film Database (Q1139587)
    Data typeString
    Template parametersfdb in sv:Mall:Filmfakta
    Domainfilm (Q11424)
    Allowed valuesnumbers
    ExampleSimple Simon (Q1659521) → 69473
    Formatter URLhttp://www.sfi.se/sv/svensk-filmdatabas/Item/?type=MOVIE&itemid=$1
    Motivation

    Used widly on sv.wp and is a database of films and actors etc. (also see sv:Mall:SFDb; a common acronym used for this database is SFDb) (t) Josve05a (c) 22:28, 12 September 2015 (UTC)

    Discussion

    Swedish Film Database company ID

    DescriptionSwedish database of companies related to films
    RepresentsSwedish Film Database (Q1139587)
    Data typeString
    Allowed valuesnumbers
    ExampleAnagram Produktion (Q10410032) → 348624
    Formatter URLhttp://www.sfi.se/sv/svensk-filmdatabas/Item/?type=COMPANY&itemid=$1
    Motivation

    Used widly on sv.wp and is a database of films and actors etc. (also see sv:Mall:SFDb; a common acronym used for this database is SFDb) (t) Josve05a (c) 22:28, 12 September 2015 (UTC)

    Discussion

    Swedish Film Database music ID

    DescriptionSwedish database of music related to films
    RepresentsSwedish Film Database (Q1139587)
    Data typeString
    Allowed valuesnumbers
    ExampleTitanic (Q10698747) → 2578
    Formatter URLhttp://www.sfi.se/sv/svensk-filmdatabas/Item/?type=MUSIC&itemid=$1
    Motivation

    Used widly on sv.wp and is a database of films and actors etc. (also see sv:Mall:SFDb; a common acronym used for this database is SFDb) (t) Josve05a (c) 22:28, 12 September 2015 (UTC)

    Discussion

    Swedish Film Database group ID

    DescriptionSwedish database of groups related to films
    RepresentsSwedish Film Database (Q1139587)
    Data typeString
    Allowed valuesnumbers
    ExampleABBA (Q18233) → 173225
    Formatter URLhttp://www.sfi.se/sv/svensk-filmdatabas/Item/?type=GROUP&itemid=$1
    Motivation

    Used widly on sv.wp and is a database of films and actors etc. (also see sv:Mall:SFDb; a common acronym used for this database is SFDb) (t) Josve05a (c) 22:28, 12 September 2015 (UTC)

    Discussion

    BoardGameGeek ID

    DescriptionID number for a board game in BoardGameGeek
    Template parameterapparently none, but see en:Istanbul (board game)#External links, where en:Template:Bgg title is used
    Domainboard games (Q131436)
    Allowed valuesnumbers
    Sourceexternal reference, Wikipedia list article, etc.
    Robot and gadget jobsPossibly
    Motivation

    BoardGameGeek seems to be the database for board games. Palnatoke (talk) 09:06, 4 October 2015 (UTC)

    Discussion

    @Palnatoke, Filceolaire, Runner1928:   Done BoardGameGeek ID (P2339). Datatype is "string". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:02, 23 November 2015 (UTC)


    YSO identifier

       Done: YSO ID (P2347) (Talk and documentation)
    Domainany (but not people or purely geographical places, though there are some buildings, airports etc)
    Robot and gadget jobsCould be validated by dereferencing the URI and checking the resulting HTTP status code
    Motivation

    The General Finnish Ontology YSO is a trilingual ontology (and/or advanced thesaurus) consisting mainly of general concepts (about 27,000 currently). The National Library of Finland would like to start mapping YSO to Wikidata. We could also contribute some data from YSO, e.g. labels in Finnish, Swedish and/or English, to Wikidata once a mapping has been established. --Osma Suominen (talk) 13:45, 27 October 2015 (UTC)

    Discussion

    @Osmasuominen, Runner1928, Popcorndude:   Done YSO ID (P2347). And Osmasuominen - thank you; it's great to have contributions from institutions like yours. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:17, 24 November 2015 (UTC)


    Agorha IDs

    IDs in Agorha a database maintained by Institut National d'Histoire de l'Art (Q3152376) and linking to other databases.

    The website layout is a bit confusing, so I ping user:Shonagon who might know a bit more about this sort of things, but I think I can prpose three propertes as the permalink structure appears to be straightforward for these: --Zolo 5 nov / copiededited 8 nov 2015

    Agorha person/institution ID

    Descriptionidentifier for a person or institution in the Agorha database
    Data typeString
    Domainhumans or institutions
    Allowed valuesintegers
    Example
    Formatter URLhttp://www.purl.org/inha/agorha/002/$1
    Robot and gadget jobsmix'n'match

    Agorha work ID

       Done: AGORHA work ID (P2344) (Talk and documentation)
    DescriptionAgorha work ID
    Data typeString
    Domainworks of art
    Allowed valuesintegers
    ExampleMona Lisa (Q12418) -> 12544
    Formatter URLhttp://www.purl.org/inha/agorha/003/$1
    Robot and gadget jobsmix'n'match

    Agorha event ID

    DescriptionAgorha event ID
    Data typeString
    Domainevents
    Allowed valuesintegers
    ExampleManet (Q15630512) -> 5121
    Formatter URLhttp://www.purl.org/inha/agorha/004/$1
    Robot and gadget jobsmix'n'match

    Proposal format

    @Zolo: Please complete the template for each of these nominations. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:44, 5 November 2015 (UTC)
    @Pigsonthewing: once again, what's the point of adding {{Property documentation}} here ? It would not add any useful information, and would arguably blur the connection between the three proposed properties (perhaps we should just have one property or whatever). --Zolo (talk) 15:42, 6 November 2015 (UTC)
    @Zolo: Once again, this was explained to you on 19 October, by User:Nikki. Your continued obstinacy in this matter is unbecoming of an admin. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:55, 6 November 2015 (UTC)
    @Pigsonthewing: as you can see I had replied to Nikki at the time, and so had Jura. The template would not add anything relevant for this proposal, just translate a few words, so few that it couldn't possibly include more people in the discussion. You can't assume I will comply with your request if you are unable to provide a rationale. --Zolo (talk) 07:50, 7 November 2015 (UTC)
    Interesting discussion! @Zolo: - I think you should go ahead and create those proper requests because that needs to be made in oder to complete the property (and the property will link back to this page). Not doing so just forces Andy to do it for you, which I just see as being impolite and putting the burden on the admin rather than the proposer. --Jane023 (talk) 10:05, 8 November 2015 (UTC)
    Andy has visibly no intention to add the template, and I am certainly not suggesting that he should. I would just like to know why it would be helpful to add it in this case. Afaik, the only recent discussion on the topic was in the mix'n'match section of Wikidata:Property proposal/Archive/39, and that was inconclusive at best.
    Now that there are statements on properties, mechanically copying the template from the proposal page should be avoided, as it adds a lot of redundant data that need to be cleaned up. If you look at the latest properties I created like Property talk:P2266, it does not reuse anything from the template from the discussion, nor should it. Had there be no template like here, things would have been done exactly the same way. --Zolo (talk) 10:53, 8 November 2015 (UTC)
    What seems even more problematic is that if you use the template, Pigsonthewing edits the content of the proposal template without noting the changes in the comments making it difficulte to determine what people agreed to (Diff). --- Jura 11:24, 8 November 2015 (UTC)
    Jura1 is upset because I fixed some formatting errors in a proposal he recently made. This is normal, and I reminded him on my talk page that he doesn't "own" the proposal. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:53, 8 November 2015 (UTC)
    I wasn't even involved in the proposal mentioned in the diff. --- Jura 13:55, 8 November 2015 (UTC)
    No-one said you were. The diff shows me in the process of cleaning up the template having created the property; as required by the appropriate process (Point 5 at Wikidata:Property creators#Steps when creating properties), and as every template creator should do. Nonetheless, my point about our recent interaction remains valid. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:02, 8 November 2015 (UTC)
    I think you misunderstand the outlined process. Probably because you didn't attempt to follow it. Obviously, I disagree with you doing such edits. --- Jura 14:13, 8 November 2015 (UTC)
    Jane's point is valid, but it is not necessarily me who would have to do the work; whoever creates the property would have had to create the templates, due to Zolo's disruptive refusal to do so. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:58, 8 November 2015 (UTC)
    Let's be creative. Why not divide the process into two steps : formal acceptance after the initial discussion, then creation by the proposer of the required template as a required step before the creation ? A proposal is sometime not mature enough to create the template before discussion, and the template creation is a waste of time if the proposal is rejected. author  TomT0m / talk page 14:07, 8 November 2015 (UTC)
    Because that would deprive us of the benefits of using the template from the outset; and because there is no guarantee that a proponent would return to carry out such a task; or if they did, that they would do so in a timely manner. When used properly, the current process works well (further: no cogent argument has been made that it does not; much else evidence been provided). But again, you are welcome to make such a proposal in the appropriate place, for the community to consider. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:56, 8 November 2015 (UTC)
    @Pigsonthewing: Seriously, you really think that there is evidences that all this process works fine ? Well, just compare the number of infoboxes not migrated yet ... This is so sloooooow ... I can show proposals of mine a year old ... I could read mockeries of wikipedians mock the bureaucraty required to create a single property. author  TomT0m / talk page 20:02, 8 November 2015 (UTC)
    Please explain how not using the template would improve the issues you describe - or indeed how u`sing it causes them. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 01:02, 9 November 2015 (UTC)

    This is a waste of time and energy. I just added the templates. Please do come up with a better way of handling this in the future, but not here. Probably better to move this to Wikidata talk:Property proposal. Maybe create a template like {{Proposed property}} in which you fill out all the information. Once you created the property the template will suggest the missing claims to be added and the contents of the {{Property documentation}} to be added to the talk page. Multichill (talk) 11:54, 8 November 2015 (UTC)

    Thanks for doing it, I have copied that to Wikidata talk:Property proposal--Zolo (talk) 13:41, 8 November 2015 (UTC)
    The better way of handling this is for Zolo to use the standard template in his proposals; as he has been requested to do several times, and not just by me. He is disrupting this page to make a point. If he thinks the template is subomptimal, he is welcome to suggest changes to it (or indeed, its deletion), in order that the community can reach consensus as to whether those changes should be made; or whether the previous consensus, which resulted in this template, holds. Both he and you are admins, and so should be aware that this is how Wikidata works. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:53, 8 November 2015 (UTC)
    Better pursue this off-topic discussion at Wikidata talk:Property proposal. Just some quick clarifications as I find your reaction really puzzling. I have no wish to change the property documentation template. The way Wikidata works is that we need not follow rules when none was ever decided, and none was for the property proposal format. Prior to this discussion, only one other user said we I should have added the template. I had explained why I had not, and a third user supported me, and nothing beyond that. Were it not for your puzzling reaction, there would not have been much disruption. Ok that's all for me here. --Zolo (talk) 23:29, 8 November 2015 (UTC)
    Consensus clearly exists for the process (including use of the template) outlined at the top of this and all its sister pages. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 01:09, 9 November 2015 (UTC)

    Discussion

    We noticed there was a problem with the RKDI database on Mix-n-Match - most of the automatches are incorrect - presumably these have been matched incorrectly (or something went wrong when the database was loaded by Magnus). The issue occurs at the moment the user selects the property. You need to look not just for RKD but also the suffix (@Jheald: discussed user notes for this recently on the Wikidata mailing list). --Jane023 (talk) 11:01, 8 November 2015 (UTC)
    • I think it's probably essential to have different properties, because they have different formatters. It would be horrible to have to work out the type of a thing before you could format its URL. It also would very confusing, if the numerical ranges overlap, to have the same value on a single property apparently applying to a number of different things (and make it harder to implement "unique value" constraint violations).
    At the moment we have Art UK artist ID (P1367), Art UK collection ID (P1751), Art UK venue ID (P1602) and Art UK artwork ID (P1679). Those don't appear to have caused any difficulty with data entry; and most uses of a wrong property on a particular kind of item will trigger a constraint violation. There may be a problem if the number of properties associated with a particular institution becomes larger than the size of the drop-down box, but we've not reached that extent here. Jheald (talk) 11:11, 8 November 2015 (UTC)
    Propose to rename to "FR Agorha ... ID" (including the country code)
    Agree with @Jane023: that this proliferation of props calls for some reorganization in the future. The formatter can take 2 params: authority and kind, and for each authority we need a table which kinds it supports. But this will make adding instances so much more difficult. (Note: don't call this "sub-properties" or you'll make a big confusion with rdfs:subPropertyOf). --Vladimir Alexiev (talk) 10:15, 9 November 2015 (UTC)


    Speedskatingbase.eu ID

    Template parameterid in w:no:Template:Speedskatingbase
    Domainhuman
    Robot and gadget jobscould be added to mix'n'match
    Motivation

    49696 entries, could be used to expand items about speed skaters. Sjoerd de Bruin (talk) 19:11, 11 November 2015 (UTC)

    Discussion
    •   Support. There should be personal best times for the most of notable speed skaters on Wikipedia, although the site has set some time-limits for inclusion, so it might exclude some few from the early period of speed skating round the year of 1900. I really think it is a great resource for speed skater articles. Migrant (talk) 19:34, 11 November 2015 (UTC)

    @Sjoerddebruin, Migrant, Filceolaire, Knuteinar2309:   Done SpeedSkatingBase.eu ID (archived) (P2350) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:43, 24 November 2015 (UTC)

    Elonet ID for a movie

    Template parameterWikipedia infobox parameters, "Elonet" parameter in the movie template

    Elonet is a web version of The Finnish National Filmography. Useful. Stryn (talk) 14:42, 13 November 2015 (UTC)

    Discussion

    @Stryn, Filceolaire, Máté:   Done Elonet movie ID (P2346) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:03, 24 November 2015 (UTC)


    UNESCO endangered language ID

    DomainLanguages ( items with instance of (P31) language (Q34770) )
    Allowed valuesString pattern: Only numerical characters
    Motivation

    We have been given access to the endangered languages list by UNESCO, and this property will allow us to match languages on the list to Wikidata items using Mix 'n' Match. Also allows links to be generated to the individual languages pages on the UNESCO website NavinoEvans (talk) 17:39, 19 November 2015 (UTC)

    Discussion

    @NavinoEvans, Runner1928, Filceolaire:   Done UNESCO Atlas of the World's Languages in Danger ID (P2355) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:21, 26 November 2015 (UTC)

    AIATSIS Code

       Not done
    DescriptionLanguage code in the Australian Indigenous Languages Database (AUSTLANG) maintained by the Australian Institute of Aboriginal and Torres Strait Islander Studies (AIATSIS)
    RepresentsAustralian Aboriginal languages (Q205143)
    Data typeString
    Template parameter"aiatsis" in en:template:infobox language
    Domainlanguage (Q315)
    Allowed valuesString pattern: [A-Z]\d+(\.(\d+|[A-Z]+))?\*?
    ExampleArabana (Q3507959) → L13
    SourceAustralian Indigenous Languages Database maintained by the Australian Institute of Aboriginal and Torres Strait Islander Studies
    Formatter URLhttp://austlang.aiatsis.gov.au/main.php?code=$1
    Robot and gadget jobsAIATSIS Codes could be scraped from the Australian Indigenous Languages Database, and mix-and-match used to import into Wikidata
    Motivation

    The Australian Aboriginal languages comprise up to twenty-seven language families and isolates native to the Australian Aborigines of Australia. In the late 18th century, there were between 350 and 750 distinct Aboriginal social groupings, and a similar number of languages or dialects. At the start of the 21st century, fewer than 150 Indigenous languages remain in daily use, and all except roughly 20 are highly endangered. The Australian Institute of Aboriginal and Torres Strait Islander Studies (AIATSIS) is an independent Australian Government statutory authority. It is a collecting, publishing and research institute and is considered to be Australia's premier resource for information about the cultures and societies of Aboriginal and Torres Strait Islander peoples. AUSTLANG is therefore perhaps the best catalogue of Aboriginal languages. Dhx1 (talk) 03:06, 22 November 2015 (UTC)

    Discussion

      Not done - AUSTLANG code (P1252) already exists, with the same formatter URL and alias. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:18, 26 November 2015 (UTC)

    Oops, didn't see AUSTLANG code (P1252) as already existing, I must have searched incorrectly. Thanks for finding the duplicate, and apologies for wasting time. Dhx1 (talk) 01:01, 27 November 2015 (UTC)

    Classification of Instructional Programs code

    Domainacademic discipline (Q11862829)
    Robot and gadget jobsimport from freely available database, United States Department of Education (Q861556)
    Motivation

    "The Classification of Instructional Programs (CIP) provides a taxonomic scheme that supports the accurate tracking and reporting of fields of study and program completions activity. CIP was originally developed by the U.S. Department of Education's National Center for Education Statistics (NCES) in 1980, with revisions occurring in 1985, 1990, and 2000." The current CIP is from the year 2010. This is the official taxonomy of educational fields of study for the US government, and all colleges and universities have to report graduates based on these values. CIP codes are also hierarchical: 01 is agriculture (Q11451), 01.09 is animal science (Q168091), and 01.0906 is animal nutrition science (Q4764962). This directly maps to Wikidata's instance of (P31) and subclass of (P279) schema. With this data, and creating missing academic discipline (Q11862829) entities, we can better support academic major (P812) as well. Runner1928 (talk) 19:02, 11 November 2015 (UTC)

    Discussion
      Support This certainly seems useful. ArthurPSmith (talk) 19:40, 11 November 2015 (UTC)

    @Runner1928, ArthurPSmith, Filceolaire:   Done Classification of Instructional Programs code (P2357) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:45, 26 November 2015 (UTC)


    Soccerway player id

    DescriptionPlayer id on the Soccerway website
    Data typeString
    Template parameter|1= or |id= in en:Template:Soccerway; equivalent templates in other language Wikipedias
    Domainhuman
    ExampleJavier Saviola (Q186071) → javier-saviola/121
    SourceWikipedia templates or searching the website
    Formatter URLhttp://www.soccerway.com/players/$1
    Robot and gadget jobsBots could import from templates
    Motivation

    Soccerway is a website that gives information, results and statistics about domestic and international soccer. We also have templates in quite a few Wikipedias with apparently equivalent templates, that could potentially be imported from. Silverfish (talk) 23:56, 31 October 2015 (UTC)

    Discussion


    ODIS ID

       Done: ODIS ID (P2372) (Talk and documentation)
    DescriptionIdentifiers in the Belgian ODIS (Q3956431) database
    Data typeString
    Domainperson, organization, event, building
    Allowed valuesstring of letters and numbers.
    • OR_(number) for organizations
    • EV_(number) for events
    • OB_(number) for buildings
    • PS_(number) for people
    ExampleJos De Swerts (Q2465723) → PS_21852
    Sourcehttp://www.odis.be/hercules/advancedSearch.php
    Formatter URLhttp://www.odis.be/lnk/$1
    Robot and gadget jobsWould be great to be included in Mix'n'Match
    Motivation

    Extensive database of important people and organizations in Belgium's social and cultural history. I found ~8,200 organizations, 22 families (not sure how relevant these are), 122 events, ~2,000 buildings (mostly churches), ~43,000 persons. Spinster (talk) 17:55, 8 November 2015 (UTC)

    Discussion

    @Spinster, Runner1928, Vladimir Alexiev, Filceolaire:   Done ODIS ID (P2372) — Ayack (talk) 11:23, 2 December 2015 (UTC)

    CESAR person ID

    Domainpeople
    Allowed values6 digits
    Robot and gadget jobsmix'n'match?

    7023 persons. — Ayack (talk) 19:52, 8 November 2015 (UTC)

    Discussion

    @Ayack, Runner1928, Magnus Manske, Filceolaire:   Done CESAR person ID (P2340) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:35, 23 November 2015 (UTC)

    Database of Scientific Illustrators ID

    Domaindeceased humans; illustrators of scientific publications of all genres (especially atlases, articles, textbooks)
    Sourceexternal reference, Wikipedia list article, etc.
    Robot and gadget jobsCurrently in Mix'n'match (~2000 identified)
    Motivation

    The Stuttgart Database of Scientific Illustrators 1450–1950 (Q21417186) includes records of "more than 10400 illustrators in natural history, medicine, technology and various sciences in more than 100 countries, active between c.1450 and 1950". As shown by the example given above, it includes URLs for Wikipedia articles; and VIAF IDs. Other entries include Wikimedia Commons URLs. One this property is created, I will ask the University to provide a data dump which we can parse for such URLs; and once we have parsed and imported them, invite the University to also include Wikdiata IDs. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:28, 9 November 2015 (UTC)

    Discussion
      Support Magnus Manske (talk) 13:30, 9 November 2015 (UTC)
      Support --Daniel Mietchen (talk) 14:05, 9 November 2015 (UTC)
      Support. Joe Filceolaire (talk) 08:18, 11 November 2015 (UTC)
      Support, looks good (will remove duplicate request). Andrew Gray (talk) 21:02, 24 November 2015 (UTC)

    @Magnus Manske, Daniel Mietchen, Filceolaire, Andrew Gray:   Done Stuttgart Database of Scientific Illustrators ID (P2349) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:17, 24 November 2015 (UTC)

    chemical exposure properties

    recommended time-weighted average exposure limit

       Withdrawn
    Descriptionnon-binding recommended concentration for chemical exposure in a workplace in a given work day
    Representstime-weighted average concentration (Q21010836)
    Data typeNumber (not available yet)
    Domainchemicals
    Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); duration (i.e. length of workday used in measurement) maintained by (P126) as qualifier
    Examplebutyl acetate (Q411073) → 0.00071 gram per litre (Q834105); maintained by (P126) → National Institute for Occupational Safety and Health (Q60346); duration → 10 hour (Q25235)
    SourceNIOSH pocket guide to chemical hazards, 2005 edition, 3rd printing (Q20022913) for U.S. values; potentially other sources as well
    Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
    Motivation

    James Hare (NIOSH) (talk) 20:22, 21 October 2015 (UTC)

    This proposal has been made obsolete. James Hare (NIOSH) (talk) 15:05, 1 December 2015 (UTC)
    Discussion
    See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)
    James: While the NIOSH limits may be non-binding recommendations, other countries may have legally binding limits. Will this property be usable for both cases? Joe Filceolaire (talk) 01:40, 4 November 2015 (UTC) Oops. Just noticed the the legal limit property just above. Joe Filceolaire (talk) 01:42, 4 November 2015 (UTC)

    recommended ceiling exposure limit

       Withdrawn
    Descriptionnon-binding recommended maximum concentration for chemical exposure in a given work day
    Representsceiling concentration (Q21010844)
    Data typeNumber (not available yet)
    Domainchemicals
    Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); maintained by (P126) as qualifier; duration and route of administration (P636) as optional qualifiers
    Exampleacetylene (Q133145) → 0.002662 gram per litre (Q834105); maintained by (P126) → National Institute for Occupational Safety and Health (Q60346)
    SourceNIOSH pocket guide to chemical hazards, 2005 edition, 3rd printing (Q20022913) for U.S. values; potentially other sources as well
    Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
    Motivation

    James Hare (NIOSH) (talk) 20:22, 21 October 2015 (UTC)

    This proposal has been made obsolete. James Hare (NIOSH) (talk) 15:06, 1 December 2015 (UTC)
    Discussion
    See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)

    recommended short-term exposure limit

       Withdrawn
    Descriptionnon-binding recommended concentration for chemical exposure during a brief time window
    Representsshort-term exposure limit (Q7501690)
    Data typeNumber (not available yet)
    Domainchemicals
    Allowed valuesany number with a concentration measurement such as gram per litre (Q834105); maintained by (P126) and duration as qualifiers
    Examplebutyl acetate (Q411073) → 0.00095 gram per litre (Q834105); maintained by (P126) → National Institute for Occupational Safety and Health (Q60346); duration → 15 minute (Q7727)
    SourceNIOSH pocket guide to chemical hazards, 2005 edition, 3rd printing (Q20022913) for U.S. values; potentially other sources as well
    Robot and gadget jobsPart of mass importation of the Pocket Guide to Chemical Hazards into Wikidata.
    Motivation

    James Hare (NIOSH) (talk) 20:22, 21 October 2015 (UTC)

    This proposal has been made obsolete. James Hare (NIOSH) (talk) 15:06, 1 December 2015 (UTC)
    Discussion
    See general discussion at the head of this section Joe Filceolaire (talk) 00:57, 4 November 2015 (UTC)


    R phrase

       Not done
    DescriptionEU risk phrases for chemical safety
    Data typeString
    Template parameterRPhrases in en.wp chembox
    Domainchemicals
    Allowed valuesString beginning with R, ending in numbers
    Example1,2-Dibromo-3-chloropropane -> R45, R46, R60, R25, R48/20/22, R52/53
    Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    Sourceexternal references
    Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
    Motivation

    Widely used infobox paramter on en.wp, should be indexed in Wikidata. Emily Temple-Wood (NIOSH) (talk) 18:54, 22 October 2015 (UTC)

    Discussion
      Oppose S phrases are not more valid as labeling according to EU regulation. Starting June 2015 only GHS labels are used. All values about S phrases are deprecated and I don't think this is the job of WD to archive all deprecated values especially when they are imported as deprecated. Snipre (talk) 08:28, 23 October 2015 (UTC)
    This statement is partly incorrect. Mixtures classified, labelled, packaged already placed on the market before 1 June 2015 are not required to be relabelled and repackaged in accordance with the CLP Regulation until 1 June 2017. Even after that date, articles such as cleaning products may be found in many households. --Leyo 01:31, 17 November 2015 (UTC)
    If you want to play with the words but you can't discuss the fact that starting June 2015 the GHS is the unique labelling system valid in EU (see ECHA, first lines: "From 1 June 2015, the Classification, Labelling and Packaging (CLP) Regulation will be the only legislation to apply to the classification and labelling of both substances and mixtures.". What you mentioned is a transient agreement for chemicals produced before the date. Temporary exception due to logistic reality doesn't modify the facts that you can't produces any chemical with the old label even if you can ensure the use of this product before 2017 and that all modifications of labelling between July 2015 and now are not more translated in the old system). Snipre (talk) 02:51, 17 November 2015 (UTC)
      Oppose same reason --Almondega (talk) 11:54, 2 November 2015 (UTC)
      Oppose. Though I do think we should create items for every S and R phrase so that when you find a bottle covered in dust at the back of the cupboard you can find out what it meant back in the day. What we should not do is give obsolete info on the items for the chemicals. Joe Filceolaire (talk) 01:12, 4 November 2015 (UTC)
    We can always use the rank deprecated to specify that the values are not more valid but I think we should keep the deprecated rank to filter data in the case where some are at least valid and some not. If R and S phrases were absolute we could do it but as safety data is improving with time these data are relative to a special system and a defined knowledge at time t. Snipre (talk) 12:58, 4 November 2015 (UTC)

      Not done no support --Pasleim (talk) 23:34, 28 November 2015 (UTC)

    S phrase

       Not done
    DescriptionEU safety phrases for chemical safety
    Data typeString
    Template parameterSPhrases in en.wp chembox
    Domainchemicals
    Allowed valuesString beginning with S, ending in numbers
    Example1,2-Dibromo-3-chloropropane -> S53, S45, S61
    Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    Sourceexternal references
    Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
    Motivation

    Widely used infobox paramter on en.wp, should be indexed in Wikidata. Emily Temple-Wood (NIOSH) (talk) 18:55, 22 October 2015 (UTC)

    Discussion
      Oppose S phrases are not more valid as labeling according to EU regulation. Starting June 2015 only GHS labels are used. All values about S phrases are deprecated and I don't think this is the job of WD to archive all deprecated values especially when they are imported as deprecated. Snipre (talk) 08:28, 23 October 2015 (UTC)
      Oppose same reason --Almondega (talk) 11:55, 2 November 2015 (UTC)
    See comment above. --Leyo 01:34, 17 November 2015 (UTC)
      Not done no support --Pasleim (talk) 23:35, 28 November 2015 (UTC)


    antagonist muscle

    Description...
    Data typeItem
    Template parameter"Antagonist" in en:template:infobox muscle
    Domainmuscles
    Allowed valuestext
    Examplebiceps femoris muscle (Q601016) → quadriceps femoris muscle (Q504536)
    Sourceinfobox muscle parameter
    Motivation

    These paired relations between muscles and their antagonists are well-defined, and currently absent. --Wesalius (talk) 06:38, 10 November 2015 (UTC)

      Support Seems reasonable and useful --I9606 (talk) 16:15, 10 November 2015 (UTC)

    Discussion

      Notified participants of WikiProject Medicine


    applies to taxon

    Descriptionqualifier for toxicological concentrations and doses, indicates species in which the drug was tested
    Data typeItem
    Template parameter"LD50" in en:Template:Chembox_Hazards
    Domainmolecular entity (Q2393187), e.g. chemical substance (Q79529), chemical compound (Q11173), medication (Q12140), cation (Q326277), anion (Q107968), mixture (Q169336) .
    Allowed valuestaxon (Q16521)
    Examplepotassium cyanide (Q192470) → median lethal dose (LD50) (P2240) (11 mg/kg) → route of administration (P636) (subcutaneous injection (Q2035485)) + species (house mouse (Q83310))
    Sourcesafety data sheet (Q222067), section 11
    Proposed byAlmondega (talk) 14:43, 12 October 2015 (UTC)
    Motivation

    Wikidata qualifier (Q18615010) of median lethal dose (LD50) (P2240).

      Notified participants of WikiProject Chemistry

      Notified participants of WikiProject Medicine--Almondega (talk) 14:27, 12 October 2015 (UTC)

    Discussion
      Comment @Almondega: I think a different label would be good, because we don't always link to the species of the animal (also genus etc.). Also there would be the danger of users misusing it as a property and causing problems with the taxonomy properties. Would "animal model" or "model animal" be the better name? Maybe even "observed in animal model"? --Tobias1984 (talk) 17:39, 12 October 2015 (UTC)
    or simply taxon ? Assuming species or genus are kind of taxons. Animal would suggest it's to link to an instance of animal. author  TomT0m / talk page 17:43, 12 October 2015 (UTC)
    @TomT0m: I think longer labels are much easier to understand in a semantic database, because the claims then complete a sentence. "Taxon" "Mouse" means almost nothing in my opinion. And using labels that are close to taxonomy, will result in more conflicts. For example the item Citrus × limon (Q500) can be viewed from a food or taxonomy perspective. But we can only have one label, so the conflict is between "Citrus ×limon" and "lemon". Similar for chemical compounds that are also used in pharmaceutics. People would use a property "taxon" for a lot of different things. Especially with the qualifiers I tend to think we should provide unambigeous clarity. --Tobias1984 (talk) 18:00, 12 October 2015 (UTC)
    @Tobias1984: "applies to taxon" then. I can understand the need of clear guideline, I'm a little bit more skeptical on having a lot of very closely called properties because it leads to more confusion of one each other. We have a lot of questions "which property should I use, this one or that one ?",

    so I think it actually would not hurt that taxonomy and this field would share a property if the only difference in their use is the field they apply to. Imagine in molecular biology that a protein or some hormon has a specific effect on some kind on animal, or if in taxonomy one has to specify on which taxon a claim is valid, what's the harm to use this qualifier ? How useful would it be to create qualifier "applies to taxon but only if the claim is in the taxonomy" and "applies to taxon if we're talking about a drug" ? author  TomT0m / talk page 18:15, 12 October 2015 (UTC)

    I concur with Tobias1984 that 'species' is far to broadly used a term in other senses to bind it to a property with this specificity. I also think that TomT0m is right to shoot for properties that are fairly general and multi-purpose at this stage in the game. I think a qualifier "applies to taxon" would work for this particular application and would be generally useful in other biological settings. --I9606 (talk) 18:45, 12 October 2015 (UTC)

      Comment One more : you might want to replace the main snak of all this, and make the taxon the main value of the claim. There is potentially, I guess, various type of doses that might apply to the same taxon, lethal dose, mean journal dose, I don't know. Maybe it would make sense to regroup all this kind of doses in the same statement. This would give something like

    ⟨ Chemical ⟩ can be given to taxon Search ⟨ cat ⟩
    lethal dose Search ⟨ the dose ⟩
    recommanded dose Search ⟨ another dose ⟩

    . With the benefit that the rule of thumb "the main snak should make sense by itself" would be fulfilled. author  TomT0m / talk page 19:22, 12 October 2015 (UTC)

    How about "established in taxon"? - Brya (talk) 04:10, 13 October 2015 (UTC)

    :  Support @TomT0m: I think the structure you proposed would be really better. In this case, the median lethal dose (LD50) (P2240) would be a qualifier of this property "can be given to taxon". --Almondega (talk) 12:41, 19 October 2015 (UTC)  Question @TomT0m:In this structure, as may be specified route of administration (P636)? --Almondega (talk) 13:09, 19 October 2015 (UTC)

    @Almondega: You mean "how" ? I guess the same way as a qualifier would also work. If there is alternatives to give the chemical, another statement would do the trick. author  TomT0m / talk page 17:16, 19 October 2015 (UTC)
      Support --Almondega (talk) 17:22, 19 October 2015 (UTC)
    @TomT0m, Almondega: The problem of combined values structure is the references when several values for the same specie/taxon come from several sources. Snipre (talk) 12:31, 3 November 2015 (UTC)
    @Snipre: So, how do you consider the best way to enter this information? --Almondega (talk) 12:41, 3 November 2015 (UTC)
    Like a qualifier for lethal dose or lethal concentration properties. For example, for lethal concentration properties we need the specie/taxon and the duration of the exposition so the proposed structure doesn't allow to have qualifier for qualifier.
    50 lethal dose (property): 50 mg/kg (value)
    specie/taxon (qualifier): rabbit (value)~
    route of administration (P636) (qualifier): oral (value)
    50 lethal concentration (property): 50 mg/l (value)
    specie/taxon (qualifier): rabbit (value)
    duration (qualifier): 20 min (value)
    route of administration (P636) (qualifier): inhalation (value)
    Snipre (talk) 13:20, 3 November 2015 (UTC)
    What solves this is to make one statement per source (that might give several numbers anyway). So this can be done as well with the previous model. With better "visual search" property because the dose does not mean anything without the species. author  TomT0m / talk page 13:24, 3 November 2015 (UTC)
    I remain uncomfortable with the label "applies to taxon"; it sounds like something that can be used in many circumstances. If the intent is as stated ("indicates [taxon] in which the drug was tested") then "established in taxon" would be better, although I would not want to claim this is necessarily the optimum wording. - Brya (talk) 17:32, 13 November 2015 (UTC)
    @Brya, Snipre, Tobias1984: I see no problem in this qualifier be used in other circumstances in which a qualifier "applies to taxon" is useful. --Almondega (talk) 01:03, 14 November 2015 (UTC)
    Maybe not. I just hope it does not cause confusion. - Brya (talk) 09:07, 14 November 2015 (UTC)
    We need a property creator. @Jonathan Groß: ? Snipre (talk) 15:40, 25 November 2015 (UTC)
    @Snipre: not today and not until next week, I'm afraid ... I'll be abroad. Jonathan Groß (talk) 16:34, 25 November 2015 (UTC)
    @Danrok, Joshbaumgartner, Pamputt, Pigsonthewing:? Snipre (talk) 19:49, 25 November 2015 (UTC)
    I will create this one. Danrok (talk) 21:08, 25 November 2015 (UTC)


    Köppen–Geiger climate classification system

       Not done
    DescriptionKöppen climate classification is one of the most widely used climate classification systems. It was first published by Russian German climatologist Wladimir Köppen in 1884, with several later modifications by Köppen himself, notably in 1918 and 1936. Later, German climatologist Rudolf Geiger collaborated with Köppen on changes to the classification system, which is thus sometimes referred to as the Köppen–Geiger climate classification system.
    RepresentsKöppen climate classification (Q124095)
    Data typeString
    Template parameterWikipedia infobox parameters, if any; ex: "population" in en:template:infobox settlement
    Domaintypes of items that may bear this property
    Allowed valuesFirst alphabet is A-E (upper case); altogether are: Af, Am, Aw, BWh, BWk, BSh, BSk, Csa, Csb, Cwa, Cwb, Cwc, Cfa, Cfb, Cfc, Dsa, Dsb, Dsc, Dsd, Dwa, Dwb, Dwc, Dwd, Dfa, Dfb, Dfc, Dfd, ET, EF
    Example
    Format and edit filter validation(sample: 7 digit number can be validated with edit filter Special:AbuseFilter/17)
    SourceKöppen climate classification
    Robot and gadget jobsShould or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
    Motivation

    (Add your motivation for this property here.)

    – ;Discussion Unbuttered Parsnip (talk) 12:07, 26 November 2015 (UTC)

      Not done Duplicate of an earlier proposal. @Unbuttered Parsnip, Thryduulf, TomT0m: please comment at Wikidata:Property proposal/Place#climate 2 Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:05, 27 November 2015 (UTC)


    Spacecraft code

       Not done
    DescriptionCode for this spacecraft (qualifiers)
    Data typeString
    ExampleApollo 8 (Q184201) -> spacecraft -> Apollo Command/Service Module -> Spacecraft code (qualifiers) -> 103
    Soyuz TMA-15M (Q610681) -> spacecraft -> Sojuz-TMA -> Spacecraft code (qualifiers) -> 11F732A47 No.715
    SourceNasa web site, other
    Proposed by--Adert (talk) 12:24, 6 May 2015 (UTC)
    Discussion

    The spacecraft for Apollo 8 (Q184201) (for example) should not be "Apollo Command/Service Module", but an item for the specific instance of that craft. The code should then be a property of that item. Someone at Wikidata:Project chat will probably tell you where to get help making the relevant queries. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:47, 6 May 2015 (UTC)

    I do not know ... In this case we have an item for any spacecraft that has flown in space ... I'm not sure it's a good idea --Adert (talk) 16:47, 6 May 2015 (UTC)
    No, we have an item for any craft that has flown a notable mission. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:01, 6 May 2015 (UTC)
    It is not a question of how many spacecraft we do or do not have items for, it is a question of whether or not this is an appropriate property to have for the items we do have or will have. Josh Baumgartner (talk) 04:28, 23 September 2015 (UTC)
      Oppose This should not be a generic property, but instead specific to the authority responsible for maintaining the code system. If the code is assigned by NASA, then we should have a property "NASA spacecraft code" or whatever they officially call their system. Likewise for other authorities. This way formatters and constraints can be tailored to the particular system the property represents. This is consistent with other authority control properties. Josh Baumgartner (talk) 04:28, 23 September 2015 (UTC)
      Oppose per Josh --Pasleim (talk) 12:32, 30 November 2015 (UTC)

      Not done no support. ArthurPSmith (talk) 21:45, 2 December 2015 (UTC)

    Eclipse properties

    Various properties required for storing data related to lunar eclipses. Some of these might be relevant to other celestial events.

    Gamma of eclipse

       Not done
    DescriptionMISSING
    Representsgamma (Q827951)
    Data typeNumber (not available yet)
    Domainlunar eclipses
    Allowed valuesa decimal number between approximately -1.5 and +1.5, specified to 3 decimal places
    Example????? -> -1.057
    SourceWikipedia list article, e.g. en:List of 21st-century lunar eclipses
    Please provide a description, and the item to which the example applies. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:10, 14 July 2015 (UTC)

      Not done Incomplete proposal; no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:59, 27 November 2015 (UTC)

    Magnitude of eclipse

       Not done
    Representsmagnitude of eclipse (Q1268559)
    Data typeNumber (not available yet)
    Domainlunar eclipses
    Allowed valuesa decimal number between approximately -3 and +3, specified to 3 decimal places
    Example-1.057
    SourceWikipedia list article, e.g. en:List of 21st-century lunar eclipses
    Please provide a description, and the item to which the example applies. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:11, 14 July 2015 (UTC)

      Not done Incomplete proposal; no support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:00, 27 November 2015 (UTC)


    conversion to SI base unit

    Descriptionconversion into to the SI base unit (Q223662)
    Data typeNumber (not available yet)
    Domainitems for units
    Allowed valuesnumber with SI base units
    Examplemillimetre (Q174789) → 0.001 metre (Q11573), inch (Q218593) → 0.0254 metre (Q11573)
    •   Support This in addition or independently of the property proposed above for "conversion into standard unit". --- Jura 09:39, 6 October 2015 (UTC)
    •   Comment Have we considered a generic "is equivalent to" property that would allow as many conversions as deemed fit? Or are people concerned with that getting out of hand? James Hare (NIOSH) (talk) 13:18, 7 October 2015 (UTC)
      • Various things have been discussed here and there, it's just that it hasn't gotten to the creation of new property. We could simply use the property "numeric value" for any conversion. The idea of this new property is to do SI conversion calculations when possible. We might need another property if there is a rounding issue involved converting between two non-SI units or if there are some units that can't be converted (reliably) into SI units. --- Jura 14:09, 7 October 2015 (UTC)
    •   Comment Maybe we can try to start using the above proposed property, and see if there really is something missing? I am not sure about that, but not sure enough to stall this proposal with an {{Oppose}}-vote. -- Innocent bystander (talk) 07:34, 8 October 2015 (UTC)
    •   Support. We need a generic "is equivalent to" (or "size") property but we also need a very specific property converting every measurement unit to SI units. This will be needed to create tools to compare measurements in various units with each other. The tools will need to go straight to this one single value property to get the info they need. If there are three different inches then they need three different items each with one claim using this property or, at worst various historic values and one current, preferred value. Joe Filceolaire (talk) 18:42, 19 October 2015 (UTC)
    • I've moved this up next to the related proposal. I'm not sure this separate property is really needed, but as a sub-property of the generic conversion property it may be worthwhile. Josh Baumgartner (talk) 18:59, 27 October 2015 (UTC)

    prison time served

       Not done
    Descriptionportion of prison sentence served
    Data typeNumber (not available yet)
    Template parameter?
    Domainpeople sentenced to prison property:"judicial sentence" (proposed above) → imprisonment (Q841236) or life imprisonment (Q68676)
    Allowed valuesnumber with unit day (Q573), week (Q23387), month (Q5151) or year (Q577)
    ExampleGünter Schabowski (Q57445) → 1 year (Q577)
    Sourceexternal reference, Wikipedia list article, etc.
    Motivation

    This is important to record for prisoners, as most do not serve the full length of their sentence in prison (parole, death, conviction overturned) Thryduulf (talk: local | en.wp | en.wikt) 16:05, 1 November 2015 (UTC)

    Discussion

    Not done - use significant event (P793), as above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:53, 20 November 2015 (UTC)

    ranking

       Withdrawn
    DescriptionA ranking withing any ordered list
    Data typeQuantity
    Template parameter"draft" in en:template:Infobox ice hockey player, "area_rank" (and similar) in en:template:Infobox country
    Domainpeople and events, main domain would probably be sports
    ExampleP. K. Subban (Q27535) was drafted by Montreal Canadiens (Q188143) <ranking> 43th overall; Stephen Kiprotich (Q1702) participated in athletics at the 2012 Summer Olympics – men's marathon (Q1798983) <ranking> 1st; Prince Joachim of Denmark (Q159101) is part of Line of succession to the Danish throne (Q1142246) <ranking> 6th
    Sourcemostly sports statistics
    Proposed byCirceus (talk) 17:55, 23 August 2013 (UTC)
    Discussion
    Josh Baumgartner (talk) 20:07, 18 November 2015 (UTC)
    @Joshbaumgartner: I don't think "part of" is appropriate in your last example. Please use a property more specific to sequences like part of the series (P179). author  TomT0m / talk page 12:47, 21 November 2015 (UTC)

    I should point out that none of the property mentioned by Josh existed when I originally proposed this. The property is now clearly superfluous and I am withdrawing the proposal accordingly. Circeus (talk) 13:14, 22 November 2015 (UTC)


    album

       Not done
    DescriptionThe album the single or song was released on
    Representsalbum (Q482994)
    Data typeItem
    Template parameter"van Album" in nl:Sjabloon:Infobox single
    Domainalbum (Q482994)
    Allowed valuesAny item that is an musicalbum
    ExamplePaint It Black (Q1046717) is on Aftermath (Q389281)
    Sourceexternal reference, Wikipedia list article (either infobox or source)
    Proposed byMbch331 (talk)
    Motivation

    Many singles are also part of an album. There is currently no way of linking these two, but as can be seen on several articles about singles, infoboxes mention the album they are part of. Mbch331 (talk) 20:13, 15 July 2015 (UTC)

    Discussion

      Support. The description sounds a bit weird to me though, the name of the album would be a string, not an item. How about something like "the album the single or song was released on"? - Nikki (talk) 21:53, 15 July 2015 (UTC)

    Thanks for the tip on the description. Altered it. Mbch331 (talk) 07:19, 16 July 2015 (UTC)
      Question why just not use part of (P361) ? We already know the subject is a single, that thé object is an album, si basically there is no need for this property. So I'd say   Weak oppose. What need to be thinked is that singles may be different version of the song however. TomT0m (talk) 11:55, 16 July 2015 (UTC)
    "Part of" is not quite correct, a single usually contains B-sides which are usually not part of the album. A single can be "part of" a discography, "part of" a series, "part of" a box set, which all imply that the single itself is part of the target item, whereas the meaning here is more "the main song of this single is taken from the linked album". - Nikki (talk) 04:52, 17 July 2015 (UTC)
      Oppose I agree with Nikki that a 'single' (which can contain b-sides) is not part of an 'album' (which contains songs), but the particular rendition of a 'song' can be both part of a 'single' and an 'album', thus linking the 'single' to the 'album' via the 'song':
    ⟨ song (Q7366)      ⟩ part of (P361)   ⟨ single (Q134556)      ⟩
    ⟨ song (Q7366)      ⟩ part of (P361)   ⟨ album (Q482994)      ⟩
    Josh Baumgartner (talk) 07:57, 20 September 2015 (UTC)

    Not done - no consensus. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:08, 17 November 2015 (UTC)


    Article ID

       Done: article ID (P2322) (Talk and documentation)
    Data typeString
    Domainarticle (Q191067)
    Allowed valuesno clear pattern across journals, though mostly alphanumeric; rather consistent within a given journal or publisher
    Format and edit filter validationperhaps on a per-journal basis
    Sourceideally, the article itself, sometimes the journal's table of contents
    Robot and gadget jobsprobably, on a per-journal basis
    Motivation

    As discussed here, the paper-age property page(s) (P304) does not necessarily make sense for articles in online journals. Many articles thus have a journal-specific article ID instead of (or sometimes in addition to) traditional page numbers. They predated DOIs and often form the basis for their article-specific parts but cannot be uniformly deduced from DOI (P356), nor do all journals that use them also have DOIs. I think the best way to handle this kind of information here on Wikidata is a dedicated property. Daniel Mietchen (talk) 04:29, 2 August 2015 (UTC)

    Discussion
    • @Pigsonthewing: A URL datatype could make sense if all of these IDs were formatted uniformly, but they vary a lot between journals and also over time within a given journal, while the format of the ID strings themselves varies less across journals and is rather stable over time. --Daniel Mietchen (talk) 22:04, 2 August 2015 (UTC)
    •   Question Definition : there seems to be stuffs to clarify here. To be usable, is'nt is implicit that it's the ID ... in the original publication ? If it's to be used that way, I think it's better to use as a qualifier of the published in (P1433) statement. A hint it's to be used that way : the article may be published in several journal, in that case the id only make sense associated to the journal it is publicated into. Another one : the meaning and type of ID may depend of the journal, think for example of a formatter URL. This would be best into the journal item for this property to stay generic ... author  TomT0m / talk page 10:06, 3 August 2015 (UTC)

    @Daniel Mietchen, Succu, Snipre, TomT0m, Lawsonstu, Filceolaire:   Done article ID (P2322) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:03, 17 November 2015 (UTC)

    item number/enumerator

       Not done
    Descriptionitem number
    Data typeString
    Template parameterNone yet AFAIK.
    Domainas qualifier for a work
    Allowed valuestypically numbers
    ExampleNu falmer skoven trindt om land (Q12329345) published in (P1433) Den Danske Salmebog, 2003 edition (Q12308040) → "729" [1]


    Motivation

    Some works such as songs are included in larger works, such as song books. The works may have identifiers within the work, such as consecutive numbers. There is a range of other properties that record similar concept but none that seems to be suitable for creative works. Other properties are inventory number (P217) and house number (P670) Finn Årup Nielsen (fnielsen) (talk) 16:44, 17 September 2015 (UTC)

    Discussion

    Not done - suitable properties already exist. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:33, 17 November 2015 (UTC)

    replied at

       Not done
    Descriptionintellectual work that directly have reactions on new works
    Data typeItem
    Domaininstance of (P31) : intellectual work (Q15621286) or its subclasses
    Allowed valuesinstance of (P31) : intellectual work (Q15621286) or its subclasses
    Example
    Motivation

    Many creative works are written in reply to previous ones. My examples refers to fiction/lyrics works, but it's concept is easily expandable to any human intellectual work. Current related properties (based on (P144), main subject (P921), inspired by (P941) and follows (P155)↔followed by (P156)) neither stores this information in complete way, neither allow any interested research to find things. This property should be completed by an reverse property, explained in next section. Lugusto (talk) 18:37, 31 October 2015 (UTC)

    Discussion
    • I'm afraid I lean against this. Instead we should just have the "replies to" property since the 'being a reply to' thing is always a property of the newer second article. The first article is not written to be responded to. Joe Filceolaire (talk) 09:59, 8 November 2015 (UTC)

      Not done No support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:34, 22 November 2015 (UTC)

    production code

    Template parameter
    Domainepisodes of a tv program
    Motivation

    With this property I can add this information to the infoboxes from Wikidata and it is used in more than one Wikipedia. I looked for properties that can be used to store that value but couldn't found any. -- Agabi10 (talk) 19:50, 31 October 2015 (UTC)

    Discussion

    @Agabi10, Filceolaire, Thryduulf:   Done production code (P2364). Presumably, this should be used with, or as, a qualifier of the issuing production company? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:24, 27 November 2015 (UTC)

    NMHH film rating

    Template parameter|korhatár= in hu:Sablon:Film infobox
    Domainfilm (Q11424)
    Allowed valuesTBC: NMHH I.  , NMHH II.  , NMHH III.  , NMHH IV.  , NMHH V.  , NMHH VI.  
    ExampleThe Man from U.N.C.L.E. (Q14488725) → NMHH III.
    Motivation

    Widely used in Hungarian Wikipedia. See also FSK film rating (P1981) and MPA film rating (P1657). Máté (talk) 07:30, 16 November 2015 (UTC)

    Discussion

    @Máté, Filceolaire:   Done NMHH film rating (P2363) Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:15, 27 November 2015 (UTC)

    Competitor number

       Not done
    DescriptionThe current number of a player
    Data typeNumber (not available yet)
    Template parameteren:template:Infobox football biography clubnumber
    Domainperson
    Allowed values0-1000
    Example 1MISSING
    Example 2MISSING
    Example 3MISSING
    SourceExternal reference, Wikipedia list article
    Robot and gadget jobsthey should be allowed
    Proposed byXaris333 (talk) 01:26, 3 May 2013 (UTC)
    Although admittedly a rare case, there have been historic cases of players being given the squad number 0. Thumperward (talk) 13:56, 3 May 2013 (UTC)
      Oppose unless broadened to be usable for all sports players who are assigned numbers. The label should be something more broadly applicable, such as 'jersey number' or maybe even 'competitor number', and the allowed values should be expanded to allow for 00 or larger numbers that are used in some sports. Thus we can avoid having a property like this for every sport. Joshbaumgartner (talk) 09:44, 9 May 2013 (UTC)
    I change it to competitor number. Xaris333 (talk) 17:09, 9 May 2013 (UTC)
      Support with implemented changes. Joshbaumgartner (talk) 13:07, 12 May 2013 (UTC)

      Not done - use sport number (P1618). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:28, 23 November 2015 (UTC)

    varietal

       Not done
    Descriptiontype of wine made primarily from a single named grape, herb or fruit variety
    Data typeItem
    DomainZinfandel (Q204433) (Zinfandel), Cabernet Sauvignon (Q207310) (Cabernet Sauvignon), Chardonnay (Q213332) (Chardonnay), Merlot (Q213338) (Merlot), apple (Q89) (apple), Pinot gris (Q778601) (Pinot gris), Sangiovese (Q509162) (Sangiovese), Tempranillo (Q519874) (Tempranillo), Pinot meunier (Q947208) (Pinot meunier), Pinot noir (Q223701) (Pinot noir) and many others from list of grape varieties (Q1357585) (List of grape varieties), etc.
    Allowed valuesQ, Text
    ExampleZinfandel wine (Q17329207) -> Zinfandel (Q204433)
    SourceList of grape varieties, Varietal
    Proposed bySarahStierch (talk)
    Discussion

    Varietals aren't "genres" and that is the closest thing I can find to what would fit for listing types of grapes, fruits, or herbs used to make wines, liquors, beers, ciders, etc. This is my first time requesting a property and I'm unsure on if I did it right, but, perhaps others interested can help improve this request. Thank you for your consideration. SarahStierch (talk) 17:18, 6 July 2014 (UTC)

      Comment: Sarah, could you give an example of how you see this property being used in a Wikidata statement? For something like Zinfandel (Q204433), we might be able to build a set of varietals with existing properties, e.g. "Zinfandel has use (P366) varietal". Other useful statements might be "Zinfandel instance of (P31) cultivar", "Zinfandel subclass of (P279) Vitis vinifera". That instance of and subclass of usage would be consistent with how Wikidata classifies cats and dogs, e.g. Chihuahua (Q653).
    Anyhow, food and drink is an interesting area for structured data. Let me know if the above makes sense or if you have other ideas about how to model things. Cheers, Emw (talk) 19:59, 6 July 2014 (UTC)
    Hi User:Emw! Hmmm.... I'm not really sure actually...I'm pretty open minded and didn't give that aspect much thought outside of wanting to be able to use "varietal" as a statement. I'm not too sure...I can see the cultivar and vitis vinifera probably working best as statements versus the first varietal - but, since Zinfandel is a varietal, and it's a type of vitis vinifera.....hmmmm.... I'm leaning towards your experience in this to guide me! SarahStierch (talk) 20:06, 6 July 2014 (UTC)
    Sarah, things like "Zinfandel" are tricky because they're polysemous. As you you say, Zinfandel is a type of wine and a type of grape. However, many statements for Zinfandel wine are false for Zinfandel grape, and vice versa. For example, Zinfandel wine is not susceptible to bunch rot and Zindandel grapes do not have an alcohol by volume range of 12-17%. The wine derives from the grape. I think these statements illustrate the need for two separate items for the two different senses of Zinfandel.
    This kind of polysemy exists elsewhere, e.g. with the concept "influenza". Influenza is formally a type of disease, but it is often also used to refer to a type of virus. Separating the two concepts into two Wikidata items -- influenza (Q2840) and Orthomyxoviridae (Q287246) -- allows us to be much more precise and expressive about each subject.
    Perhaps we could do the same here with Zinfandel wine and the Zinfandel grape it derives from. That is, we could reserve Zinfandel (Q204433) for the grape and create a new item Zinfandel wine (Qx) for the wine. What do you think? Emw (talk) 00:29, 7 July 2014 (UTC)
    User:Emw you are a genius! (But you probably knew that already). Making new items for wine is a GREAT idea. How do we make that happen. SarahStierch (talk) 01:59, 8 July 2014 (UTC)
    @SarahStierch: I have started Wikidata:Property_proposal/Natural_science#fruit, I think the first step would be to start creating items for the fruits and linking them with their plants.--Micru (talk) 12:33, 17 August 2014 (UTC)
    @Emw, SarahStierch, Micru: You are absolutely correct about the need for multiple items for Zinfandel (Q204433). It is all in one Wiki article, but Zinfandel wine and Zinfandel grapes are separate and distinct concepts, so if there is data that applies to one and not the other, then they certainly need a new item. It can even be appropriate to give the wine and grapes each their own new item, while retaining the original Zinfandel (Q204433) to cover the general concept of Zinfandel, inclusive of both the wine and grapes, that is discussed in the Wiki article. We currently have made from material (P186) (alias ingredient) that can link the wine item with the grape item. Josh Baumgartner (talk) 22:46, 30 October 2015 (UTC)
      Oppose use instance of (P31) or subclass of (P279) --Pasleim (talk) 16:25, 25 August 2015 (UTC)
      Oppose and recommend made from material (P186) instead. Josh Baumgartner (talk) 22:46, 30 October 2015 (UTC)

    @SarahStierch:   Not done This is a valid use-case, but we already have made from material (P186). I also note that, on Zinfandel wine (Q17329207), we already have natural product of taxon (P1582) -> Zinfandel (Q204433). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:51, 23 November 2015 (UTC)

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