[dxwg] Defend the use of opaque URIs for profiles (#663)

• From: Nicholas Car via GitHub <sysbot+gh@w3.org>
• Date: Tue, 15 Jan 2019 05:17:52 +0000
• To: public-dxwg-wg@w3.org
• Message-ID: <issues.opened-399191941-1547529471-sysbot+gh@w3.org>

nicholascar has just created a new issue for https://github.com/w3c/dxwg:

== Defend the use of opaque URIs for profiles ==
From Gregg Kellogg via the W3C JSON-LD CG:

> There certainly is a conversation on the difference between the profile parameter, and Accept-Profile header, which looks like a good direction for you, IMHO. It would be useful to be able to content-negotiate over this; an opaque frame URL is not helpful, as it would be challenging to know what it meant if it wasn’t registered. We came down on the use of the profile parameter to specify registered profiles, that may imply specific contexts or frames to be used as part of the profile specification. Of course, the profile URI could, itself, be used to returned the context or frame.

Please view or discuss this issue at https://github.com/w3c/dxwg/issues/663 using your GitHub account

Received on Tuesday, 15 January 2019 05:17:54 UTC