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: Trading Partner Logical Identification based on EDIFACT or X12qualifiers


you wrote:
> I think we both believe that a repository interface can be useful but its
> use should not be mandatory.

Completely agree.

> However if ebXML were to define a programmatic API to the repository and
> make it a mandatory part of the ebXML-defined repository, that would
> benefit software providers by assuring that the same software
> could be used
> with all repository implementations.

To build a regrep interface that meets the above assertion that "the same
software could be used with all repository implementations.", the RegRep
team should consider doing the following:
- define the list of regrep functions/methods using an Interface Definition
Language (such as that defined with CORBA)
- describe each function/method [in]/[out] parameter in detail
- define a complete set of error messages
- describe the wire-protocol used for function/method invocation and return
results (or refer to an existing standard)
  - define the various transport level bindings for HTTP, FTP, SMTP
- provide a granular level of security so that access to functions/methods
can be controlled
- permit the use of encryption and digital signatures on [in]/[out]

If the above items were presented as part of a regrep interface then I would
agree with the earlier assertion.

Dick Brooks
Group 8760
110 12th Street North
Birmingham, AL 35203
Fax: 205-250-8057

InsideAgent - Empowering e-commerce solutions

[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