[Esip-discovery] associating datasets with services in casts

[Hua, Hook (388C)]

This data to service "matchup" is an interesting one. I can see the associations be done in many ways. Here are 3 approaches within the current framework:

(1) for both collection-level and granule-level DataCasts, could include a set of rel links for associated services.

(2) for ServiceCasting, could also include a set of rel links for associated DataCasts. Also, there is nothing to stop us from including OpenSearch OSDDs and granule-level search links.

(3) make matchup an OpenSearch capability. that is, a search for a given dataset would only show results where that dataset shows up in DataCasts AND ServiceCasts. So the results show the matched up associations. Vice-versa for querying for services.

It appears that (1) and (2) require minimal changes. They are essentially service mashups. (3) is quite interesting as it is about using OpenSearch in a new way--as a match-maker.

--Hook

________________________________________
From: esip-discovery-bounces at lists.esipfed.org [esip-discovery-bounces at lists.esipfed.org] On Behalf Of Lynnes, Christopher S. (GSFC-6102) [christopher.s.lynnes at nasa.gov]
Sent: Wednesday, April 20, 2011 10:46 AM
To: esip-discovery at lists.esipfed.org
Subject: [Esip-discovery] associating datasets with services in casts

Within EOSDIS, we have a few projects (Reverb, Simple Subset Wizard, EOSDIS Service Interface) that need to share information about which datasets are associated with which services.  Are there any ideas out there on how we might implement this association within the servicecasting framework?

This dataset-service association seems like a fundamental issue for services in general...Does it warrant a discussion in an ESIP breakout session?
--
Dr. Christopher Lynnes     NASA/GSFC, Code 610.2    phone: 301-614-5185


_______________________________________________
Esip-discovery mailing list
Esip-discovery at lists.esipfed.org
http://www.lists.esipfed.org/mailman/listinfo/esip-discovery