<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    I like the idea of leaning on an existing API, like OpenSearch or a
    CSW.  Both would work.  This is what I imagined what the OWS Common
    "OtherSource" was designed for.  I find using an existing API is a
    nicer approach than creating something new.  (Similar to Tim Bray's
    <a
href="http://www.tbray.org/ongoing/When/200x/2006/01/08/No-New-XML-Languages">"Don't
      Invent XML Languages</a>" adage.)<br>
    <br>
    Tim<br>
    <br>
    <div class="moz-cite-prefix">On 06/08/2015 1:36 PM, Panagiotis
      (Peter) A. Vretanos wrote:<br>
    </div>
    <blockquote cite="mid:55C38D1D.6040403@cubewerx.com" type="cite">Simon
      at al.
      <br>
      <br>
      Already done ... but we used an OpenSearch API rather than XPath
      letting the underlying server pick nay query technology it likes.
      <br>
      <br>
      <a class="moz-txt-link-freetext" href="https://portal.opengeospatial.org/files/?artifact_id=54580">https://portal.opengeospatial.org/files/?artifact_id=54580</a>
      <br>
      <br>
      Ciao.
      <br>
      <br>
      On 08/05/2015 05:56 PM, <a class="moz-txt-link-abbreviated" href="mailto:Simon.Cox@csiro.au">Simon.Cox@csiro.au</a> wrote:
      <br>
      <blockquote type="cite">ØTherefore, we have prepared a WCS
        Extension which I want to propose for voting
        <br>
        at the Nottingham TC. This extension introduces a very simple
        concept: an XPath
        <br>
        expression can be submitted which is evaluated on the
        Capabilities document on
        <br>
        server side. This allows applications to get exactly what they
        need, without
        <br>
        excess data transfer. If you feel that this is a way forward,
        maybe you want to
        <br>
        support this in the upcoming TC meeting - any such support is
        greatly appreciated!
        <br>
        <br>
        And perhaps better still, submit this idea as an OWS Common CR
        or as input to
        <br>
        the upcoming revision.
        <br>
        <br>
        *From:*Requests
        <br>
        [<a class="moz-txt-link-freetext" href="mailto:requests-bounces+simon.cox=csiro.au@lists.opengeospatial.org">mailto:requests-bounces+simon.cox=csiro.au@lists.opengeospatial.org</a>]
        *On Behalf
        <br>
        Of *Peter Baumann
        <br>
        *Sent:* Wednesday, 5 August 2015 5:31 PM
        <br>
        *To:* Timothy Astle <a class="moz-txt-link-rfc2396E" href="mailto:timothy.astle@caris.com"><timothy.astle@caris.com></a>;
        <a class="moz-txt-link-abbreviated" href="mailto:requests@lists.opengeospatial.org">requests@lists.opengeospatial.org</a>
        <br>
        *Subject:* Re: [Requests] OGC Web Coverage Service - Transaction
        operation
        <br>
        extension - Comment
        <br>
        <br>
        Dear Timothy,
        <br>
        <br>
        after completion of the RFC period I'm coming back to your (very
        thoughtful)
        <br>
        questions below.
        <br>
        <br>
        Re Req 8: This actually is a known issue with OWS Common. A
        service provider can
        <br>
        decide which elements to expose in a Capabilities document,
        which has been
        <br>
        considered sufficient in the past. Alas, it does not solve the
        issue - practice
        <br>
        shows that either you get not enough information, or too much
        (such as all
        <br>
        coverages listed). In fact, the Capabilities mechanism is way
        too static and
        <br>
        inflexible.
        <br>
        <br>
        OGC has started thinking about how to fix and modernize, but
        there is no relief
        <br>
        on the horizon soon. Therefore, we have prepared a WCS Extension
        which I want to
        <br>
        propose for voting at the Nottingham TC. This extension
        introduces a very simple
        <br>
        concept: an XPath expression can be submitted which is evaluated
        on the
        <br>
        Capabilities document on server side. This allows applications
        to get exactly
        <br>
        what they need, without excess data transfer. If you feel that
        this is a way
        <br>
        forward, maybe you want to support this in the upcoming TC
        meeting - any such
        <br>
        support is greatly appreciated!
        <br>
        <br>
        Re References to grids: Core and extensions have been formulated
        very carefully
        <br>
        so as to allow all coverage types defined, which includes point
        clouds and
        <br>
        meshes. Currently, there is one extension which specifically
        refers to grids,
        <br>
        that is WCS Scaling: change of resolution is an operation
        meaningful on grids
        <br>
        only (at least that is my current understanding). Concretely
        speaking about
        <br>
        WCS-T, a point cloud (MultiPointCoverage) or mesh
        (MultiCurveCoverage or
        <br>
        MultiSurfaceCoverage or MultiSolidCoverage) can be inserted and
        deleted, and can
        <br>
        even be updated. Of course, update of a mesh requires more
        complex consistency
        <br>
        constraints to be respected, but that is inherent to the
        definition of such mesh
        <br>
        types, so does not have to be treated separately here.
        <br>
        <br>
        Actually, there is nothing in the mask parameter that confines
        us to a grid.
        <br>
        Consider a point cloud, for example, The mask in this case will
        contain the
        <br>
        direct positions of the points to be updated, associated with a
        range value of
        <br>
        "1" (likely in this case the "0" points will simply be left
        out), and this
        <br>
        guides the server on the points to be updated - say, with a new
        temperature
        <br>
        value. Hence, I'd claim that this definition works on all
        coverage types -
        <br>
        kindly let me know should I miss something here, it's a good
        opportunity to
        <br>
        catch any and all hiccups.
        <br>
        <br>
        And obviously there is one: searching for the root cause of your
        concern I find
        <br>
        occurrences of "maskGrid", a leftover forgotten in an earlier
        renaming action. I
        <br>
        have corrected this, and it actually resolves an inconsistency -
        good catch!
        <br>
        <br>
        Thank you again for the encouraging assessment and your
        thoughtful comments.
        <br>
        Looking forward to further discussion in future.
        <br>
        <br>
        best regards,
        <br>
        Peter
        <br>
        <br>
        On 2015-06-26 20:48, Timothy Astle wrote:
        <br>
        <br>
            A couple of questions:
        <br>
        <br>
            _Requirement 8 _
        <br>
            /After completion of a successful InsertCoverage request,
        the identifier of
        <br>
            the coverage established in the server’s offering shall be
        listed as an
        <br>
            existing coverage in this WCS service’s Capabilities
        document./
        <br>
        <br>
            OGC 06-121r9 (OGC Web Services Common Standard) still allows
        for the idea of
        <br>
            an "otherSource" for finding OWS content.  Is the above
        requirement
        <br>
            mandating thatwhen implementing a WCS-T, you must describe
        the coverage in
        <br>
            the Capabilities' CoverageSummary list?  I'm concerned that
        when dealing
        <br>
            with a large amount of coverages, that could really degrade
        the performance
        <br>
            of a system.
        <br>
        <br>
            _References to Grids_
        <br>
        <br>
            I definitely see value to this transactional extension to
        WCS.  I'm
        <br>
            definitely interested to watch WCS grow beyond gridded
        data.  In this
        <br>
            particular extension, I seereferences to gridsand
        grid-related terminology
        <br>
            and concepts.  I'm concerned that if / when point clouds or
        TINsare
        <br>
            introduced as extensions, that this specification might not
        makesense in
        <br>
            some contexts.  For example, if a WCS was created that
        specialized in TINs,
        <br>
            the optional grid parameters wouldn't really apply.  Is the
        intent that this
        <br>
            is a "grid transactional operation extension" or a "general
        coverage
        <br>
            operation extension"?  Would a future point cloud
        transactional extension be
        <br>
            created for point cloud operations?  I guess I'm just asking
        for clarification.
        <br>
        <br>
            Thank you for your time and consideration.
        <br>
        <br>
            --
        <br>
        <br>
            Tim Astle
        <br>
            Development Manager for Web Technologies
        <br>
        <br>
            *CARIS* <a class="moz-txt-link-rfc2396E" href="http://www.caris.com"><http://www.caris.com></a>
        <br>
            115 Waggoners Lane
        <br>
            Fredericton, New Brunswick
        <br>
            Canada    E3B 2L4
        <br>
            Tel: +1.506.458.8533     Fax: +1.506.459.3849
        <br>
            <a class="moz-txt-link-abbreviated" href="http://www.caris.com">www.caris.com</a> <a class="moz-txt-link-rfc2396E" href="http://www.caris.com"><http://www.caris.com></a>
        <br>
        <br>
            *Connect with CARIS*
        <br>
            Twitter <a class="moz-txt-link-rfc2396E" href="http://www.twitter.com/CARIS_GIS"><http://www.twitter.com/CARIS_GIS></a> | LinkedIn
        <br>
           
        <a class="moz-txt-link-rfc2396E" href="http://www.linkedin.com/groups?mostPopular=&gid=3217878"><http://www.linkedin.com/groups?mostPopular=&gid=3217878></a>
        | Facebook
        <br>
           
<a class="moz-txt-link-rfc2396E" href="https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878"><https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878></a><br>
            | Google+
        <br>
           
        <a class="moz-txt-link-rfc2396E" href="https://plus.google.com/b/114389770462919844434/114389770462919844434/posts"><https://plus.google.com/b/114389770462919844434/114389770462919844434/posts></a>
        |
        <br>
            YouTube <a class="moz-txt-link-rfc2396E" href="http://www.youtube.com/user/CARISGIS"><http://www.youtube.com/user/CARISGIS></a>
        <br>
        <br>
            Download your free copy of CARIS Easy View today!
        <br>
            <a class="moz-txt-link-abbreviated" href="http://www.caris.com/easyview">www.caris.com/easyview</a> <a class="moz-txt-link-rfc2396E" href="http://www.caris.com/easyview"><http://www.caris.com/easyview></a>
        <br>
        <br>
           
_________________________________________________________________________<br>
            This email and any files transmitted with it are
        confidential and intended
        <br>
            only for the addressee(s). If you are not the intended
        recipient(s) please
        <br>
            notify us by email reply. You should not use, disclose,
        distribute or copy
        <br>
            this communication if received in error.
        <br>
        <br>
            Any views or opinions expressed in this email are solely
        those of the author
        <br>
            and do not necessarily represent those of the company. No
        binding contract
        <br>
            will result from this email until such time as a written
        document is signed
        <br>
            on behalf of the company.
        <br>
        <br>
        <br>
        <br>
        <br>
            _______________________________________________
        <br>
        <br>
            Requests mailing list
        <br>
        <br>
            <a class="moz-txt-link-abbreviated" href="mailto:Requests@lists.opengeospatial.org">Requests@lists.opengeospatial.org</a> 
        <a class="moz-txt-link-rfc2396E" href="mailto:Requests@lists.opengeospatial.org"><mailto:Requests@lists.opengeospatial.org></a>
        <br>
        <br>
            <a class="moz-txt-link-freetext" href="https://lists.opengeospatial.org/mailman/listinfo/requests">https://lists.opengeospatial.org/mailman/listinfo/requests</a>
        <br>
        <br>
        <br>
        <br>
        --
        <br>
        <br>
        Dr. Peter Baumann
        <br>
        <br>
          - Professor of Computer Science, Jacobs University Bremen
        <br>
        <br>
            <a class="moz-txt-link-abbreviated" href="http://www.faculty.jacobs-university.de/pbaumann">www.faculty.jacobs-university.de/pbaumann</a> 
        <a class="moz-txt-link-rfc2396E" href="http://www.faculty.jacobs-university.de/pbaumann"><http://www.faculty.jacobs-university.de/pbaumann></a>
        <br>
        <br>
            <a class="moz-txt-link-abbreviated" href="mailto:mail:p.baumann@jacobs-university.de">mail:p.baumann@jacobs-university.de</a> 
        <a class="moz-txt-link-rfc2396E" href="mailto:p.baumann@jacobs-university.de"><mailto:p.baumann@jacobs-university.de></a>
        <br>
        <br>
            tel: +49-421-200-3178, fax: +49-421-200-493178
        <br>
        <br>
          - Executive Director, rasdaman GmbH Bremen (HRB 26793)
        <br>
        <br>
            <a class="moz-txt-link-abbreviated" href="http://www.rasdaman.com">www.rasdaman.com</a>  <a class="moz-txt-link-rfc2396E" href="http://www.rasdaman.com"><http://www.rasdaman.com></a>,
        <a class="moz-txt-link-abbreviated" href="mailto:mail:baumann@rasdaman.com">mail:baumann@rasdaman.com</a>  <a class="moz-txt-link-rfc2396E" href="mailto:baumann@rasdaman.com"><mailto:baumann@rasdaman.com></a>
        <br>
        <br>
            tel: 0800-rasdaman, fax: 0800-rasdafax, mobile:
        +49-173-5837882
        <br>
        <br>
        "Si forte in alienas manus oberraverit hec peregrina epistola
        incertis ventis dimissa, sed Deo commendata, precamur ut ei
        reddatur cui soli destinata, nec preripiat quisquam non sibi
        parata." (mail disclaimer, AD 1083)
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        <br>
        _______________________________________________
        <br>
        Requests mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:Requests@lists.opengeospatial.org">Requests@lists.opengeospatial.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://lists.opengeospatial.org/mailman/listinfo/requests">https://lists.opengeospatial.org/mailman/listinfo/requests</a>
        <br>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <div class="moz-signature">-- <br>
      <div style="width:600px;"> Tim Astle<br>
        Development Manager for Web Technologies<br>
        <br>
        <a href="http://www.caris.com" style="color:#004680;"><strong>CARIS</strong></a><br>
        115 Waggoners Lane<br>
        Fredericton, New Brunswick<br>
        Canada    E3B 2L4<br>
        Tel: +1.506.458.8533     Fax: +1.506.459.3849<br>
        <a href="http://www.caris.com" style="color:#004680;">www.caris.com</a>
        <p style="margin-top:20px;"> <strong style="color:#373737;">Connect
            with CARIS</strong><br>
          <a href="http://www.twitter.com/CARIS_GIS"
            style="color:#004680;">Twitter</a> | <a
            href="http://www.linkedin.com/groups?mostPopular=&gid=3217878"
            style="color:#004680;">LinkedIn</a> | <a
href="https://www.facebook.com/pages/CARIS-The-Marine-GIS-Experts/123907500987669?v=app_4949752878"
            style="color:#004680;">Facebook</a> | <a
href="https://plus.google.com/b/114389770462919844434/114389770462919844434/posts">Google+</a>
          | <a href="http://www.youtube.com/user/CARISGIS"
            style="color:#004680;">YouTube</a> </p>
        <p style="margin-top:16px; line-height:1.2em;">Download your
          free copy of CARIS Easy View today!<br>
          <a href="http://www.caris.com/easyview" style="color:#004680;">www.caris.com/easyview</a></p>
        <p style="font-size:0.8em;">_________________________________________________________________________<br>
          This email and any files transmitted with it are confidential
          and intended only for the addressee(s). If you are not the
          intended recipient(s) please notify us by email reply. You
          should not use, disclose, distribute or copy this
          communication if received in error.</p>
        <p style="font-size:0.8em;"> Any views or opinions expressed in
          this email are solely those of the author and do not
          necessarily represent those of the company. No binding
          contract will result from this email until such time as a
          written document is signed on behalf of the company.</p>
      </div>
    </div>
  </body>
</html>