Ok, I understand that: the choice is between to store or not to store the source of the data by grouping the triples in graphs. Of course it's up to core developers to choose. Another set of questions: 1) how the s13n's programming interfaces for extension developers will look like? 2) what is the priority of this task? 3) Is it possible to sponsor the development to make it quicker? I think that the companies interested in this feature can build together a fund/grant to support the volunteer. WikiVote can definitely take part in that sponsorship campaign. ----- Yury Katkov, WikiVote
On Fri, Nov 16, 2012 at 9:35 PM, Jeroen De Dauw <jeroended...@gmail.com> wrote: > Hey, > > >> Can you clarify the idea of named graphs a little bit? And what >> storage overhead we have in them? > > > Instead of having rows such as > > ( subject id, property id, value ) > > in the store, you instead have > > ( subject id, property id, value, graph id ) > > Of course our schema is more complex then this, but it's the same idea. > > Cheers > > -- > Jeroen De Dauw > http://www.bn2vs.com > Don't panic. Don't be evil. > -- ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
