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

Separate API triples from data triples required to find operations #47

Open
bergos opened this issue Aug 5, 2019 · 0 comments
Open

Comments

@bergos
Copy link
Contributor

bergos commented Aug 5, 2019

The data triples to find the matching operation should be separated from the API triples. Data triples means all triples required to find the class type or the class type of a property.

Example

The server has to handle a request to /project/1.

The following SPARQL query covers the logic to find the type of the class:

SELECT * WHERE {
    </project/1> a ?type
}

Which would work for:

</project/1> a p:Project;
  rdfs:label: "first project".

And this query covers the logic to find the class type of a property:

SELECT * WHERE {
  ?class a ?type .
  ?class ?property </project/1> .
}

Which would work for:

</projects> a p:ProjectContainer;
  ex:contains </project/1>.

The logic in this issue is given as SPARQL, but in the actual implementation it should be possible to handle this with any object that implements a Store interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant