Re:, Enumerations and Wikidata proposal

I see the wish to have a bit more stable identifiers for enumerated values, but I have serious doubts that importing snapshots of those into the namespace is a lasting solution. If there is one thing I have learned from deriving vocabularies from external standards like eClass etc., it's that infrequent, static translations of an independently evolving external standard cause a lot of problems.

Language and standards are living things and they need to evolve.

If the sponsors of need more stability, they should IMO use cached versions of Wikidate entries internally for data quality heuristics in markup. 

It would also be useful to have a better versioning mechanism directly built into Wikidata.

But exporting static snapshops does not seem to be a good move to me.

By the way, we have shown a few years ago that even Wikipedia URIs are pretty stable at the level of what they identify despite the heavy amount of edits, see

Just my two cents, of course ;-)



martin hepp          @mfhepp

> On 11 Apr 2017, at 18:16, R.V.Guha <> wrote:
> There are many 'lists' or 'enumerations' (such as the list of countries, languages, ...). Often, markup wants to refer to items from such lists. Since we have the corresponding types, pages can refer to them via descriptions (e.g., 'a country with the name xxx'). It would be useful to have canonical lists of urls for items on these lists to help with reconciliation, etc. 
>  The proposal is to periodically (with every release) import particular lists from Wikidata into ''. So, '', '', etc. Along with each item (such as, we should also import a set of attributes/relations from Wikidata so that we have a description of the node, which can help with recon using reference by description. It will also include a sameAs link to the corresponding Wikidata item.
> will also suggest the use of Wikidata as a common, canonical entity repository for targets of the sameAs relation.
> Denny & Guha

Received on Thursday, 13 April 2017 11:37:03 UTC