Property talk:P2456
Documentation
identifier for author entries in the DBLP computer science bibliography (use portion of DBLP person key after pid/)
\d{2,3}\/\d+(-\d+)?[a-zA-Z-]*(-\d+)?|[a-z]\/[0-9A-Za-z]*(-\d+)?
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P2456#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2456#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P2456#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2456#Type Q5, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2456#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2456#Scope, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Pattern ^/(\d{2,3}/\d+|[a-z]/[a-zA-Z][0-9A-Za-z]*)$ will be automatically replaced to \1. Testing: TODO list |
Pattern ^/?(\d{2,3}/\d+|[a-z]/[a-zA-Z][0-9A-Za-z]*)\.html$ will be automatically replaced to \1. Testing: TODO list |
|
Objections and corrections
editI realize this property was already created, however, I strongly disagree with how it is implemented. It should not just be a relative URL as that could include anything. For example, these all refer to the basically the same thing and should not be included:
- http://dblp.org/news/2016
- http://dblp.org/news/hc/2016
- http://dblp.org/news/hy/2016
- http://dblp.dagstuhl.de/news/2016
- http://dblp.dagstuhl.de/news/hc/2016
- http://dblp.dagstuhl.de/news/hy/2016
- http://dblp.uni-trier.de/news/2016
- http://dblp.uni-trier.de/news/hc/2016
- http://dblp.uni-trier.de/news/hy/2016
- http://dblp2.uni-trier.de/news/2016
- http://dblp2.uni-trier.de/news/hc/2016
- http://dblp2.uni-trier.de/news/hy/2016
Also it should be noted all the following are references to basically the same person at DBLP:
- http://dblp.org/pers/l/Ley:Michael
- http://dblp.org/pers/hd/l/Ley:Michael
- http://dblp.org/pers/ht/l/Ley:Michael
- http://dblp.org/pers/hc/l/Ley:Michael
- http://dblp.dagstuhl.de/pers/l/Ley:Michael
- http://dblp.dagstuhl.de/pers/hd/l/Ley:Michael
- http://dblp.dagstuhl.de/pers/ht/l/Ley:Michael
- http://dblp.dagstuhl.de/pers/hc/l/Ley:Michael
- http://dblp.uni-trier.de/pers/l/Ley:Michael
- http://dblp.uni-trier.de/pers/hd/l/Ley:Michael
- http://dblp.uni-trier.de/pers/ht/l/Ley:Michael
- http://dblp.uni-trier.de/pers/hc/l/Ley:Michael
- http://dblp2.uni-trier.de/pers/l/Ley:Michael
- http://dblp2.uni-trier.de/pers/hd/l/Ley:Michael
- http://dblp2.uni-trier.de/pers/ht/l/Ley:Michael
- http://dblp2.uni-trier.de/pers/hc/l/Ley:Michael
However, though these also refer to the same person at DBLP, these use the specified stable DBLP Person ID "l/MichaelLey":
- http://dblp.org/pid/l/MichaelLey
- http://dblp.org/rec/pid/l/MichaelLey
- http://dblp.dagstuhl.de/pid/l/MichaelLey
- http://dblp.dagstuhl.de/rec/pid/l/MichaelLey
- http://dblp.uni-trier.de/pid/l/MichaelLey
- http://dblp.uni-trier.de/rec/pid/l/MichaelLey
- http://dblp2.uni-trier.de/pid/l/MichaelLey
- http://dblp2.uni-trier.de/rec/pid/l/MichaelLey
The DBLP Person ID is specified here:
- "How to find the key of a person, a publication, or a stream?". FAQ. DBLP.
- Ley, Michael (2009). DBLP: Some Lessons Learned (PDF). VLDB. Proceedings of the VLDB Endowment. 2 (2). pp. 1493–1500. doi:10.14778/1687553.1687577. ISSN 2150-8097.
It also mentions publication keys and stream keys are separate name spaces and the publication keys can be used for linked data.
I propose this property be converted to DBLP pID used to refer to people (and we can later consider DBLP pubID or other possible identifiers with other properties). Uzume (talk) 17:45, 19 July 2016 (UTC) Erledigt
- I thought I would add that I have come across some links that do this:
- So apparently SIGMOD (Q7390336) and International Conference on Very Large Data Bases (Q7907150) have some sort of mirror/redirection logic—just adding to the list of URL synonyms that are out in the wild. 50.53.1.33 11:02, 8 November 2016 (UTC)
Format constraint
editWe have several exceptions to the format constraint now, which suggests the format constraint is incorrect. Is it possible to rewrite it so that all valid ids are recognised? — Martin (MSGJ · talk) 12:52, 11 March 2022 (UTC)