Property talk:P10692

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

DBLP event ID
identifier for scientific events in the DBLP computer science bibliography

Applicable "stated in" value	dblp computer science bibliography (Q1224715)
Data type	External identifier
Domain	event (Q1656682)
Example	ACM/IEEE Joint Conference on Digital Libraries 2002 (Q109515931) → conf/jcdl/jcdl2002 The 10th International Conference on Knowledge Capture (Q109471275) → conf/kcap/kcap2019 Twenty-first National Conference on Artificial Intelligence (Q73134823) → conf/aaai/aaai2006 Visualization in Medicine and Life Sciences II - Progress and New Challenges (Q106087666) → books/daglib/0027960 4th Asian Conference on Machine Learning, ACML 2012, Singapore, Singapore, November 4-6, 2012 (Q106330794) → journals/jmlr/jmlrp25 Seventeenth Conference on Theoretical Aspects of Rationality and Knowledge, TARK 2019, Toulouse, France, 17-19 July 2019 (Q106246384) → series/eptcs/eptcs297 Philosophy and Theory of Artificial Intelligence, PT-AI 2011, Thessaloniki, Greece, October 3-4, 2011 (Q106332070) → series/sapere/sapere5
Source	https://dblp.org/
Formatter URL	https://dblp.org/db/$1
See also	DBLP venue ID (P8926), DBLP publication ID (P8978), DBLP author ID (P2456)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P10692 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 2,497 Main statement 2,490 out of 45,000 (6% complete) 99.7% of uses Qualifier 7 0.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10692#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10692#Unique value, SPARQL (every item), SPARQL (by value)

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10692#Entity types

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10692#Scope, SPARQL

Type “event (Q1656682)”: item must contain property “instance of (P31), subclass of (P279)” with classes “event (Q1656682)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P10692#Type Q1656682, SPARQL

Proceedings != Events

Dear all, MRA from DBLP here. We agree that dblp event IDs are an important concept. But please be aware that the ID format https://dblp.org/db/$1.html you created here does, in fact, not link to events, but to proceedings volumes in dblp. Those two concepts are not the same, and there is a many-to-many relationship between those. Modeling of events is actually not yet final in dblp, and I unfortunately cannot give you a correct ID and/or link target for events yet. So before entering tens of thousands of of improper links that need to be corrected at a later date, please be aware of those points I already added to the property proposal discussion, which are still relevant today:

• As for the events of a conference series, the modeling 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 events 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'.

-- MRA (talk) 10:08, 20 May 2022 (UTC)

@MRA: I totally agree and believe this was created in error with little useful feedback. In general one can use either the DBLP publication ID (P8978) or DBLP venue ID (P8926) which are stable and the contents are often 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 which are used for other things. I see no reason to want to create/keep a property and any 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) via such. Thank you for your feedback here. —Uzume (talk) 01:31, 22 June 2022 (UTC)