wsrp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: WSRP draft .9 comments
- From: Michael Freedman <michael.freedman@oracle.com>
- To: wsrp <wsrp@lists.oasis-open.org>
- Date: Tue, 17 May 2005 15:59:55 -0700
I have made it through section 6.4. Here are my comments so far:
- supportedFeatures in serviceDescription: should we prefix these
with wsrp: thereby allowing non-standard features to referenced [aka
extensions].
- Lifetime in both RegistrationState and RegistrationContext. This
sticks out like a sore thumb. It seems to be there so
ModifyRegistration can continue to return a RegistrationState. I
suggest instead it return a ModifyRegistrationResult that contains both
a RegistrationState and a Lifetime. If we do this should each be
optional and signify that that omission means no changes? Or does the
producer have to explicitly return items because omission means null?
- ClientData Type section. First sentence is: "The MarkupParams structure carries
information concerning the user agent using this type." This seems out
of date. Suggest a better introduction to what the clientdata
structure is about.
- HandleEventsFailed
is inconsistent with our CopyPortlets/Import/ExportsFailed structures.
Should we reconsider and have the structure return the QNames of the
events that failed [and mutliple for any given reason]. Do we really
care to handle the odd situation that the array contains teh same
events twice? We could always tell the Consuemr that if it is bothered
by this to send them in different requests. Another possibility is
that the Event type get a new field to carry a consumer supplied ID
that can be used to reference in the subsequent failed array.
- Section 6.1.23
EventParams Type -- description of portletStateChange: reference that
this impacts processing of an event needs to be updated to reflect that
handleEvents is now a bulk operation. Second sentence seems to have a
misplaced semicolon.
- Can someone
clarify the use case for resource form submission/file upload? Is this
merely because we didn't prohibit it in 1.0? Should we be more
restrictive in our API? Part of my objection is this gives the portlet
a loophole to change state during render but without access to
navigational state updates.
- Section 6.3
Getresource: sentence [line 2253] "This operation is used whenever the
URL activated has ..." would be better as "This operation is used
whenever the activated URL has ..."
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]