- to map (to link) the SchemaOrg's vocabulary into Wikidata;
- to map the Wikidata's vocabulary into SchemaOrg;
- offer a well-founded methodology for taks 1 and 2.
- Quering-Wikidata and installing SQL tool
- Wikidata state summarizations
- Project's kanban with tasks and its status
- Collaborative spreadsheet for endorse and votation and its preservated versions.
The core vocabulary currently consists of 597 Types, 875 Properties, and 114 Enumeration values.
So, there are ~1500 items to be mapped, in both Wikidata-side source codes and SchemaOrg-side source code.
The first aim was expressed as SchemaOrg's issue-280,
"Schema.org should have mappings to Wikidata terms where possible" (Dan Brickley - SchemaOrg coordinator).
This project intends to enhance the SchemaOrg core items definitions, citing in each core item its corresponding Wikidata item (e.g., add Wikidata-ID in the text of RFD-comment or linking explicitally adding RDF-statement to the external equivalent), and to link SchemaOrg items in the source code of corresponding Wikidata items.
There are some consensus about mappig task in the "full community", but the production of results was growing slowly,
And the initial goal changed from "map SchemaOrg to Wikidata" to "map Wikidata to SchemaOrg", causing some confusion in the team and lost of voluntaries... After two years and some work, we (a little group of voluntaries) noticed again that we need the initial goal.
In this project we want to join the two sides of the bridge!
Wikidata and SchemaOrg also represent two choices of concept-semantic definition strategies, extensional and intensional:
SchemaOrg definition approach is straightforward and pragmatic. A short phrase intentionally defines each entry (class or property), and the real concept is built extensionally by the community of users, with extension at initial samples or statistics of use.
Wikidata definition strategy is based on Wikipedia. All entries (mainly stable classes) define intention associating an item with corresponding Wikipedia's entry.
So, providing SchemaOrg-side, we enhance the correct use and avoid confusion for SchemaOrg users. Providing wikidata-side, we improve Wikidata definition and offer access to Wikidata users the biggest semantic corpus sampler of the Web.
... spiral of review-campaigns ...
Working on SchemaOrg side
Working on Wikidata side
... See also Wikidata's Guidelines for external relationships. ...
Complementing with DBpedia's methodology and tools
Wikidata state summarizations: