Page 1 OpenSearch Project CEOS WGISS Meeting #40 Interoperability Interest Group M.Albani, P.Mougnaud, A.Della Vecchia (ESA) Yves Coene (Spacebel) WGISS#40 | OpenSearch | 1 Oct 2015

Page 2 Outline Developer's Guide Future of OpenSearch Project WGISS#40 | OpenSearch | 1 Oct 2015

Page 3 Developer's Guide ESA provided feedback on v1.3 of Developer's Guide Recommendation to refactor and not introduce additional requirements in Developer Guide. –Refer to Best Practice requirements when providing guidance –Move agreed additional requirements to update of Best Practice document, e.g. CEOS-DG-006 (geo:geometry profiles) CEOS-DG-014 (preserve all info in URL template) CEOS-DG-018 (rel=first, previous, next, last, self) CEOS-DG-021 (dc:date) CEOS-DG-022 (atom:link types) WGISS#40 | OpenSearch | 1 Oct 2015

Page 4 Future of OpenSearch Project Update of CEOS OpenSearch Best Practice v1.0.1 Refactoring and finalisation of Developer's Guide Conformance test environment –Definition of CEOS Conformance Test to verify compliance wrt CEOS BP of external OpenSearch servers WGISS#40 | OpenSearch | 1 Oct 2015

Page 5 Future of OpenSearch Project Update of CEOS OpenSearch Best Practice v1.0.1 –Clarify/strengthen applicability of OGC specifications (e.g. page 9 "encouraged"). Distinguish between applicable and reference documents. –Implementation feedback (clients, servers, tests) –Additional requirements (e.g. from original Developer's Guide) CEOS-DG-006 (geo:geometry profiles) CEOS-DG-014 (preserve all info in URL template) CEOS-DG-018 (rel=first, previous, next, last, self) CEOS-DG-021 (dc:date) CEOS-DG-022 (atom:link types) Atom:link describedby should contain Media type attribute. Guidance for in OSDD. (*) Numbering taken from Developer Guide v1.3 WGISS#40 | OpenSearch | 1 Oct 2015

Page 6 Future of OpenSearch Project Update of CEOS OpenSearch Best Practice v1.0.1, e.g. –BP-004: Unclear what are the conditions a server should comply with, to state that it complies with the CEOS Best Practice v E.g. is compliance with CEOS-BP-009 (which is [optional] and not a [requirement]) required ? –BP-011: should be clarified to state that the dc: namespace used in this requirement should correspond to the dc: namespace defined in OGC r8. –BP-014: Best Practice should provide an encoding example for multi-polygon footprint. Using corresponding GML in georss:where violates the (limited) GML schema referred to from GEORSS Web pages. –BP-016 wording to be updated to clarify that this applies to Granule search responses only. WGISS#40 | OpenSearch | 1 Oct 2015

Page 7 Future of OpenSearch Project Update of Best Practice to: –Define expected behaviour of wildcards in search parameters (eo:platform="SPOT*") –Guidance on returning multiple browse images (multi-polygon). –Guidance for search parameter names: E.g. {eo:platform} (OGC r5) versus {echo:satellite}, {eo:parentIdentifier} versus {catsi:datasetId} etc. –Guidance for parameter values: E.g. {eo:orbitDirection} = "DESCENDING" or "D" ? –In case of syndication/aggregation, provide provenance information as rel="via" links at feed level in similar way as WGISS#40 | OpenSearch | 1 Oct 2015

Page 8 Future of OpenSearch Project Update of Best Practice to: –Extend/Clarify Parameter extension 1.0 Draft2 Define priority of template versus Param extension in case parameter list is different. Distinguish between exhaustive and non-exhausive list of elements in –E.g. and pattern attribute present -> non-exhaustive. without pattern attribute -> exhaustive list ? Options (for instrument) depending on choice for other parameters (e.g. for platform) WGISS#40 | OpenSearch | 1 Oct 2015

Page 9 Future of OpenSearch Project –Guidance on how to return multiple files as "rel=enclosure" (e.g. Metalink file as enclosure) Other: –Improve/extend OGC r5 with (subset of) CEOS Best Practice requirements? –Change request to Parameter extension of OpenSearch or update of this specification ? WGISS#40 | OpenSearch | 1 Oct 2015