Hippo

Hippo actively involved in specification of open standards

Because of the major impact of Open Standards in Content Management & Portal Technology, Hippo is actively involved in the specification of several Java Specification Request (JSR) standards.

The JSR standards are specified through the industry and community wide supported Java Community Process standardization group (JCP).

A new JSR standard is specified within the JCP by an Expert Group (EG) consisting of key software providers and open source community members. A new JSR can only be accepted as official standard by the JCR Executive committee after one or more public reviews. Besides the specification itself, a JSR also provides a Java Application Programming Interface (API), a reference implementation (including the source) and a Technology Compatibility Kit (TCK) which can be used to test and validate custom implementations for compliance to the specification.

Hippo is involved as Expert Group Member for the specification of the following JSR Standards in progress:

  • JSR 283: Content Repository for Java(TM) Technology API Version 2.0.
    The goal for version 2.0 of the Content Repository API specification is further expansion of the current JSR 170 standard, in particular in the field of of management, additional standard content types, search protocols, version management, etc.
  • JSR 286: Portlet Specification 2.0. The goal for version 2.0 of the Portlet Specification is further expansion of the current JSR 168 standard, better support for common web development standards like Java(TM) Servlet, JavaServer(TM) Page (JSP) and JavaServer(TM) Faces (JSF), as well as alignment with Java(TM) Enterprise Edition 1.4 and Web Services for Remote Portlet 2.0 (WSRP 2.0).
  • JSR 301: Portlet Bridge Specification for JavaServer(TM) Faces. This specification will define the semantics of a JSR 168/JSR 286 portlet for accessing JSF based applications within a Portal.

Furthermore, Hippo is implementing and providing the following official JSR standards in the Hippo Portal and Hippo CMS products:

  • JSR 168: Portlet Specification 1.0. This specification enables interoperability between Portlets and Portals. A JSR 168 Portlet compliant to JSR 168 can be used in any JSR 168 compliant Portal. For this purpose, the specification defines a set of APIs to support aggregation, personalization, presentation and security.
    JSR 168 was accepted as standard in October 2003.
  • JSR 170: Content Repository for Java(TM) technology API. This specification provides a standard API to access content repositories in Java(TM) 2, independently of implementation. JSR 170 was accepted as standard in June 2005.