Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properties that exist but not for the required class #6

Open
alexdma opened this issue Apr 23, 2018 · 0 comments
Open

Properties that exist but not for the required class #6

alexdma opened this issue Apr 23, 2018 · 0 comments
Labels
evaluation Issues that aim at getting better evaluation results

Comments

@alexdma
Copy link
Collaborator

alexdma commented Apr 23, 2018

The following query obtains information about schools in http://opendatacommunities.org/sparql

PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
SELECT DISTINCT ?id ?name WHERE { 
  ?school a <http://statistics.data.gov.uk/def/geography/LocalEducationAuthority> 
   ; skos:notation ?id 
   ; skos:prefLabel ?name 
}

Both SKOS properties are used in the target datasets at http://data.admin.ch/query/, but neither of them for the class http://schema.org/School, which would be the preferred one to have in the recommendation.

Currently, all the recommendations preserve both SKOS properties, causing the optimal query not to be recommended at all. Indeed, the optimal query has nothing in common with the original one except for the rdf:type property. That one would be:

PREFIX schema: <http://schema.org/>
SELECT DISTINCT ?id ?name WHERE { 
  ?school a schema:School
   ; <http://gov.genealogy.net/ontology.owl#hasDenomination> ?id
   ; schema:legalName ?name
}

Find a way to lose shared properties (and detect when they should be lost) in the generalization, without causing a combinatorial explosion of the specialization tree (note: this is a bitch tough).

@alexdma alexdma added the evaluation Issues that aim at getting better evaluation results label Apr 23, 2018
alexdma added a commit that referenced this issue Apr 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
evaluation Issues that aim at getting better evaluation results
Projects
None yet
Development

No branches or pull requests

1 participant