Open Source and Open Standards Perspective from Fujitsu

  • Slides: 7
Download presentation
Open Source and Open Standards Perspective from Fujitsu • Mostly known in US and

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 1 All Rights Reserved, Copyright © FUJITSU LIMITED 2004

Open Standard and e. Business/e. Gov • OASIS, W 3 C, IETF, CEFACT, WS-I…

Open Standard and e. Business/e. Gov • OASIS, W 3 C, 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. 2 All Rights Reserved, Copyright © FUJITSU LIMITED 2004

Web Services / e. Business Technology Specifications Overview (Dec 2004) eb. XML Content UBL

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

Fujitsu related contribution Content OASIS System Resource mgmnt. WS-RF WS-DM WSRF TC Co-Chair Flow

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

Open Source and Open Standards Clear Synergy: • Open Standards rely on Open Source

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: RM 4 GS (reliable messaging for Grids) • Hermes (OSS eb. XML) 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 (open 3. org). • In both cases, we want: • control by a community of users / ISV companies • licensing favorable to OEM as well as end-user 5 All Rights Reserved, Copyright © FUJITSU LIMITED 2004

Open Source vs Open Standards • The Essence of Open Source is in its

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) orgowned 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) 6 All Rights Reserved, Copyright © FUJITSU LIMITED 2004

7 All Rights Reserved, Copyright © FUJITSU LIMITED 2004

7 All Rights Reserved, Copyright © FUJITSU LIMITED 2004