tag:blogger.com,1999:blog-6848574.post111076778225298902..comments2024-02-14T04:44:39.043-06:00Comments on Working notes: Paulahttp://www.blogger.com/profile/03653112583629043593noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-6848574.post-1110836857290449982005-03-14T15:47:00.000-06:002005-03-14T15:47:00.000-06:00I'm glad someone else is finally seeing the light ...I'm glad someone else is finally seeing the light with tucana:is. The real problem I had was from a coding perspective is that it smells - it's a special case in a number of places in the code.<BR/><BR/>I remember being told that tucana:is could be considered as being "constraining the graph with all values in it". I think this is a bit of a hack - and doesn't really match what the other constraints do. They either implicitly constrain what is in the FROM clause or explicitly constraint what in the IN.<BR/><BR/>One way to save tucana:is would be for it to operate in this manor - constraining the FROM or IN. Then it is a normal constraint and can be joined.<BR/><BR/>Also when you talk about adding assignment the other suggestion I had apart from doing it within the WHERE is to do it before the SELECT. Similar to the PREFIX clause in SPARQL but it assigns variables.<BR/><BR/>I also had some realisation about the different SPARQL operations (CONSTRUCT for example) and how we could do that with assign clause - I think that would be very interesting.Andrewhttps://www.blogger.com/profile/00667948202593884438noreply@blogger.com