- From: John Arwe <johnarwe@us.ibm.com>
- Date: Tue, 29 Jul 2014 16:18:27 -0400
- To: "public-ldp-wg@w3.org Working Group" <public-ldp-wg@w3.org>
- Message-ID: <OFB5D6CD27.56A00ABB-ON85257D24.006E06CD-85257D24.006F8E81@us.ibm.com>
In the course of starting to process Mr. Speicher's comments [3], I noticed that we had nowhere said (aside from examples) that when initiating paging with a 303 that there should be a Location response header linking to the first page [oooops]. Neither could I find where we said normatively that the 2NN representation should be the first page. The changes to render that explicit are now at [1] and [2]. I also noticed that we had two different normative clauses regarding initiating paging, separated by 10 others (added at different points in time, editors wanted to preserve existing numbering), that were somewhat conflicting. These were 6.2.6 (long-standing text Should 2NN, May 303 or anything else) and the recently added 6.2.17 (Must>Should Not initiate paging unless client is paging-aware). 6.2.6 could have been read to say 303 is always an option (no requirement that the client support paging in there), and people are probably aware of the recent discussions. I collapsed those both into 6.2.6 (.17 is just commented out, so look at the source if you want to see it), and made it work such that if the client supports 2NN, the server is always allowed to initiate paging. Since I don't recall any WG discussion of that specific case, pointing that out explicitly here in case anyone objects. Otherwise my intent was to make no normative changes. [1] https://dvcs.w3.org/hg/ldpwg/rev/ffda91dd27b7 [2] https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html [3] http://lists.w3.org/Archives/Public/public-ldp-wg/2014Jul/0059.html Best Regards, John Voice US 845-435-9470 BluePages Cloud and Smarter Infrastructure OSLC Lead
Received on Tuesday, 29 July 2014 20:19:02 UTC