On 12/12/12 11:20 AM, Gregory Williams wrote:
On Dec 12, 2012, at 7:24 AM, Kingsley Idehen wrote:The problem is that these graphs are purpose specific. For instance, they don't have anything to do with DBpedia, they are installed by for use by our Faceted Browser (re. <facets>). Basically, this is where it gets confusing since we have two usage scenarios overlapping. These special system graphs aren't part of the DBpedia data space, they are only created when the Faceted Browser component is installed. Of course, if you want to make use of them in a more generic sense, you can just copy the data to an appropriately named graph inline with the SPARQL specs for graph IRIs. I hope this helps you understand what's happening here. Basically, this is about special systems data installed by specific application modules that serve specific application needs.Hi Kingsley, I understand "what's happening here." And you're free to do it that way. I just don't think you should be claiming that what you're doing is acceptable for a conforming SPARQL implementation.
I am not claiming that these application-specific graph identifiers are SPARQL compliant. I don't believe that being SPARQL accessible (via accident or follow-your-nose) implies that every named graph in a Virtuoso DBMS is denoted in conformance with SPARQL.
Here's our little error here, we should have simply made these graph inaccessible via our graph level acl functionality. That way, they never drift into scope while remaining accessible to the actual applications that depend on them etc..
This named graph behavior isn't standard, and makes it impossible for clients to correctly find that data using exploratory queries (whether or not you think the data is relevant to them).
The issue is the data isn't relevant to them in the standard access context. That's the problem. If it was supposed to be available in that context, of course the IRIs would be in SPARQL standards compliant.
Since this simply isn't a big deal for us, I am just going to have all the graph identifiers changed to IRIs. In addition, still have ACLs protect those that are specifically for application use.
Kingsley
.greg ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
-- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________ Virtuoso-users mailing list Virtuoso-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtuoso-users
