[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dcml-frame] Implementation Subgroup
I agree, we need to identify the interfaces. But frankly an interface in a document is not worth nearly as much as an interface combined with an actual implemtation of that interface. And since we've already defined the key data interface in the current specification, we should implement it to see if it works. If it doesn't, or it's the wrong interface, or whatever, we should sharpen our pencils and try again. -- Tim Cummins, Fred A wrote: > Tim, > > My expectation was to focus on interfaces to services to > achieve interoperability between products developed by > different vendors. OASIS specifications for DCML should > define interfaces and product vendors should define > implementations. > > We should identify and specify priority interface(s) that have > market value and would be implemented by product vendors. > > Fred > > >>-----Original Message----- >>From: Tim Howes [mailto:howes@opsware.com] >>Sent: Tuesday, October 25, 2005 3:30 PM >>To: dcml-frame@lists.oasis-open.org >>Subject: [dcml-frame] Implementation Subgroup >> >>Hi all. Here's what I think the implementation subgroup that >>we talked about on today's call should focus on. >>Please send me your comments, but this is what I've >>had in mind. -- Tim >> >>The implementation subgroup is tasked with creating a freely >>available open source implementation of a DCML- based solution >>to the ITIL configuration management problem as described by >>the process subgroup. The first use case implemented will be >>one that incorporates CIM and other data sources. This >>implementation will >>provide: >> >>- a concrete example that furthers people's understanding >> of DCML, how it relates to CIM, and the problems that >> it is meant to solve; >> >>- example code that will encourage vendors to create >> their own implementations; >> >>- a proving ground for changes to our use cases, the >> technical definition of DCML itself, and the relationship >> between DCML and other standards. >> >>The implementation will strive to be of actual use, but more >>important is its educational purpose. As such, we will strive >>to make it very easy to download and get started with (e.g., >>download and run in less than >>5 minutes). >> >>Our deliverables include >> >>- Detailed description of what we will build >> >>- Detailed project plan with milestones and dates >> >>- The software itself >> >>- Documentation and other materials >> >>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]