Wikidata:Property proposal/Term

From Wikidata
Jump to: navigation, search

Property proposal: Generic Authority control Person Organization
Event Creative work Term Space
Place Sports 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. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the proposal, 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/06.

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]


   Under discussion
Description amount of optical magnification provided
Data type Quantity
Domain sensors, optical devices, etc.
Allowed units degree
Example No. 30 Sighting Telescope (Q29048358) → 1.9

Distinct spec for optical devices. Existing properties don't seem to do the job. Josh Baumgartner (talk) 04:18, 29 March 2017 (UTC)

  • Symbol support vote.svg Support Thryduulf (talk) 20:18, 5 May 2017 (UTC)
  • Symbol support vote.svg Support this is more for microscopes (and camera lenses?) than for telescope I would think? ArthurPSmith (talk) 18:18, 8 May 2017 (UTC)
  • Is there any prior art how other ontologies model this property? ChristianKl (talk) 21:00, 14 May 2017 (UTC)
    • Most likely, but I don't have a specific one at hand. Josh Baumgartner (talk) 23:58, 23 May 2017 (UTC)
  • Can you express the domain in terms of Wikidata items? That makes it setting the constraints clearer. ChristianKl (talk) 21:02, 14 May 2017 (UTC)
    • I have in mind items which would be within device (Q1183543), though I don't necessarily think it needs to be constrained if others come up with different ways to use it. Josh Baumgartner (talk) 23:58, 23 May 2017 (UTC)
  • @Joshbaumgartner: This could be ready, if you would address ChristianKl's concerns? ArthurPSmith (talk) 19:40, 15 May 2017 (UTC)

software life cycle state[edit]

   Under discussion
Description Describes the status of a software/website/product/etc.
Represents state (Q3505845)
Data type Item
Template parameter "estado actual" on w:es:Plantilla:Ficha de sitio web
Allowed values If possible, elements that are a instance of software version type (Q28530564)
Example OpenStreetMap (Q936)active (Q29415466)
Planned use Set the property on all items that are a instance of software, website, software standard, etc.
Robot and gadget jobs

This property is useful in many Wikipedia articles. Giovanni Alfredo Garciliano Diaz (talk) 21:32, 15 April 2017 (UTC)

Pictogram voting comment.svg Comment "current" would be something true at the time a statement was entered, but it may not be correct later. If we have thousands of items in wikidata with "current status" entries of "active", say, how do we know they are actually still "active"? Perhaps instead just a generic "status" property would be helpful, with a rule to generally use a point in time (P585) qualifier. We do have a number of properties that could be considered subproperties of a generic "status" - canonization status (P411) for example so I think it would be useful to have. ArthurPSmith (talk) 18:33, 17 April 2017 (UTC)
@ArthurPSmith: I'm according you, a statement with a point in time (P585) will be useful, after all, this property is only a generic property... Also, the possible values can be, for example: active (Q29415466), "inactive", "discontinued", "on development", etc. Giovanni Alfredo Garciliano Diaz (talk) 01:18, 26 April 2017 (UTC)
As soon as we have calculated values, properties that describe 'current' situations, could be transferred to calculations based on date values. --Hannolans (talk) 10:30, 28 April 2017 (UTC)
I would propose to have a more defined name, as now, it could also be the status of a building, the copyright status etc. --Hannolans (talk) 10:32, 28 April 2017 (UTC)
@Hannolans: Then we would need many properties for each type of item, e.g., for software items, we would need a "development state" property, and as possible values, active (Q29415466), "inactive", "discontinued", "on development", etc.; for website items, we would need a "development state", with its possible values, "online", "offline", etc.; and for a standard, we would need a standard state, with his possible values, "draft", "standard", "candidate to standard", "rejected", etc. I propose to create this property, and the previous items, and use this property only in case when doesn't exists a more specific property. Giovanni Alfredo Garciliano Diaz (talk) 19:13, 6 May 2017 (UTC)
The description only talks about software. But the proposal is broader? So for example, a person can have a status 'live' or 'dead', or 'married', 'unmarried'? --Hannolans (talk) 19:40, 6 May 2017 (UTC)
@Hannolans: No, for those there should be other more specific properties. This property is related with software items. Giovanni Alfredo Garciliano Diaz (talk) 23:36, 17 May 2017 (UTC)
I would suggest to call it something like 'Software life cycle state" in that case. 'Current state' can mean anything--Hannolans (talk) 00:02, 18 May 2017 (UTC)
@Hannolans: Can I change the name of this proposal? Or I must to create a new proposal? Giovanni Alfredo Garciliano Diaz (talk) 19:17, 21 May 2017 (UTC)
I think changing 'en = current status' and 'es = Estado actual' is enough--Hannolans (talk) 19:19, 21 May 2017 (UTC)
NB: I would remove 'current', as we would have multiple states with a start and end date (alpha from to, beta from to). --Hannolans (talk) 19:39, 21 May 2017 (UTC)
@ChristianKl:, @Hannolans: I've changed the property name. Giovanni Alfredo Garciliano Diaz (talk) 02:38, 26 May 2017 (UTC)
Symbol oppose vote.svg Oppose towards the present name. If a status is only true at a particular moment of time properties like "start time", "end time" and "point in time" should be used. Using "end time"="NoValue" is also a possible way to signal that the project is still active. ChristianKl (talk) 17:52, 22 May 2017 (UTC)
Discovered we already have version type (P548). See Wikidata:WikiProject_Informatics/Software --Hannolans (talk) 06:59, 26 May 2017 (UTC)

Registration required[edit]

   Under discussion
Description Describes if it's necessary to register in this website for use it.
Represents Login (process) (Q472302)
Data type Item
Template parameter "registro" in w:es:Plantilla:Ficha de sitio web
Allowed values yes (Q6452715), no label (Q29415813), no (Q1814990), no label (Q29415850)
Example OpenStreetMap (Q936)no label (Q29415850)
Planned use Set this property on all items that are a instance of website
Robot and gadget jobs

This property is useful in many Wikipedia articles. Giovanni Alfredo Garciliano Diaz (talk) 23:07, 15 April 2017 (UTC)

  • Symbol support vote.svg Support, but "required" is probably a better value than "yes", and more values are required than just those four - e.g. the infobox at en:English Wikipedia notes that registration is optional but required for "certain tasks including: protected page edit, page creation, file upload". One (but not necessarily the best) way to model this would be a "registration required for" value, qualified with applies to part (P518) statements. Thryduulf (talk) 15:42, 22 April 2017 (UTC)
    • @Thryduulf: I'm according you. I have put those elements almost as an example, they are the most general items that I believe can be established. I think maybe later more people will add more items as they are needed, e.g., the user only choose between three values: "required for" (this value can have a qualifier, applies to part (P518)), "required" and "not required", Giovanni Alfredo Garciliano Diaz (talk) 00:31, 26 April 2017 (UTC)

AUR package[edit]

   Under discussion
Description Indicates the official name of the package on the Arch's User Repository
Data type External identifier
Example dislines (Q29566755) → dislines
Planned use Que esté asignada a los paquetes de software que apliquen
Formatter URL$1/
Robot and gadget jobs
See also Arch package (P3454)

There is a property for the Arch's official packages. But exists a second repository where the users can upload their own packages: the AUR. Giovanni Alfredo Garciliano Diaz (talk) 01:58, 26 April 2017 (UTC)


Sample image[edit]

   Under discussion
Description indicates an image that is a sample of the corresponding typeface.
Data type Commons media file
Template parameter muestra en es:Plantilla:Ficha de tipografía
Domain Items that are a instance of typeface
Example Times New Roman (Q213048)commons:File:Times New Roman sample.svg
Planned use Set this property on all items that are a instance of typeface
Robot and gadget jobs

There is no a property like this, the Image property don't made this job. Giovanni Alfredo Garciliano Diaz (talk) 14:54, 26 May 2017 (UTC)



RFE symbol[edit]

   Under discussion
Description Indicates the symbol of the phonetic alphabet of the Revista de Filología Española corresponding to an AFI phoneme
Represents RFE Phonetic Alphabet (Q2839576)
Data type String
Template parameter "rfe" en es:Plantilla:Ficha de AFI.
Example voiced palatal nasal (Q463495) → ṋ
Source es:Alfabeto fonético de la RFE
Planned use set it on all elements that would require it, so the infoboxes will use it
Robot and gadget jobs
See also Kirshenbaum (P3625)

Set it, so the infoboxes can use it. Giovanni Alfredo Garciliano Diaz (talk) 00:09, 13 May 2017 (UTC)

  • @Giovanni Alfredo Garciliano Diaz:Currently, the name doesn't say much about what the property is about. I think the description also doesn't provide much information for a lay-person. Can you provide a more informative name and description? ChristianKl (talk) 10:55, 24 May 2017 (UTC)
@ChristianKl: Surely. ­­Giovanni Alfredo Garciliano Diaz (talk) 13:21, 24 May 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