Wikidata:Property proposal/solved by algorithm
Jump to navigation
Jump to search
solved by algorithm[edit]
Originally proposed at Wikidata:Property proposal/Generic
Not done
| Description | subject is a computational or mathematical problem, object is an algorithm, object solves subject |
|---|---|
| Data type | Item |
| Domain | item |
| Example 1 | cycle detection (Q60614789) → Floyd Cycle Detection Algorithm (Q1588200) |
| Example 2 | shortest path problem (Q1058754) → Bellman–Ford algorithm (Q816022) |
| Example 3 | single-source shortest path problem (Q105136353) → Bellman–Ford algorithm (Q816022) |
| Planned use | See this discussion for another case where this property could be used – and considering the number of computational/mathematical problems solved by some algorithm, there should be many more. |
| See also | computes solution to (P2159) |
Motivation[edit]
Sorry if this request is not as elaborated as it could be. Basically I’m suggesting to create an inverse property to computes solution to (P2159), to provide computational or mathematical problems with the algorithm(s) they are solved by. We appear to already have approximation algorithm (P1171), but no property for algorithms delivering exact solutions. --2A02:8108:50BF:C694:146A:852:36CA:CE6E 20:28, 16 October 2022 (UTC)
PS. We do have solved by (P1136), which is restricted to human (Q5) values. --2A02:8108:50BF:C694:146A:852:36CA:CE6E 20:30, 16 October 2022 (UTC)
Discussion[edit]
- This may be sometimes too many.--GZWDer (talk) 20:47, 16 October 2022 (UTC)
Oppose Inverse properties are not necessary and slightly harmful in Wikidata. ArthurPSmith (talk) 17:50, 17 October 2022 (UTC)
- Oppose no reason for the desireability of having an inverse property was provided. ChristianKl ❪✉❫ 13:36, 1 December 2022 (UTC)
Not done no support for creation --DannyS712 (talk) 17:25, 14 December 2022 (UTC)
