Date and location
The workshop takes place Sunday May 8th, 2011, at Liip in Zurich, Feldstrasse 133.
Some people might arrive on saturday already and if there is interest, we can append a hackday on monday 9th.
Sunday, 8th of May
Start: 10 am. (David will be around from a quarter past 9) We will order some food for lunch and those who want are invited for dinner at 6:30 pm.
- The JCR and PHPCR in practice
- API and compatibility tests for PHPCR
- Implementing PHPCR into your CMS
- Semantic enrichment and VIE with PHPCR
- Challenge the PHPCR API. Is JCR_TO_PHPCR right? Too many changes? Should we do more?
- Discuss the Jackalope transport layer (PHPCR implementations could share most of the implementation code and only differ on backends, encapsulated by the transport layer)
Monday, 9th of May
Start: 10 am. (David will be around from 9)
- doctrine-phpcr-odm, the phpcr database abstraction layer for symfony2
- symfony2 content management framework
Please add yourself to list.
|Henri Bergius||Sunday, Monday||Midgard||Twitter, Github, Blog|
|David Buchmann||Sunday, Monday||Liip AG||Symfony2 CMF, Jackalope, Twitter, Github, Blog|
|Lukas Kahwe Smith||Saturday, Sunday, Monday (or in other words I will be around)||Liip AG||Symfony2 CMF, Jackalope), Twitter, Github, Blog|
|Eero af Heurlin||Sunday, Monday||Midgard||Qaiku, Github|
|Jordi Boggiano||Partly Sat/Sunday, Monday||Nelmio||Twitter, Github, Blog|
|Benjamin Eberlei||Saturday, Sunday|
See also this workshop on Lanyrd
Introduction to Content Repositories
Content Repository is a programming interface for connecting with various persistent data stores. On the Java side, the JCR specification has gained quite a bit of traction, allowing for easy decoupling of a Content Management System from the actual storage implementation. On PHP side there have been several content repositories in use, like Apache CouchDB and Midgard, each with vendor-specific APIs.
The PHPCR effort aims to provide a standard API that can be used by any PHP content management system to interface with any content repository. The first PHPCR implementation is Jackalope, which allows PHP systems to use Apache Jackrabbit as their content store and eventually also will support direct storage. There is also a Midgard PHPCR provider in the works.
As described by David Nuescheler, the advantages of using a standard content repository interface are:
- Functional Definition of a ‚ÄúContent Repository‚ÄĚ
- Common Vocabulary!
- No longer learn (dozens of) (ugly) proprietary APIs
- Write (mostly) portable code, for Document Management, Web Content Management, Source Code Control
- Compare Repository Functionality
- No more information silos and vendor Lock-in Content-Centric Infrastructure
PHPCR has been submitted for inclusion into the JCR specification.
Importance for IKS
As described by the IKS charter:
Interactive Knowledge Stack (IKS) is an open source community, whose projects are focused on building an open and flexible technology platform for semantically enhanced Content Management Systems (CMS).
The PHP Content Repository efforts help to extend the IKS ideas and functionalities to the PHP space, which comprises of some of the most popular CMSs out there. A standard content repository interface for example helps CMS developers to describe their contents in a semantic way using IKS tools like OntoGen. It also helps in deploying interaction tools like VIE into a CMS.
Users of PHPCR
- Original PHPCR hackday announcement
- Liip's workshop announcement with dates
- Bergie's workshop announcement