[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
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"
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC