Page MenuHomePhabricator

take into account additional Properties for mapping to schema.org
Open, Needs TriagePublic

Description

Problem:
Currently we only look at one Property to find the mappings to schema.org. There are however a few more we should take into account to increase our coverage:
P1628 We already do this
P1709
P2888
P2235
P2236

Acceptance criteria:

  • additional Properties are taken into account for finding mappings to schema.org

Event Timeline

Restricted Application added a project: Wikidata. · View Herald TranscriptApr 9 2020, 7:30 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript

@Lydia_Pintscher Oops! You forgot to include the main one also !!! .... Equivalent Property P1628 :-)

Tarrow added a subscriber: Tarrow.Apr 30 2020, 1:14 PM

We leave this for another sprint!

General thoughts were this might be quite some work.

We decided not to pick this up again. In order to help us decide if we pick this up or not we need to see how many extra schema.org properties we might match if we branched away from just using P1628.

Tarrow updated the task description. (Show Details)May 7 2020, 12:53 PM

If it helps or is needed, the query that you can use is here:

SELECT ?wd ?wdLabel ?corrName ?schema
{
  values (?corr ?corrName) 
    {(wdt:P2235 "superProp") (wdt:P2236 "subProp") (wdt:P1628 "equivProp") (wdt:P1709 "equivClass") (wdt:P2888 "exactMatch")}
  ?wd ?corr ?schema
  filter(regex(str(?schema), "schema.org"))
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
} order by ?corrName ?schema