8300 2009-11-14 03:16:18 +0000 Transfer: unnecessary descriptions of extension elements 2010-03-17 11:35:53 +0000 1 1 1 Unclassified WS-Resource Access Transfer FPWD All All CLOSED REMIND hasProposal P2 normal --- 1 gilbert.pilz gilbert.pilz dug public-ws-resource-access-notifications oldest_to_newest 29573 0 gilbert.pilz 2009-11-14 03:16:18 +0000 The presence of extensibility points within WS-Transfer is called out in Section 2.4 "Considerations on the Use of Extensibility Points". However, there are several places where such extensibility points are redundantly mentioned. These are: 3.1 Get [Body]/wst:Get This is a REQUIRED element that has no defined child element content. *However, it MAY include child element content as defined by an extension(s).* [Body]/wst:GetResponse This REQUIRED element MUST have as its first child element, an element that comprises the representation of the resource. *Additional extension elements MAY be included after the element representing the resource.* 3.2 Put [Body]/wst:Put This REQUIRED element MUST have as its first child element, an element that comprises the representation of the resource that is to be replaced. *Additional extension elements MAY be included after the element representing the resource.* [Body]/wst:PutResponse This REQUIRED element, if it contains any child elements, MUST have as its first child element, an element that comprises the representation of the resource that has been updated. *Additional extension elements MAY be included after the element representing the resource.* 3.3 Delete [Body]/wst:Delete This is a REQUIRED element that has no defined child element content. *However, it MAY include child element content as defined by an extension(s).* [Body]/wst:DeleteResponse This REQUIRED element *MAY contain extension elements.* Proposal: remove all redundant mentions of extensibility. 30996 1 bob 2010-01-12 21:17:47 +0000 resolved as proposed