RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me you rs.

[Scott Hinkelman <srh@us.ibm.com>]

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074

---------------------- Forwarded by Scott Hinkelman/Austin/IBM on
01/17/2001 04:01 PM ---------------------------
Scott Hinkelman
01/17/2001 03:50 PM

To:   "Nieman, Scott" <Scott.Nieman@NorstanConsulting.com>
cc:
From: Scott Hinkelman/Austin/IBM@IBMUS
Subject:  RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me you
      rs.  (Document link: Scott Hinkelman)

yes of course. my note was prompted mostly by Marty's comment about
standards under development. So, back on track, sorry, and away the
LCS snake pit....

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



"Nieman, Scott" <Scott.Nieman@NorstanConsulting.com> on 01/17/2001 03:40:45
PM

To:   Scott Hinkelman/Austin/IBM@IBMUS, ebXML Repository
      <ebxml-regrep@lists.ebxml.org>
cc:
Subject:  RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me you
      rs.



The security aspects were voted on, and approved by this team.

This does not imply LCS.

Scott

-----Original Message-----
From: Scott Hinkelman [mailto:srh@us.ibm.com]
Sent: Wednesday, January 17, 2001 3:11 PM
To: Nieman, Scott
Cc: Martin W Sachs; 'William J. Kammerer'; ebXML Repository
Subject: RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me
you rs.


So we are back to the Registry LCS (library control system) discussions. If
the Registry is to be an LCS,
then what about checkin, checkout, unlock, verision extraction,
item-dependency per build/promotion, etc?
I still believe the LCS dimention is a secondary *large* issue beyond
public runtime, and many groups
will do LCS functions elsewhere.

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



"Nieman, Scott" <Scott.Nieman@NorstanConsulting.com> on 01/17/2001 02:59:03
PM

To:   Martin W Sachs/Watson/IBM@IBMUS
cc:   "'William J. Kammerer'" <wkammerer@foresightcorp.com>, ebXML
      Repository <ebxml-regrep@lists.ebxml.org>
Subject:  RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me you
      rs.



We can also set up "groups" via the security mechanisms, and access control
policies for each group.

Scott

-----Original Message-----
From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
Sent: Wednesday, January 17, 2001 2:43 PM
To: Nieman, Scott
Cc: 'William J. Kammerer'; ebXML Repository
Subject: RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me
you rs.



Scott's scenario can be accomplished by having a "test" copy of the
registry and repository solely for standards under development and
accessible only by the standards developers.  That avoids the need to
include public/private aspects of the repository information into the
reg/rep specifications.

Regards,
Marty

****************************************************************************


*********

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
****************************************************************************


*********



"Nieman, Scott" <Scott.Nieman@NorstanConsulting.com> on 01/17/2001 01:22:05
PM

To:   "'William J. Kammerer'" <wkammerer@foresightcorp.com>, ebXML
      Repository <ebxml-regrep@lists.ebxml.org>
cc:
Subject:  RE: Re TP EDI Enabled ? Or, I'll show you mine if you show me you
      rs.



>>For what possible reason would I want or need to keep that stuff private?

Consider a scenario in which a standards development organization
implements
an ebXML compliant registry.  That organization would not want the public
to
see the gory details of "work in progress", but only see specifications
that
are approved by the entire organization at large.

Scott

-----Original Message-----
From: William J. Kammerer [mailto:wkammerer@foresightcorp.com]
Sent: Wednesday, January 17, 2001 6:57 AM
To: ebXML Repository
Subject: Re TP EDI Enabled ? Or, I'll show you mine if you show me
yours.


David RR Webber, arguing (I believe) that information placed into the
registry and repository becomes "public domain," asks "What happened to
the public domain requirement?"  Supposedly, "Klaus was adament that UN
legal would advise that all information be treated as such otherwise big
problems follow. Obviously its up to the SO to decide if they want their
info' to be PD by putting in the registry - if not - don't!"

Dear David:

Klaus was undoubtedly referring to the ebXML specifications and
standards, if "public domain" is indeed the correct term at all.  Since
all ebXML materials have a copyright asserted, they are not public
domain.  Instead, they're simply freely available, thus lubricating the
path to universal adoption by removing one possible cost barrier.

Regardless, whether the ebXML standards specifications are "public
domain" or not, freely available or not, the software which vendors
create conformant with those standards is still private property. And
the information stored in repositories may or may not be kept private
depending on the whim of the repository owner and the submitting
organization.

I just happen to feel that there's probably not much trading partner
information that one would place in the registry and repository that
warrants secrecy.  I'll willingly give you my public key, my MSH
address(es), my DUNS number, the EDI transactions or ebXML messages that
I support, and my standard trading partner agreement.  For what possible
reason would I want or need to keep that stuff private?

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Memorial Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"Commerce for a New World"