1 / 17

Web Experience Management Interoperability TC

Web Experience Management Interoperability TC. F2F Meeting in April 2012. Photo by Kevin Clausse - http:// flic.kr /p/6M1xa2. Photo by Patricia Drury - http:// flic.kr /p/7V5e3g. Agenda. Hashtag ? # wemi Introduction: Who is who… and why are you here?

ellema
Download Presentation

Web Experience Management Interoperability TC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Experience Management Interoperability TC F2F Meeting in April 2012 Photo by Kevin Clausse - http://flic.kr/p/6M1xa2

  2. Photo by Patricia Drury - http://flic.kr/p/7V5e3g

  3. Agenda • Hashtag? #wemi • Introduction: Who is who… and why are you here? • Discussions with Gartner (Mick) & Forrester (Steven) • Road to WEMI 1.0

  4. Goal of the TC • define a simple domain model for WEM and an abstract feature set to be commonly implemented by WCM/WEM System • It is a goal to explicitly use existing systems as a point of reference but be open towards extensions that may be generally useful • specify a default bindingas a lightweight, resource-oriented, HTTP-based protocol • http://www.oasis-open.org/committees/wemi/charter.php

  5. Use Cases • For the initial set of deliverables, the TC will target a very focused set of use cases: • Display and Mashup Content from a WCM • Index Content and Metadata • Export all Content / Migration • The following use cases are out-of-scope for the initial set of deliverables: • Entitlement and Access Control • Versioning and Records Management • Data Ingestion / Write operations

  6. Roadmap to WEMI V1.0 6

  7. Break Photo by Wilsonious - http://flic.kr/p/dEa9C

  8. From Thomas Lund Sigdestad <tsi@enonic.com>

  9. Use Cases • Display and Mashup Content from a WCM • Sitemap(s) to discover content • Query content e.g. give me all articles from last months • Getting the content a rendition & raw data • Providing a context • Index Content and Metadata • Export all Content / Migration

  10. Terms • Page • Context • Sitemap • Image • Text • Article • User • Content • Layout • Region • Forms • Part • Widget • Reference • Tags • Activity • Folder • Rendition • Template

  11. Simple Model • sitemap – list of pages with optional hierarchy information • has pages • has section(s) • article.json • aside.html • section • ….

  12. Discovery: Resource Catalog • /sitemap.json • entry • type: page, sitemap • url: /iphone/features/ • Last Modified timestamp • /sitemap.html

  13. Discovery: Query • Simple query syntax • q=

  14. Page / Section Structure • %page%.html • fully rendered page/section • %page%.json • LastModified • CreatedDate • key = value • key = value

  15. Context • Pass context from consumer to producer • Store in Cookie? • Do we need to discover context?

  16. Authentication to service • HTTP return codes and authentication

  17. Next • Task List • Teams? • Use Case Collection • Next Call(s)? Next week – Wednesday (5pm) • Task from the meeting • Groups? • Next F2F – June? / September

More Related