search

ProfileNegotiation / I-D-Profile-Negotiation

Internet-Draft: Indicating and Negotiating Profiles in HTTP
https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation.html
2 stars 3 forks source link

[Use case] JSON-LD framing #27

Closed ericprud closed 5 years ago

ericprud commented 7 years ago

JSON-LD: specify the json-ld profile implies a need for separate specification of a document form (e.g. json-ld:compacted) and the framing. This could be handled analogously to the pairs used to represent XML namespace and schemaLocations. Gregg drafted an example:

Accept-Profile: <http://www.w3.org/ns/json-ld#compacted https://example.com/context.jsonld>

Related: #21

larsgsvensson commented 6 years ago

I understand Gregg's example, but wonder if those aren't two different kinds of profiles. The qustion is of course if that matters and if we cann differentiate between them.

Usually I've seen the first one passed as a parameter in the Accept-Header: Accept: application/ld+json; profile='http://www.w3.org/ns/json-ld#compacted'

RubenVerborgh commented 5 years ago

We currently don't have a mechanism for stating combined profile preferences, and do not have one in mind for this first draft. This might be a later extension.

Currently, they could be stated as independent preferences (that the server will try to satisfy), or @larsgsvensson's suggestion above can be followed.