wsrp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [wsrp] v17 comment
- From: Rich Thompson <richt2@us.ibm.com>
- To: wsrp <wsrp@lists.oasis-open.org>
- Date: Wed, 31 May 2006 07:31:45 -0400
I think the placement is simply a question
of whether the additional sentences are describing the use of the field
or of the structure. We have no single guiding principle, but have usually
kept discussion specific to a field within the field description.
Rich
Michael Freedman <michael.freedman@oracle.com>
05/30/06 08:00 PM
|
To
| wsrp <wsrp@lists.oasis-open.org>
|
cc
|
|
Subject
| [wsrp] v17 comment |
|
Section 6.1.12:
publicValues: The Portlet can declare a portion of its navigational state
to the Consumer for the purpose of coordination with other components the
Consumer is aggregating. This declared portion of the Portlet's navigational
state is stored and managed by the Consumer in a manner equivalent to the
opaque portion and carried to the Portlet in this field on all relevant
invocations [A502]
[A503]
[C404].
The Portlet also returns the current values for the publicly exposed portion
of its navigational state using this field. [C405].
Why isn't the description merely: The portion of the Portlet's navigational
state which is exposed to the consumer for coordination with other components
in the Consumers scope. The rest of the description if needed
should be moved into the explanatory paragraph that is below the field
descriptions.
-Mike-
- References:
- v17 comment
- From: Michael Freedman <michael.freedman@oracle.com>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]