Property talk:P8926
Jump to navigation
Jump to search
Documentation
DBLP venue ID
identifier for venue entries in the DBLP computer science bibliography (use portion of DBLP stream key after streams/)
identifier for venue entries in the DBLP computer science bibliography (use portion of DBLP stream key after streams/)
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P8926#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8926#Format, 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/P8926#Unique value, SPARQL (every item), SPARQL (by value)
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/P8926#Single value, SPARQL
Type “scientific conference series (Q47258130), scientific journal (Q5633421), conference proceedings series (Q27785883), academic journal (Q737498), disciplinary repository (Q5281480), academic workshop series (Q47459256), workshop proceedings series (Q99524688), book series (Q277759)”: item must contain property “instance of (P31)” with classes “scientific conference series (Q47258130), scientific journal (Q5633421), conference proceedings series (Q27785883), academic journal (Q737498), disciplinary repository (Q5281480), academic workshop series (Q47459256), workshop proceedings series (Q99524688), book series (Q277759)” 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/P8926#Type Q47258130, Q5633421, Q27785883, Q737498, Q5281480, Q47459256, Q99524688, Q277759, SPARQL
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/P8926#Scope, SPARQL
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/P8926#Entity types
Corrections
[edit]As per Wikidata:Property proposal/DBLP journal ID and Property talk:P2456#Objections and corrections, I rectified this property converting it to generalize it from just conferences to all streams/venues that DBLP has stream identifiers for. It should be noted that the current formatter URL (P1630) links by prefixing with https://dblp.org/db/
and suffixing with a /
. If it was just the prefix it would allow many more things than just records with DBLP streams identifiers e.g., if we allowed conf/icdt/icdt2020 we could get the contents for ICDT 2020, however, this does not have a stream ID (although DBLP states it has a BHT key of db/conf/icdt/icdt2020.bht
). —Uzume (talk) 11:47, 9 December 2020 (UTC)
- @Uzume: I don't understand sense of external id for mixed "streams". It's simple to create "DBLP journal ID", "DBLP conference ID", etc. And it's intuitive way how to do. e.g. Validation: You can simply validate instance of conference with "DBLP conference ID". In other way you need to know what is conference part of common external id, because it isn't described anywhere. I am against common external ids. Skim (talk) 23:31, 9 December 2020 (UTC)
- @Skim: You are welcome to discuss with Schloss Dagstuhl – Leibniz Center for Informatics (Q879857) about how they handle their identifiers. For Wikidata, it is better we do not attempt to manipulate their identifiers too much as they may well decide to change their formats and break things here. If it helps I added some instructions on how to obtain property values for this property from the stream keys published by dblp computer science bibliography (Q1224715). —Uzume (talk) 02:35, 10 December 2020 (UTC)
Categories:
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with format constraints
- Properties with unique value constraints
- Properties with single value constraints
- Properties with constraints on type
- Properties with scope constraints
- Properties with entity type constraints