Hi all, On a side note I would like to mention that "labels" and "aliases" are external identifiers, perhaps not as accurate as database IDs, as natural language users tend to stretch the conceptual boundaries, but they can also be referenced and sourced.
If, as Lydia says, database IDs will have their own section (either only in the frontend, or also in the backend), I would recommend to use a similar method for sourcing+qualifying labels, as "natural language identifiers" and "database identifiers" share the same problems. On Freebase, database keys had a separate tab. Not sure if that is the right approach... Cheers, Micru On Sat, Apr 4, 2015 at 3:45 PM, Andy Mabbett <[email protected]> wrote: > On 4 April 2015 at 10:20, Thomas Douillard <[email protected]> > wrote: > > > I guess a class of properties ''external identifier definition property'' > > with isbn <instance of> external identifier prop could be useful as > well. > > The property for an ORCID iD (P 496), for example, is an instance of > "Wikidata > property for authority control for people" (Q19595382). That, in turn > is a sub-class of "Wikidata property for authority control" > (Q18614948) > > -- > Andy Mabbett > @pigsonthewing > http://pigsonthewing.org.uk > > _______________________________________________ > Wikidata-l mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata-l > -- Etiamsi omnes, ego non
_______________________________________________ Wikidata-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-l
