Re: [dxwg] Profile negotiation [RPFN]

Sorry, but I need an answer that is not tautological.

I imagine the IETF will be asking the same question. Why do you think 
you need to enable this type of negotiation versus allowing discovery 
via links? Clients can get from one representation to another by 
following links (either in a browser or in an API). That is plenty 
webby. Why is automated discovery needed? There are plenty of 
differentiating features of web data resources that a user could want; 
why make this particular level of differentiation negotiated? Do you 
have a real need to require profile creators to register their profiles 
with IETF? This is more work for IETF and for profile creators. (If you 
have a way around that, it would help to hear it.)

Don't get me wrong. I'm not trying to shut down discussion of profile 
negotiation. I'm trying to stimulate the production of actual use cases 
that can guide the generation of realistic requirements. Reiterating the 
solution doesn't address that.


On 6/1/18 11:28 PM, Ruben Verborgh via GitHub wrote:
>> 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:
>> 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.

Annette Greiner
NERSC Data and Analytics Services
Lawrence Berkeley National Laboratory

Received on Monday, 4 June 2018 19:06:46 UTC