I'm looking at the rdf.web bundle. I though it would be nice to make the backup-functionality available from the menus.
The problem is that the menu functionality is platform specific so it shouldn't be in an rdf.*-bundle. This is possibly the reason why the sparql-endpoint isn't available via menus. The graph-management page however is menu-accessible, and a few ssp violate the principle of having no rdf->platform dependencies as well. Shall I rename the artifact to platform.rdf.web or are there other suggestions? Cheers, Reto On Tue, Jun 21, 2011 at 8:53 AM, Hasan Hasan <[email protected]> wrote: > agree, for sure it is better if we can keep information whether a > serialized > graph was coming from an mgraph or a graph. > and this can be an improvement issue to be solved later after the release. > if one has time to do it before the release I wouldn't stop him from doing > it ;) > > cheers > hasan > > On Tue, Jun 21, 2011 at 8:43 AM, Reto Bachmann-Gmuer <[email protected] > >wrote: > > > In the triplecollections.nt file in a backup-zip all triple collections > are > > described to be of type <http://clerezza.org/2009/11/backup#Graph>. > > Shouldn't different types be used for graphs and mgraphs? I don't see how > > restoring an instance is possible from such a backup zip without knowing > > when to create a graph and whn to create an mgraph. > > > > Cheers, > > Reto > > >
