Ok, done for the next release. Meanwhile I trust you have already  
changed this in your version :)

Holger


On Apr 30, 2009, at 12:51 PM, Schmitz, Jeffrey A wrote:

>
> Hi Holger,
>  I have another request I think.  Unless I'm overlooking something, I
> don't see any way to create a QueryExecution object with a
> QuerySolutionMap if I use the ARQFactory class.  Would it be  
> possible to
> add a function that would allow a QuerySolutionMap to be specified?
>
> e.g.
>
>       public QueryExecution createQueryExecution(Query query, Model
> model, QuerySolutionMap varMap) {
>               if(query.getGraphURIs().isEmpty()) {
>                       List<String> namedGraphURIs =
> ARQFactory.getNamedGraphURIs(query);
>                       if(namedGraphURIs.isEmpty()) {
>                               return
> QueryExecutionFactory.create(query, model, varMap);
>                       }
>                       else {
>                               Dataset dataset = getDataset();
>                               if(dataset != null) {
>                                       return
> QueryExecutionFactory.create(query, dataset, varMap);
>                               }
>                               else {
>                                       return
> QueryExecutionFactory.create(query, model, varMap);
>                               }
>                       }
>               }
>               else {
>                       return createRemoteQueryExecution(query);
>               }
>       }
> Thanks,
> Jeff
>
>
> -----Original Message-----
> From: Holger Knublauch [mailto:hol...@topquadrant.com]
> Sent: Friday, April 24, 2009 4:13 PM
> To: topbraid-composer-users@googlegroups.com
> Subject: [tbc-users] ANN: SPIN 1.0.0
>
>
> As we are nearing the 3.0 release of TopBraid Suite, I am declaring  
> the
> SPIN system ontologies [1] and the SPIN API [2] to be out of beta  
> stage.
> There have been very little changes since the December release, and I
> appreciate the feedback from the user community that has confirmed and
> validated the initial design. I also welcome feature requests about  
> what
> could go into a future SPIN release 1.1 - with the goal of leaving it
> light-weight but meeting other real-world requirements.
>
> More news will follow once 3.0 is out.
>
> Regards,
> Holger
>
> [1] http://spinrdf.org
> [2] http://topbraid.org/spin/api
>
>
>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
To post to this group, send email to topbraid-composer-users@googlegroups.com
To unsubscribe from this group, send email to 
topbraid-composer-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/topbraid-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to