RE: [UnionModel] question about unexpected behaviour

Hi Claude, Thanks for your analysis! It was (of course) not my intention to get a dataset with 4 graphs , but is sure explains the strange behavior. I wanted to replicate the behavior of defaultUnionGraph option that is available in TDB. The reason I cannot use TDB's defaultUnionGraph

Re: [UnionModel] question about unexpected behaviour

Barry, You create a dataset that is comprised of the following: defaultGraph -> unionModel namedGraph(https://www.tno.nl/agrifood/graph/pizza/data) namedGraph(https://www.tno.nl/agrifood/graph/pizza/onto)

Re: [UnionModel] question about unexpected behaviour

Barry, You could create a union graph that is used for an InfModel. Not sure why you want a UnionGraph but ... I think you want to start with a TDB Model and wrap that as a SecuredModel (See comments in permissions re: SecuredModel vs SecuredGraph) Using a SecuredModel as the basis for an