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

rr:joinCondition #421

Open
Maatary opened this issue Jul 3, 2019 · 2 comments
Open

rr:joinCondition #421

Maatary opened this issue Jul 3, 2019 · 2 comments
Labels

Comments

@Maatary
Copy link

Maatary commented Jul 3, 2019

Hi,
the following paper by @jasonslepicka says that Karma do not support rr:joinCondition.

I was just wondering, is there a way in Karma to deal with foreign Keys ? Mean i have two tables where Table A represent an entity and Table B represent another one, and Table A has a foreign key toward Table B.

I want to make sure that URI of the Foreign Key in A correspond to the URI of the Primary Key of B.

More generally Is there anyway to verify that when generating mappings, that the entities they generate actually link well ?

@GreatYYX
Copy link
Member

GreatYYX commented Jul 3, 2019

If you construct URIs of primary and foreign key in the same way, then yes, they are linked together.

To verify, upload triples to a triple store or use RDF graph library like rdflib (python) or Jena (java), then do sparql queries.

@Maatary
Copy link
Author

Maatary commented Jul 5, 2019

Thanks for the answer. What you describe is what we do at the moment, we verify connectivity once the data is loaded in the Triple-store. This approach can be problematic, because when we have a lot of table to map mistakes happen, when those table generate several millions of triple each, the approach becomes a bit annoying, because it requires to restart expensive processes.

To understand that, one has to put himself in the context of a pipeline that load huge amount of data producing billions of triples. The pipeline reads the mapping models connect to the source and produce the RDF. The appraoch of waiting the data to hit the triple store, can significantly be slow as a process, as it requires to restart several materialization of the RDF produce depending if the mapping connect or not.

I was hoping to verify things directly at the mapping file level, just making sure that the template used where there is a joincondition is the same between primary and foreign key.

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

No branches or pull requests

3 participants