> ACTION-108: Raise second and third editorial note as new issue and they will be deleted (see http://www.w3.org/2002/ws/ra/tracker/actions/108).

Reference: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Sep/0108.html 

The WS-Enumeration protocol relies on the absence of the Expire element to indicate infinite lifetime. Whereas, the optional /wsenp:Enumeration/wsenp:MaxExpires policy assertion parameter relies on the value 'PT0S' to indicate that an endpoint supports enumerations with an infinite lifetime. At the Hursley F2F, to avoid confusion, the WG assigned an action to Asir to raise this as a separate issue.

WG resolutions for issues 7478 [1] and 7587 [2] reinforced that the absence of the Expire element indicates infinite lifetime.

Proposal

s/Note: a value of "PT0S" indicates that this endpoint supports enumerations with an infinite lifetime./The implied default is indefinite (no expiry)./

There is a precedent in WS-RA specs for relying on the absence of policy assertion parameters to signal defaults. TransferResource policy assertion says, "Unless support for OPTIONAL operations is explicitly indicated by either the PutOperationSupported or DeleteOperationSupported parameters only the Get operation is supported."

The same reasoning applies to the following policy assertion parameters:

/wsenp:Enumeration/wsenp:MaxTime
/wsevp:EventSource/wsevp:MaxExpires

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7478#c4
[2] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7587#c3

Regards,

Asir S Vedamuthu
Microsoft Corporation