07:42:43 RRSAgent has joined #dxwgcneg 07:42:43 logging to https://www.w3.org/2018/06/06-dxwgcneg-irc 07:43:03 Zakim has joined #dxwgcneg 07:43:39 RRSAgent, please make logs public 07:43:50 q? 07:44:02 Action-123? 07:44:02 Sorry, but no Tracker is associated with this channel. 07:44:43 trackbot, associate this channes with #dxwg 07:44:43 Sorry, LarsG, I don't understand 'trackbot, associate this channes with #dxwg'. Please refer to for help. 07:44:51 trackbot, associate this channel with #dxwg 07:45:04 Action-123? 07:45:04 Sorry, but no Tracker is associated with this channel. 07:45:28 trackbot, start meeting 07:45:28 Sorry, but no Tracker is associated with this channel. 07:46:37 trackbot, associate this channel with #dxwg 07:49:20 RRSAgent, please draft minutes v2 07:49:20 I have made the request to generate https://www.w3.org/2018/06/06-dxwgcneg-minutes.html LarsG 07:49:59 RRSAgent, please make logs public 07:50:30 present+ 08:02:56 ncar has joined #dxwgcneg 08:03:03 present+ 08:04:13 Agenda: https://www.w3.org/2017/dxwg/wiki/Meetings:CNEG-Telecon2018.06.06 08:05:21 regrets+ antoine 08:05:30 regrets+ RubenVerborgh 08:06:17 Meeting: Content (Negotiation) Subgroup 08:06:22 Chair: LarsG 08:06:56 scribenick: ncar 08:07:13 Scribe: Nick 08:07:18 TOPIC: recap of plenary profiles work 08:08:26 previous plenary content discussed 08:10:16 https://www.w3.org/2018/06/05-dxwg-minutes 08:24:34 TOPIC: discussion about profile negociation 08:28:18 this group is waiting for Requirements finalisation from theplenary group 08:28:47 this group commits to aligning different implementations of profileneg mechanisms 08:29:45 TOPIC: (from agenda) the role of description - is there any requirement to advertise what profiles exist and where is metadata about these held 08:30:00 Yes, this seems to be emerging from the Plenary group's workj 08:30:20 TOPIC: (from the agenda) do we need to do anything about URL parameters that take precedence over, and can substitute for, headers in negotiation 08:31:11 yes, we will resolve this by alining implementations (HTTP layer, browser layer) and also b following web norms (exact URIs trump HTTP headers) 08:31:52 TOPIC: (from agenda) possible use of tokens representing profiles identified by URIs 08:34:02 example: gnafld.net/address/GAACT714845933?_view=alternates 08:41:16 discussed at length! 08:41:34 TOPIC: (from agenda) conformance with parent profiles - do services advertise just the most specialised or all profiles they conform to? Do clients have to select a level that matches what the service knows about. 08:44:52 example: https://github.com/w3c/dxwg/tree/gh-pages/profiledesc/examples 08:48:45 we understand this is analagous to SPARQL queries not finding upper classes due to systems not doing inferencing up subClassOf chains 08:50:59 we could advertise something like "make sure you set fallback options in an Accpept-Profile header" 08:52:57 we admit we don't have all the answers when servers don't know they contain information according to a Profile of other Profiles/Standards they don't know about and can't advertise 08:54:22 TOPIC: (from agenda) what is required within DXWG above and beyond the IETF activity? 08:54:45 The direction of profile work is being set now by Plenary group. 08:56:06 Looks like we will have a technology-independent Profiling Gudance document then 3 technology-specific implementations: HTTP profile neg, in-browser profile neg, Profile Dec ontology 08:58:17 TOPIC: next meeting 08:58:22 In a fortnight 09:04:24 present- 09:04:44 RRSAgent, please generate minutes v2 09:04:44 I have made the request to generate https://www.w3.org/2018/06/06-dxwgcneg-minutes.html LarsG 09:04:55 trackbot, end meeting 09:04:55 Sorry, but no Tracker is associated with this channel. 09:05:16 (thanks, was about to do that) 09:05:50 I will record this text in case minutes not generated 11:28:04 Zakim has left #dxwgcneg