> > On 27 Oct 2015, at 16:09, Jack Hodges <[email protected]> wrote: > > @Holger, I think that is a very good question. Yes, it might include > transitive dependencies. If we start from the imported graphs list that is > provided for the export, it would be the minimum set of graphs in that set > that are actually referenced by the graph being exported. One problem is that > I may have imported more graphs (for whatever reason) than I am actively > using in this particular graph, or the imports may have more classes and > instances defined than are actually being used. Clearly I cannot expect to > export partial graphs but within that limitation it would be nice to export a > minimal set. > > @David, that might be an option to try, but that could also be an option in > TBC could it not? I mean, instead of having everyone do it themselves?
The tool really does not have a way of knowing what subset of the data, ontology classes/properties, etc. are of interest for export. The general requirement for such a thing quickly get out-of-hand (e.g. Do we include instances of reference data or background facts or not? How can you distinguish reference data and background facts from interesting data instances? How far up superclass hierarchy should be included?, Are other subclasses of used superclasses to be included? What about super-property hierarchy? What about annotation properties? What about any classes of class aka meta-classes aka punning?. So, what we aim to do in TB is to give you tools and languages (i.e. SPIN) to make doing this more straightforward. When I run into this, I write SPIN/SPARQL to do the job - either to select and construsct what I want up front, or to delete what I don’t want after the full export. Cheers, David > > Thank you both for your replies... > > Jack > > On Monday, October 26, 2015 at 1:59:54 PM UTC-7, Jack Hodges wrote: > In the Export/Merge/Convert RDF Graphs option I get a list of potential > graphs to export. I am expected to select those graphs I wish to export. > > Is there a way to export only those graphs that the selected graph directly > depends upon (or those that directly depend through relationships to the > selected graph)? > > Or is that what is being done already? > > I ask because if I select 'all' of the graphs I get many more classes and > instances than I actually need, but it would be difficult (to say the least) > to go through and cherry pick those graphs that are specifically required to > support a given graph. > > Jack > > -- > You received this message because you are subscribed to the Google Group > "TopBraid Suite Users", the topics of which include Enterprise Vocabulary > Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid > Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. > To post to this group, send email to [email protected] > --- > You received this message because you are subscribed to the Google Groups > "TopBraid Suite Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
