Yes just to confirm - SM functions embedded into SM scripts may either return a graph (sml:ReturnRDF) or a node (sml:ReturnNode). sml:ReturnXML is not supported in those cases. So maybe you are able to use sml:ReturnNode to return the XML nodes as a single string literal.

Holger


On 5/27/2014 18:42, Nicolae Marasoiu wrote:
Hi again,

Yes, it works after removing the inner function. Directly binding an xsd:string to the rdf:XmlLiteral works indeed. Somehow, passing through ReturnXML node messed it up. Also my colleague said it does not work for him because he does not have <?..> antet.

Thanks

On Tuesday, May 27, 2014 11:22:58 AM UTC+3, Nicolae Marasoiu wrote:

    Hi Scott,

    No, unfortunately this happens to me and an experienced colleague
    who just worked around it with xpath to avoid the impossible
    conversion.

    So I have an xsd:string stored in a ?xmlStringResult output
    variable from the PostRequest.
    I see the XML in debug, very well formed and including the <?..>
    antet.
    Then I have an XML return node, which shows binding xml with the
    same text (it is a sparql expression binding, the usual that i use).
    Coming out of the function and going to the next node in the upper
    function, the next module is another function expecting an
    rdf:XMLLiteral typed value.
    I see in debugger that that parameter is not bound to anything
    when bindings are applied,even though i triple checked that the
    variable is routed and i can see it routed with gray arrows in the
    bottom and upper part of the 2 modules.
    i use TBC=ME 4.4.0.

    Thanks
    Nicu

    On Monday, May 26, 2014 6:06:28 PM UTC+3, Nicolae Marasoiu wrote:

        Hi,

        I use sml:PostRequest and have a resulting xsd:string value,
        holding an XML data string payload.

        The next step would be to convert it to RDF.

        But sml:ConvertXMLToRDF takes an rdf:XmlLiteral value.

        How to convert between the 2 types?

        Thanks,
        Nicu

--
-- 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 Insight, SPARQLMotion, SPARQL Web Pages 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
---
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 topbraid-users+unsubscr...@googlegroups.com <mailto:topbraid-users+unsubscr...@googlegroups.com>.
For more options, visit 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), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL 
Web Pages 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
--- 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 topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to