Portal Domain Standards Taxonomy

Note: I have not covered audio, data and video messaging standards – but could be part of Portal domains

Portal Modules

• JSR 168 (Java Spec Request) for interoperability of portlets across different platforms

• Remote Portlets (WS-RP) - (I believe this is an emerging standard)

• (See need to check auto generation of WSDL from XML and autogeneration of Scheme and screens from Portlets. I recommend you check the Vendors out on this approach and where they are currently going)

Presentation

• XML (Data)

• XSLT (Structure)

• CSS (Design)

• JAVAScript / ECMA (Behaviour)

• AJAX (find out which version vendors may be supporting – I believe this is still emerging standard but we need to keep an eye on it)

Content

• W3C's XML Schema (XML, XSL, XSD)

• ebXML Collaboration Protocol Profile (CPP) references schema for instance data being used in a service or collaboration of services

• WML – (Mobile content XML schema)

• Complex schemas - OASIS - RAD/WAS 6.x (Note this does not support complete range of OASIS schemas – need to check this)

Web services

• WS*I - WS-I Simple SOAP Binding Profile.

• WS-I is an industry consortium formed to promote interoperability among Web services across platforms, applications and programming languages. WS-I profiles define sets of Web services specifications that work together to support specific types of solutions. The profiles are designed to provide developers with mechanisms for building interoperable, attachment-enabled applications. The profiles are currently available for download from the WS-I Web site (www.ws-i.org/ ). ( I recommend you find out which version Vendors are using)

• WSDL (W3C) used to express related schema fragments constrain XML instance data being passed in and out of services

• W3C's XML Schema

• JAXM - Java XML Messaging for asynchronous exchange of XML as opposed o web services.

• Note: JAXM requires SOAP with attachments to work which means it could be excluded from standard)

• Check if the recommended Java standards for exposing interoperable Web services is JAX-RPC, which can be used for Document as well as RPC style Web services

Connectivity protocols

• HTTP/S

• HTML

• JavaScript

• There will be more based on what client needs – recommend you check this.

Registry

• ISO/IEC 11179 Part 3 (ISO standard for metadata registries)

• OASIS ebXML Registry-Repository Technical Specifications

• OASIS UDDI Technical Specification

• UDDI version 2 (supports external UDDI) future moving to v3

Note on UDDI:

• Taxonomy classification is clumsy and its tModel implementation does not fit well with Web service definition language (WSDL)

• The effort to implement a registry function with UDDI is better suited for a proven technology such as a web site of a document management solution.

• The effort to abstract a Web Service location and provide high availability is better handled by a proven technology such as DNS

• There are little or no implementations in the marketplace. Most organisations are using less sophisticated methods of registering and locating their web services….. I recommend checking this further on current maturity with vendors

Workflow/Process management

• BPEL v1.1 (v2 out 2006)

• BPEL 2.0 is a huge step forward from BPEL 1.1. Whereas BPEL 1.1 provided a framework for BPM, BPEL 2.0 is moving towards allowing for the portability of execution of business processes across vendors, and as such, is an important hallmark in the industry.

Frameworks

• J2EE Framework

• .NET Framework

• DotNET

• COBRA

• WSDL (W3C)

• ASP.NET

Security

• Federated ID using Liberty / SAML standard

• Support external access directories RAD NS and LDAP

• Netlogin (Activity Directory and LDAP

• X.509 Digital certificates and OCES Certificates

• Act 404

• (I recommend you check your Industry Standards – North America etc as this is a whole universe on its own…)

#Portal #Standards