[acs-wg] Roadmap...

[Keisuke Fukui]

Hi Mike,

Thanks for a heads up!
It's been a while since we talked. How are you?

I inserted some comments to show my understanding among your quote.

Michael Behrens wrote:
> All,
> The Roadmap editor would like to get some input for the new OGSA RoadMap 
> document....what is currently in the document is shown below....perhaps 
> we can update the dates with the actual values and propose challenging 
> v2 draft date?  Open for discussion....we'll be able to meet at GGF-18 
> and discuss, however the mark-ups are needed before the end of this month.
> 
> Thanks!
> 
> 1.1        Application Content Service Specification Version 1.0
> 
> The grid community currently manually creates and manages grid application content consisting of executables, scripts, and data.  The Application Content Service (ACS) specification specifies a set of Web services that provide a way to archive components for stable storage and retrieval within a standardized format.  This allows grid applications and their data to be packaged, stored, and then referenced over time as needed across domains.
> 
> ACS does not interpret or execute information in the contents; rather it just manages the contents for use by other OGSA services.

I don't think we need updates here.

> 
> 1.1.1        Development Schedule
> 
> The Application Content Service Working Group (ACS-WG) is now developing this specification. 
> 
> Milestones
> 
> /*First draft available, June 2005
> 
> Ready for public comment review, October 2005
It was November in fact.

> 
> GFD-R.P publication, December 2005

It's still hanging around GGF document pipeline with some other
expected GFD-R.P. There is no issues to block publication, but it
is purely administrative work to be done. So there is nothing to be
done from our side in my understanding.

> 
> Table 4‑11 ACS Specification 1.0 document schedule
> 
> The final specification is expected to be completed during 2005.  The Business Grid Computing project will provide an open-source reference implementation by early 2006.

As such, the ACS 1.0 specification is completed waiting to be published. Maybe
we can propose ACS 2.0 schedule here, but wee need some planning to refer to that.
Reference implementation status should be updated to reflect both NAREGI PSE
and Business Grid Project.

> 
> 1.1.2        Referenced Specifications 
> 
> This specification will refer to OGSA WSRF Basic Profile 1.0 and the Installable Unit Deployment Descriptor (IUDD) specification being developed by the OASIS SDD-TC.  Either RNS or WS-Naming is also expected to be referenced, since application archives can be referenced externally.
We don't have a reference to the IUDD in ACS1.0. We may refer to ACS2.0 about SDD specification.

> 
> Table 4‑12 ACS 1.0 referenced specifications
> 
> 1.1.3        Expected Use
> 
> Given that ACS and IUDD are complementary, IUDD will refer to ACS in order to cover grid scenarios. Since ACS provides an API to an archive for applications and data, it is anticipated that job management and advanced execution specifications would use the application archive interface for applications under the control of a business manager. Thus future EMS architecture documents and advanced EM profiles may refer to the ACS specification. Also, since the application archive may include multiple component types, including configuration description and job control flow, future versions of the XML-CDL specification may refer to the ACS specification.

I don't have necessity to update in my perspective here. Do you?


I think it is a good time to have teleconference this week to cover GGF18
planning and this. Mike, are you available at the regular wg call schedule
(Wednesday night) this week? Anyone else?

 -Keisuke