Open Change Requests

1
Open Change Requests
2
304 Extensions field

• Section All definitions of extensions field
• Old text The extensions field MAY be used to
  extend this structure. Extension elements MUST be
  from namespaces other than WSRP.
• New text The extensions field MAY be used to
  extend this structure. Elements defined in the
  WSRP namespace MAY be used, but overlap with the
  fields already defined in this structure SHOULD
  be avoided.
• Define a wsrp_extensions namespace instead
  copying appropriate element definitions. Add
  pointers to these definitions in first discussion
  of extensions.
• Errata? No

3
304 Extensions field

• Section 5.1.1 (errata? No)
• Old text While the element definitions for these
  extensions are required to be in a namespace
  other than WSRP, the reuse of the types defined
  within the WSRP namespace by those definitions is
  encouraged as this increases the likelihood of
  the receiving partner being able to deserialize
  the extension in a useful manner.
• New text The use of the types defined within the
  XML Schema and WSRP namespaces is encouraged as
  this increases the likelihood of the receiving
  partner being able to deserialize the extension
  in a useful manner. Overlap with the fields
  defined in the structure being extended SHOULD be
  avoided.

4
305 InconsistentParameter fault definition

• Section 13 (Page 75)
• Old text Used when a Consumer supplies a
  portletHandle that is not scoped by the supplied
  registrationHandle.
• New Text Used when a Consumer supplies
  inconsistent parameters (e.g. when a
  portletHandle is not scoped by the supplied
  registrationHandle).
• Errata? No

5
306 Add default cacheControl?

• Section Section 5.1.11
• Old Text
• New Text
• O cacheControl CacheControl
• Rejected
• Change conformance statement about missing
  cacheControl to say that this just means the
  Producer is not giving any guidance regarding the
  caching of the markup fragment.
• Errata? no

6
307 Add ModifyRegistrationRequired fault?

• Section All operations that accept
  registrationContext and can return
  InvalidRegistration fault
• Old Text
• New Text Add ModifyRegistrationRequired fault to
  all operations that accept registrationContext
  and can return InvalidRegistration fault.
• Errata? No

7
308 Add requestMethod?

• Section 6.1.9 MarkupParams Type
• Requested by Subbu Allamaraju
• Old Text
• New Text O string requestMethod
• requestMethod This field indicates the type of
  the HTTP request used by the client to submit
  data to the Consumer. The Consumer MUST supply a
  valid HTTP method as specified in Section 5.1.1
  of RFC 2616 as a value for this field.
• Rejected
• Errata? no

8
309 Add processContentslax?

• Proposed Change ltcomplexType name"Extension"gt
  ltsequencegt ltany namespace"other"
  processContents"lax"/gt lt/sequencegt lt/complexTy
  pegt
• Reasoning The current definition of the
  Extension type makes it hard for
  producers/consumers/intermediaries to validate
  the Envelope of messages using extensions. If a
  producer/consumer uses extensions but does not
  make it available to the receiver/intermediary
  (very common in practice), and if the
  receiver/intermediary is an off-the-shelf tool
  without entity resolution support, it will
  conclude that the message is invalid. - By
  adding processContents"lax", we can instruct the
  receiver/intermediary to try to validate on a
  best-effort basis. - An alternative is to
  specify "skip" for processContents. But I (Subbu)
  am not sure of any advantage to this choice.
• Subbu to explore whether an extension element
  could turn the processing back to strict.