[Esip-discovery] Testbed project - service validation insight needed

[Christine White]

Hello Discovery Cluster,
There has been some progress on our Testbed project - we were able to deploy the out-of-the-box Geoportal Server software on an Amazon Web Services instance - see http://
23.23.211.222:8080/geoportal. As an anonymous user to the geoportal, you can search for resources using the Search tab (although I didn't register many yet, just some ArcGIS Server services for test purposes).  I will be adding folks that are on our Discovery Testbed tester list as users who can login and add resources later on.

So now that we have the test environment in place, it is time to make progress on development. On our last call, some folks volunteered to provide insight on the custom development and services to be used for testing. There are a few questions regarding the customizations that I could use some help on - so if you have answers/opinions, please speak up!


1.       According to DCP1 (http://wiki.esipfed.org/index.php/Discovery_Cast_Atom_Response_Format_v1.1) documentation, it seems that the only required elements in a response (except for those required by ATOM 1.0) are the <georss:box>. However, is it expected that compliant responses should also include at least the time:start/time:end?  So our minimum set should be at least these three things - <georss:box>, <time:start>, and <time:end> - in addition to the ones already required by ATOM 1.0, correct?



2.       It seems ideal that we could register a cast and then search it's <entry> items, as documented in the Query aggregated data and services use case<http://wiki.esipfed.org/index.php/Query_aggregated_data_and_services>.  So what this would look like: after a cast is validated, it could appear as an endpoint whose entries can be accessed/filtered/searched. Am I on the right track?



3.       From the Discovery Cluster wiki, I see links to the OpenSearch Services<http://wiki.esipfed.org/index.php/Discovery_OpenSearch_Services>, DataCasting Services<http://wiki.esipfed.org/index.php/Discovery_DataCasting_Services> and ServiceCasting Services<http://wiki.esipfed.org/index.php/Discovery_ServiceCasting_Services> example pages. In the examples from these pages, I see casts formatted in both ATOM v1.0 and RSS 2.0, and understand that an OpenSearch response can also be formatted in JSON and other formats.  Are we only focusing on validating against the DCPs e.g., ATOM v1.1 at this point? If we agree on validating more, then we will need a URL to the desired specification/version.

Many thanks for your help,

Christine White
---------------------------
SDI Solutions Team, Esri
909-793-2853 x 4355
cwhite at esri.com<mailto:ceggers at esri.com>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.esipfed.org/pipermail/esip-discovery/attachments/20120430/810e5a49/attachment.html>