<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hey Chris,<div><br></div><div>the way to verify who is right is to look at the schema, so:</div><div><br></div><div><a href="http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd">http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd</a></div><div><br></div><div>it defines:</div><div><br></div><div><span class="webkit-html-attribute-name" style="font-family: monospace; font-size: 13px;">xmlns:ows</span><span style="color: rgb(136, 18, 128); font-family: monospace; font-size: 13px;">="</span><span class="webkit-html-attribute-value" style="font-family: monospace; font-size: 13px;"><a href="http://www.opengis.net/ows/1.1">http://www.opengis.net/ows/1.1</a></span><font color="#881280" face="monospace" size="2">”</font></div><div><font color="#881280" face="monospace" size="2"><br></font></div><div><font color="#881280" face="monospace" size="2"><br></font><div>so this is the correct namespace URI to use.</div><div apple-content-edited="true"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br></div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Best regards,</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Bart</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br></div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">--</div><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Bart van den Eijnden<br>Front-end Developer | Boundless<br>@boundlessgeo</div>
</div>
<br><div><div>On 26 May 2014, at 10:30, Christopher Eykamp <<a href="mailto:christopher.eykamp@tudor.lu">christopher.eykamp@tudor.lu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
  
    <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
  
  <div text="#000000" bgcolor="#FFFFFF">
    Hi Tim,<br>
    <br>
    Thanks for the reply.  I am less familiar with the standards than
    you are, so can you tell me how one can determine that the second
    schema is for WCS 1.1.0, and not the first?  From the names, I would
    conclude that the first is correct, and that the second is... also
    correct?<br>
    <br>
    In any event, I will need to find a way to parse this document (I
    don't control the server, and our partner who does is probably
    unable to resolve things on their end).  I will look into Bart's
    suggestion to see if that offers a way forward.<br>
    <br>
    Thanks!<br>
    <br>
    Chris<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 05/23/2014 06:25 PM, Timothy Astle
      wrote:<br>
    </div>
    <blockquote cite="mid:537F768F.2030700@caris.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
      <font size="-1"><font face="Lucida Console">I believe you've hit
          an oddity in the WCS sc<font face="Lucida Console">hemas<font face="Lucida Console">.</font><br>
            <br>
            <font face="Lucida Console"><font face="Lucida Console">Look
                at this one:<br>
                <font face="Lucida Console"><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://schemas.opengis.net/wcs/1.1.0/wcsDescribeCoverage.xsd">http://schemas.opengis.net/wcs/1.1.0/wcsDescribeCoverage.xsd</a><br>
                  <br>
                  <font face="Lucida Console">Now look at this one:<br>
                    <font face="Lucida Console"><a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd">http://schemas.opengis.net/wcs/1.1/wcsDescribeCoverage.xsd</a><br>
                      <br>
                      <font face="Lucida Console">Do you <font face="Lucida Console">s</font>e<font face="Lucida Console">e a difference in the
                          ows namespace?</font>  From what I recall, the
                        second one is correct<font face="Lucida Console"><font face="Lucida Console">.  <font face="Lucida
                              Console">A few years ago I was in a simi<font face="Lucida Console">lar situation.</font></font></font></font></font></font></font></font></font></font></font></font></font> 
      <font face="Lucida Console">I'm thinking ArcGIS <font face="Lucida Console">Server<font face="Lucida Console"> might
            be <font face="Lucida Console">generating XML using the
              wrong s<font face="Lucida Console">chemas<font face="Lucida Console">.</font></font></font></font></font></font><br>
      <br>
      <font face="Lucida Console">So I believe OL is correct and the <font face="Lucida Console">"<font face="Lucida Console">problem" is
            with ArcGIS Server, leading f<font face="Lucida Console">rom
              the</font> OGC schema confusion.<font face="Lucida
              Console">  I<font face="Lucida Console">'d love to know
                the history behind it.<br>
                <br>
                <font face="Lucida Console">Do you have control over the
                  ArcGIS <font face="Lucida Console">Server ins<font face="Lucida Console">tance?  It could be
                      something you want to bring up with ESRI.</font></font></font><br>
              </font></font></font><br>
            <font face="Lucida Console">Cheers,</font><br>
          </font></font><br>
      <font face="Lucida Console">Tim</font><br>
      <br>
      <br>
      <br>
      <br>
      <div class="moz-cite-prefix">On 23/05/2014 12:19 PM, Christopher
        Eykamp wrote:<br>
      </div>
      <blockquote cite="mid:537F66EE.80003@tudor.lu" type="cite">Hello,
        <br>
        <br>
        I am getting the attached response from an ArcGIS WCS server,
        with request DescribeCoverage and protocol version 1.1.0. 
        OpenLayers (latest 1.x from GitHub) cannot retrieve the Title or
        Abstract attributes because the namespaces referenced in the
        OpenLayers.Format.WCSDescribeCoverage.v1_1_0 object conflict
        with what is referenced in the document. <br>
        <br>
        Specifically, the OpenLayers namespaces object includes this
        line: <br>
        <br>
            ows: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/ows/1.1">"http://www.opengis.net/ows/1.1"</a>
        <br>
        <br>
        This in turn is used to generate a namespaceAlias lookup, which
        will return "ows" when looking up <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/ows/1.1">"http://www.opengis.net/ows/1.1"</a>.
        However, in this case, I need "ows" to be mapped to <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/ows">"http://www.opengis.net/ows"</a>. 
        If I make that change in the namespaces definition, tests
        break.  Unfortunately, given the way the aliases are defined, I
        cannot add a second namespace that maps to "ows", which might
        fix my problem. <br>
        <br>
        I am unsure how to proceed.  I can't tell if I am encountering a
        misbehaving server, or if this is just a limitation of the way
        OpenLayers is architected (hard-coded namespaces that can only
        have one namespace map to a given alias).  Or have I
        misunderstood something at a more fundamental level? <br>
        <br>
        Thanks for your advice! <br>
        <br>
        Chris <br>
        <br>
        <br>
        <br>
        <CoverageDescriptions xmlns=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/wcs/1.1">"http://www.opengis.net/wcs/1.1"</a>
        xmlns:ows=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/ows">"http://www.opengis.net/ows"</a>
        xmlns:owcs=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/wcs/1.1/ows">"http://www.opengis.net/wcs/1.1/ows"</a>
        xmlns:xsi=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>
        xmlns:gml=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/gml">"http://www.opengis.net/gml"</a>
        xsi:schemaLocation=<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://www.opengis.net/wcs/1.1../wcsDescribeCoverage.xsdhttp://www.opengis.net/wcs/1.1/ows../owsDataIdentification.xsd">"http://www.opengis.net/wcs/1.1

          ../wcsDescribeCoverage.xsd http://www.opengis.net/wcs/1.1/ows
          ../owsDataIdentification.xsd"</a>><CoverageDescription><ows:Title>OSDATA.OS_25K_RASTER_1</ows:Title><ows:Abstract/><Identifier>1</Identifier><Domain><SpatialDomain><ows:BoundingBox

        crs="urn:ogc:def:crs:OGC::imageCRS"
        dimension="2"><ows:LowerCorner>0
        0</ows:LowerCorner><ows:UpperCorner>16273
        8848</ows:UpperCorner></ows:BoundingBox><ows:BoundingBox
        crs="urn:ogc:def:crs:EPSG::4326"><ows:LowerCorner>-2.4975225300277217

        57.00034657412791</ows:LowerCorner><ows:UpperCorner>-2.0000237693585987

        57.270861907368726</ows:UpperCorner></ows:BoundingBox><GridCRS><GridBaseCRS>urn:ogc:def:crs:EPSG::4326</GridBaseCRS><GridOrigin>-2.4975072449484337

        57.27084662228944</GridOrigin><GridOffsets>3.057015857620272e-005

        -3.0570158576202496e-005</GridOffsets></GridCRS></SpatialDomain></Domain><Range><Field><Title>Field_1</Title><Abstract>Field_1</Abstract><Identifier>Field_1</Identifier><Definition><owcs:AnyValue/></Definition><NullValue>256</NullValue><NullValue>256</NullValue><NullValue>256</NullValue><owcs:InterpolationMethods><owcs:DefaultMethod>nearest</owcs:DefaultMethod><owcs:OtherMethod>bilinear</owcs:OtherMethod><owcs:OtherMethod>bicubic</owcs:OtherMethod></owcs:InterpolationMethods><Axis

        identifier="BAND"><AvailableKeys><Key>1</Key><Key>2</Key><Key>3</Key></AvailableKeys><owcs:DataType>Byte</owcs:DataType></Axis></Field></Range><SupportedCRS>urn:ogc:def:crs:EPSG::4326</SupportedCRS><SupportedCRS>urn:ogc:def:crs:EPSG::4326</SupportedCRS><SupportedFormat>image/GeoTIFF</SupportedFormat><SupportedFormat>image/NITF</SupportedFormat><SupportedFormat>image/HDF</SupportedFormat><SupportedFormat>image/PNG</SupportedFormat></CoverageDescription></CoverageDescriptions>

        <br>
        _______________________________________________ <br>
        Dev mailing list <br>
        <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a> <br>
        <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a>
        <br>
        <br>
        <br>
      </blockquote>
      <br>
      <div class="moz-signature">-- <br>
        <meta http-equiv="Content-Type" content="text/html;
          charset=ISO-8859-1">
        <div style="width:570px;"> Tim Astle<br>
          Development Manager<br>
          Web Technologies<br>
          <br>
          <a moz-do-not-send="true" 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>
          <span style="color:#004680;"><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.caris.com/">www.caris.com</a></span><p style="margin-top:40px; font-family:'Trebuchet MS', Arial,
            Helvetica, sans-serif;"> <span style="color:#004680;"><strong>CARIS

                2014</strong></span><br>
            June 2-5, 2014 | Brest, France | 2-5 juin, 2014<br>
            Join us in France at CARIS 2014 as we focus on Developing
            the Blue Economy. <span style="color:#004680;"><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.caris.com/caris2014/">www.caris.com/caris2014/</a></span><br>
            Venez nous rejoindre en France pour CARIS 2014 et appuyons
            ensemble l'Économie Bleue. <span style="color:#004680;"><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.caris.com/caris2014-fr/">www.caris.com/caris2014-fr/</a></span></p><p style="margin-top:40px; line-height:1.2em;
            font-weight:bold;">Download your free copy of CARIS Easy
            View today!<br>
            <span style="color:#004680;"><a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="http://www.caris.com/easyview">www.caris.com/easyview</a></span></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>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a></pre>
    </blockquote>
    <br>
  </div>

_______________________________________________<br>Dev mailing list<br><a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>http://lists.osgeo.org/mailman/listinfo/openlayers-dev</blockquote></div><br></div></body></html>