Martynas, > I am not convinced your use case requires a whole new concept (and > following implementations) of "Linked Data profiles". > > I have outlined practical solutions you already can use now: > 1. use a single description including all vocabularies
I have real customers that say already now that this solution is not acceptable to them. > 2. make separate resources with separate descriptions Could work, but I prefer a resource-centric model where I simply deliver different descriptions about the same resource. > 3. give the client SPARQL access Not all clients want to talk sparql. > It seems to me that you have a hypothetical solution and are looking > for a problem. Might be. I'm still not convinced of the opposite being true, though. Best, Lars