[wsrp-wsia] WSRP conf call on JSR168-WSRP aligment

[Alejandro Abdelnur <alejandro.abdelnur@sun.com>]

Dear WSRP TC and JSR168 EG,

*This email is being sent to the WSRP TC and JSR168 EG aliases*

Following is a brief summary of today's WSRP conference call on
WSRP-JSR168 alignment.

Please let me know of any corrections on this.

For the open issues, we'll open an WSRP issue. WSRP will prioritize
discussion on these issues.

Regards.

Alejandro

JSR168-WSRP issue list

1------------------------------------------------------------------
Action definition differs between JSR168 and WSRP.

OPEN, waiting on WSRP.
WSRP TC has to further discuss what is their definition of action.

2------------------------------------------------------------------
JSR168 allows setting properties not defined in the portlet
definition.

OPEN, shouldn't be an issue.

Coming Wed WSRP will discuss this topic, JSR168 EG members are
welcome to participate.

    Conf call info:
      Wed Oct 23
      9:00 AM (CA Time)
      phone    +1 877.299.7551
      passcode 2696#

3------------------------------------------------------------------
JSR168 property types String/String[], WSRP allows <any>

CLOSED. Non-issue.

4------------------------------------------------------------------
JSR168 properties definition includes non-modifiable flag.

OPEN, waiting on JSR168 resolution on this. WSRP has asked for a
use case where this info is required by the consumer.

5------------------------------------------------------------------
JSR168 does not defined property medatadata

CLOSED. Non-issue.

6------------------------------------------------------------------
JSR168 defines the concept of windowID.

OPEN, waiting on WSRP. WSRP has to discuss the introduction of the
consumer managed refHandle.

SIDE NOTE: vendors planning to provide JSR168-WSRP products would
have to agree on set of common WSRP extensions for JSR168 support
to ensure interoperability if WSRP spec does not provide support
for some JSR168 required functionality.

7------------------------------------------------------------------
JSR168 wants CCS styles prefix to be more generic, portlet- or
fragment-.

OPEN, shouldn't be an issue. Taken offline, if better name is not
found we would fallback to portlet-

8------------------------------------------------------------------
JSR168 extensions are string name-value pairs. WSRP allows <any>

OPEN, waiting on WSRP decision on how extensions will be expressed
as there is some debate on that.

9------------------------------------------------------------------
JSR168 needs list of valid portlet-modes and window-states in the
performInteraction and getMarkup calls.

OPEN, needs more discussion in the WSRP side.

10-----------------------------------------------------------------
JSR168 defines a simple expiration cache mechanism.

OPEN, waiting on WSRP caching model to see if can be adopted.

11-----------------------------------------------------------------
JSR168 can not model the WSRP entity creation using copy-on-write
without exposing it to the portlet.

OPEN, waiting on WSRP as this mechanism is being debated and there
is a new proposal.

12-----------------------------------------------------------------
JSR168 windowState and portletMode constants are the same.

OPEN, low priority. waiting on WSRP to consider new names.

13-----------------------------------------------------------------
JSR168 localization support for portlet definition information.

CLOSED. JSR168 will provide localization through the xml:lang
attribute. This could be mapped to the WSRP metadata offered by
the JSR168 producer.

14-----------------------------------------------------------------
JSR168 user-info are String name-value pairs, WSRP defines
structured data.

CLOSED. JSR168 producer can convert the user-info to name-value
pairs. JSR168 EG will consider making a recommendation on user-info
attribute names in the portlet spec.

15-----------------------------------------------------------------
JSR168 allows portlets to access uploaded data from the
performInteraction and getMarkup methods. WSRP only from the first
one.

OPEN, this requires more discussion on WSRP.

16-----------------------------------------------------------------
JSR 168 portlet definition defines valid modes per markupType.

OPEN, waiting on WSRP. WSRP has to evaluate what information should
be per markupType.

-------------------------------------------------------------------