Wikidata:Property proposal/PLDB ID
Programming Language Database ID
editOriginally proposed at Wikidata:Property proposal/Authority control
Description | identifier for a programming language's unique ID in the Programming Language Database |
---|---|
Represents | Programming Language DataBase (Q115663399) |
Data type | External identifier |
Domain | item; programming language (Q9143) computer language (Q629206) |
Allowed values | /^[a-zA-Z0-9-_]+$/ |
Example 1 | JavaScript (Q2005) → javascript |
Example 2 | C++ (Q2407) → cpp |
Example 3 | Perl (Q42478) → perl |
Example 4 | R (Q206904) → r |
Example 5 | Rust (Q575650) → rust |
Example 6 | Prolog (Q163468) → prolog |
Example 7 | Dart (Q406009) → dart |
Example 8 | OCaml (Q212587) → ocaml |
Example 9 | OpenCL (Q681360) → opencl |
Example 10 | Nim (Q20080327) → nim |
Example 11 | fish (Q307263) → fish |
Source | https://pldb.com/ |
Planned use | I will be adding WikiData ID values for entries in the PLDB soon. I'd be interested in writing a bot to do the reverse and automatically add PLDB ID values to WikiData but I'd have to review the guidelines around that first. Lastly, I'd like to explore writing some cross-checking logic for weird or missing values on both projects. |
Number of IDs in source | 4,222 (as of Dec 10, 2022) |
Expected completeness | eventually complete (Q21873974) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://pldb.com/languages/$1.html |
Robot and gadget jobs | converting the ids to urls. In the future we may also cross check both databases to find inconsistencies |
Applicable "stated in"-value | Programming Language DataBase (Q115663399) |
Distinct-values constraint | yes |
Wikidata project | WikiProject Computer Science (Q6526225) |
Motivation
editPLDB is an independent, open-source, community effort to create a database of programming languages (including markup languages and even some file formats) and their characteristics. Linking to domain-specific databases like these is extremely valuable to WikiData because, unlike the WikiData project, these databases can support highly specific fields like what characters a language uses for comments, how many job listings are available on certain platforms for that language, or what papers/conference talks/etc mention the language.
In addition, PLDB already has great support for other even smaller projects as well as some that, imo should already have had their own WikiData property (e.g. HOPL which tries to track the geneology of different programming languages).
Lastly, this link is can greatly benefit both projects by making it easier to write scripts/bots that can flag inconsistent data values for particular fields that we should expect to map up. If WikiData later adds a property that PLDB already has, it'd be trivial use PLDB's values as a launching point.
I will also have a PR up soon in the GitHub repo for this project to link up entries in PLDB with their corresponding WikiData ids. Tr3ndyBEAR (talk) 23:44, 10 December 2022 (UTC)
- Yes linking to more domain specific knowledge sources that support distinct-values constraint with no implied notability would differentiate wikidata from other similar websites.
- Link exchanges are what www was founded on, I am having a nostalgic flashback. Granted, its not for directories but for enumerating knowledge sources but it is still nostalgic. 117.213.160.246 02:13, 11 December 2022 (UTC)