Difference between revisions of "Talk:Service Collaboration Demos"

Revision as of 10:20, June 1, 2006

Discussion on Service_Collaboration_Demos.

To add to the discussion, log in to DataFed wiki
Begin each entry with ====Username: Subject====
To respond, add dots ====......Username: Subject====
Indent response text by adding : for each tab.
Sign your entry by ending with '~~~~',

PZhao: Lets Discuss Chaining Specifics

We take lots of time to discuss the WCS capability. But we still have no a clear scenario for this service chain demo (maybe I miss something). I think it is time to discuss what services will be used and how to chain them based on the existing service capabilities, not just WCS. PZhao 23 May 2006 (EDT)

......RHusar: RE: Lets Discuss Chaining Specifics

I am happy that you brought up this issue. At the last NASA Web Services telecon Liping had a really nice suggestion that I fully subscribe to.

 1. We all expose our respective DATA ACCESS services so the other Chainers can assess our DATA. 
 2. Next we access each others remote data through formal standard interfaces, WCS and/or SOAP
 3. Then we perform WS chaining within our own backyard using our respective  BPEL, SciFlo, WIPE, or DataFed workflow engines
 4. At ESIP:
      a. demonstrate our respective data access and chaining operations; 
      b. we describe our approach and experiences; 
      c. compare with each other's approach and experiences.

This simplification would allow us to make it through the first, obviously very difficult hurdle of accessing each others data. It would also demo service chaining within our own home environments. Based on last Monday's telecon Brian also agreed with the simplified approach to our first interoperability demo.

In order to make a step in this direction we have prepared a somewhat formal description of our data access services as applied to a set of nine "interesting" air quality datasets DataFed_Data_Access_Services.

Liping, please note that these air quality datasets could be potentially useful for the Denver IGARSS06 GSN demo as well. In fact, I stuck a few notes in this regard into the above wiki page. I would like to talk to you more about the GSN demo, possibly before the May 31 telecon. If we play our cards right we may be able to combine this ESIP service chaining effort with the GSN demo. What do you think?

@@ Line 3: / Line 3: @@
 <center>'''''Discussion on [[Service_Collaboration_Demos]].'''''</center>
 {{edithelp}}<br>
-====MSchulz: Questions about the Wiki====
+====PZhao: Lets Discuss Chaining Specifics====
-I think your idea with the wiki pages is great! For exchanging and establishing ideas on standards and tools for the [http://datafedwiki.wustl.edu/images/b/b6/060314Schulz_IspraReport.doc intercomparison work] in an interactive way. Thanks a lot for pointing us to this. At this point, in the beginning, it would be really important to  choose a representative entry point. Which has some longer life time. which is even not linked too much to an individual organisation. Otherwise a discussion on standards makes no sense. I think also GEMS is not the right thing, since it is a project and by definition will end in some years. So I have some questions ( also to the colleagues):
+We take lots of time to discuss the WCS capability. But we still have no a clear scenario for this service chain demo (maybe I miss something). I think it is time to discuss what services will be used and how to chain them based on the existing service capabilities, not just WCS. [[User:PZhao|PZhao]] 23 May 2006 (EDT)
+====......RHusar: RE: Lets Discuss Chaining Specifics====
-. Is ESIP the right federation to keep this? (I have not heard of it before)Isnt that purely American?
+:I am happy that you brought up this issue. At the last NASA Web Services telecon Liping had a really nice suggestion  that I fully subscribe to.
-. Wouldn't it be better to have for example an IGAC administrated wiki page? I must admit that I find it nice to just start and may be we can copy everything to another place once we found it.
+. We all expose our respective DATA ACCESS services so the other Chainers can assess our DATA.
+. Next we access each others remote data through formal standard interfaces, WCS and/or SOAP
-. Who will be the administrator and can create new pages for example in your initial set-up?
+. Then we perform WS chaining within our own backyard using our respective  BPEL, SciFlo, WIPE, or DataFed workflow engines
+. At ESIP:
-. Who can change the general outline of these pages? I think there is always too much meta communication on how to edit and who has edited and when etc on these wiki pages.
+       a. demonstrate our respective data access and chaining operations;
+       b. we describe our approach and experiences;
-. Is there an administrator at ESIP who would react within a day or two if we had small wishes? [[User:MichaelSchulz|MichaelSchulz]] 13:21, 11 May 2006 (EDT)
+       c. compare with each other's approach and experiences.
-====......RHusar: RE: Questions about the Wiki====
+This simplification would allow us to make it through the first, obviously very difficult hurdle of accessing each others data. It would also demo service chaining within our own home environments. Based on last Monday's telecon Brian also agreed with the simplified approach to our first interoperability demo.
-:1. This wiki is part of the Earth Science Information Partners Federation, [http://esipfed.org/ ESIP] wiki. We chose ESIP
+In order to make a step in this direction we have prepared a somewhat formal description of our data access services as applied to a set of nine "interesting" air quality datasets [[DataFed_Data_Access_Services]].
+Liping, please note that these air quality datasets could be potentially useful for the Denver IGARSS06 GSN demo as well. In fact, I stuck a few notes in this regard into the above wiki page. I would like to talk to you more about the GSN demo, possibly before the May 31 telecon. If we play our cards right we may be able to combine this ESIP service chaining effort with the GSN demo. What do you think?