Core spec: PullMessagesResponse/CurrentTime description contradicts sibling operations

[amakrushin]

The description of CurrentTime in PullMessagesResponse is wrong -- The date and time when the messages have been delivered by the web -- devices cannot know the time in future, when their responses will be transferred over the network; also, the description doesn't match the similar descriptions for the CurrentTime in CreatePullPointSubscriptionResponse and RenewResponse:

• CreatePullPointSubscriptionResponse - Current time of the server for synchronization purposes
• RenewResponse - The current server time.

Most accurate and useful description in the CreatePullPointSubscriptionResponse.

Also note WS-ResourceLifetime description, more useful and accurate:

The CurrentTime resource property may be used by a client to determine the clock skew between the client and the service, within a margin of error determined by the round-trip latency of the message exchange to retrieve that value. This clock skew and margin of error can then be factored into subsequent decisions of when to send subsequent requests to change the termination time, and what termination times to request.

Suggested fix

Replace the description in PullMessagesResponse and RenewResponse with the description in thee CreatePullPointSubscriptionResponse.

Locations

• doc/Core.xml 9.1.2 Pull messages, response CurrentTime
• doc/Core.xml 9.1.3 Renew, response CurrentTime
• wsdl/ver10/events/wsdl/event.wsdl:159
• wsdl/ver10/events/wsdl/event-vs.wsdl:159

Related

• Remove mention of Renew in the CreatePullPointSubscription #515
• Clarification PullPoint subscription and renewal #506
• RFC: Adding progressive XML lint for the specs #726
• Agentic review and linting #798

[HansBusch]

Agree with the proposal to use everywhere Current time of the server for synchronization purposes.

[amakrushin]

May i ask for review, @HansBusch ?

#829