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

Complex datastructures for objects #7

Open
topfs2 opened this issue Sep 24, 2012 · 1 comment
Open

Complex datastructures for objects #7

topfs2 opened this issue Sep 24, 2012 · 1 comment

Comments

@topfs2
Copy link
Owner

topfs2 commented Sep 24, 2012

With all the search tasks providing many owl:sameAs it is showing that its necessary that they can provide all the data they have gathered and not only the url. This so that the client can make a better decision without resorting to ask heimdall about all the urls.

An example might be searching for a movie the site might return ID (which is resolved to an url) along with name, year and thumbnail. Being able to emit these alongside the URL would be greatly beneficial for the client so that it can choose and solve possible dissambiguation problems.

A way to solve this would be to allow entire subjects (or part of them) to be an object. If the subject contains an dc:identifier (url) the client knows it can ask for more data there.

@topfs2
Copy link
Owner Author

topfs2 commented Sep 24, 2012

This is partly blocked by #9

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

No branches or pull requests

1 participant