Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-05-03 Thread Jerven Tjalling Bolleman
Hi Egon, All, If something is identifiable by a String, but there is no official RDF serialization. Then I would make the identifier property in question a subproperty of https://www.wikidata.org/wiki/Property:P973 The value should then be the "most" official url of a webpage having the

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-05-02 Thread Egon Willighagen
Hi Jerven, all On Fri, Apr 29, 2016 at 3:29 PM, Jerven Tjalling Bolleman wrote: > Could I be so bold to suggest that in Wikidata we should strive > to use external URI's for identifiers not Strings. > > For example in Wikidata, there are a lot of UniProt accessions. >

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-05-02 Thread Julie McMurry
> "For instance: in the following contexts expand the CURIE to the chembl webpage, in these other contexts, expand to the (sometimes unresolvable) HTTP URI, in these other contexts, expand to the wikidata page for the entity. " This context-specific expansion is of course not to preclude the use

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-04-29 Thread Markus Kroetzsch
I tend to agree with Jerven. He is right to say that URIs work best as identifiers. However, some things should still be kept in mind: * The strings we are talking about are in fact IDs and not ambiguous: no string id identifies multiple objects. * The problem is in finding the right web page

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-04-29 Thread Jerven Tjalling Bolleman
Could I be so bold to suggest that in Wikidata we should strive to use external URI's for identifiers not Strings. For example in Wikidata, there are a lot of UniProt accessions. e.g. behind the property https://www.wikidata.org/wiki/P352 and there is a formatter for a URL. I think this is the

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-04-28 Thread Sebastian Burgstaller
Thanks for your replies! I like the idea of a resolver service on labs, but I think it cannot solve the issue. e.g. for ChEMBL and IUPHAR (international union of pharmacology), there is no way to guess from the identifier onto the sub-domain this identifier belongs to. For ChEMBL, the pattern is:

Re: [Wikidata] Multiple properties/identifiers for the same resource

2016-04-27 Thread Markus Kroetzsch
On 27.04.2016 21:13, Sebastian Burgstaller wrote: Hi everyone, I am lately facing the following problem: There are many (biomedical) resources we import data from, which consist of several parts. And for each of these parts, they use either a different identifier structure, or they use the same

[Wikidata] Multiple properties/identifiers for the same resource

2016-04-27 Thread Sebastian Burgstaller
Hi everyone, I am lately facing the following problem: There are many (biomedical) resources we import data from, which consist of several parts. And for each of these parts, they use either a different identifier structure, or they use the same identifier structure but with different accession