Currently DBLP ID is modeled as External identifier for the Event Series or the Event. However, with regards to using the DBLP ID in this way Marcel Ackermann wrote the following:
"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.
Also, please don't semantically confuse the table of contents of a proceedings volume, e.g. given by resource URI
with the actual conference event of JCDL 2002. They may be closely related, and often in a one-to-one relationship, but they are not the same. In general, the relation is many-to-many with plenty of crazy examples for crazy situations.
Additionally, conference event do not have a final ID in dblp, yet. In past collaborations we used intermediate resource URIs like
to identify an event (and they still do work), but it remains undecided if that will be their final form. 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."
Therefore, it might be better to consider the DBLP ID as an identifier for a Publication .
Currently DBLP ID is modeled as External identifier for the Event Series or the Event. However, with regards to using the DBLP ID in this way Marcel Ackermann wrote the following:
"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.
Also, please don't semantically confuse the table of contents of a proceedings volume, e.g. given by resource URI
https://dblp.org/db/conf/jcdl/jcdl2002
with the actual conference event of JCDL 2002. They may be closely related, and often in a one-to-one relationship, but they are not the same. In general, the relation is many-to-many with plenty of crazy examples for crazy situations.
Additionally, conference event do not have a final ID in dblp, yet. In past collaborations we used intermediate resource URIs like
https://dblp.org/db/conf/jcdl/index#2002 https://dblp.org/streams/conf/jcdl#2002
to identify an event (and they still do work), but it remains undecided if that will be their final form. 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."
Therefore, it might be better to consider the DBLP ID as an identifier for a Publication .