Wikidata:Property proposal/DBLP event ID
DBLP event ID edit
Originally proposed at Wikidata:Property proposal/Creative work
| Description | identifier for scientific events in the DBLP computer science bibliography |
|---|---|
| Data type | External identifier |
| Domain | scientific conference series (Q47258130) |
| Example 1 | ACM/IEEE Joint Conference on Digital Libraries 2002 (Q109515931) → conf/jcdl/jcdl2002 |
| Example 2 | The 10th International Conference on Knowledge Capture (Q109471275) → conf/kcap/kcap2019 |
| Example 3 | Twenty-first National Conference on Artificial Intelligence (Q73134823) → conf/aaai/aaai2006 |
| Source | dblp computer science bibliography (Q1224715) |
| Planned use | ConferenceCorpusBot |
| Number of IDs in source | ~45000 |
| Expected completeness | complete for events that are part of a conference series already referenced/indexed by dblp |
| Formatter URL | https://dblp.org/db/$1.html |
| Robot and gadget jobs | Planned ConferenceCorpus Bot |
| See also | https://www.wikidata.org/wiki/Property:P8926 |
| Wikidata project | Scholia (Q45340488) |
Motivation edit
Scientific event Series already have a dblp reference - external link while the events themselves do not since the pattern for the ids is slightly different and therefore the existing property can not be used. It will be useful for wikidata users to more quickly get to the actual dblp page for single event and e.g. find the relevant papers there.
Discussion edit
https://www.wikidata.org/wiki/Property:P8978 has been used in the past for this in some instances but it doesn't work in all cases: https://dblp.org/rec/conf/iwmm/ismm2020.html does not work it needs to be https://dblp.org/db/conf/iwmm/ismm2020.html
Currently the workaround seems to be to use https://www.wikidata.org/wiki/Property:P973 as in https://www.wikidata.org/wiki/Q106337697 -> conf/tacas/tacas2020-1
- I generally
Support this but if the value always starts with "conf/", this prefix should better be moved to the formatter URL https://dblp.org/db/conf/$1.html -- JakobVoss (talk) 11:04, 12 November 2021 (UTC)
Comment Full disclosure: I work on the dblp infrastructure. I'd like to add some information/clarifications to the proposal:
- Please be aware that there already is a "dblp venue id" https://www.wikidata.org/wiki/Property:P8926 which does represent the conference series (as well as journals and book series), which somehow should act as the parent for conference events. E.g., JCDL is https://dblp.org/streams/conf/jcdl
- As for the events of a conference series, the modelling of that part is still an ongoing and by far not finished process at dblp. Historically, events had been "entered" as inhomogeneously and manually created HTML fragments on static web pages, and we are still in the process of reverse engineering them into truly identifiable entities within dblp. A fair number of events are already uniquely identifiable, but many are still not.
- Please don't semantically confuse the table of contents of a proceedings volume (e.g. given by a resource URI like https://dblp.org/db/conf/jcdl/jcdl2002) with the actual conference event (e.g. JCDL 2002: https://www.wikidata.org/wiki/Q109515931). They may be closely related, and often in a one-to-one relation, but they are not the same. In general, the relation between conference events and proceedings volumes is many-to-many, with plenty of crazy examples for crazy situations.
- Additionally, conference event do not have a final ID in dblp, yet. We are currently using an intermediate resource URI (e.g. https://dblp.org/streams/conf/jcdl#2002 for JCDL 2002) to identify an event, but it remains undecided if that will be the final format. Furthermore, although in many cases like the example above, the event is identified by a four digit year, this does not always have to be the case. In general, we might use arbitrary, unique alphanumeric fragments like '2000-summer' or '1998eu'.
- I hope this information helps. There is still a lot of work to do on our end before we can confidently consider conference events first-class citizens within dblp's data model, but we try to improve. -- MRA (talk) 11:10, 16 November 2021 (UTC)
- Support —MasterRus21thCentury (talk) 18:51, 19 April 2022 (UTC)
- Support, an important property for literature.--Arbnos (talk) 15:00, 23 April 2022 (UTC)
- @WolfgangFahl, JakobVoss, MRA, Arbnos:
Done: DBLP event ID (P10692) —MasterRus21thCentury (talk) 18:39, 25 April 2022 (UTC)
Oppose for the reason mentioned by MRA. @WolfgangFahl: In general one can use either the DBLP publication ID (P8978) or DBLP venue ID (P8926) or which are stable and the contents are available via one extra click from there. Besides the fact that the naming of this proposed property is questionable as multiple proceeding publications can and have been generated at/by single events (and sometimes the reverse when multiple events happen at the same time and location), there is no stable API for linking or searching for these and any formatter URL (P1630) one might conceive of will also be able to link to other arbitrary "BHT" HTML fragments like https://dblp.org/db/about/advisoryboard.html which are used for other things. I see no reason to want to create a property and claims that link directly to such pages (and in any cases where we do, a URL property, of which we already have many, should suffice). —Uzume (talk) 01:24, 22 June 2022 (UTC)
