ebxml-regrep message

OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: RE: Registry Services Specification v0.4

I am OK with that time.  I will schedule, even if it only to be you and I.
I will send the dialup instructions.

Let me retrieve a list from the listserv, and forward it to you,
highlighting those who actively participate.


-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com]
Sent: Thursday, September 07, 2000 4:04 PM
To: Nieman, Scott
Cc: 'Farrukh Najmi'; ebxml repository
Subject: Re: Registry Services Specification v0.4


I second your thought on a meeting tomorrow. Unfortunately the earliest I am
available is 4pm EDT.
I can stay as late as needed but cannot start earlier. Would 4-5:30pm EDT
for everyone? Does
anyone want to host the conference call? If not I will be glad to.

Lastly, Scott for my benefit could you list the constant (active) members of
the team and their affiliations, so
I can get to know people.



"Nieman, Scott" wrote:

> I do believe it is agressive, but not unreasonable.  I can setup a
> teleconference tomorrow (9/8) afternoon if people would like.  My
> time is 1:30pm -3pm.  Takers?
> Scott
> -----Original Message-----
> From: Farrukh Najmi [mailto:Farrukh.Najmi@East.Sun.COM]
> Sent: Thursday, September 07, 2000 1:39 PM
> To: ebxml repository
> Subject: Registry Services Specification v0.4
> Attached you will find the 0.4 version of the Registry Services
> Specification. major changes include:
> -Query/Retrieval support with place holder for keyword search support
> -All ebXML TRP messages in the spec now have schema definitions in the
> appendix.
>  These (as is the rest of the spec) are to be viewed as a starting point
> for discussions.
> With these changes, we have what I consider to be the essential aspects
> of Registry Services
> needed for Tokyo POC. This brings me to an important point:
> There is a lot of downstream work that needs to happen in POC in time
> for Tokyo to get
> participants to implement Registry Services and clients. This cannot
> begin until we as a team have
> worked through all the issues that need resolution in order to have the
> first working version
> of the Registry Services spec (lets call it 1.0 version). So far I have
> not heard from any of the team
> members on v0.3. I am sure there are good reasons (vacations etc.) but
> this is worrisome.
> I would like to propose the following plan to make regrep a reality for
> Tokyo POC:
> <pleading>
> Please don't consider the plan to be overly prescriptive.
> It only reflects the realities we face.
> </pleading>
> 1. We begin dialog on the 0.4 version of the spec right away by email
> and con call.
> 2. We set a goal that we will have all issue on the table by September
> 15th.
> 3. We set a goal that we will resolve all issues and reach agreement on
> v1.0
>  (working version of the spec) by September 21.
> 4. We set a goal that we will deliver v1.0 for use by POC with final
> changes
>  by COB September 22.
> I realize that this is aggressive. IMHO we need to stick to this
> schedule if
> participants are to have time to implement this functionality.
> To begin progress on item 1. I propose that we hold a conference call
> early next week
> (1.5 hour slot) to have a focused review of v0.4 of the spec.
> I will be glad to host the call (logistics when dates are firmed). Here
> are my
> preferred time slots in which the call could fit. Please let me know
> your prefs:
> -Mon 9/11 Any time between 12pm-4pm EDT
> -Tue 9/12 Any time between 12pm-3:30pm EDT
> --
> Regards,
> Farrukh Najmi

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC