Re: [web-annotation] Protocol examples should use comma separated headers in examples

So I had this wonderful proposal for fixing this, but just found that 
it looks like LDP just provides multiple `include` values as space 
delimited IRIs:

 Clients interested only in information about the container (for 
example, which membership predicate it uses) and its membership might 
use this hint on a GET request: Prefer: return=representation; 

[`include` is not (as yet) a registered 
 so perhaps we'll need more information added to my note commit that 
explains its usage. And perhaps we should help LDP (or whoever) get 
`include` registered.


GitHub Notification of comment by BigBlueHat
Please view or discuss this issue at
 using your GitHub account

Received on Tuesday, 2 August 2016 14:53:34 UTC