[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsrp-wsia] Change requests for TC Call, Thursday, March 6th
There was a request that we try and walk through these requests in section order in order to reduce the context switching necessary. These have been so ordered with some commentary about the nature of the change request as well. I expect to walk through the change requests in this order: Small editorial/grammar changes (I do not expect to walk through these unless there are objections): 202 – Provide reference to the schema datatype definitions Section 5.1.15 / Page 24 / Line 6 / Andre Kramer 203 – Wording for resend cached data Section 6.1.1 / Page 26 / Line 36 / Andre Kramer States preference for the wording from initCookie() fault processing 211 – NamespacePrefix is now a separate field Section 5.1.11 / Page 20 / Line 44 / Rich Thompson Reference to the additional field is now needed in this conformance statement 212 – markupCharacterSet is now an array Section 6.1.9 / Page 30 / Line 30 / Rich Thompson Grammar didn't get updated when the field became an array. 217 – Update section reference Section 6.4 / Page 41 / Line 18 / Rich Thompson Current reference is wrong as things have moved around 219 – Producer invalidation of registrationHandles Section 7.2 / Page 48 / Line 36 / Rich Thompson Rephrases for clarity 225 – Specifying preferred character set Section 10.1 / Page 55 / Line 16 / Rich Thompson Correct optionality & the change to array of char sets. 226 – Resource URL Section 10.2.1.1.4.1 / Page 58 / Line 31 / Rich Thompson Make the conformance stand-alone 227 – Explicitly specify the relevant portlet url parameters Section 10.2.2.11 / Page 62 / Line 10 / Rich Thompson Be explicit about what portlet URL parameters are being referred to. Substantive changes: 187 – Cacheability and perform*Interaction Section 6.3.x / Page 39 / Line 9 Two alternatives proposed for clarifying how the protocol has clues for interactions impacting caching. Discussion has centered around whether we want anything in the spec until we define full invalidation caching. 173 – What does it mean to support registration? Section 8.3 / Page 52 / Line 20-22 We have a conformance statement regarding Producers supporting registration. It currently points at the requireRegistration flag ... not an exact match. 162 – Require Consumers to support UTF-8? Section 10.1 / Page 55 / Line 22 Proposal notes that we imply the answer to this question is yes and suggests adding a conformance statement to that effect. 143 – Properly encode '&' in examples and BNF Section 10.2.1 & 10.2.2 / Page 58 & 61 / Line 15 & 24 Question raised is whether or not the fragment containing a URL destined for consumer rewriting needs to be strictly XML compliant. If so, our '&' should be changed to '&'. 177 – Templates MUST send placeholders Section 10.2.2.1 - 10.2.2.8 / Page 61 Change 'SHOULD' to 'MUST' for the placement of fundamental parameters in action, etc templates (not for the default templates). 164 – Namespacing Portlet URL Parameters Section 10.3 / Page 64 / Line 18 Alternate text suggested for clarity reasons. 138 – How does info get to proxied resources (Insert a new section 10.4?) Section 10.4 (insert a new section at this point in the spec) In addition to a new section to discuss proxied resources, this request raises the question of how does a resource get access to information. Current discussion has noted three existing techniques and proposed one new technique. The three existing are: 1) Cookies that are properly defined/processed relative to cookie domains. 2) URL-encoding of the information. 3) URL-encoding of an indirection to the information. The proposed new technique is to define HTTP headers that carry UserContext and UserProfile information. The portlet could use portlet URL parameters to control whether or not these two items are supplied to a resource. 193 – Asserting multiple standard user categories Section B.2 / Page 77 / Line 25 Adds explicit statements that multiple std user categories can be asserted and that there are no correlations between them. 192 – Prevent localization of standard user category names Section 5.1.9 / Page 18 / Line 36 Notes that the description for std user categories are their names and they are not localized. 200 – Clarify response to ignoring security request Section 5.1.11 / Page 21 / Line 1 / Andre Kramer Specifies what Producer should do when security requests are ignored. 201 – PortletDescription applies to clones Section 5.1.11 & 6.3.3 / Page 21 / Line 29 / Andre Kramer Proposes which fields from PortletDescription are required to apply to clones as well. 195 – Add registrationMethods Section 5.1.18 / Page 23 / Line 7 Proposal adds a field to enable a Producer to provide guidance for how to register. In-band technique is identified by the portType name as this eliminates dependencies on particular bindings while not inventing yet another name. 204 – Fields for cache key Section 6.1.2 / Page 27 / Line 33 / Andre Kramer Proposes several additional fields also be part of cache keys 141 – Add previous windowState and mode? Section 6.1.2 / Page 26 / Line 46 This would place the burden of remembering the previous windowsState and mode on the Consumer and thereby permit the Portlet to know about interesting transitions that do not involve user interactions with the Portlet's markup. 205 – Template requirements Section 6.1.6 / Page 29 / Andre Kramer Proposes explicit language for how templates may be dependent on markupType. 206 – Values for extensible items such as modes Section 6.1.9 and 7.1.1 / Page 31 / Line 13 / Andre Kramer Consumer vs custom modes and window states 230 – Setting navState Section 6.1.9 / Page 30 / Line 24 / Andre Kramer Be more explicit about how navState is set. 213 – Require modes, windowstates & userAuthentication are URIs Section 6.1.9 / Page 31 / Line 20 / Rich Thompson Proposes the recommendation become a rewuirement. 215 – Delete statement about “private conversational state” Section 6.1.19 / Page 38 / Line 19 / Rich Thompson Suggests deleting this statement as it is either incomplete or wrong. 218 – Old sessionId semantics in 6.7.3 Section 6.7.3 / Page 44 / Line 2 / Rich Thompson Proposal lines these statements up with 6.1.1 207 – PortletDescription dependent on UserContext? Section 8.2 / Page 36 / Andre Kramer Questions whether getPortletDescription() should take a UserContext parameter Conformance statements: 179 – Drop duplicate extensions conformance statement Section 3.3 / Page 11 / Line 5-6 Proposal notes that this is a weaker version of a conformance statement from 5.1.1 183 – Drop extension field's conformance statement? Section 5.1.1 / Page 16 / Line 29 This changes the oft used statement about extensions to something more closely resembling defining the field. 184 – Handle truncation Section 5.1.2 / Page 16 / Line 41 Makes statement stand-alone 185 – ResetProperty name conformance statement Section 5.1.13 / Page 21 / Line 23 Makes statement stand-alone 186 – PropertyDescription name description Section 5.1.15 / Page 22 / Line 10 Makes statement stand-alone 188 – Conformance -> Semantics (#1) 26 proposed changes that drop conformance language that is viewed as untestable. 189 – Processing groupID duplicate Section 3.8 / Page 13 / Line 14-15 Proposal notes this is a duplicate and suggests a forward reference to the section instead. 190 – User Categories in PortletDescription Section 5.1.11 / Page 20 / Line 5-7 Proposal notes this is a duplicate conformance statement (ref: 5.1.9) using more convoluted English. 191 – Namespace prefixing Section 10.3 / Page 63 / Line 12 Changes SHOULD to MUST and notes that JavaScript names may not start with a numerical character. 196 – Making conformance statements stand-alone 20 requests to make various conformance statements sensible when they are extracted from the specification. 197 – Specifying WSDL file locations Section 14 / Page 72 / Line 2 Rewords this conformance statement to say the WSDL on OASIS is the normative copy of the WSDL. 198 – Require Consumers to supply CSS stylesheets? Section 10.5 / Page 65 / Line 20 Proposal adds a conformance statement requiring Consumer to support the std CSS classes the spec defines. 199 – Conformance -> Semantics (#2) 13 proposed changes that drop conformance language that is viewed as untestable. 208 – Conformance test requires cycling Consumer? Section 6.1.3 / Page 27 / Line 15-19 / Rich Thompson Current language will require cycling of the Consumer during conformance testing. Do we really want to require this? 209 – Invalidates "cached" markup Section 6.1.4 / Page 27 / Line 24 / Rich Thompson Inserts the word "cached" 210 – Duplicate conformance statements Details a number of duplicate conformance statements with proposals for the duplicates changing to semantic language rather than conformance language. 214 – userContextKey conformance statement Section 6.1.19 / Page 38 / Line 8 / Rich Thompson Clarity and testability 216 – Reword intro for performBlockingInteraction Section 6.3.2 / Page 39 / Line 31 / Rich Thompson Current intro has untestable conformance statements 220 – Rephrase multiple registrations Section 7.2 / Page 48 / Line 47 / Rich Thompson Make it clear and testable 221 – Defining invalidated registrationHandle Section 7.4 / Page 49 / Line 19 / Rich Thompson Be explicit about what invalidates a registrationHandle 222 – Throwing InvalidRegistration Section 7.4 / Page 49 / Line 20 / Rich Thompson Be explicit about what to do when an invalid registration handle is supplied to the Producer. 223 – Supporting cloning requires supporting releasePortlet Section 8 / Page 49 / Line 40 / Rich Thompson How strongly do we want to tie releasePortlet() to clone-before-write 224 – Conformance -> semantic language Section 8.3 / Page 51 / Line 11 / Rich Thompson We can't test what a Producer does internally. 228 – namespacePrefix encoding Section 10.3 / Page 63 / Line 13 / Rich Thompson Make it stand-alone 229 – wsrp-mode & wsrp-windowState processing Sections 10.2.1.1.1 & 10.2.1.1.2 & 10.2.1.4 & 10.2.1.5 / Page 59 / Rich Thompson Consolidate these repeating statements and move to 10.2 231 – portlet URL parameter usage Section 10.2.1.4 & 10.2.1.5 / Page/Line: (60/27) & (60/36) / Andre Kramer Add conformance statements about when a portlet URL parameter can be used 232 – wsrp-token usage Section 10.2.1.1.5.1 / Page 60 / Line 11 / Andre Kramer Add conformance statements about when a portlet URL parameter can be used 233 – When do query string parameters become formParameters? Section 10.2.1.1.1 & 10.2.1.1.2 / Page/Line: (58/34) & (59/6) / Andre Kramer Be explicit about when formParameters are supplied to the Producer Rich Thompson ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]