Wikidata:Property proposal/Term

From Wikidata
Jump to: navigation, search

Property proposal: Generic Authority control Person Organization
Event Creative work Term Space
Place Sister projects
Economics Transportation Natural science Property metadata

See also[edit]

This page is for the proposal of new properties.

Before proposing a property
  1. Check if the property already exists by looking at Wikidata:List of properties (manual list) and Special:ListProperties.
  2. Check if the property was previously proposed or is on the pending list.
  3. Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
  4. Select the right datatype for the property.
  5. Start writing the documentation based on the preload form below and add it in the appropriate section.

Creating the property

  1. Change status=ready on template to attract the attention of a property creator.
  2. Creation can be done after 1 week by a property creator or an administrator.
  3. See steps when creating properties.

On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2017/01.

To reduce page size and functions for better loading,

  1. For transportation-related item property proposals, see Wikidata:Property proposal/Transportation.
  2. For economics-related item property proposals, see Wikidata:Property proposal/Economics.
  3. For natural science-related item property proposals, see Wikidata:Property proposal/Natural science.

Products & software products[edit]

Languages[edit] language status[edit]

   Under discussion
Description language status identifier by using EGIDS scale
Data type Item
Domain language in the world
Allowed values listed here
Example Indonesian (Q9240) → 1 national

This property is important, we have UNESCO language status (P1999), we should have language status too. Beeyan (talk) 10:00, 2 November 2016 (UTC)

  • Keen support, but would prefer an item data type, like UNESCO language status (P1999). John Vandenberg (talk) 13:25, 2 November 2016 (UTC)
  • Symbol support vote.svg Support with datatype of "item". Only 13 items should be required. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:01, 2 November 2016 (UTC)
  • External ID is absolutely wrong for this, this is a classification, not a unique id that would be applied to each item where the property is used. I support if datatype is "item", or "string". ArthurPSmith (talk) 18:25, 2 November 2016 (UTC)
  • Pictogram voting comment.svg Comment last property proposal: Wikidata:Property proposal/Archive/33#EGIDS language status --Pasleim (talk) 21:48, 2 November 2016 (UTC)
    • Thanks @Pasleim: for referring previous discussion with the same property. --Beeyan (talk) 08:39, 3 November 2016 (UTC)
  • Note I can see the merit of having the EGIDS status, but ethnologue isn't always a reliable source for that (see the previous discussion). Uanfala (talk) 10:26, 5 November 2016 (UTC)
    • For most languages there simply haven't been any language vitality studies published, so if the property values get filled in from ethnolgue's best guesses, they'll be largely unreliable. Uanfala (talk) 11:59, 5 November 2016 (UTC)
  • Pictogram voting comment.svg Comment If we talk about reliable source, UN Atlas of the World's Languages in Danger also has some flaws. They're using old resources and not showing the recent status. Reliable sources are hard to find for defining language status, as we encounter so many contradictory resources. If we can get this property on Wikidata, we could see the differences between sources :) --Beeyan (talk) 05:15, 6 November 2016 (UTC)
  • Pictogram voting comment.svg Comment One of the previous objections was that Wikipedia would use this data, e.g. in an infobox, and all of the caveats are lost. Perhaps we can avoid that problem by always using 'deprecated' for any value which isnt from a reliable vitality study. We should be able to build a constraint to enforce that - "if no source, or source is ethnolgue, warn if the value status is not deprecated". John Vandenberg (talk) 06:24, 6 November 2016 (UTC)
    • It would not be appropriate to use the deprecated rank with the property proposed here (it would be fine for instance of (P31) statements though). Deprecated means that a statement is wrong and always was wrong, but if Ethnologue says that the status is X, then "the status in Ethnologue is X" is a true statement, even if people think Ethnologue is wrong to say that. For example, if Ethnologue says a language is extinct but we know it isn't because there are native speakers, we can mark a instance of (P31) extinct language (Q45762) statement as deprecated because we know that "it is an extinct language" is wrong, but "Ethnologue language status" "extinct" shouldn't be marked as deprecated because "Ethnologue says that it's extinct" is still completely true. - Nikki (talk) 10:35, 22 December 2016 (UTC)
  • Pictogram voting comment.svg Comment Please provide an example that uses an item. ChristianKl (talk) 19:27, 15 November 2016 (UTC)
  • Support Per nom. Iazyges (talk) 21:51, 15 November 2016 (UTC)
  • Symbol oppose vote.svg Oppose per previous discussion. Visite fortuitement prolongée (talk) 22:25, 15 November 2016 (UTC)
  • Pictogram voting comment.svg Comment Is there any outside discussion by linguistics about the status of Ethnologue that we can use to guide our decision? ChristianKl (talk) 10:45, 18 November 2016 (UTC)
    • Example: Indonesian (Q9240) → 1 national (it should be filled by an item data, just like UNESCO language status (P1999), cc: @ChristianKl:. Beeyan (talk) 08:14, 29 November 2016 (UTC)
      • @Beeyan: Saying "it should be different" isn't the point. Please actually create the example that you are looking for. This example just refers to a string. ChristianKl (talk) 15:54, 29 November 2016 (UTC)
      • @ChristianKl: there's no point creating the items if the property is not approved, and it's clear the intention is to use items as for similar properties, so I don't see why you are requiring Beeyan to do this now? ArthurPSmith (talk) 19:16, 29 November 2016 (UTC)
        • I don't think that this property needs to exist for the categories to exist. In general I think the point of a property proposal is to decide on the structure of something is supposed to be modeled. It doesn't make sense that the actual acct of modeling happens outside of the visibility that the property proposal process provides. ChristianKl (talk) 11:00, 30 November 2016 (UTC)

signed form[edit]

   Under discussion
Description manually coded form of this language
Represents Manually coded language (Q1808730)
Data type Item
Template parameter |sign= in en:template:Infobox language
Domain languages

Fills a template need. ~nmaia d 18:04, 11 January 2017 (UTC)


phonetic algorithms[edit]

This proposal includes three related properties.


   Under discussion
Description a phonetic algorithm for indexing names by sound, as pronounced in English
Represents Soundex (Q1502023)
Data type String
Domain names
Allowed values [A-Z](000
Example Robert (Q4927937) → R163
Source Can be computed by names
Planned use For queries
Robot and gadget jobs Yes

Cologne phonetics[edit]

   Under discussion
Description a phonetic algorithm which assigns to words a sequence of digits, the phonetic code
Represents Cologne phonetics (Q1795856)
Data type String
Domain names
Allowed values 0?[1-8]*
Example Müller (Q8157228) → 657
Source Can be computed by names
Planned use For queries
Robot and gadget jobs Yes


   Under discussion
Description a phonetic algorithm
Represents Soundex (Q1502023)
Data type String
Domain names
Allowed values [ASPTKFMN1]{6}
Example Thompson (Q2803433) → TMPSN1
Source Can be computed by names
Planned use For queries
Robot and gadget jobs Yes

Symbol support vote.svg Support at least Soundex. These are very useful for comparing names that may be spelled many different ways. ArthurPSmith (talk) 19:38, 17 January 2017 (UTC)

processes and production[edit]

This section is intended for industrial or other types of processes and processing industry that performs a task from some kind of products and processes them to create something else

A particular case that has a section for property proposal on is own is Transportation