[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: TPA & ebXML; more thoughts
Chris,
I agree with you on the no-dependancy. "Sendinding/execution" of an ebXML
message should not depend on regrep.
In general, I believe we should have as loosely coupled ebXML parts as
possible, but it does need to hang together.
I will hold my opinion in URNs for now, but I think we agree some sort of
context is needed. Much of this issue on
identification must be agreed upon in CC/BP/RegRep.
TPA Status plays well to TPA Change, and how to indicate it to involved
engines. As I think we would agree,
this is ebXML-environment characteristic that technically a TRP impl should
not depend on, but is needed
to make it work from a system level.
Thanks,
Scott Hinkelman
Senior Software Engineer, SWG IBM Austin
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074
Christopher Ferris <chris.ferris@east.sun.com>@lists.oasis-open.org on
07/06/2000 04:36:12 PM
Sent by: owner-ebxml-transport@lists.oasis-open.org
To: ebXML-Transport@lists.oasis-open.org
cc:
Subject: Re: TPA & ebXML; more thoughts
It would seem to me that there should be no requirement for
a regrep in the context of sending ebXML messages governed
by a TPA. I could see the regrep as being used to "advertise"
or provide a discovery capability for established templates,
however, you could simply place a TPA document on the filesystem
with equal effect.
If you are considering context in the same manner as we have been
discussing other identifiers (address for instance) which might
refer to the naming scheme used to craft the ID, then I guess
I agree. I still think that this is all unnecessary if we simply
chose to adopt use of URNs which carry their own context.
I do like the idea of the "dry run" capablity. RosettaNet has
this, and it seems to me to be quite a necessity. However, the
caching and purging seem to be getting into areas which would
traditionally be implementation specific performance optimizations.
Maybe what's really missing here is the notion of the status of
a TPA:
- development (discovery?)
- system test
- production
Maybe this opens the floodgates of the discovery discussion which
has been lurking in the dark recesses of eachother's minds!
Chris
srh@us.ibm.com wrote:
>
> Some more thoughts:
> Eventually we need to think about the end to end sequence within the
ebXML
> environment, meaning, when does the
> RegRep get accessed for such configuration information, etc. Thinking of
> the TPA as a configuration file,
> requires identification (TPAid) but further requires context (not to go
> into this here as CC/BP are currently wrestling this concept).
> So, I suggest we think TPAidContext and TPAid.
>
> Performance and Configuration Changes leads to thoughts toward
> a TRP implementation should be able to cache a Config file (TPA)
document
> as a configuration for a process between specific
> partners. We could consider some sort of "dry-run" capability of a
business
> process where it would give the TRP engines
> the opportunity to insure they are ready with the correct configuration
by
> TPAidContext and TPAid.
> They could remain "ready" (have cached
> the config file if needed, alocated system resources if needed, etc) for
a
> given period, and could expose TRP-level
> common query interfaces (more thoughts here abound) to obtain the
> ready-timeout period, etc. This leads to
> thinking about the ability to force a cache purge during the dry run for
> cases where the config file has changed.
>
> etc etc.
>
> Scott Hinkelman
> Senior Software Engineer, SWG IBM Austin
> 512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
> srh@us.ibm.com, Fax: 512-838-1074
>
> "Sohaib.J.Kidwai" <sohaibk@ecomxml.com>@lists.oasis-open.org on
07/06/2000
> 01:33:59 PM
>
> Sent by: owner-ebxml-transport@lists.oasis-open.org
>
> To: John Ibbotson/UK/IBM@IBMGB, <ebXML-Transport@lists.oasis-open.org>
> cc:
> Subject: TPA & ebXML
>
> Hello John,
>
> Thanks for this document. Just to add a comment, the negotiation of a
> Trading Partner Agreement itself can be done using the ebXML framework. A
> tpaML document could be exchanged (possibly several times) between two
> trading partners over the ebXML framework until the trading partners have
> come to an agreement over its final form. The final tpaML document could
> then be used to provide configuration information as you mentioned in
your
> email, for all future ebXML exchanges. Although this brings us to a
chicken
> and egg problem of, how the first exchange was possible without a trading
> partner agreement!
> Just some thoughts.
>
> Regards,
> Sohaib.J.Kidwai
> Architect
> EComXML Inc.
> Reply To: sohaibk@ecomxml.com
> Phone: (215)321-5569 (x104)
> Fax: (215) 321-1172
> http://www.ecomxml.com
>
> -----Original Message-----
> From: owner-ebxml-transport@lists.oasis-open.org
> [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of
> john_ibbotson@uk.ibm.com
> Sent: Thursday, July 06, 2000 11:23 AM
> To: ebXML-Transport@lists.oasis-open.org
> Subject: TPA - Initial thoughts
>
> As discussed on the conference call, here is the initial draft document
on
> Trading Partner Agreements
> (See attached file: ebXML TRP and TPAs.doc)
> John
>
> MQSeries Technical Strategy & Planning,
> IBM UK Ltd, Hursley Park,
> Winchester, SO21 2JN
>
> Tel: +44 (0)1962 815188
> Fax: +44 (0)1962 816898
> Notes Id: John Ibbotson/UK/IBM
> email: john_ibbotson@uk.ibm.com
>
> =======================================================================
> = This is ebxml-transport, the general mailing list for the ebXML =
> = Transport project team. The owner of this list is =
> = owner-ebxml-transport@oasis-open.org =
> = =
> = To unsubscribe, send mail to majordomo@lists.oasis-open.org with =
> = the following in the body of the message: =
> = unsubscribe ebxml-transport =
> = If you are subscribed using a different email address, put the =
> = address you subscribed with at the end of the line; e.g. =
> = unsubscribe ebxml-transport myname@company.com =
> =======================================================================
>
> =======================================================================
> = This is ebxml-transport, the general mailing list for the ebXML =
> = Transport project team. The owner of this list is =
> = owner-ebxml-transport@oasis-open.org =
> = =
> = To unsubscribe, send mail to majordomo@lists.oasis-open.org with =
> = the following in the body of the message: =
> = unsubscribe ebxml-transport =
> = If you are subscribed using a different email address, put the =
> = address you subscribed with at the end of the line; e.g. =
> = unsubscribe ebxml-transport myname@company.com =
> =======================================================================
--
_/_/_/_/ _/ _/ _/ _/ Christopher Ferris - Enterprise Architect
_/ _/ _/ _/_/ _/ Phone: 781-442-3063 or x23063
_/_/_/_/ _/ _/ _/ _/ _/ Email: chris.ferris@East.Sun.COM
_/ _/ _/ _/ _/_/ Sun Microsystems, Mailstop: UBUR03-313
_/_/_/_/ _/_/_/ _/ _/ 1 Network Drive Burlington, MA 01803-0903
=======================================================================
= This is ebxml-transport, the general mailing list for the ebXML =
= Transport project team. The owner of this list is =
= owner-ebxml-transport@oasis-open.org =
= =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org with =
= the following in the body of the message: =
= unsubscribe ebxml-transport =
= If you are subscribed using a different email address, put the =
= address you subscribed with at the end of the line; e.g. =
= unsubscribe ebxml-transport myname@company.com =
=======================================================================
=======================================================================
= This is ebxml-transport, the general mailing list for the ebXML =
= Transport project team. The owner of this list is =
= owner-ebxml-transport@oasis-open.org =
= =
= To unsubscribe, send mail to majordomo@lists.oasis-open.org with =
= the following in the body of the message: =
= unsubscribe ebxml-transport =
= If you are subscribed using a different email address, put the =
= address you subscribed with at the end of the line; e.g. =
= unsubscribe ebxml-transport myname@company.com =
=======================================================================
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC