New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Web Experience Management Interoperability (WEMI) and DotNetNuke


Last week I travelled to Copenhagen, Denmark to participate in the kick-off meeting for the Web Experience Management Interoperability (WEMI) technical committee (TC) which was recently formed by OASIS ( Organization for the Advancement of Structured Information Standards). OASIS is widely respected as a leading web standards consortium which drives the development, convergence and adoption of open standards for the global information society. OASIS is also the home of CMIS, a Content Management Interoperability Services standard that originated in 2009, which in fact served as the catalyst for the new WEMI initiative.

Where CMIS is focused on an open standard that defines an abstraction layer for controlling diverse document management systems and repositories using web protocols, WEMI is more focused on the exchange of unstructured content between web publishing systems. The name “Web Experience Management” was chosen purposely so that the standard is applicable to the broadest audience possible and is not specific to a specific web publishing system architecture, as this initiative is intended to be applicable to Content Management Systems (CMS), Web Content Management (WCM), Web Engagement Management (WEM), Portals, Site Builders, and many others. The founding members of the WEMI TC include many of the world’s leading authorities on web publishing including Magnolia, Acquia (Drupal), Hippo, Sitecore, SDL, Liferay, TYPO3, Jahia, TerminalFour, Adobe, Telerik, Enonic, GX Software, and of course, DotNetNuke.

The kick-off meeting occurred on April 3rd and was graciously hosted by Sitecore, which was one of the determining factors for the venue being located in Copenhagen ( Sitecore is based in Denmark ) - the other factor being the fact that 11 out of the 14 organizations represented are based in Europe. From a business model perspective, the TC is comprised of both traditional proprietary software vendors, as well as organizations acting as stewards of large open source projects. And from a technology perspective, 3 systems were based on .NET, 2 systems was based on PHP, and 9 systems were based on Java technology. The delegates sent by each organization generally had a strong technology background ( ie. CTO or Chief Architect ), some had experience in defining other web standards in the past, and some were even members of the CMIS initiative.

In its charter, WEMI has three general goals which were utilized to help guide the discussion:

  • define a simple domain model and an abstract feature set to be commonly implemented by participating systems
  • explicitly use existing systems as a point of reference but also be open to extensions that may be generally useful
  • specify a default binding as a lightweight, resource-oriented, HTTP-based protocol

These goals were manifested in a very focused set of use cases:

  • Display and Mashup Content from a WCM
  • Index Content and Metadata
  • Export all Content / Migration

And the charter also provided guidance which was intended to prevent dreaded scope creep. It accomplished this by spelling out the use cases which are considered to be out of scope for the initial set of deliverables:

  • Entitlement and Access Control
  • Versioning and Records Management
  • Data Ingestion / Write operations

Depending on their specific needs, organizations seemed to favor some of the use cases more than others, but the thing which I found especially encouraging was that there appeared to be immediate consensus that all members were facing the same content challenges and were willing to collaborate to create a common framework for solving the problem. This made the initial meeting very productive in terms of keeping the discussion focused and moving in the same direction.

Another item which was encouraging was the fact that nobody in the group seemed to be afflicted with the Not-Invented-Here (NIH) syndrome – meaning everyone was fairly open to utilizing existing standard and protocols where they make sense. A case in point was a preference to utilize the work done in the W3C HTML5 specification for helping us define the domain model. Another observation I made during the discussions was that there appeared to be an opportunity of utilizing existing light-weight data protocols such as the Open Data Protocol (OData) or Google’s Data Protocol (GData) for inspiration and guidance.

Overall I thought that the trip was productive but exhausting. Between flights, airport layovers, train connections, and navigating the streets of Copenhagen, it took me almost 24 hours to travel from my home in Vancouver to my hotel in Copenhagen. Coupled with a 9 hour time zone differential, I was surprised but relieved to avoid any jet lag symptoms on the day of the actual meeting. And as is usually the case with these types of events, I found the conversations with the other members outside of the WEMI meeting to be equally as stimulating and valuable, as the meeting itself. 


There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out