Re: Priorities: POC and RS Specification

["Munter, Joel D" <joel.d.munter@intel.com>]

Hi Scott,

On 13 Nov you offered to (within a few days): to summarize the Tokyo meeting
activities, to clearly identify the decisions made, any actions taken, and
to publish on this list service.  I have not seen that documentation yet.
Have you completed this?  

Please let those who were not in Tokyo have a full, complete, and unbiased
report of what transpired with respect to the Registry and Repository Team
at the Tokyo meetings. I have been asked by others in my travels and cannot
answer with any accuracy.

Sincerely,
Joel Munter


-----Original Message-----
From: Nieman, Scott [mailto:Scott.Nieman@NorstanConsulting.com]
Sent: Monday, November 20, 2000 7:36 AM
To: 'ebxml-regrep@lists.ebxml.org '; 'Krishna Sankar '
Subject: Priorities: POC and RS Specification


I believe that we need to prioritize in this order
1) ad-hoc query
2) authentication
3) pub-sub (if time permits; since this is in the v2 bucket)

I would like each of these services proposals written out as if they were
chapters in the Registry Services specification.  Perhaps we need an Outline
in the RS spec and put in placeholders until the chapters are approved.

Also, I strongly believe that this document have appendices that cover the
business use cases (how a SO is registered, how a classification scheme is
added, how to associate a Managed Object to a classification, etc.) so that
people picking up the specification understand there are some real life
applications that these services can support.

Scott 

-----Original Message-----
From: Krishna Sankar
To: Munter, Joel D; ebXML-poc@lists.ebxml.org
Cc: ebxml-regrep@lists.ebxml.org
Sent: 11/17/00 2:03 PM
Subject: RE: upcoming POC work?

Hi,

	In Tokyo, the regrep team has prioritized the capabilities into
various
buckets. Ad Hoc Query is in Phase 1 scope and so we will show Ad Hoc
query
in Vancouver. From what I know, the pub-sub is not in Phase 1 and so
will
not be in Vancouver.

	cheers

	Scott/Farrukh, can we get that prioritized list of features ?

-----Original Message-----
From: Munter, Joel D [mailto:joel.d.munter@intel.com]
Sent: Friday, November 17, 2000 8:26 AM
To: ebXML-poc@lists.ebxml.org
Subject: RE: upcoming POC work?


Mark,

Based on Reg/Rep team discussions in Tokyo, should we also assume that
the
following will be targeted for POC in Vancouver?
	Reg/Rep - Ad Hoc query
	Reg/Rep - Publish and Subscribe
Thanks,
Joel Munter

-----Original Message-----
From: Mark A. Hale [mailto:mark.hale@interwoven.com]
Sent: Thursday, November 16, 2000 10:27 AM
To: hdain@ectone.com; ebXML-poc@lists.ebxml.org
Subject: RE: upcoming POC work?


Dain,

Thank you for the interest and welcome.  At this time, the POC is
collecting
topics for the Vancouver demonstration.  The discussions to date
included
things such as:

	Security
	Reliable Messaging
	Business Processes/Core Components
	International Trading
	Marketplaces
	Multiple Transports

We hope to have a list by the first week of December so we can begin to
narrow down the list.  Please feel free to add topics (by posting to
this
list) that are representative of new specification functionality.

	Thanks,

	Mark


________________________________________________________________________
Mark A. Hale                                            408-220-7483 tel
Standards Architect                                     408-774-2002 fax
Interwoven                                     mark.hale@intwerwoven.com
1195 W. Fremont Avenue                         http://www.interwoven.com
Sunnyvale, CA  94087



> -----Original Message-----
> From: Hansen Dain [mailto:hdain@ectone.com]
> Sent: Wednesday, November 15, 2000 12:46 PM
> To: ebXML-poc@lists.ebxml.org
> Subject: RE: upcoming POC work?
>
>
> What remaining POC work is there to be completed? Our company
> would like to
> sign up to help out for any upcoming work. I would like to be in on a
> conference call if there is one scheduled. Please let me know the
details,
> since I am new to this. Thanks,
>
> -Dain
>
> Dain Hansen
> ECtone
> dhansen@ectone.com
>
>
>