[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-comment] XML as returning type of getMarkup()
Hi Timo,
The WSIA/WSRP committees have focused most of their attention on
"plug-and-play" visual portlets that return markup which is readily embeddable
into a page. In most cases, that means HTML markup, although other markup types
are also possible.
The committees have not spent time discussing a scenario in which the
returned markup needs to be transformed in a portlet-specific way (as this would
not enable true plug-and-play). It is likely that it is possible to implement
such a scenario using a WSIA/WSRP portlet architecture one way or another.
However, when the Producer of the service returns plain data (i.e., XML), it is
unclear whether one should be using a portlet architecture or just use a plain
remote XML Web service - similar to the way one would bring data from an
external data source. The portlet architecture would likely not add much value
in such a case.
To use visual interactive WSIA/WSRP services that are customizable via an
internal XML/XSL architecture, one may propose an architecture that
stores the XSL document as part of the Consumer-specific configuration
information on the portlet end (more specifically, as part of the Entity, and
even more specifically, as a Property). With such an architecture, the
portlet would still be returning HTML markup to the Consumer, but it would allow
the Consumer (and potentially the user) to have finer control over the
presentation. However, WSIA and WSRP do not standardize the way in which such
architectures are created, so that (for example) the scheme of the underlying
document would need to be published in a completely custom way (e.g., as part of
the description), etc.
Hope that helps - please consider this a personal view of the
specification, other members may have different viewpoints,
Eilon
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC