Wikidata:Property proposal/Generic

From Wikidata
Jump to: navigation, search
Shortcut: WD:PP/GEN

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:AllPages.
  2. Check if the property is already pending or has been rejected.
  3. Check if you can give it similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data automatically can be transferred. See wd:Infoboxes task force for suggestions.
  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. Creation can be done after 1 week by a property creator or an administrator.
  2. See steps when creating properties.

Add a request

This page is archived, currently at Archive 24.

To add a request, you should use this form:

=== {{TranslateThis
| de = <!-- PROPERTY NAME IN German (optional) -->
| fr = <!-- PROPERTY NAME IN French (optional) -->
<!-- |xx = property names in some other languages -->
}} ===
{{Property documentation
|status                 = <!--leave this empty-->
|description            = {{TranslateThis
  | en = put English description for property here, e.g. same as in the infobox documentation
|infobox parameter      = put Wikipedia infobox parameters here, if existing; ex: "population" in [[:en:template:infobox settlement]]
|datatype               = put datatype here (item, string, media, coordinate, monolingual text, multilingual text, time, URL, number)
|domain                 = types of items that may bear this property; preferably use Q templates, as specialized as possible, or text. ''e.g.'' {{Q|6999}} (astronomical object), {{Q|12136}} (disease), {{Q|11436}} (aircraft), and more generally {{Q|2221906}} (place), {{Q|43229}} (organization), {{Q|1656682}} (event), {{Q|386724}} (creative work), etc.  Special values (having specialized validation schemes): Persons, Taxons
|allowed values         = type of linked items (Q template or text), list or range of allowed values, string pattern...
|suggested values       = (deprecated)
|source                 = external reference, Wikipedia list article (either infobox or source)
|example                = sample items that would use that property, with proposed values; example: {{Q|1}} => {{Q|2}}
|filter                 = (sample: 7 digit number can be validated with edit filter [[Special:AbuseFilter/17]])
|robot and gadget jobs  = Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.)
|proposed by            = ~~~
(Add your motivation for this property here.) ~~~~

For a list of infobox parameters, you might want to use table format:

{{List of properties/Header}}

{{List of properties/Row|id=
|title          = audio
|type           = media
|qualifier      =
|description    = Commons sound file
|example-subject= Q187 <!-- Il Canto degli Italiani -->
|example-object = Inno di Mameli instrumental.ogg


For blank forms, see Property documentation and List of properties/Row


Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: language independent or context-specific label

Motivation. Sometimes it is needed to use a label as a qualifier of another property, or there is a label that only was valid during a certain period (to be used with qualifier "start/end date"). I also think that it could be used to model systems since inputs and outputs usually require a way of name the signals.--Micru (talk) 17:12, 8 July 2014 (UTC)

contained in[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: a material entity located inside another one with no parts in common

Basic property.--Micru (talk) 13:55, 9 July 2014 (UTC)

  • Symbol oppose vote.svg Oppose. contained_in had been a property of the Basic Formal Ontology (BFO), but it's being removed from BFO 2 per the draft specification in favor of a more generalized located in (P276) property. I think that's a move in the right direction; we can use located in to capture the meaning of contained in. Emw (talk) 03:56, 10 July 2014 (UTC)
  • @Emw: are you sure of that? Looking at "3.6.4 Location" it seems that it has been replaced by occupies_spatial_region which is similar to "contained in". The problem of "located in", also identified in BFO2, is that it needs some prepositional modifier to indicate the location relation between both entities. Instead of "contained in", we could think of a qualifier of "located in", maybe "spatial relation" with values "on", "inside", "above", etc.? --Micru (talk) 07:18, 10 July 2014 (UTC)

has role[edit]

Wikidata:List of properties • v · d · e
Status:    1452
  • Description: something the subject does because of some special natural, social, or institutional set of circumstances

Needed to express which function a given part has in a system (it might be different depending on the system). Notifying @Emw:--Micru (talk) 14:32, 9 July 2014 (UTC)

Simply put, roles are things that are optionally manifested in other things. Roles are realized in things by virtue of some special natural, social, or institutional set of circumstances. Roles depend on those things for their existence. For example, roles include any of our various occupations, or the steering (Q499159) of a rudder (Q209760) from Micru's example. One would say that "E. coli has role pathogen", for example, because such bacteria do not have that role when outside an animal's gut. In contrast, one would not say "heart has role circulation", because hearts are typically found in bodies pumping one. (However one might say "heart has role dinner" when being eaten by a lion.) Another example is something like "hydrogen has role nutrient", as stated in the BFO ontology ChEBI, the reference ontology for chemicals of biological interest.
This brings me to how I would change the 'Description' value of this proposed property. It currently reads "the function an element fulfills in a given system". "Function", "element" and "system" all have significant meaning and would cause alignment problems with BFO ontologies as proposed.
"Function" in BFO is closely related to "role", but not the same. Functions manifest in something by virtue of its physical structure. "Function" differs from "role" in that the former always or almost always manifests in something by virtue of its physical structure, while the latter optionally manifests in something. For example, the means "heart has function circulation" would be preferred over "heart has role function", because hearts almost always circulate blood, and do so by virtue of their physical structure. Same with "hammer has function impact nails".
"Element" has strong associations with the set theory operator element of (ϵ). The distinction between an "element" and a "set" is what differentiates the basic membership properties instance of (P31) and subclass of (P279) -- these are often analogized to "element of" and "subset of". I would not want the proposed wording to imply that has role is only applicable for instances and not for classes. BFO permits usage of has role on both instances and classes and the proposed property should do the same.
Finally, "system" is a vague term and seems likely to produce undue confusion. Certainly Coco Chanel (Q45661) has a specific kind of role, the occupation fashion designer (Q3501317), and Escherichia coli (Q25419) has role pathogen (Q170065), but to say that either subject is "in a given system" is rather obtuse. Things that have a role can be part of a system, but that should not be necessary and so shouldn't be in the description. I think we can safely drop the word "system" from the description.
I would word the description as "something the subject does because of some special natural, social, or institutional set of circumstances", per BFO.
Micru, thanks for proposing this property. I think it's likely to become a significant positive outcome of the Wikidata:Requests_for_comment/Refining_"part_of" RFC. Emw (talk) 03:49, 10 July 2014 (UTC)
Description changed as per Emw's comment.--Micru (talk) 07:22, 10 July 2014 (UTC)
That sounds useful. But as the role/function distinction suggests, that may be tricky to work out. Something about which I was wondering: it would be interesting to have a property that would say the areas of intervention of a particular administrative unit (eduction, security, etc.) Would that be possible to say that with this property or would it pave the way to irredeemable messiness ? @Innocent bystander: --Zolo (talk) 09:04, 10 July 2014 (UTC)
@Zolo: "Has role" is for entities that change their function depending on the context. I do not think that an organization adopts different roles, it is created with a fixed set of "functions" in mind and it always fulfills those, for that reason I would recommend using use (P366) or proposing a new "organization function" property if p366 seems too bound to artificial objects.--Micru (talk) 07:30, 11 July 2014 (UTC)
  • Perhaps this should have a different label, so that users don't accidentally select it when they mean to add character role (P453). --Yair rand (talk) 16:31, 10 July 2014 (UTC)
  • @Yair rand: I have been thinking about this, and I reached the conclusion that the confusion would be normal because... they are the same property. Well, character role (P453) is constrained to "interpretative roles", but there is the question if we can generalize character role (P453) for all uses, or if we can exclude "interpretative roles" from this generic one. Would a "Constraint:Item|NOT property=cast member (P161)" work?.--Micru (talk) 07:30, 11 July 2014 (UTC)
    I'm afraid I don't see the similarities or associations between the two properties at all. --Yair rand (talk) 00:40, 15 August 2014 (UTC)
Symbol support vote.svg Support I think this property would be very useful in book cataloging, for qualifying the very various roles of the authors : editor, translator, preface, etc.,
and yes Micru, organizations can have different roles in the same action, depending on many things, time, money, politics, etc. : an organisation can also be authoring a book... as author, as editor, as publisher... and it may also (for administrations), lead a politic, finance it, coordinate, etc. --Hsarrazin (talk) 15:33, 14 August 2014 (UTC)

✓ Done as invalid ID (P1452). Similar to character role (P453), but p453 is constrained to people, while this new property can be used for everything. Notification: @Hsarrazin, Yair rand, Innocent bystander, Zolo, Emw:--Micru (talk) 14:47, 20 August 2014 (UTC)

@Hsarrazin, Yair rand, Innocent bystander, Zolo, Emw: Ups, I have just noticed that "has role" is redundant with as (P794). I will ask for a merge.--Micru (talk) 21:52, 20 August 2014 (UTC)
D - I had not seen it either… just added an alias to make it more explicit… --Hsarrazin (talk) 22:18, 20 August 2014 (UTC)

number of parts[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: the number of parts that this object has in total or of a specific type (when qualifying "has part")

Different meaning than number of instances (P1114).--Micru (talk) 14:40, 9 July 2014 (UTC)

  • Pictogram voting comment.svg Comment: two-wheeler (Q233040) currently uses has part (P527) with wheel (Q446): number of instances (P1114) = 2 --- Jura 17:26, 9 July 2014 (UTC)
  • Symbol oppose vote.svg Oppose. I support the spirit of this property -- capturing cardinality constraints -- but I think we should use a generic cardinality property and merge number of instances (P1114) and this proposed property into it. (As a practical matter I would redefine P1114 to have the semantics of that generic property.) That's much closer to how OWL and existing major ontologies handle cardinality constraints. "Cardinality" might be too stuffy as a label for such a property -- perhaps we could get by with 'number' or 'has number', and supply a description that indicates it doesn't take phone numbers? Emw (talk) 04:02, 10 July 2014 (UTC)

has agent[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: entity that performs this action

With aliases: "performed by", "done by", "executed by".--Micru (talk) 14:14, 11 July 2014 (UTC)

transliteration type[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: used as qualifier of any transliterated name or label to indicate the system used

Motivation: Wikidata:Project_chat#How_to_handle_native_language_names.3F--Micru (talk) 12:12, 15 July 2014 (UTC)

so what was Hu Jintao's birthname? How many birth names did he have (with different transliterations) and are these really all birth names?
I agree something needs to be done but we need a solution that works for people with multiple names. I need to think about this. Filceolaire (talk) 22:28, 17 July 2014 (UTC)
@Filceolaire: Yes, actually you are right, we'd need a generic transliteration (monolingual string) with this property as qualifier (description changed accordingly). It would be easier to have the name as an independent item, because then we'd be able to put all transliterations for that name together, but that again seems to be in the domain of linguistic data... --Micru (talk) 06:56, 18 July 2014 (UTC)
Consider Joseph Stalin (Q855).
  • birth name:იოსებ ბესარიონის ძე ჯუღაშვილი (in Georgian)
    • Transliteration:Ioseb Besarionis dze Jughashvili (English)
    • Transliteration:Iósif Vissariónovich Dzhugashvili (spanish)
  • Known as:Ио́сиф Виссарио́нович Ста́лин
    • Transliteration:Iosif Vissarionovich Stalin (English)
  • Known as:Ио́сиф Ста́лин (Russian)
    • Transliteration:Joseph Stalin (English)
    • Transliteration:José Stalin (Spanish)
    • Transliteration:Josef Stalin (Spanish)
Qualifiers can't have qualifiers so I'm not sure where to put the 'transliteration type' property.
it does look like we need a 'known as' property and a 'transliteration' (or maybe 'localisation') property. Filceolaire (talk) 11:50, 18 July 2014 (UTC)
@Filceolaire: I don't think that we can do that with qualifiers, because also transliterations may have sources. I have tried to replicate with items your structure here: (talk) 12:47, 18 July 2014 (UTC)
Still thinking about this. So basically we have 2 solutions:
  • Each time we want to describe a name, we create a separate item. Which means that if we want to get the Arabic transliteration of Richard Wagner we do it through Richard (Q1249148) and Wagner (Q2539239). There are 2 issues first that it may seem unwieldy and requires creating items even for nicknames and given names that were given to only one person. More importantly, it may not always give a correct result. One case in point is transforming transmogrigying a name into Chinese (not sure it would be called transliteration, but it is needed notheless). For instance, Richard appears to be rendered the differently in Chinese in Richard Wagner and in Richard the Lionheart.
  • Using qualifiers. That seems to require create new properties, like, I guess a string-type "first name" property in addition to the current item-type one. It would also create massive redundancy (repeating the 10s of transliteration of the same first name in 1000s of items). And as Micru notes that may also have issues for sourcing (which actually is an issues I have encountered several times with statements containing qualifiers, so there may be something more general at stake here).
We could also make a mix of the two, but that may not be very intuitive.
We could also decide that we can let the software do the job for simple cases (providing standard transliterations of Greek or Russian words for English-speaking users iappears to be pretty mechanical and straightforward). But it would not work for all cases, so that would not really solve anything. -Zolo (talk) 13:24, 18 July 2014 (UTC)n
@Zolo: you forgot to mention the third option, which is to treat the whole name as an item, and then transcribe/adapt it as a whole, linking to linguistic data when/if available with qualifiers (see linked items).
I think we should not enforce any solution, just offer a path for the names of an item to grow organically depending on the number of editors interested in the item: first only labels (as now), then use monolingual properties for transliterations all in the same item, and when the item grows too big, then split it into subitems (see my example).--Micru (talk) 13:37, 18 July 2014 (UTC)
When we get a 'monolingualtext' datatype I look forward to getting the 'official name' property and will be proposing a number of other name properties. Also proposing that the datatype for the 'birth name' be changed from 'string'.
When we get a multilingual text' datatype I will be proposing a 'localised version' property with multilingual text datatype, to use as a qualifier for the name properties. For some languages there may well be more than one commonly used localisation for famous names (e.g. for languages using more than one script). For many small languages the wikidata transliteration will effectively become the default name for that person/country/company since no one else has ever bothered to write about that item in that language before.
Note that there is still no place to put a 'transliteration type' property but we do get a 'language' qualifier for free for each 'localised version'. Filceolaire (talk) 19:29, 18 July 2014 (UTC)

end reason[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: qualifier used to supplement "end date"

The main inspiration for this qualifier proposal is including an explanation of why a marriage ended (e.g., divorce (Q93190), annulment (Q701040)), something often kept track of in infoboxes but not included in Wikidata so far. We can definitely broaden it to include any more information about why something started or ended though, such as if someone transferred schools, dropped-out, etc. Cbrown1023 talk 02:30, 6 August 2014 (UTC)

If this is to be used for many properties, I don't think that "reason" is the right word here. --Yair rand (talk) 22:31, 6 August 2014 (UTC)
What do you suggest? I couldn't come up with a better name either, but "end reason" is the best one we came up with. If we agree it's a good idea, though, the good thing about Wikidata being a wiki is that we can always change the name or add new aliases. Cbrown1023 talk 01:32, 7 August 2014 (UTC)
  • Symbol support vote.svg Support--Micru (talk) 14:10, 14 August 2014 (UTC)

listed in[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Data type: items that are real lists
  • Domain: any item that is not itself a list
  • Allowed values: items that are real lists
  • Suggested values: (deprecated)
  • Source: Externe Referenzen, Listenartikel in der Wikipedia (entweder Infobox oder Quelle)
  • Example item and value: island of Japan => listed in=> list of islands of Japan
  • Robot and gadget jobs: Führen Bots oder Helferlein irgendwelche Tätigkeiten mit dieser Eigenschaft aus oder sollten sie solche Tätigkeiten ausführen? (etwa in dem sie andere Eigenschaften auf Konsistenz überprüfen, Daten sammeln etc.)
  • Proposed by: Oursana (talk)

Motivation. We need this property to link items to their lists.Oursana (talk) 13:26, 12 August 2014 (UTC)

  • Pictogram voting question.svg Question: I fail to see why we need to link items to lists. And I fail to see the purpose of items such as island of Japan (Q17308006) in the example. The items for any Japanese island, can just have statements declaring them to be 1) Japanese, and 2) islands, so why should they need island of Japan (Q17308006)? Please explain, regards Dipsacus fullonum (talk) 23:40, 15 August 2014 (UTC)

file URL[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: Like image (P18), but for non-free files.
  • So... how to use those links? Is those URLs are allowed to be embedded? Do they have privacy policy? Does site that uses Wikidata need to inform users that some of queries are sent to unknown website? Will this website be happy for direct-linking of images? At least, do you understand, this property will be unusable on wikimedia project without complex bot-support system on local wikis? -- Vlsergey (talk) 14:33, 15 August 2014 (UTC)
  • Symbol support vote.svg Support I've been thinking about something like this for many months. --Jakob (talk) 00:14, 16 August 2014 (UTC)
  • Symbol oppose vote.svg Oppose: Non-free images cannot be used, so I see no the point in linking to them. Regards, Dipsacus fullonum (talk) 14:03, 21 August 2014 (UTC)

has quality[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: the entity has an inherent or distinguishing characteristic that cannot be migrated
  • Necessary to describe generic qualities of concepts. Micru (talk) 15:25, 15 August 2014 (UTC)

used by[edit]

Wikidata:List of properties • v · d · e
Status:    In progress
  • Description: the person or organization that uses an object or a facility
  • Generic property for linking the entity being used and agent using it (the above "has agent" links an action with the agent performing it).--Micru (talk) 11:04, 17 August 2014 (UTC)