You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, every EDB predicate can only be based on one data source. However, all file-based inputs (n3, csv) as well as in-memory facts declared directly are presumably managed in the same in-memory data structure. It would be useful if VLog could simply add facts from several such sources to the same EDB predicate rather than requiring each input to use a different predicate. For example, it would be good if several n3 files or several csv files could be loaded into the same predicate.
DBMS-based inputs or SPARQL sources should probably not be merged in this way (since this would incur significant cost), but that's fine.
The text was updated successfully, but these errors were encountered:
Currently, every EDB predicate can only be based on one data source. However, all file-based inputs (n3, csv) as well as in-memory facts declared directly are presumably managed in the same in-memory data structure. It would be useful if VLog could simply add facts from several such sources to the same EDB predicate rather than requiring each input to use a different predicate. For example, it would be good if several n3 files or several csv files could be loaded into the same predicate.
DBMS-based inputs or SPARQL sources should probably not be merged in this way (since this would incur significant cost), but that's fine.
The text was updated successfully, but these errors were encountered: