1. Tweaking CWIC Practices to Fit
11/23/2018 9:08 AM
Tweaking CWIC Practices to Fit
Archie Warnock
Lingjun Kang
Genyong Yu
CWIC Development Team Workshop
Greenbelt, MD February 2015
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Unsupported Search Terms
11/23/2018 9:08 AM
 Unsupported Search Terms 
Scenario: Client submits a request containing terms that are not supported by either CWIC or the data provider system
Server response
How does the server respond?
Error – runs the risk of frustrating users who can’t filter results as desired
Ignore the unsupported term – runs the risk of returning irrelevant results
Pros & Cons?
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Data Center Limitations
Scenario: Remote data provider system has performance or resource limitations
Spatial footprint too large
Temporal range too large
Server actions
Ignore limitations and expect error response from data provider
Filter request ahead of time to return error response
What if limitations aren’t fixed/codified?
Search timout?
Communication of limitations from provider?
Pros & Cons?

4. Results Sorting
Scenario: Client requests results sorted on some parameter
Server action:
Request result sorting from data provider
What if data provider does not support sorting on that (or any) parameter?
Return error?
Ignore request and return results sorted as data provider chooses?
Sort results at CWIC?
How to handle pagination?
Pros & Cons?

5. Additional Response Formats
CWIC can supply other response formats
Internal result set architecture lends itself to flexible response formats
HTML?
RSS?
KML?
Priorities?

6. Spatial Polygon Search
Is there a need to support search for more general spatial structures?
Not all data providers support search for anything but bounding rectangle
Server actions:
Translate spatial structure to MBR and search?
Return error (data provider specific)
Pros & Cons?

7. Proposed Changes Dublin Core CSW response
Replace (bogus) start/end date elements <dc:coverage.dateStart> <dc:coverage.dateEnd> with <dc:coverage>startdate/enddate</dc:coverage>
NOTE: Dublin Core spec recommends <dc:coverage>start=…; end=…</dc:coverage>
See period/
See also which recommends start/end but is a year before the DC document (2006)