Yano, thank you for your kind reply. It is useful to distinguish between adoption -- operational use of the software in production, and agreement, recommendation, approval, etc. of technical designs by engineers. I think we all share a total commitment to standards processes on this list, so, here are my thoughts. There are hundreds or thousands, of approved, issued, final, etc. technical specifications throughout the standards bodies and even more, among commercial consortia, that are dead specifications, i.e. they never achieved operational use in production. MOST of them were a success for their authors: they sold their work, to their employers or clients :-( Drawing on the good reputation of previous, successful standards, these projects cashed in, for themselves but subtracted from the reputation of standards processes, and standards professionals. It is terribly expensive in terms of time and resources, when a standards effort involves so many thousands of people like ebXML. We all need the most clear and precise feedback possible, from manufacturers, distribution companies, services companies, banking and every other sector. Magazines for example, publish some case studies sometimes. But they are so isolated. Even the OAG, which is highly coordinated by a very small team, has the devil of a time figuring out who, or how many, sites are using the stuff. Finally, not all will agree, but I believe in B2B commerce or *any other technology* involving end-to-end communication between unrelated companies, the sign of a mature spec. is when it appears in open source software. Kudos to the open source ebXML regrep. Need to see more like that. In conclusion we need to see more A) reports of companies in production, at least bi-lateral case studies, B) openly-published details of the software and tools they are using, and C) open source versions that work. I suspect, that's what it will take to launch the revolution. Todd At 04:29 AM 10/3/2003, Yano Keisuke wrote: >Dear Todd Boyle, > >Please let me introduce some recent examples of ebXML adoption in Japan. > >1. Just today JEITA EC Center [1] has released the news of the > development of the new B2B e-commerce specification named ECALGA. > This spec adopts ebXML Message Service, CPPA, and BPSS. Its > interoperability test has successfully done among four ebXML > implementations. The spec will be published in December. > This news is available at http://ec.jeita.or.jp/body/ec002.html > written in Japanese. > >2. The ContentsBusinessXML specification uses ebXML BPSS to describe > business processes even though it is a non-normative part of the spec. > This spec defines the XML vocabulary used to get a permission to > distribute copyrighted contents such as movies or animations. > The XML Consortium [2] and the Digital Content Association of Japan [3] > have published the spec as a Recommendation last month. The press > release in Japanese is available at > >http://www.xmlconsortium.org/release/pdf/20030929_contentsBusinessXML.pdf . > The spec is available at the web site of the XML Consortium. > >In addition, this message tells us CPPA adoptions in Japan: > http://lists.oasis-open.org/archives/ebxml-cppa/200310/msg00003.html > >[1] http://ec.jeita.or.jp/ >[2] http://www.xmlconsortium.org/ >[3] http://www.dcaj.org/ > >Regards, > >Yano Keisuke >yano@jp.fujitsu.com
<<attachment: winmail.dat>>