On Mar 8, 2012, at 2:07 PM, Guilherme Scomparim wrote:

> Hi Holger,
>  
>   That is really good news. When is the 3.6.0 final going to be available

Not sure yet, but we are working on it. Goal is still the end of March or early 
April.

>  
>   Would something like this work in SWP then?
>  
>  <ui:if ui:condition="{= bound(?Graph1) }">
>     <sml:ImportRDFFromWorkspace sm:baseURI= "{= ?Graph1}" 
> sml:ignoreImports="false">
>         <ui:if ui:condition="{= bound(?Graph2) }">
>                <sml:ImportRDFFromWorkspace sm:baseURI= "{= ?Graph2}" 
> sml:ignoreImports="true">
>                    <sml:Merge>
>                         <sml:ApplyTopSPIN>
>                                 <sml:ApplyConstruct sml:constructQuery = "{=
>                                                                               
>                 CONSTRUCT {
>                                                                               
>                ?sGraph1 Graph1:prop1 Graph1:thing1
>                                                                               
>                ?Graph1 Graph1:prop2 Graph2:thing2
>                                                                               
>                 }
>                                                                               
>                WHERE { 
>                                                                               
>                ?sGraph1 Graph1:prop1 Graph1:thing1
>                                                                               
>                 ?Graph1 Graph1:prop2 Graph2:thing2
>                                                                               
>                 }
>                                                                               
>                          }"/>
>                         </sml:ApplyTopSPIN>
>                 </sml:Merge>
>            </sml:ImportRDFFromWorkspace >
>         </ui:if>
>     </sml:ImportRDFFromWorkspace >
>  </ui:if>

You can replace sml:ImportRDFFromWorkspace with <ui:setContext 
ui:queryGraph="..."> where the query graph could be {= ui:graphWithImports(...) 
}". So no need for that module. From your example above I don't exactly 
understand your intention as the sml:Merge doesn't seem to do anything. But if 
you want to first apply TopSPIN and then run a CONSTRUCT, and then do something 
with the constructed triples, then you could do this using

<sml:ApplyTopSPIN>
        <!-- In this block the additional triples are visible, i.e. the default 
query graph includes inferences -->
        <ui:update ui:updateQuery="{! 
                        INSERT { 
                                GRAPH ui:tempGraph {
                                        # constructed triples go here
                                }
                        }
                        WHERE {
                                # query condition goes here
                        } }" />
        <!-- and any number of other updates to ui:tempGraph. This essentially 
plays the role of sml:ApplyConstruct -->
</sml:ApplyTopSPIN>
<!-- Here you can do something with the triples from ui:tempGraph because that 
graph is visible for the life time of the SWP engine -->

>  
> Before the 3.6.0 is available, can I test this by making the sm:Modules 
> subclass of ui:element?

Not yet but this is how it is implemented in 3.6.0. I'll also respond to your 
private email off-list (once I get a breather)...

Cheers,
Holger

-- 
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
topbraid-users@googlegroups.com
To unsubscribe from this group, send email to
topbraid-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en

Reply via email to