Looks nice. I like how you've made a "triple" be a "resource". A couple of comments... 1. Why is resource (and literal) creation bound to the model? Can a resource or literal that is created in one model be used in a different model? If not, why not? If so, should these be moved to RDFUtil, or another interface that is used for resource management? 2. Also, it seems like you might want to be able to compose models without combining them, at least for read-only operations. Compare pseudo-SQL create view foo as select * from table1 union select * from table2 vs. create table foo select * from table1 into foo select * from table2 into foo Allows combining of data across arbitrary Model implementations. chrisReceived on Monday, 6 December 1999 15:14:39 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:21 UTC