Shortcuts: WD:PP/GEN, WD:PP/Generic

Wikidata:Property proposal/Generic

From Wikidata
Jump to navigation Jump to search


Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Computing Lexeme

See also

[edit]

This page is for the proposal of new properties.

Before proposing a property

  1. Search if the property already exists.
  2. Search if the property has already been proposed.
  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. Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
  6. Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.

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 creation of the proposal, by a property creator or an administrator.
  3. See property creation policy.

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 2024/07.

General

[edit]

‎relates to sustainable development goal, target or indicator

[edit]
   Under discussion
Descriptionindicates a relation between the subject and the SDGs or one of the components
Data typeItem
Domainitem
Allowed valuesItems that are instance of (P31): Sustainable Development Goal (Q53580881), Sustainable Development Goal Target (Q56724848), or Sustainable Development Goal Indicator (Q56726345). And also Sustainable Development Goals (Q7649586) itself.
Example 1biodiversity (Q47041)Sustainable Development Goal 15 (Q53581245)
Example 2climate change adaptation (Q260607)Target 13.1 of the Sustainable Development Goals (Q57590883)
Example 3Sendai Framework for Disaster Risk Reduction (Q22907841)Indicator 13.1.2 of the Sustainable Development Goals (Q57595592)
Example 4early neonatal mortality rate (Q97210258)Indicator 3.2.2 of the Sustainable Development Goals (Q57595404)
Planned useAdd on phenomena, processes and policies.
Wikidata projectWikiProject Sustainable Development (Q56507949)

Motivation

[edit]

A property like this will make it much easier to connect Wikidata items to the Sustainable Development Goals (Q7649586) and enable a straightforward and queryable data model. Ainali (talk) 15:25, 19 May 2024 (UTC)[reply]

Daniel Mietchen (talk) 21:28, 15 May 2018 (UTC) Gregor Hagedorn (talk) 15:38, 23 September 2018 (UTC) Ainali (talk) 08:00, 14 October 2018 (UTC) Michael Cieslik (talk) 13:52, 26 November 2018 (UTC) Pdehaye (talk) 00:50, 16 February 2019 (UTC) Cassandreces (talk) 17:22, 19 February 2019 (UTC) Pauljmackay (talk) 18:32, 2 March 2019 (UTC) Will (Wiki Ed) (talk) 16:31, 24 March 2020 (UTC)[reply]
Notified participants of WikiProject Sustainable Development. Ainali (talk) 15:38, 19 May 2024 (UTC)[reply]

Discussion

[edit]
  •  Support We need better mechanisms to tag relationships of Wikidata entities to such measures of sustainable development, and the proposed approach looks good to me. --Daniel Mietchen (talk) 00:43, 20 May 2024 (UTC)[reply]
  •  Oppose Generally, is a label that's longer than the property description a bad indication.
Properties exist to specify how two entities are related. This property just says that they are somehow related which is very imprecise. If we take early neonatal mortality rate (Q97210258) and Indicator 3.2.2 of the Sustainable Development Goals (Q57595404), I would call that relationship something like "is measured by" (and maybe we can find an even better name). ChristianKl22:45, 21 May 2024 (UTC)[reply]
I agree that it is a long label, and was contemplating inf the "relates to the SDGs" would have been a good enough one, but thought that it might not have shown the intended use clearly enough. But perhaps that should be switched, I am very open to that.
Regarding specifying the relation, generally I would agree with you. But in this collection, and for all different kinds of items and how they could be connected with the goals, targets or indicators, it would be too complex to create an overview in a query to find out what is having a relation to, for example, a specific indicator. Yes, it is a generic relation, but as the relations are to a well-defined and particularly notable subset of items of high general interest, I think it is called for. Ainali (talk) 06:39, 22 May 2024 (UTC)[reply]
If I want to know what has relationships to a specific indicator, I could just look at that page and use the reverse label. I would expect that there are also other ways you can write your query.
As far as this being a particularly notable subset of items, to me that means that it's even more important to be specific about how they relate to other items. ChristianKl14:24, 23 May 2024 (UTC)[reply]
  •  Oppose The SDGs are unscientific, flawed, and self-defeating / self-contradicting. The main reason for why this shouldn't be included however is that nearly everything has some kind of relation to them (colloquially speaking). Instead of using very flawed overly broad subjective inspecific goals some alternative(s) could be used and these may already exist such as climate change mitigation (Q898653), methane emissions mitigation (Q124806283) or pollution prevention (Q7225750) which are in need of complements and expansion. --Prototyperspective (talk) 11:38, 24 May 2024 (UTC)[reply]
  •  Support -- LevandeMänniska (talk) 12:39, 2 June 2024 (UTC)[reply]
  •  Support Would be useful for eg many governmental projects explicitly targeting sustainability goals. -- Arvelius (talk) 13:10, 2 June 2024 (UTC)[reply]
    How would it be "useful"? Also I don't see why it wouldn't be better to just use clearer alternatives. Prototyperspective (talk) 13:18, 2 June 2024 (UTC)[reply]
    Are you arguing against the SDGs? This property proposal is not about their usefulness, but how we can describe what is happening in the world, and in that sense it is useful. Whether you like them or not, it is undeniable a framework that is used by the United Nations and a majority of the member states when developing policy. Besides the examples above we have items like Sustainable Development Goal 12 in the European Union (Q122222559), Sustainable Development Goals and Australia (Q104856926), Sustainable Development Investment Partnership (Q25215461), Q110547062 etc. Even for a critic, it would be useful to be able to see how things connect according to this framework, especially since it won't exclude other properties to be developed if you have suggestions on other frameworks to document. One could say that religion or worldview (P140) or official religion (P3075) are not useful nor scientific, but as Wikidata editors, we should describe that those are used in the world, whatever we ourselves think about them. Ainali (talk) 08:55, 3 June 2024 (UTC)[reply]
    Yes but that is only one of two objections I have against including these, please see above for some links about why I object to them, e.g. because they're themselves against sustainability, and the other reason. Countries don't actually use this framework when making policy, and there have been studies about whether they do. Again, nearly everything has a relation to them in some way. Instead, of linking this at nearly every page and advocating for SDGs on Wikidata, with btw no usefulness beyond that, people should invest their time in expanding and integrating specific goals such as "Methane emissions reduction". Official religion for example is scientific as that can be objectively evaluated, in many cases countries have that even codified somehow. Yes, we should describe things of the real world which is why there is a wikidata item and Wikipedia article(s) for the SDGs, they don't need to be linked at every economy or environment-related page. Prototyperspective (talk) 12:04, 3 June 2024 (UTC)[reply]
    I would oppose less if this was used only sparingly for items as related to each as early neonatal mortality rate (Q97210258) to Indicator 3.2.2 of the Sustainable Development Goals (Q57595404). And, again, more specific goals and problems are not yet well featured in WD so it would be better if people did that first or at least alongside this instead of mostly only having SDG items and properties. SDGs are not good or well suited as the only framework for considering global issues / problems in terms of measuring, formalizing and addressing them. Prototyperspective (talk) 09:39, 4 June 2024 (UTC)[reply]
    @Ainali:, could you please clarify the comments above by @Prototyperspective:. @Prototyperspective, ChristianKl: any changes in your opinion? Regards, ZI Jony (Talk) 06:43, 5 July 2024 (UTC)[reply]
    @ZI Jony Sure. The request for other goals is a bit of whataboutism in my opinion. We can of course have several properties for different frameworks in Wikidata, but the lack of interest in other frameworks is not relevant to this proposal. Regarding the framework not being used is an unsupported claim. It is clear that the EU member states, for example, report about their progress and that it is aggregated upwards so there must be hundreds if not thousands of civil servants dedicated just to the reporting. Ainali (talk) 13:01, 5 July 2024 (UTC)[reply]
    Thank you, it makes sense...I only very weakly oppose it at this point (mainly due to concerns of how the property would be used) but think the item should only be used for items directly matching the SDG goal as the one in the example not also to items somewhat related/relevant to them. Prototyperspective (talk) 14:40, 5 July 2024 (UTC)[reply]
    I still think that it's better to specify the nature of a how the two relate in a property and not only that the object of the property has something to do with sustainable development goals. ChristianKl19:33, 6 July 2024 (UTC)[reply]
    @Ainali:, could you please look into comments above. Regards, ZI Jony (Talk) 03:55, 17 July 2024 (UTC)[reply]
    @Ainali:, could you please look into comments above by @Prototyperspective, ChristianKl:. Regards, ZI Jony (Talk) 04:06, 21 July 2024 (UTC)[reply]
    Yes! I think a way to mitigate blatant adding of only loosely connected items would be to have a property constraint reminding that this property needs a source. That way, at least someone else has had the judgement to make the connection, rather than it being "original research" by the Wikidata user. Ainali (talk) 09:22, 25 July 2024 (UTC)[reply]
  •  Support AmandaSLawrence (talk) 02:23, 4 June 2024 (UTC) Would be useful for grouping SDG related entities and reuse of wikidata in SDG projects[reply]

agent of action

[edit]

Motivation

[edit]

I would like to create a data model to describe notable actions agents have made that are described in various Wikimedia articles. We should allow users to document actions so that they can be used to create timelines of events that can then be easily translated. They can also be used as a source to generate detailed Wikipedia article content for Abstract Wikipedia.

This property is the first to be proposed of the data model and follows the Schema.org data model for actions: https://schema.org/Action

participant (P710) exists, however that's usually used usually for events and not actions. It also requires that you use object has role (P3831) to specify the role of the participant. For a relationship as critical and common as an agent is to the action they perform, we should have a dedicated property and not be required to add object has role (P3831)agent (Q24229398) to every single agent statement. Lectrician1 (talk) 22:08, 30 January 2023 (UTC)[reply]

Discussion

[edit]

exception to constraint (lexeme)

[edit]

Motivation

[edit]

For constraints, we need the equivalent of exception to constraint (P2303), but for lexemes. In particular, it is necessary for identifier properties used on lexemes (usually linking to dictionaries which often have a few weird exceptions like natural languages often have).

Lucas Werkmeister (WMDE)
Jarekt - mostly interested in properties related to Commons
MisterSynergy
John Samuel
Sannita
Yair rand
Jon Harald Søby
Pasleim
Jura
PKM
ChristianKl
Sjoerddebruin
Fralambert
Manu1400
Was a bee
Malore
Ivanhercaz
Peter F. Patel-Schneider
Pizza1016
Ogoorcs
ZI Jony
Eihel
cdo256
Epìdosis
Dhx1
99of9
Mathieu Kappler
Lectrician1
SM5POR
Infrastruktur

Notified participants of WikiProject property constraints

Cheers, VIGNERON (talk) 12:37, 1 October 2023 (UTC)[reply]

Discussion

[edit]

voting date

[edit]
   Under discussion
Descriptionvote date, date on which people decided or cast their ballot
Representslegal act (Q1864008)
Data typePoint in time
Template parameter"date votation" in fr:modèle:Infobox Initiative suisse
Example 1French constitutional referendum, 1958 (Q2319128)28 septembre 1958
Example 2Federal popular initiative "for the protection against gun violence" (Q663241)13 février 2011
Example 31932 German presidential election (Q706684)13 mars 1932 + 10 avril 1932
Example 4Veil Act (Q3258255)20 décembre 1974
Example 52024 United Kingdom general election (Q78851988)4 juillet 2024
Example 62000 United States elections (Q7892455)7 novembre 2000
Single-value constraintyes but there can be exceptions (two-round system (Q615255))
Wikidata projectWikiProject Law (Q8486941) WikiProject Human Rights (Q115677469)

Motivation

[edit]

To help distinguish votes/votations/referendums/laws between announcement date (P6949) effective date (P7588) and date of promulgation (P7589) and publication date (P577)Bouzinac💬✒️💛 05:25, 2 July 2024 (UTC)[reply]

Discussion

[edit]
  • Given that there are going to be a lot of expections I don't think a single value constraint is a good idea. Many modern elections allow people to cast their ballets before polls open via mail-in voting. The current description would suggest that all dates where mail-in voting was acting would be a "date de vote". ChristianKl21:42, 8 July 2024 (UTC)[reply]
    @Bouzinac:, could you please clarify the comments above by @ChristianKl:. Regards, ZI Jony (Talk) 03:31, 12 July 2024 (UTC)[reply]
    Yes, it's difficult to model since you have plenty of ways to voting. There are countries where double voting is common (first round and second round), where you can cast ballot in different ways (voting proxy, mail, etc). There would be three way to solving this:
    • either set a "date of vote/last day of possible vote" and having a single-value-constraint. It would mean the last day where a ballot can be casted/counted is the one to record.
    • or set a "date of vote(s)" and having a single-value-suggestion. Letting people set the context with qualifyers.
    • or decide to rephrase the property as to the main date (the most common significative date : that is the date where most of ballots are to be decisive/counted) + single value constraint
    I don't have any preference. Thoughts? Bouzinac💬✒️💛 19:21, 12 July 2024 (UTC)[reply]
    @ChristianKl:, would you like to give your final opinion based on the response? Regards, ZI Jony (Talk) 03:18, 14 July 2024 (UTC)[reply]
    Given that the property still lacks an English name, it's far from a state where it warrents anything like a final response.
    The ideal way forward would be to look at prior art and see how other people define the concept to see whether someone else has already come up with a good definition. Maybe, some UN agency that cares about voting has a controlled vocabulary that has a term? Maybe someone else? ChristianKl11:51, 15 July 2024 (UTC)[reply]
    @ChristianKl: proposal updated by @Swpb:. Regards, ZI Jony (Talk) 04:08, 17 July 2024 (UTC)[reply]

‎object of action & object class of action

[edit]

‎object of action (aliases: action applies to item | target of action | undergoer | patient )

[edit]

‎object class of action (aliases: action may apply to items of the class | target class of action | undergoer class | patient class )

[edit]
Descriptionclass of objects to which an action or class of actions may occur
Representsundergoer (Q111335542)
Data typeItem
Domaininstance or subclass of occurrence (Q1190554)
Example 1window cleaning (Q3124765)object class of actionwindow (Q35473)
Example 2Date cultivation in Dar al-Manasir (Q5227606)object class of actiondate (Q1652093)
Example 3(as qualifier) HTTP client (Q2979024)has use (P366)sending (Q115088683)object class of actionHTTP request (Q4344724)
Example 4(as qualifier) 2022 United States infant formula shortage (Q112002363)has effect (P1542)dilution (Q3028008)object class of actioninfant formula (Q2287198)

Motivation

[edit]

Needed to link occurrences to items that are affected, more broadly than possible with existing properties. This proposal addresses the concerns of the previous proposals here and here. Specifically, there was concern that taking both instances and classes as values would lead to ambiguity, so I've split the proposal in two: one property for actions that apply to specific objects, and one property for actions that may apply to members of a class.

I'm proposing these as both main and qualifier properties. Although main statements could be recast to use the properties as qualifiers (e.g., fall of the Berlin Wall (Q69163529)instance of (P31)demolition (Q331483)object of actionBerlin Wall (Q5086)), I think the direct linking of occurrence and object makes for easier querying.

A major immediate use of these properties will be migration away from of (P642). They represent a well-defined thematic relation (Q613930) (see also WikiProject Events and Role Frames), vs. the hundreds of relations that "of" is used for. The use case is captured on WikiProject Data Quality/Issues/P642 as "oc5".

The only existing property approaching this role is participant (P710), but it is restricted to people/groups of people, and does not specify whether they occupy a semantic role of agent or patient. victim(s) (P8032) and target (P533) would be sub-properties of "‎object of action".

@ChristianKl, Liuxinyu970226, Push-f, JAn Dudík, Lectrician1, BlaueBlüte: (previous participants)

Swpb (talk) 19:28, 16 July 2024 (UTC)[reply]

Discussion

[edit]
Thanks! Swpb (talk) 00:22, 25 July 2024 (UTC)[reply]
You're welcome. Regards, ZI Jony (Talk) 10:15, 25 July 2024 (UTC)[reply]

tastes like

[edit]
   Under discussion
Descriptiontaste that a food or drink has
Data typeString
Example 1apple pie (Q1068034)schmeckt nachapple (Q89)
Example 2Cuba libre (Q471753)schmeckt nachcola (Q134041)
Example 3Nogger (Q1995439)schmeckt nachchocolate (Q195)
Wikidata projectBunte Tüte (Q127598560)

Motivation

[edit]

(Die Eigenschaft "schmeckt nach" ermöglicht eine präzise Beschreibung des Geschmacks von Lebensmitteln und Getränken auf Wikidata. Dies ist besonders nützlich für die Gastronomie, Lebensmittelwissenschaft und Konsumenten, die nach spezifischen Geschmäckern suchen. Darüber hinaus trägt die Eigenschaft zur Bereicherung der Datenbank bei und unterstützt die Verknüpfung von Produkten und deren Geschmacksprofilen auf einer strukturierten und zugänglichen Weise.)  – The preceding unsigned comment was added by Geja3001 (talk • contribs) at 14:38, July 18, 2024‎ (UTC).

Discussion

[edit]

identifier of FranceTerme

[edit]
   Under discussion
Descriptionidentifier of a term recommended by the Commission d'enrichissement de la langue française (French language enrichment commission)
RepresentsFranceTerme (Q3080560)
Data typeExternal identifier
Example 1commonality (Q110765520)[1]
Example 2no frills (Q1365464)[2]
Example 3fake news (Q28549308)[3]
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.culture.fr/franceterme/terme/$1

Motivation

[edit]
FR: FranceTerme regroupe les termes recommandés et publiés au Journal Officiel de la République Française. A l'heure actuelle, cette base de données compte 8060 termes qui pourraient être liés à Wikidata. YotaMoteuchi (talk) 08:05, 24 July 2024 (UTC)[reply]
EN: FranceTerme includes recommended terms published in the Journal Officiel de la République Française. At present, this database contains 8060 terms that could be linked to Wikidata. YotaMoteuchi (talk) 08:05, 24 July 2024 (UTC)[reply]

Discussion

[edit]

‎has semantic role

[edit]
   under discussion
Descriptionitem that describes a role in an event/action class
Data typeItem
Domainitem, occurrence (Q1190554)
Example 1military offensive (Q2001676)"has semantic role"attacker (Q31924059)object has role (P3831)agent (Q392648)
Example 2military offensive (Q2001676)"has semantic role"defender (Q111729140)object has role (P3831)theme (Q118826633)
Example 3throwing (Q12898216)"has semantic role"actor (Q23894381)object has role (P3831)agent (Q392648)
Example 4throwing (Q12898216)"has semantic role"target (Q1047579)object has role (P3831)theme (Q118826633)
Example 5throwing (Q12898216)"has semantic role"projectile (Q49393)object has role (P3831)destination (Q111335358)
Planned useadd to (possibly newly created) items describing occurrences/actions
Expected completenessalways incomplete (Q21873886)


This proposal is a substantial revision of Wikidata:Property proposal/has semantic role.

Motivation

[edit]

Consider concepts that describe classes of events, actions and processes, roughly the subclasses of "occurrence (Q1190554)". For the lack of a better inclusive term, we call them "event/action" classes. (They are sometimes called "eventualities" in linguistic literature.) All event/action classes have core semantic roles, as illustrated by widely used resources such as "FrameNet (Q1322093)", "VerbNet (Q7920918)" and "PropBank (Q7250039)". For example, “eating" has an "eater" and something "eaten"; "throwing" has the "thrower", the "target" and the "projectile". These roles are not optional. Every act of "eating" has an "eater" and something "eaten" independently of how it is expressed and in what language. While Wikidata has over 300 existing properties for roles in event/action instances (e.g., "participant (P710)", "victim(s) (P8032)"), there are very few that are used with event/action classes. The two most common are "practiced by (P3095)" and "uses (P2283)". The vast majority of event/action classes have no statements describing semantic roles. For example, until very recently, "military offensive (Q2001676)" didn't have any semantic roles at all. Clearly, every military offensive has an attacker and a defendant. We added these roles using two statements:

military offensive (Q2001676)has characteristic (P1552)attacker (Q31924059)object has role (P3831)agent (Q392648)

military offensive (Q2001676)has characteristic (P1552)defender (Q111729140)object has role (P3831)theme (Q118826633)

Here, "agent (Q392648)" and "theme (Q118826633)" are instances of "thematic relation (Q613930)". The property "has characteristic (P1552)" is extremely generic and has many uses. Our proposed “has semantic role” property would be a specific sub-property of "has characteristic (P1552)" for designating semantic roles.

Some of the existing event/action classes already have statements indicating semantic roles. For example, the creator in "creation (Q11398090)" is indicated by the "practiced by (P3095)" property. We would not change this, but, since this property has many uses, we added a qualifier:

creation (Q11398090)practiced by (P3095)creator (Q2500638)object has role (P3831)agent (Q392648)

The item "creation (Q11398090)" did not have a statement for the "object of creation" role. So, we added:

creation (Q11398090)has characteristic (P1552)artificial object (Q16686448)object has role (P3831)theme (Q118826633)

If we had the proposed "has semantic role" property, we would have used it instead of the generic "has characteristic (P1552)" property.

This proposal is a part of a wider project: "Wikidata:WikiProject_Events_and_Role_Frames". We encourage the interested parties to visit and join the project discussion. Anatole Gershman (talk) 21:53, 23 July 2024 (UTC)[reply]

Discussion

[edit]
 Strong support I find the proposal much improved and fully support it. Peter F. Patel-Schneider (talk) 23:18, 24 July 2024 (UTC)[reply]
I am very happy with this proposal and also strongly support it. MarthaStonePalmer (talk) 22:48, 24 July 2024 (UTC)[reply]

‎FDC ID

[edit]
   Under discussion
DescriptionU.S. Department of Agriculture FoodData Central ID
Representsfood (Q2095)
Data typeExternal identifier
Example 1chicken egg (Q15260613)747997
Example 2apple (Q89)168204
Example 3whole wheat bread (Q14650718)335240
Example 4Coca-Cola (Q2813)2678649
Sourcehttps://fdc.nal.usda.gov/
Number of IDs in source467293 (according to the tab bar)
Formatter URLhttps://fdc.nal.usda.gov/fdc-app.html#/food-details/$1/nutrients
See alsoUSDA NDB number (P1978)

Motivation

[edit]

contains nutritional data about generic foods (13807) and branded food products (453486). USDA NDB number (P1978) seems to be an entirely different id but the website provides a mapping to the FDC ID:

buttermilk (Q106612)USDA NDB number (P1978)1088 → FDC ID → 2259792

Shisma (talk) 07:42, 25 July 2024 (UTC)[reply]

Discussion

[edit]

@Elf_Pavlik, Kolja21, Pigsonthewing, Vladimir Alexiev, Bluerasberry, Hackfish:

Teolemon
Vladimir Alexiev
Ash_Crow
d1g
Dhx1
Tris T7 TT me
Gobonobo
Ainali
Wkee4ager
Rtnf
Dguarrac
Middle river exports (talk) 13:59, 5 September 2022 (UTC)[reply]
Wolfgang8741

Notified participants of WikiProject Food