I wonder if we can separate the channel discussion from the mapping between iCalendar and jBPM (inparticular TaskInstance). First for read and then for create / update...the semantics should be the same irrespective of channel (e-mail, HTTP, RSS, etc). First mapping iCalendar properties to jBPM. I chose to map to VTODO (tasklist). The mapping of many properties is fairly obvious. As noted in my orginal post a few properties don't have obvious mappings: DTSTART (scheduled start date) LOCATION / GEO (location of task) PERCENT (percent complete) CATEGORIES (could map to task name?) CLASS (privacy) RESOURCES (I mapped actors to attendees) STATUS (e.g. assigned, accepted, declined, etc) So one obvious question is whether any of the above have equivalents in jBPM or do they point to extensions for jBPM? From Tom's earlier response it sounds like assignment state will be supported in 4. As a matter of interest what have you intended for the task management module now shown in the jBPM 'architecture' graphic? In looking at it the other way round (i.e. what can't be mapped from jBPM) the obvious question is how to deal with task specific variables? Are there any others? I can see three possibilities for task specific variables, an ATTACH (atttachment), embed them in the DESCRIPTION (currently only plain text) or 'X-' properties. Of course the question is how would a calendar user agent handle these? DESCRIPTION is fine for read only, but if we want to update? I was wondering with a XUL based UI such as Lightning / Sunbird if one could create task specific UIs that extend the basic calendar agent functionality... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138406#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...