[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [regrep] Core Components and version 3
Message text written by Chiusano Joseph > We absoltely do not meet most CCTS requirements in V3 already, in the manner in which the CCTS team would like us to meet them (that is, explicitly in the information model). < >>>> Joe, We definately need to get this quantified. At the risk of sounding like a broken record - we've been down this path before. The original CCTS requirements read like a NASA space mission. I spent days in Tokyo going over what the CCTS team thought their mission profile looked like - and theoretically how the RIM can support rich information querying. When you distill this down into real business requirements - around what an end user needs to support them building and using re-usable content structures - and discovering such existing components - you have a much more attainable set of deliverables. Yes it would be nice to be able to answer a query for "lefthanded mesoean indian artifacts from the 4th dynasty with applicability to production of culinary dishes containing aromatic spices for gout sufferers". Frankly however I'd rather build a V4.0 around what 95% of business users need to architect a simple cost effective solution. I don't want to prejudge what that list is - since I'd rather re-visit this with a clean slate based around the latest specification. Attaining that list is critical to setting the scope and purpose of the V4 requirements. Then we can deliver sensible specifications that vendors can implement quickly and affordably. Notice we achieved that with our V3.0 spec's and that is a critical success factor. End users want registry technology that is broadly affordable. Thanks, DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC