Re: Comments on the Triple Patterns Fragments draft

• From: Ruben Verborgh <ruben.verborgh@ugent.be>
• Date: Tue, 14 Oct 2014 16:22:56 +0100
• To: Markus Lanthaler <markus.lanthaler@gmx.net>
• Cc: public-hydra@w3.org
• Message-Id: <9408C2D7-F9F5-4AD3-B005-5C3CF33AB48C@ugent.be>

> I would thus suggest to change the spec as follows [2]:
> 
>  In order to allow browser applications to access fragments, Cross-
>  Origin Resource Sharing [CORS] **has to be** enabled on the server. To
>  this end, triple pattern fragments servers **SHOULD** emit the
>  following header and value on all HTTP responses to requests for
>  triple pattern fragments, regardless of their status code:

While I do agree, just a small remark:
as was mentioned in previous discussions,
the TPF spec will be rewritten so that the focus is the document;
HTTP will just be one possible implementation.
There will likely be no normative statements about HTTP,
and hence, also not about CORS.

In the meantime, however, the above is fine with me!

Ruben

PS Said rewrite is planned for November.

Received on Tuesday, 14 October 2014 15:23:23 UTC