-
Notifications
You must be signed in to change notification settings - Fork 13
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
Member extraction algorithm and blank node graphs #113
Comments
Additionally: The main goal of this entire spec is to be able to package triples. If there’s one system, I believe we probably should not mix it with other systems (this is a design choice I guess). So we could change the algorithm in a way which makes sure that
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Blank node graphs are a neat trick. For example:
When having parsed the page containing the data, we can be certain we got all triples possible within
_:b0
, as the scope of this blank node is limited to this page. We can also be certain that this graph will never conflict with a graph from another source.This means we could use blank node graphs as a package as part of a member and give a specific purpose to parts of our graph. I.e.:
Then we must be able to have a smarter way of dealing with blank node graphs, which at this moment is not specified at all in the member extraction algorithm.
Proposal:
The text was updated successfully, but these errors were encountered: