- From: Karen Coyle <kcoyle@kcoyle.net>
- Date: Fri, 8 Dec 2017 02:37:45 -0800
- To: public-dxwg-wg@w3.org
Annette, thanks for the reality check. And as Ruben says, the main aim is to access data that matches one or more application profiles. On 12/8/17 1:24 AM, Ruben Verborgh wrote: > Hi Annette, > >> In my mind, the conneg bit that's needed is about adding the ability to negotiate not the profile itself but the distribution (of a dataset) that supports a preferred profile. The only requirement seems to be: 6.8.3 Profile negotiation Create a way to negotiate choice of profile between clients and servers Perhaps that needs to be more specific so that it is clearly about choosing data that is consistent with a given application profile. kc > > The second is our main aim, > but conneg clearly also makes sense for the profile itself > if that is available in multiple representations. > >> Content negotiation already has the capability to handle the case of requesting a copy of astrodcat itself as astrodcat.rdf vs astrodcat.xml vs astrodcat.json. > > Indeed, it's this mechanism I propose to reuse > (but no need to mandate that). > > Ruben > -- Karen Coyle kcoyle@kcoyle.net http://kcoyle.net m: 1-510-435-8234 (Signal) skype: kcoylenet/+1-510-984-3600
Received on Friday, 8 December 2017 10:38:16 UTC