Re: [dxwg] Profile negotiation [RPFN]

> I'm talking about the motivation to use negotiation.

Negotiation is what gets clients to the representation with the preferred profile.

> If the only motivation is to have the same resource available in conformance to different profiles

No, that's not the motivation. We can do that with existing technologies already.

What existing technologies don't do, is automatically getting a resource in a profile the client understands.

> I don't see any particular reason to have profile negotiation that works like content negotiation.

It's just like negotiating between XML or JSON, except more fine-grained:
https://ruben.verborgh.org/articles/fine-grained-content-negotiation/

> Having multiple profiles available is realized already by just offering a version of the dataset that conforms to one profile under one URL and a version that applies to another under another URL.

But how does the client get from one to the other?
Our answer: content negotiation.



-- 
GitHub Notification of comment by RubenVerborgh
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/74#issuecomment-394062783 using your GitHub account

Received on Saturday, 2 June 2018 06:28:45 UTC