From: Rose B. <ros...@gm...> - 2014-10-06 17:09:41
|
Dear Bryan, I have Uniprot data in turse triple form (ttl) and I want to load it in bigdata and I want to query it using bigdata. On the web page http://wiki.bigdata.com/wiki/index.php/NanoSparqlServer it is mentioned that I should look at the example: NSSEmbeddedExample.java. However when I check out the code: svn checkout svn://svn.code.sf.net/p/bigdata/code/trunk bigdata-code I am unable to find this example. Can you please help me with this. I am a complete novice at Java (Although I work on C/C++ and Python extensively), therefore I am not able to understand as to how should I load large datasets into Bigdata and how should I query them. Perhaps a step-by-step guide for users like me who are not familiar with Java will be of great help. Thanks & Regards, Jyoti On Mon, Oct 6, 2014 at 8:40 PM, Bryan Thompson <br...@sy...> wrote: > Certainly. There are a number of resources at http://blog.bigdata.com. > There is a chapter length paper on the bigdata architecture at [1]. This is > also linked from that blog page. You might also be interested in our other > project, which is http://mapgraph.io. > > If you are only storing the source of a triple, then the named graphs > mechanism is sufficient since the URI of the named graph can be used for the > source URI. > > However, if you want to associate more metadata with each triple then RDR is > the way to go. > > Thanks, > Bryan > > [1] http://www.bigdata.com/whitepapers/bigdata_architecture_whitepaper.pdf > > ---- > Bryan Thompson > Chief Scientist & Founder > SYSTAP, LLC > 4501 Tower Road > Greensboro, NC 27410 > br...@sy... > http://bigdata.com > http://mapgraph.io > > CONFIDENTIALITY NOTICE: This email and its contents and attachments are for > the sole use of the intended recipient(s) and are confidential or > proprietary to SYSTAP. Any unauthorized review, use, disclosure, > dissemination or copying of this email or its contents or attachments is > prohibited. If you have received this communication in error, please notify > the sender by reply email and permanently delete all copies of the email and > its contents and attachments. > > > On Mon, Oct 6, 2014 at 11:05 AM, Rose Beck <ros...@gm...> wrote: >> >> Dear Bryan, >> >> For now we are just using RDR for storing provenance or source of >> triples. All these questions arise in my mind out of curiosity :) >> >> I saw bigdata slides at >> http://www.cse.unsw.edu.au/~iwgdm/2012/Slides/bigdata.pdf. And I am >> pretty curious to read more about: how Bigdata implements vectored >> query execution and what engineering goes behind its analytic mode of >> execution. If possible, can you please point me to resources from >> which I learn more about the same? >> >> >> Thanks & Regards, >> Rose >> >> >> On Mon, Oct 6, 2014 at 8:15 PM, Bryan Thompson <br...@sy...> wrote: >> > Rose, >> > >> > I think that the requirement for statement level metadata should be >> > orthogonal to the decision to use named graphs. Statement level >> > metadata >> > can be used for a variety of purposes. For example, it can be used for >> > security, it can be used to provide the source of the statement (which >> > is >> > often the use case for named graphs), to associate an author with a >> > statement, to associate a creation time with a statement, to associate a >> > weight with an edge of a graph, etc. >> > >> > What is the use case that motivates the RDR mechanisms for you? Perhaps >> > if >> > you can explain that I can provide an example of how this might be >> > relevant >> > in the context of named graphs for your application. However, the >> > feature >> > is not currently supported for the quads mode of the bigdata database, >> > so >> > this is a somewhat academic question. >> > >> > Thanks, >> > Bryan >> > >> > ---- >> > Bryan Thompson >> > Chief Scientist & Founder >> > SYSTAP, LLC >> > 4501 Tower Road >> > Greensboro, NC 27410 >> > br...@sy... >> > http://bigdata.com >> > http://mapgraph.io >> > >> > CONFIDENTIALITY NOTICE: This email and its contents and attachments are >> > for >> > the sole use of the intended recipient(s) and are confidential or >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure, >> > dissemination or copying of this email or its contents or attachments is >> > prohibited. If you have received this communication in error, please >> > notify >> > the sender by reply email and permanently delete all copies of the email >> > and >> > its contents and attachments. >> > >> > >> > On Mon, Oct 6, 2014 at 10:40 AM, Rose Beck <ros...@gm...> >> > wrote: >> >> >> >> Dear Bryan, >> >> >> >> Probably I am new to the field. But since you are an experienced >> >> person in the field, therefore can you please help me understand that: >> >> when we apply RDR mechanism to triples, then what is the practical >> >> use-case application of using named graph mechanism? I mean I >> >> understand intuitively but I still am not able to get the practical >> >> significance of using named graphs. >> >> >> >> >> >> Thanks & Regards, >> >> Rose >> >> >> >> On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...> >> >> wrote: >> >> > The purpose of RDR is to permit statements about statements. >> >> > >> >> > The purpose of named graphs is to allow statements to be collected >> >> > into >> >> > containers. >> >> > >> >> > With RDF* support for named graphs, you could do both. >> >> > >> >> > Whether or not this is a good idea is an interesting question. >> >> > Consider, >> >> > that named graphs could be interpreted as just a special case of a >> >> > statement >> >> > about a statement where the database then applies special indexing >> >> > (typically by maintaining additional indices for fast access by the >> >> > named >> >> > graph). >> >> > >> >> > For example, given: >> >> > >> >> > <<:a :b :c> :namedGraph :d> >> >> > >> >> > If we assume that ":namedGraph" has the semantics of the SPARQL named >> >> > graphs >> >> > mechanism, then this RDR assertion says that the statement :a :b :c >> >> > exists >> >> > in the named graph :d. >> >> > >> >> > If so, then the RDR mechanisms always apply to triples and the named >> >> > graphs >> >> > mechanism just specifies the containers within which a given triple >> >> > (including an RDR triple) is visible. >> >> > >> >> > Thanks, >> >> > Bryan >> >> > >> >> > ---- >> >> > Bryan Thompson >> >> > Chief Scientist & Founder >> >> > SYSTAP, LLC >> >> > 4501 Tower Road >> >> > Greensboro, NC 27410 >> >> > br...@sy... >> >> > http://bigdata.com >> >> > http://mapgraph.io >> >> > >> >> > CONFIDENTIALITY NOTICE: This email and its contents and attachments >> >> > are >> >> > for >> >> > the sole use of the intended recipient(s) and are confidential or >> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure, >> >> > dissemination or copying of this email or its contents or attachments >> >> > is >> >> > prohibited. If you have received this communication in error, please >> >> > notify >> >> > the sender by reply email and permanently delete all copies of the >> >> > email >> >> > and >> >> > its contents and attachments. >> >> > >> >> > >> >> > On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...> >> >> > wrote: >> >> >> >> >> >> Dear Bryan, >> >> >> >> >> >> Thanks for the enlightening write-up about RDR. But I have a >> >> >> question >> >> >> in the write-up you wrote "In the future, we plan to add support for >> >> >> RDF* and SPARQL* to the quads mode of the platform as well. This >> >> >> will >> >> >> allow statement level metadata to co-exist seamlessly with the named >> >> >> graphs model." But I dont understand the need for supporting RDF* >> >> >> and >> >> >> SPARQL* in quads mode. I mean I dont understand as to why do we need >> >> >> to allow statement level metadata to co-exist with named graph >> >> >> model. >> >> >> Can you please explain this with an example. >> >> >> >> >> >> >> >> >> Thanks & Regards, >> >> >> Rose. >> >> >> >> >> >> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...> >> >> >> wrote: >> >> >> > I've added a page to the wiki based on that blog post: >> >> >> > >> >> >> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right >> >> >> > >> >> >> > Thanks, >> >> >> > Bryan >> >> >> > >> >> >> > ---- >> >> >> > Bryan Thompson >> >> >> > Chief Scientist & Founder >> >> >> > SYSTAP, LLC >> >> >> > 4501 Tower Road >> >> >> > Greensboro, NC 27410 >> >> >> > br...@sy... >> >> >> > http://bigdata.com >> >> >> > http://mapgraph.io >> >> >> > >> >> >> > CONFIDENTIALITY NOTICE: This email and its contents and >> >> >> > attachments >> >> >> > are >> >> >> > for >> >> >> > the sole use of the intended recipient(s) and are confidential or >> >> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure, >> >> >> > dissemination or copying of this email or its contents or >> >> >> > attachments >> >> >> > is >> >> >> > prohibited. If you have received this communication in error, >> >> >> > please >> >> >> > notify >> >> >> > the sender by reply email and permanently delete all copies of the >> >> >> > email >> >> >> > and >> >> >> > its contents and attachments. >> >> >> > >> >> >> > >> >> >> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...> >> >> >> > wrote: >> >> >> >> >> >> >> >> Dear all, >> >> >> >> >> >> >> >> I have downloaded bigdata.war and have deployed it using sesame >> >> >> >> HTTP >> >> >> >> API. Now I am not getting as to how should I load rdf >> >> >> >> triples/provenance with triples to bigdata using >> >> >> >> nanosparqlserver? I >> >> >> >> am using sesame HTTP API (using apache tomcat). Can someone >> >> >> >> please >> >> >> >> help. >> >> >> >> >> >> >> >> I intend to use mysql, native java and postgres with sesame. Any >> >> >> >> help >> >> >> >> will be deeply appreciated. >> >> >> >> >> >> >> >> Regards, >> >> >> >> Rose >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> >> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> >> >> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >> >> >> >> Reports >> >> >> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White >> >> >> >> paper >> >> >> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog >> >> >> >> Analyzer >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> >> >> >> Bigdata-developers mailing list >> >> >> >> Big...@li... >> >> >> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> >> >> > >> >> >> > >> >> > >> >> > >> > >> > > > |