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/12.

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]

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
Motivation

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

Discussion
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)
Symbol support vote.svg SupportDimon4ezzz (обс.) 14:32, 18 August 2017 (UTC)
Pictogram voting comment.svg Comment Maybe a more appropiate name could be «Developer state». And we could be to expand the use to other items. Giovanni Alfredo Garciliano Diaz (talk) 00:15, 4 October 2017 (UTC)

Registration required[edit]

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

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

Discussion
  • 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)
  • Symbol support vote.svg SupportDimon4ezzz (обс.) 14:37, 18 August 2017 (UTC)
  • Symbol oppose vote.svg Oppose Hmm, I don't think we have any boolean properties currently, and I'm not sure this one should be either. I think this property should instead be labeled "access" or something like that (see for example protocol (P2700) which is a similar property for access to data sites) and values would be the particular type of accessibility available - for example "open", "free registration", "paid subscription", etc. ArthurPSmith (talk) 16:45, 18 August 2017 (UTC)
  • Symbol oppose vote.svg Oppose access has many more variants than registration yes or no, so better store access information with qualifiers, e.g. mandates (P4424). -- JakobVoss (talk) 19:43, 11 November 2017 (UTC)

partition identifier[edit]

Description string that contains the identifier of a filesystem contained in a partition
Represents Partition type (Q17042692)
Data type String
Template parameter Template:Infobox file system (Q10777901) → partition identifier
Domain instance of (P31)file system (Q174989)
Example ext4 (Q283827) → 0x83
Source en:Partition type
Planned use I think this property can be used with a "partition table" qualifier, with values like GUID Partition Table (Q603889) or Master boot record (Q624752)
Robot and gadget jobs No
Motivation

(Añade tu motivación por esta propiedad aquí). Giovanni Alfredo Garciliano Diaz (talk) 19:44, 18 August 2017 (UTC)

Discussion

Tobias1984
Emw
Zuphilip
Danrok
콩가루
TomT0m
DrSauron
Ruud Koot
Andreasburmeister
Toto256
MichaelSchoenitzer
Metamorforme42
Pixeldomain
User:YULdigitalpreservation
Dipsode87
Azertus
Pintoch
Jsamwrites
Fractaler
Giovanni Alfredo Garciliano Diaz
Jura
FabC
Pictogram voting comment.svg Notified participants of WikiProject Informatics ChristianKl (talk) 13:39, 30 October 2017 (UTC)

@YULdigitalpreservation, Giovanni Alfredo Garciliano Diaz, Jsamwrites: done: partition type identifier (P4654)Pintoch (talk) 14:53, 13 December 2017 (UTC)

partition table[edit]

Description qualifier for "partition identifier" that determines what partition table is used with the identifier.
Represents partition table (Q614361)
Data type Item
Example ext4 (Q283827) (partition identifier property) → 0x83, "partition table" qualifier → Master boot record (Q624752)
Motivation

To be used with "partition identifier" property. Giovanni Alfredo Garciliano Diaz (talk) 02:29, 25 August 2017 (UTC)

Discussion
@YULdigitalpreservation, Giovanni Alfredo Garciliano Diaz: done: partition table type (P4653)Pintoch (talk) 14:54, 13 December 2017 (UTC)

Languages[edit]

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 code (P3625)
Motivation

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

Discussion
  • @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)

Popcorndude Nikki SynConlanger Infovarius Pictogram voting comment.svg Notified participants of WikiProject Linguistics

numerical value of a character[edit]

   Under discussion
Description numeric value of a a letter
Data type String
Example א (Q16725860) → 1; Т (Q182438) → 300; (Q3594887) → 300; Ա (Q2323337) → 1; (Q4997131) → 1
Planned use Apply to all alphabet letter items. Maybe this can use a writing system (P282) qualifier.
Motivation

Add these values to Wikidata. Giovanni Alfredo Garciliano Díaz diskutujo 19:08, 14 November 2017 (UTC)

Discussion
  • Symbol support vote.svg Support David (talk) 07:16, 15 November 2017 (UTC)
  • Pictogram voting comment.svg Comment This could be a more general property for scripts such as Greek, Cyrillic, and Arabic which also have associated numeral systems, or for something like Aryabhata and Katapayadi with Indian scripts. Mahir256 (talk) 07:21, 15 November 2017 (UTC)
  • What's gematria? ChristianKl () 18:04, 15 November 2017 (UTC)
  • It would be nice if you could put at least part of that information in the description. ChristianKl () 18:15, 16 November 2017 (UTC)
Then it's not Gematria, it's something else. If you want to generalize it modify the description, source, subject item, etc. and add some examples in other languages. ArthurPSmith (talk) 15:23, 17 November 2017 (UTC)
@ArthurPSmith: I did. --Giovanni Alfredo Garciliano Díaz diskutujo 23:18, 19 November 2017 (UTC)
@Giovanni Alfredo Garciliano Diaz: can you clarify - does Gematria itself have numeric codes for other alphabets, or is that example you added from another coding system? If it does have numeric codes for other alphabets can you point to a source (the linked eswiki page only has Hebrew letters). How much of Unicode does it cover? ArthurPSmith (talk) 19:53, 20 November 2017 (UTC)
In fact, I think we already have a property for this - code (P3295), with qualifier encoding (P3294). ArthurPSmith (talk) 15:29, 17 November 2017 (UTC)

new version of the proposal[edit]

definition in sign language[edit]

   Under discussion
Description media file (video or still picture) showing the entity definition in sign language (use P407 to specify which sign language)
Represents sign language (Q34228)
Data type Commons media file
Domain all
Allowed values (all video or image extensions)
Example
See also label in sign language (P2919)
Motivation

Beeyan


Pictogram voting comment.svg Notified participants of WikiProject Language

VIGNERON (talk)
Mathieudu68 (talk)
Tpt (talk) (si besoin d'aide technique)
Ayack (talk) (surtout pour les MH)
Aga
Ash Crow (talk)
Tubezlob (talk)
PAC2 (talk)
Thierry Caro (talk)
Pymouss (talk)
Pintoch (talk)
Alphos (talk)
Nomen ad hoc (talk)
Framawiki (talk)
GAllegre (talk)
Peter17 (talk)
Pictogram voting comment.svg Notified participants of WikiProject France

Wikimedia France is currently working with Signes de Sens in order for them to release entries from their French sign language dictionary Elix as open source. Entries in Elix have two videos, one signing the label (which will be used with label in sign language (P2919) in Wikidata) and one with the definition: we need a new property for them. Of course, as for label in sign language (P2919), it is neither limited to this set, nor to French sign language. Sylvain WMFr (talk) 17:59, 29 November 2017 (UTC)

Discussion
  1. Symbol support vote.svg Support seems like a very good idea, yes, since sign language (Q34228) cannot be written, and thus needs a video :) --Hsarrazin (talk) 20:33, 29 November 2017 (UTC)
    1. Why? We don't have a property for written definitions either. ChristianKl () 00:39, 1 December 2017 (UTC)
  2. Symbol support vote.svg Support. Nomen ad hoc (talk) 09:36, 30 November 2017 (UTC).
  3. Symbol support vote.svg Support, sounds^Wlooks really cool − Pintoch (talk) 10:51, 30 November 2017 (UTC)
Décrit à l'URL expects an URL, not a media. We need an equivalent of label in sign language (P2919) for descriptions. There are roughly 10000 videos of definitions. -Ash Crow (talk) 20:27, 29 November 2017 (UTC)
  • Symbol oppose vote.svg Oppose as proposed. Wikidata items are not defined by words and sign language is basically about representing words. Calling the resource a dictionary indicats that it's about words and not items and thus it might be better to link it when there's the lexeme datatype.
The concept of a definition is different from a description. But even if you would propose a property for descriptions I find it unlikely that your 10000 videos would accurately describe the linked Wikidata items. You don't get accurate descriptions of English items by looking at a dictionary for English. ChristianKl () 00:32, 1 December 2017 (UTC)
Sign language is a language ; a sign or a sequence of signs is a way to represent a concept directly, in the same way you would do with words in another languages. About descriptions and definitions : yes, they are not the same. But if we want people to be able to contribute and navigate in Wikidata in sign languages, we need to start somewhere, and definitions are not that bad descriptions (we still can make new videos with something that is a better description... It's a wiki!). Léna (talk) 14:18, 1 December 2017 (UTC)
The problem is that there's a good chance that the information that you are going to display is wrong. Having a wrong description is worse than having no description. If the French translation of the sign language for life is correct than the the definition says that it's about either an animal or a plant. As far as Wikidata is concerned other taxa of other kingdoms besides the plant and animal kingdom are also alive.
We rejected in the past properties that provide a textual definition. Rejecting properties that provide textual descriptions but allowing properties that provide a definition in sign language is inconsistent. ChristianKl () 03:40, 2 December 2017 (UTC)
  • Symbol support vote.svg Support This does sound like the way to create non-verbal versions of wikidata descriptions, so I think it's a good idea. However - there are many different sign languages, so this would also need a qualifier indicating which one (see en:List of sign languages). ArthurPSmith (talk) 16:43, 1 December 2017 (UTC)
  • @ArthurPSmith: The suggested property isn't called "description in sign language", so it's not equivalent to label in sign language (P2919). It's corresponds to https://www.wikidata.org/wiki/Wikidata:Property_proposal/definition which we rejected in the past. Additionally, the data set that's supposed to be used is not written to describe the Wikidata items that we have. The first example that given is a wrong description for the property in question and likely many further entries will be also wrong. You could argue that having wrong descriptions doesn't really matter because few people will use the sign language videos anyway, but I don't think that's a good principle based on which to build up our data. ChristianKl () 03:48, 2 December 2017 (UTC)
  • @ChristianKl, Sylvain WMFr: - sorry, I didn't catch the distinction between "definition" and "description", however, I believe the intent here is to have a sign-language description, since there isn't any alternate way to do that with our current wikidata system (is there?). Sylvain WMFr, as proposer can you clarify on this? As to the first definition being "wrong" - it doesn't look wrong to me, it seems to match the descriptions in French and German quite well - "life" (Q3) is the state of being a living thing. The English description attempts to be prescriptive on what life is, rather than the somewhat circular descriptions of other languages, which is fine, but I don't think that means the sign language definition has to match that. ArthurPSmith (talk) 15:25, 4 December 2017 (UTC)
  • As far as I can access it does say that life refers to animals or plants. Our Wikidata item has a scope that's more wide. Recently we had a discussion around behavior (Q9332) and it's scope. The item got a description that limited it to the behavior of animals as the word is used with that scope in many context. I fixed it and moved the notion of animal behavior to animal behavior (Q2990593).
The goal of a Wikidata description is to give the reader an idea about how an item is supposed to be used and the scope is important information that's to be communicated. Taking word definitions from a Wikidictionary is unlikley to produce descriptions that match our scope.
I can understand the desire to integrate a French sign language dictionary into Wikidata, but dictionary integration should wait till we have Wikidictionary integration.ChristianKl () 15:36, 4 December 2017 (UTC)
I'm sorry, I'm not following what you mean - how does Wiktionary integration have any relevance to this? A "definition" implies specifying meaning - what a dictionary does is group different meanings of a single string of text together, but each individual meaning (each definition) is its own concept, which is what wikidata QID's are about. So the sign language "definition" or "description" belongs on the concept, not on the Wiktionary entry (for example life in English Wiktionary has 8 definitions, though about half of them could be said to match the concept Q3 so that's another bit of confusion here). ArthurPSmith (talk) 18:51, 4 December 2017 (UTC)
As far as I understand there's an existing dictionary with lexemes that have names in French sign language, which have definition in French sign language.
There's interest to integrate that data in our universe. When we have a the lexeme datatype we can easily have one item for every one of those entries. Those entries can interlinked with other language in the same way we interlink other lexemes on Wikidictionary across languages. ChristianKl () 15:11, 6 December 2017 (UTC)
 ? A sign-language lexeme is surely completely divorced from any existing or proposed entity in wikidata. I'm not sure how you would even label a signed lexeme in English or another verbal language - "Sign made by raising second and third digits of right hand in a V shape while ... "? I am very sure this is NOT what the original proposer here is advocating for, but rather associating signed labels (yes extracted from this sign language dictionary) and the associated descriptions (from the dictionary definitions) to the wikidata concepts associating with those meanings. @Sylvain WMFr: can you please clarify? ArthurPSmith (talk) 17:08, 6 December 2017 (UTC)
To me it seems like the proposer simple want to copy the entries of the dictionary Elix over to Wikidata. ChristianKl () 23:40, 6 December 2017 (UTC)
  • Symbol support vote.svg Support Pamputt (talk) 18:50, 3 December 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