Objections and corrections
I 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:
Also it should be noted all the following are references to basically the same person at DBLP:
However, though these also refer to the same person at DBLP, these use the specified stable DBLP Person ID "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". VLDBProceedings of the VLDB Endowment 2 (2): 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)
- I thought I would add that I have come across some links that do this:
- So apparently SIGMOD (Q7390336) and VLDB (Q7907150) have some sort of mirror/redirection logic—just adding to the list of URL synonyms that are out in the wild. 22.214.171.124 11:02, 8 November 2016 (UTC)