Hi Gary,

the response from 2014 is still valid. Using POST multipart parameters is certainly working (technically). I am not aware of means to access the request body directly. I am not an expert on this topic, but doesn't the protocol support some kind of gzipping of parameters?

Holger


On 19/10/2017 5:33, Gary Murphy wrote:
It's a few years on since this was answered in 2014, and we're several TBCME versions later, but I was wondering ... is this still true?  Is there no means for SPARQLMotion (or swp) to stream in RDF from a request body? For my application using sml:ImportXMLFromURL isn't possible as the source could be coming from within a firewall, and using post parameters would mean having to encode the body of the RDF, which would become expensive for very large graphs.

I have 5.4 although I haven't begun to really explore it yet, but would such a feature be part of the newer versions?

On Thursday, April 17, 2014 at 6:55:30 PM UTC-4, Holger Knublauch wrote:

    Hi Tim,

    I don't think SPARQLMotion can currently parse the request body,
    so you would need to use named values. However, I don't see a
    problem with that, see

    
http://stackoverflow.com/questions/2943477/is-there-a-max-size-for-post-parameter-content
    
<http://stackoverflow.com/questions/2943477/is-there-a-max-size-for-post-parameter-content>

    Note that SPARQLMotion can handle file uploads via HTML forms, if
    that is an option.

    HTH
    Holger


    On 4/18/2014 6:15, Tim Smith wrote:
    Hi Scott,

    I am using SPARQLMotion.  I know if I define a set of input
    variables to a script, those variables are bound for use within
    the script.

    If I were to send a request with something like the information
    below as part of the request, how do I reference this data within
    the script?

    Thanks,

    Tim


    <?xml version="1.0" encoding="UTF-8"?>
    <Breakdown
    xmlns:attributes="http://www.be-informed.nl/BeInformed/Attributes
    <http://www.be-informed.nl/BeInformed/Attributes>"
    xmlns:fo="http://www.w3.org/1999/XSL/Format
    <http://www.w3.org/1999/XSL/Format>">
        <Information>
            <MaterialTradeName>L&amp;G Raw</MaterialTradeName>
            <ManufacturerName>L&amp;G</ManufacturerName>
            <GCAS>1</GCAS>
            <PGIRMSCode>4</PGIRMSCode>
        </Information>
        <IntentionalConstituents>
            <MaterialClass>AminesAmidesDEAEtc</MaterialClass>
            <Region>Europe</Region>
            <Name>A1</Name>
            <CAS>1-1-1</CAS>
            <CASEquivalent/>
            <CASEqNumber/>
            <OtherRegulatoryIds/>
            <RegulatoryIdentificationNumber/>
            <INCI/>
            <ChemicalStructure/>
            <ConstituentFunction/>
            <Feedstock/>
            <LowerSpecificationLevel/>
            <UpperSpecificationLevel/>
            <SpecificationLevels/>
            <Explains/>
            <CarbonChainDistributions/>
        </IntentionalConstituents>
        <IntentionalConstituents>
            <MaterialClass>Betaines</MaterialClass>
            <Region>Europe</Region>
            <Name>A2</Name>
            <CAS>2-2-2</CAS>
            <CASEquivalent/>
            <CASEqNumber/>
            <OtherRegulatoryIds/>
            <RegulatoryIdentificationNumber/>
            <INCI/>
            <ChemicalStructure/>
            <ConstituentFunction/>
            <Feedstock/>
            <LowerSpecificationLevel/>
            <UpperSpecificationLevel/>
            <SpecificationLevels/>
            <Explains/>
            <CarbonChainDistributions/>
        </IntentionalConstituents>
        <UnintentionalConstituents>
            <MaterialClass>DyersAndColorants</MaterialClass>
            <Region>Europe</Region>
            <Name>U3</Name>
            <CAS>3-3-3</CAS>
            <CASEquivalent/>
            <CASEqNumber/>
            <OtherRegulatoryIds/>
            <RegulatoryIdentificationNumber/>
            <INCI/>
            <MaxLevelExpected/>
            <LimitOfDetection/>
            <SpecificationLevels/>
            <Explain/>
        </UnintentionalConstituents>
    </Breakdown>


    On Thu, Apr 17, 2014 at 3:33 PM, Scott Henninger
    <[email protected] <javascript:>> wrote:

        Tim; if you are using SPARQLMotion, there is no reason to
        worry about the details of get/post.  This is taken care of
        by the sparqlmotion servlet inside of TopBraid. Just use the
        REST URL to call the script and the infrastructure will take
        care of the rest.

        -- Scott

        On 4/17/2014, 10:11 AM, Tim Smith wrote:
        Hi - I have a need to create/update resources in our triple
        store.  The data required is bigger than can be defined
        using attributes of a GET request and I understand GET is
        supposed to be used to /get/ objects not create/update them.

        My question is if I call the web service using a POST
        request, how do I access the message body to parse the
        payload?  I would like to be able to pass in an XML
        structure to be parsed as the amount and structure of the
        data makes enumerating it as arguments impossible.

        My knowledge of REST is a bit limited so maybe I'm trying to
        do something that can't be done or maybe I'm missing
        something simple here...

        Thanks for your help!

        Tim

-- -- 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
        [email protected] <javascript:>
        To unsubscribe from this group, send email to
        [email protected] <javascript:>
        For more options, visit this group at
        http://groups.google.com/group/topbraid-users?hl=en
        <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 [email protected]
        <javascript:>.
        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), TopBraid Composer,
        TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web
        Pages and SPIN.
        To post to this group, send email to
        [email protected] <javascript:>
        To unsubscribe from this group, send email to
        [email protected] <javascript:>
        For more options, visit this group at
        http://groups.google.com/group/topbraid-users?hl=en
        <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 [email protected]
        <javascript:>.
        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), TopBraid Composer, TopBraid
    Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
    To post to this group, send email to
    [email protected] <javascript:>
    To unsubscribe from this group, send email to
    [email protected] <javascript:>
    For more options, visit this group at
    http://groups.google.com/group/topbraid-users?hl=en
    <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 [email protected] <javascript:>.
    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 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.

--
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.

Reply via email to