08/22/2004 3:13 PM
post4435
|
SF-CDL spec for community practice track
Jun's presentation at GGF11 (page 15 of http://tinyurl.com/49wkv )said that the purpose of XML-CDL is composability and
interoperability and the minutes underpins the characteristics of the two CDLs as follows;
> Note that the SF CDL is intended to be more user-friendly /
> user-tractable, while the XML CDL is more standardised, is the interop
> format (i.e. we can translate from various front ends into the XML
> form), but is less user-friendly to use directly.
The BizGrid system (platform) and other grid systems (platforms) may decide to adopt XML-CDL as their description
language. And a CDL translator would enable these systems (platforms) to accept a description written in SF-CDL. (
Similarly they could choose to implement other proprietary languages and use XML-CDL for interoperability.) So I am not
sure how much interest there would be in implementing SF-CDL. Keeping in mind that Proposed Recommendations need two
interoperable implementations within 2 years to become Recommendations I am doubtful that SF-CDL would make it to the
Recommendation stage.
So if I understand the roles of the two CDLs correctly, I think SF-CDL specification should be "community practice"
track instead of "recommendation" track. Community Practice Documents (GFD-C), inform and influence the community
regarding an approach or process that is considered to be widely accepted by consensus and practice in the Grid
community. I think in this sense SF-CDL is excellent evidence and will guide XML-CDL and related platforms.
|
|
|