[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp-wsia] [change request #199] Conformance -> Semantics (#2)
Document: Spec Requested by: Rich Thompson Reasoning: Julie MacNaught & I have been walking through the Conformance statements from a conformance testing perspective. We would suggest that the following are important semantic statements, but are not testable conformance statements. Rather than a large number of change requests, here are the last 13 rewordings that remove the conformance language while keeping the semantics. I have included IDs on each for easy referencing. ID: A Section: 8 Page/Line: 49/34 Old text: A Consumer MAY request a unique configuration of one of these Portlets, either in an opaque manner ... New text: A Consumer can request a unique configuration of one of these Portlets, either in an opaque manner ... ID: B Section: 8.5 Page/Line: 53/7 Old text: Since setPortletProperties() is interacting only with the published portion of the Portlet’s state, it MUST always be safe for the Portlet to modify its state (i.e. equivalent to portletState set to “ readWrite” for a performInteraction() invocation). New text: Since setPortletProperties() is interacting only with the published portion of the Portlet’s state, it is always safe for the Portlet to modify its state (i.e. equivalent to portletState set to “ readWrite” for a performInteraction() invocation). ID: C Section: 8.7 Page/Line: 53/44 Old text: While it is possible the set of properties MAY change with time (e.g. the Portlet dynamically creates or destroys properties), Producers and Portlets SHOULD make the returned modelDescription as complete as possible. New text: While it is possible the set of properties can change with time (e.g. the Portlet dynamically creates or destroys properties), Producers and Portlets SHOULD make the returned modelDescription as complete as possible. ID: D Section: 9.2 Page/Line: 55/3 Old text: The Portlet MAY choose to change behavior based on this value, for example it may generate markup that ... New text: The Portlet can choose to change behavior based on this value, for example it may generate markup that ... ID: E Section: 9.3 Page/Line: 55/7 Old text: A Consumer MAY implement access control mechanisms that restrict which End-Users may access which Portlets and operations on those Portlets. Additionally, a Producer MAY implement access control programmatically through the use of facilities such as an authenticated user identity. New text: A Consumer can implement access control mechanisms that restrict which End-Users may access which Portlets and operations on those Portlets. Additionally, a Producer can implement access control programmatically through the use of facilities such as an authenticated user identity. ID: F Section: 10.1 Page/Line: 55/18 Old text: The Portlet MAY generate markup in the UTF-8 character set encoding if it is unable to generate the requested character set. New text: The Portlet is allowed to generate markup in the UTF-8 character set encoding if it is unable to generate the requested character set. ID: G Section: 10.2 Page/Line: 56/20 Old text: Consumers SHOULD seek to minimize this impact on performance by using efficient encoding and parsing mechanisms New text: Consumers can minimize this impact on performance by using efficient encoding and parsing mechanisms ID: H Section: 10.2 Page/Line: 56/29 Old text: If a Portlet is unable to completely write the portlet URLs for its markup, it MUST set the needsUrlRewriting flag in the returned MarkupResponse structure to “true”. New text: If a Portlet is unable to completely write the portlet URLs for its markup, it sets the requiresUrlRewriting flag in the returned MarkupContext structure to “true”. ID: I Section: 10.2.1.1.4.2 Page/Line: 58/39 Old text: Consumers MAY want to process such resources in a manner that allows caching of the resulting resource by the End-User’s user-agent. New text: Processing such resources in a manner that allows caching of the resulting resource by the End-User’s user-agent can improve performance for the End-User. ID: J Section: 10.2.1.1.4.2 Page/Line: 58/41 Old text: In particular, Consumers MAY process namespace rewriting by using a prefix that is unique to the user/Portlet pair ... New text: In particular, Consumers can process namespace rewriting by using a prefix that is unique to the user/Portlet pair ... ID: K Section: 10.4 Page/Line: 64/5 Old text: So in order to be aggregated, the Portlet MUST ensure its markup conforms to the following general guidelines New text: So in order to be aggregated, the Portlet's markup needs to conform to the following general guidelines Note: This one is a prestatement of a stronger conformance statement from each of the *ML sections. ID: L Section: 11.1 Page/Line: 69/13 Old text: User information MAY be passed to the Producer when a Consumer invokes certain operations. New text: User information can be supplied to the Producer when a Consumer invokes certain operations. ID: M Section: 11.2 Page/Line: 69/17 Old text: If the user identity required by the back-end application is not the same as that authenticated or otherwise supplied by the Consumer, the Portlet MAY request the End-User to provide the necessary information New text: If the user identity required by the back-end application is not the same as that authenticated or otherwise supplied by the Consumer, the Portlet can request the End-User to provide the necessary information
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC