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

Message text written by INTERNET:dick@8760.com
In this case I believe it is each implementers CHOICE as to HOW their
Trading Partner
information is provided. Some may consider this information sensitive and
will want to tightly control distribution/access.

ebXML should recommend a solution to make the information available
programmatically but it should be implementers choice as to whether or not
to deploy.

Have we reached agreement?


Yes - that's not a problem.  You should always have the option to
control access.  The RegRep side can obviously design in a complete
range of such, and I'm sure individual vendors will build and market

Basically you have everything between a 'transponder beacon' thru 
to a 'bank vault' model!

I've sent out another email wanting to step next to exactly what is it
we should be potentially looking up in any case!   I think that will
significantly help narrow down issues.

Thanks, DW.

[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