Thread: Issues in timeseries application.wadl?

Started: 2014-04-18 20:23:43
Last activity: 2014-04-22 19:58:59
Topics: Web Services
Andrew Barbour
2014-04-18 20:23:43
I'm not sure if this message made it originally, so my apologies if anyone
receives this twice...

~~~

Hi all,

In regards to http://service.iris.edu/irisws/timeseries/1/application.wadl ...

I'm just wondering about two things:

1. Is it a problem that the taper query has 'name="tapper"', or does the
name get reinterpreted internally?

2. Why are the parameters under 'application//method//request//param'
rather than
'application//resources//resource//resource//method//request//param' as
with "distaz" or "sacpz", for example? As far as I can tell, timeseries is
the only oddity.

thanks,
Andy

  • Bruce Weertman
    2014-04-18 20:34:01
    Thanks Andy. I’ll take a look at it.
    The tapper is certainly a typo.
    Just curious. What are you doing with the wadl?
    -B
    On Apr 18, 2014, at 1:23 PM, andy barbour <andy.barbour<at>gmail.com> wrote:

    I'm not sure if this message made it originally, so my apologies if anyone receives this twice...

    ~~~

    Hi all,

    In regards to http://service.iris.edu/irisws/timeseries/1/application.wadl ...

    I'm just wondering about two things:

    1. Is it a problem that the taper query has 'name="tapper"', or does the name get reinterpreted internally?

    2. Why are the parameters under 'application//method//request//param' rather than 'application//resources//resource//resource//method//request//param' as with "distaz" or "sacpz", for example? As far as I can tell, timeseries is the only oddity.

    thanks,
    Andy

    _______________________________________________
    webservices mailing list
    webservices<at>iris.washington.edu
    http://www.iris.washington.edu/mailman/listinfo/webservices

    --------------------------------------
    Bruce R Weertman
    Software Engineer
    IRIS DMC
    1408 NE 45h St, Suite 201
    Seattle, WA 98105

    bruce<at>iris.washington.edu
    (206) 547-0393



    • Andrew Barbour
      2014-04-18 21:37:12
      Hi Bruce,

      OK, good to know.

      In regards to the .wadl files... I'm developing a package for the R
      programming language, and I use the wadl files to generate a list of query
      parameters for a given webservice (so I don't have to remember them, or
      visit the webpage each time). If you're interested the code is being
      developed here: https://github.com/abarbour/irisws

      thanks,
      Andy



      On Fri, Apr 18, 2014 at 1:34 PM, Bruce Weertman
      <bruce<at>iris.washington.edu>wrote:

      Thanks Andy. I’ll take a look at it.
      The tapper is certainly a typo.
      Just curious. What are you doing with the wadl?
      -B
      On Apr 18, 2014, at 1:23 PM, andy barbour <andy.barbour<at>gmail.com> wrote:

      I'm not sure if this message made it originally, so my apologies if
      anyone receives this twice...

      ~~~

      Hi all,

      In regards to
      http://service.iris.edu/irisws/timeseries/1/application.wadl ...

      I'm just wondering about two things:

      1. Is it a problem that the taper query has 'name="tapper"', or does
      the name get reinterpreted internally?

      2. Why are the parameters under 'application//method//request//param'
      rather than
      'application//resources//resource//resource//method//request//param' as
      with "distaz" or "sacpz", for example? As far as I can tell, timeseries is
      the only oddity.

      thanks,
      Andy

      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices

      --------------------------------------
      Bruce R Weertman
      Software Engineer
      IRIS DMC
      1408 NE 45h St, Suite 201
      Seattle, WA 98105

      bruce<at>iris.washington.edu
      (206) 547-0393


      _______________________________________________
      webservices mailing list
      webservices<at>iris.washington.edu
      http://www.iris.washington.edu/mailman/listinfo/webservices


      • Rob Casey
        2014-04-18 22:27:07

        I wonder if we should at all make mention of our R code for MUSTANG? I don't think that Jon has made his version of the code public yet.

        Just thinking out loud. Maybe better to keep it internal until we start talking about a distributed MUSTANG-lite. Andy might feel better about using a WADL for his stuff anyway.

        -RobC


        On Apr 18, 2014, at 2:37 PM, andy barbour wrote:

        Hi Bruce,

        OK, good to know.

        In regards to the .wadl files... I'm developing a package for the R programming language, and I use the wadl files to generate a list of query parameters for a given webservice (so I don't have to remember them, or visit the webpage each time). If you're interested the code is being developed here: https://github.com/abarbour/irisws

        thanks,
        Andy



        • Andrew Barbour
          2014-04-19 17:12:13
          I can't say I wouldn't be curious to see an 'official' set of R codes...
          I'll stay tuned.


          On Fri, Apr 18, 2014 at 3:27 PM, Robert Casey <rob<at>iris.washington.edu>wrote:


          I wonder if we should at all make mention of our R code for MUSTANG? I
          don't think that Jon has made his version of the code public yet.

          Just thinking out loud. Maybe better to keep it internal until we start
          talking about a distributed MUSTANG-lite. Andy might feel better about
          using a WADL for his stuff anyway.

          -RobC



          On Apr 18, 2014, at 2:37 PM, andy barbour wrote:

          Hi Bruce,

          OK, good to know.

          In regards to the .wadl files... I'm developing a package for the R
          programming language, and I use the wadl files to generate a list of query
          parameters for a given webservice (so I don't have to remember them, or
          visit the webpage each time). If you're interested the code is being
          developed here: https://github.com/abarbour/irisws

          thanks,
          Andy



          _______________________________________________
          webservices mailing list
          webservices<at>iris.washington.edu
          http://www.iris.washington.edu/mailman/listinfo/webservices



          • Chad Trabant
            2014-04-22 05:56:07

            Hi Andy,

            To fill in some gaps there, we have an internal data processing system that uses R and a library/module has been developed to fetch data from our web service interfaces. We’ve discussed the possibility of releasing it but have not come to any conclusion yet. I imagine it might best work as a collaborative development/maintenance, where we release what we’ve got and let the community of R users build on it. I’m curious how many R users would use a web service access library?

            If you do end up creating web service access code for R you might consider releasing it in SeisCode (https://seiscode.iris.washington.edu/) or having a bookmark in SeisCode to help folks find your work.

            regards,
            Chad

            On Apr 19, 2014, at 10:12 AM, andy barbour <andy.barbour<at>gmail.com> wrote:

            I can't say I wouldn't be curious to see an 'official' set of R codes... I'll stay tuned.


            On Fri, Apr 18, 2014 at 3:27 PM, Robert Casey <rob<at>iris.washington.edu> wrote:

            I wonder if we should at all make mention of our R code for MUSTANG? I don't think that Jon has made his version of the code public yet.

            Just thinking out loud. Maybe better to keep it internal until we start talking about a distributed MUSTANG-lite. Andy might feel better about using a WADL for his stuff anyway.

            -RobC



            On Apr 18, 2014, at 2:37 PM, andy barbour wrote:

            Hi Bruce,

            OK, good to know.

            In regards to the .wadl files... I'm developing a package for the R programming language, and I use the wadl files to generate a list of query parameters for a given webservice (so I don't have to remember them, or visit the webpage each time). If you're interested the code is being developed here: https://github.com/abarbour/irisws

            thanks,
            Andy



            _______________________________________________
            webservices mailing list
            webservices<at>iris.washington.edu
            http://www.iris.washington.edu/mailman/listinfo/webservices


            _______________________________________________
            webservices mailing list
            webservices<at>iris.washington.edu
            http://www.iris.washington.edu/mailman/listinfo/webservices


            • Andrew Barbour
              2014-04-22 19:58:59
              Hi Chad,

              Thanks for the info.

              The collaborative approach seems more in line with the spirit of R, which
              has seen exponential growth in user-contributions (see, for example,
              http://r4stats.com/2013/03/19/r-2012-growth-exceeds-sas-all-time-total/).
              If you do plan to release it, I would argue for CRAN (
              http://cran.us.r-project.org/).

              It's difficult to say how may people might use it; there are seismologists
              that actively maintain packages though (e.g., Jonathan Lees).

              -Andy



              On Mon, Apr 21, 2014 at 10:56 PM, Chad Trabant <chad<at>iris.washington.edu>wrote:


              Hi Andy,

              To fill in some gaps there, we have an internal data processing system
              that uses R and a library/module has been developed to fetch data from our
              web service interfaces. We’ve discussed the possibility of releasing it
              but have not come to any conclusion yet. I imagine it might best work as a
              collaborative development/maintenance, where we release what we’ve got and
              let the community of R users build on it. I’m curious how many R users
              would use a web service access library?

              If you do end up creating web service access code for R you might consider
              releasing it in SeisCode (https://seiscode.iris.washington.edu/) or
              having a bookmark in SeisCode to help folks find your work.

              regards,
              Chad

              On Apr 19, 2014, at 10:12 AM, andy barbour <andy.barbour<at>gmail.com> wrote:

              I can't say I wouldn't be curious to see an 'official' set of R codes...
              I'll stay tuned.


              On Fri, Apr 18, 2014 at 3:27 PM, Robert Casey <rob<at>iris.washington.edu>wrote:


              I wonder if we should at all make mention of our R code for MUSTANG? I
              don't think that Jon has made his version of the code public yet.

              Just thinking out loud. Maybe better to keep it internal until we start
              talking about a distributed MUSTANG-lite. Andy might feel better about
              using a WADL for his stuff anyway.

              -RobC



              On Apr 18, 2014, at 2:37 PM, andy barbour wrote:

              Hi Bruce,

              OK, good to know.

              In regards to the .wadl files... I'm developing a package for the R
              programming language, and I use the wadl files to generate a list of query
              parameters for a given webservice (so I don't have to remember them, or
              visit the webpage each time). If you're interested the code is being
              developed here: https://github.com/abarbour/irisws

              thanks,
              Andy



              _______________________________________________
              webservices mailing list
              webservices<at>iris.washington.edu
              http://www.iris.washington.edu/mailman/listinfo/webservices


              _______________________________________________
              webservices mailing list
              webservices<at>iris.washington.edu
              http://www.iris.washington.edu/mailman/listinfo/webservices



              _______________________________________________
              webservices mailing list
              webservices<at>iris.washington.edu
              http://www.iris.washington.edu/mailman/listinfo/webservices



Page built 16:09:52 | v.995c67d7