Sorry, but aliases are not deferred labels. We use an alias to disambiguate between properties.
I don't think we have anything that is equivalent to DCterms coverage,... At least I hope not! An alias does not imply equivalence, not by a long shot. On Wed, Jul 8, 2015 at 5:45 PM, Daniel Kinzler <[email protected]> wrote: > Am 08.07.2015 um 17:34 schrieb John Erling Blad: >> You asked for an example, end those are valid examples. It is even an >> example that use one of the most used ontologies on the net. Other >> examples from DCterms is coverage, which can be both temporal and >> spatial. We have a bunch of properties that can have an alias "DCterms >> coverage", a country for example or a year. > > For cross-linking properties with other vocabularies, we use P1628 "Equivalent > Property", not aliases. I don't see how an alias would be useful for that. > P1628 > allows you to specify URIs, and it is itself marked as equivalent to > owl:equivalentProperty, so it can be used directly by reasoners. > >> Use a separate list of "deferred labels", and put the existing label >> on that if someone tries to edit the defined (preferred) label. That >> list should be unique, as it should not be possible to save a new >> label that already exist on the list of deferred labels. At some >> future point in time it can be implemented some clean up routine, but >> I think it will take a long time before name clashes will be a real >> problem. > > That's the idea, yes, we just call the deferred labels "aliases". > > > -- > Daniel Kinzler > Senior Software Developer > > Wikimedia Deutschland > Gesellschaft zur Förderung Freien Wissens e.V. > > _______________________________________________ > Wikidata mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata _______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
