Wikidata:Property proposal/source of transfer & destination of transfer

From Wikidata
Jump to navigation Jump to search

‎source of transfer & destination of transfer[edit]

‎source of transfer[edit]

Originally proposed at Wikidata:Property proposal/Generic

Descriptionentity that a transferred item is initially associated with, before this process associates it with another entity (the destination of transfer) [aliases: source / sender]
Representssource (Q31464082)
Data typeItem
Example 1pitch (Q1063937)source of transferpitcher (Q1048902) / pitch (Q1063937)destination of transfercatcher (Q1050571)
Example 2data import into Wikidata (Q107661232)destination of transferWikidata (Q2013)
Example 3Alaska Purchase (Q309029)source of transferRussian Empire (Q34266)destination of transferUnited States of America (Q30)
Example 4radio broadcast (Q64707203)source of transfertransmitter (Q190157) / radio broadcast (Q64707203)destination of transferradio receiver (Q159391)
See alsoaddressee (P1817), start point (P1427) / destination point (P1444), target (P533), participant (P710)

‎destination of transfer[edit]

Originally proposed at Wikidata:Property proposal/Generic

Descriptionentity that a transferred item comes to be associated with as a result of this process [aliases: recipient / receiver / destination ]
Representsrecipient (Q20820253)
Data typeItem
Example 1see #source of action
Example 2see #source of action
Example 3see #source of action

Motivation[edit]

source (Q31464082) and recipient (Q20820253) are fundamental thematic roles in transfers (i.e., processes where an item starts off associated with one entity and becomes associated with another), and we do not currently have a simple way to express them. The only existing approach is to assign sources/recipients as values of participant (P710), uses (P2283), has part(s) (P527), or another property, and then to qualify those statements with object has role (P3831). participant (P710) is currently limited in scope to "person[s], group[s] of people or organization[s]", and uses (P2283) and has part(s) (P527) are vague and ill-suited to these roles. This approach is awkward and inconsistently used on main statements, and does not work at all when a source or destination is given by a qualifier.

We currently have some properties for specific types of transfers, such as addressee (P1817) for correspondence and start point (P1427) and destination point (P1444) for travel. The proposed properties would take those as sub-properties, while generalizing to all types of transfers, including physical, digital, legal, etc. (Note: although transfers may involve a wide variety of relations, including physical possession/containment, inclusion as a part, ownership, employment, etc., that does not mean the scope of the proposed properties is unlimited: values of "source" and "destination" must fulfill those thematic relations in context. In other words, there must be an item that is initially associated with the "source", and that comes to be associated with the "destination" in the same way, as a result of the process described by the subject.)

The item being transferred may be specified with uses (P2283) where necessary (leaving open the possibility of a future property for the thematic role of "item transferred"). It should be noted that the source of a transfer is not necessarily the cause of the transfer.

@Push-f, The-erinaceous-one, ZI Jony: Pinging based on participation in the last proposal; SM5POR already expressed intent to sit this one out.

Swpb (talk) 19:15, 17 April 2024 (UTC)[reply]

(By the way, there is another active proposal, "Event role", that seeks to link all sorts of events to the roles therein. The present proposal seeks to link transfers (a specific type of event) to the entities that occupy the specific roles (inherent to transfers) of source and destination. So these proposals are not competing, and are in fact complimentary. Swpb (talk) 20:31, 17 April 2024 (UTC))[reply]

Discussion[edit]

Easy:
1. pitch (Q1063937) → throwing (Q12898216)subclass of (P279)transfer (Q125506646)
2. Alaska Purchase (Q309029)instance of (P31)selling (Q3380760) (→ financial transaction (Q1166072) → transfer (Q125506646))
3. radio broadcast (Q64707203) → ... → information exchange (Q6031064)subclass of (P279)transfer (Q125506646)
Swpb (talk) 19:42, 22 April 2024 (UTC)[reply]
It mixes physical transfers and logical one, could be an issue if we are not careful. parent class tree. It's currently both a subclass of "spatio-temporal entity" (something physical) and "non-physical entity", a contradiction. I'm surprised it's not found as a disjointness violation. author  TomT0m / talk page 20:43, 22 April 2024 (UTC)[reply]
transfer (Q125506646) is not a subclass of abstract entity (Q7048977). It is supposed to include both physical and "logical" (e.g. information, legal) transfers; this does not create a contradiction. Swpb (talk) 20:28, 23 April 2024 (UTC)[reply]
@ChristianKl:, would you like to give your opinion based on the response? Regards, ZI Jony (Talk) 06:40, 26 April 2024 (UTC)[reply]
I waited some to see whether other people have more input, but I  Support it in the current state. ChristianKl ❪✉❫ 21:02, 28 April 2024 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/source_of_transfer_%26_destination_of_transfer&oldid=2143632121"