ACTION-243: Go back through the discussion, come to a conclusion, discuss with antoine and work out what requirement #267 actually meant

Go back through the discussion, come to a conclusion, discuss with antoine and work out what requirement #267 actually meant

State:
closed
Person:
Rob Atkinson
Due on:
November 1, 2018
Created on:
October 25, 2018
Associated Product:
Content Negotiation by Application Profile
Related emails:
No related emails

Related notes:

its definitely a DCAT expressivity problem - data distribution services will need to describe both the service profile(s) - which may introduce containers and the data payload profile(s) for data within those containers

The conneg requirement may be for negotiation of the container - for example Accept-Encoding can ask for gzip, which has a container and a manifest.

Rob Atkinson, 25 Oct 2018, 07:44:10

doiscussed in CNEG - needs more thought but UC is at https://w3c.github.io/dxwg/ucr/#ID51
https://w3c.github.io/dxwg/ucr/#RDIC

Rob Atkinson, 16 Jan 2019, 20:52:27

Display change log.


Caroline Burle <cburle@nic.br>, Peter Winstanley <pedro.win.stan@gmail.com>, Chairs, Philippe Le H├ęgaret <plh@w3.org>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 243.html,v 1.1 2021/06/28 08:09:45 carcone Exp $