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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: Re: TRP Work Plan - Version 17 Aug 00




David Burdett wrote:
> I think it should be possible for two parties communicating using the TRP
> spec to achieve COMPLETE interoperability without implementing ANY of the
> Interface spec - i.e. conformance to the wire protocol alone should suffice.
> Do you agree?

My assertion would be that successfully achieving interoperable
implementations of the wire protocol will require semantic knowledge
that is not imparted stricly from the fields in the header themselves
and can benefit from awareness of the Interface. But that's just a
hunch, since we aren't "there" yet. Regardless, the two levels must be
kept in synch for a developer to stand a chance of implementation, as
well as for us to actually get the spec work done. Witness the deltas
that are appearing elsewhere.

-gvh-
begin:vcard 
n:Van Huizen;Gordon
tel;work:510-848-1988
x-mozilla-html:TRUE
url:http://www.sonicmq.com
org:Progress Software;XML and Internet Technology
adr:;;14 Oak Park;Bedford;MA;01730;
version:2.1
email;internet:gvh@progress.com
title:Director, Product Management
fn:Gordon Van Huizen
end:vcard


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Search: Match: Sort by:
Words: | Help


Powered by eList eXpress LLC