1. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 1 Open Source and Open Standards Perspective from Fujitsu Mostly known in US and EU as computer maker … But a large software vendor in Japan In any case, NOT a photo film company … Jacques Durand Director of Standards and Engineering Fujitsu Software San Jose, California

2. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 2 Open Standard and eBusiness/eGov OASIS, W3C, IETF, CEFACT, WS-I … Necessary for defining an Interoperable Infrastructure. We enter a phase of supply chains integrations Critical for software companies like Fujitsu that target a global market BUT there is a dark side: Open technical forums or rubber-stamping bodies ? IPR and legal issues: late or no IP disclosure, stealth IP, too many patents, licensing with strings Monopolies don t need standards, unless they make them.

3. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 3 Messaging/Event Basic Protocol Registry Security Web Services / eBusiness Technology Specifications Overview (Dec 2004) Transaction WS-CAF WS-Transaction Content UBL Flow WSCI System Resource Mgmnt. UDDI WS-Inspection SOAP IIOP HTTP HTTPS WSDL JMS SWA DIME WS-RM WS-Addressing WS-Reliability WS-MD WS-Event WS-Routing WS-Notification HTTPR Negotiation/Policy WS-Policy WS-PolicyAttachement WS-PolicyAssertions Liberty WS-Trust WS-SecurityConversation WS-Federation WS-SecurityPocily WS-Authorization WS-Privacy Standard Standardizing Published only Non-Published ebXML MS ebXML RR ebXML CPPA ebXML BPSS ebXML CC ebXML BP AP SSB BP AP SSB BSP WS-RF WSPL MIME WS-I BTP BPEL4WS WS-DM WS-Security Royalty Free Licensing in progress

4. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 4 Fujitsu related contribution Transaction Content Flow System Resource mgmnt. Registry Basic Protocol Messaging/Event Negotiation/Policy Security UDDI WS-Reliability WS-RF WS-CAF WS-Notification ebXML MS WSRF TC Co-Chair WSRM TC Chair Proposing an initial Spec WSRM TC Chair Proposing an initial Spec ebXML IIC TC Chair OASIS JCPOMG JMS IIOP BP AP SSB BP AP SSB BSP UDDI Founding Member* ebXML Asia Committee WS-I Board Member Mike DeNicola* Technical Advisory Board Member Jacque Durand* J2EE/SE EC Member * Board Member Architectural Board Member Board Member * Liaison Committee Chair Japan SIG Facilitator Former Test Tool WG Chair Interoperability Task Group Co-Chair Succeeded Interoperability test among 19 Asian organizations DOPG Founding Member Spokesman Web Services Core Technology Sub WG Chair WS-Security BTP BPEL4WS WS-DM *Only one member from Asia

5. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 5 Open Source and Open Standards Clear Synergy: Open Standards rely on Open Source implementations for marketing and to help adopters jump-start their development Fujitsu/NEC/Hitachi: RM4GS (reliable messaging for Grids) Hermes (OSS ebXML) is customized by large users (CDC) Open Source wants to rely on Open Standard for broader acceptance, and non-encumbered IP. open source did not penetrate the EAI space until related standards emerged (XML, JCA) to build on (open3.org). In both cases, we want: control by a community of users / ISV companies licensing favorable to OEM as well as end-user

6. All Rights Reserved, Copyright © FUJITSU LIMITED 2004 6 Open Source vs Open Standards The Essence of Open Source is in its Licensing which gives some added freedom to evolve/use the code. Similar as Open Standards? Not really, due to software specifics. But same principle: involving the user community guarantees the best evolution path for the technology. From the OEM (or ISV) perspective (as opposed to end-user) org- owned IP is best for Standards as well as for Open Source : Ironically, licenses that are too open (BSD) are risky for OEMs, lead to unstable codebase (proprietary forks) FSF style licenses (GPL, LGPL) protect IP, are increasingly preferred (Linux, Jboss)