[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: Priorities for Vancouver POC
reply: I strongly disagree. I believe that there are many issues yet to be dealt with that are heavily dependent upon a well designed and specified security model. e.g., We have yet to address the security aspects of "distributed" registry/repository. Security must be specified and worked sooner rather than later. In direct contrast, I believe that Ad Hoc query can easily be added later. Joel -----Original Message----- From: Prasad Yendluri [mailto:pyendluri@webmethods.com] Sent: Thursday, November 30, 2000 2:06 PM To: ebxml-regrep@lists.ebxml.org Subject: Re: Priorities for Vancouver POC Farrukh, IMHO security (authetication or authorization) is a well understood aspect and will easily fall in place anytime. Enriching the "registry" capabilities should be a priority. Hence I would vote for ad hoc query capability Thanks, Prasad Farrukh Najmi wrote: > In today's POC con call today I was asked to gather input from the > Registry team on our priorities for Registry functionality that should > be implemented and shown for Vancouver. The one guideline we must bear > in mind is that any functionality that we suggest for POC must be > speced. > > According to our phased delivery plan developed at Tokyo, we have the > following new functionality planned for our specs for Release 1 > (Vancouver time frame): > > -Registry security (authentication and authorization) > -Ad hoc query capability > > Please share your sense of priorities for what Registry functionality > should be implemented and shown for the Vancouver POC. Please indicate > priority (1 being highre priority than 2). > > -- > Regards, > Farrukh
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC