W3C home > Mailing lists > Public > public-schemaorg@w3.org > April 2017

Re: Schema.org, Enumerations and Wikidata proposal

From: Thomas Pellissier Tanon <thomas@pellissier-tanon.fr>
Date: Tue, 11 Apr 2017 19:05:22 +0200
To: "schema.org Mailing List" <public-schemaorg@w3.org>
Message-Id: <D9AEC5B3-4F3D-457E-82F7-93EA59C3BC20@pellissier-tanon.fr>
Maybe irrelevant:

I have beginning to work on a project that seems related. It aims to create a "lazy developper friendly" frontend for Wikidata using schema.org terms.
A demo is available here: https://kb.askplatyp.us (the endpoinds other than /api/v1/entity/ and /api/v1/search/simple are very experimental).
It is updated daily from Wikidata. The source code is here: https://github.com/askplatypus/platypus-kb-lucene
The mapping of properties and classes is currently very partial and hardcoded in the implementation for more stability.


> Le 11 avr. 2017 à 19:00, R.V.Guha <guha@guha.com> a écrit :
> On Tue, Apr 11, 2017 at 9:42 AM, Dan Brickley <danbri@google.com> wrote:
> Someone is also bound to mention versioning and whether Wikidata's
> type and property names are volatile and whether we should use Q12345
> IDs instead; I suggest we defer that conversation for now.
> Which is kind of why it would be better to periodically copy over. The stability expectations of wikidata vs schema.org are different.
> guha

Received on Tuesday, 11 April 2017 17:06:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:12:35 UTC