15:34:04 RRSAgent has joined #json-ld 15:34:04 logging to https://www.w3.org/2019/10/25-json-ld-irc 15:34:05 rrsagent, set log public 15:34:05 Meeting: JSON-LD Working Group Telco 15:34:05 Date: 2019-10-26 15:34:05 Agenda: https://lists.w3.org/Archives/Public/public-json-ld-wg/2019Oct/0009.html 15:34:05 ivan has changed the topic to: Meeting Agenda 2019-10-26: https://lists.w3.org/Archives/Public/public-json-ld-wg/2019Oct/0009.html 15:34:06 Chair: azaroth 15:34:06 Regrets+ gkellogg, bigbluehat, harold 15:56:47 pchampin has joined #json-ld 16:01:41 azaroth has joined #json-ld 16:01:56 present+ 16:02:04 ajs6f has joined #json-ld 16:02:11 present+ 16:02:42 present+ 16:02:55 regrets+ jeff_mixter 16:02:59 regrets+ hsolbrig 16:03:50 scribenick: ajs6f 16:03:51 present+ 16:04:00 TOPIC: Approve minutes of previous call 16:04:07 PROPOSAL: Approve minutes of previous call: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-10-18-json-ld 16:04:09 +1 16:04:16 +1 16:04:18 +1 16:04:25 +1 16:04:28 RESOLVED: Approve minutes of previous call: https://www.w3.org/2018/json-ld-wg/Meetings/Minutes/2019/2019-10-18-json-ld 16:04:31 +1 16:04:37 TOPIC: Announcements / Reminders 16:05:01 present+ 16:05:35 present+ dlehn 16:05:36 azaroth: We are rapidly apporaching CR 16:05:40 next week's call will be 1h earlier in Europe 16:05:43 TOPIC: Issues 16:06:24 azaroth: 5PM central europse, 4PM UK 16:06:45 s/europse/europe/ 16:06:49 SUBTOPIC: Register profiles with IANA 16:07:16 azaroth: we have some new URIs for values of profile 16:07:23 ... they must be registered with IANA 16:07:32 ... gkellog offered to do this 16:07:34 q+ 16:07:35 ACTION: bigbluehat to register profiles with IANA 16:07:42 s/gkellog/bigbluehat/ 16:07:45 ack ivan 16:07:47 ivan: it was bigbluehat, not gkellogg 16:08:04 ... this should go via W3C channels, not directly 16:08:25 ... not sure what the mechanism is for profiles 16:08:31 ... i will ask 16:08:37 ACTION: ivan to check with plh if he is the right contact person 16:09:01 azaroth: for the annotation WG it was easy 16:09:51 https://github.com/orgs/w3c/projects/4?fullscreen=true 16:10:03 q+ 16:10:08 azaorth: no more topics to be discussed on calls 16:10:16 ack ivan 16:10:25 s/azaorth/azaroth 16:10:43 ivan: i am representing the DID WG 16:10:46 https://github.com/w3c/json-ld-syntax/issues/287 16:10:50 ... in this question 16:11:12 q+ 16:11:18 ack dlongley 16:11:26 TOPIC: application/jsonld 16:11:35 dlongley: this might be better if people could rad over the DID spec issue first, 16:11:58 ... but it's not clear how to handle mimetypes 16:12:07 q+ 16:12:11 ... this is documented at the discussion there (at DID) 16:12:12 q+ re application/ld+json (with a profile) 16:12:14 ack pchampin 16:12:42 pchampin: the goal is to be able to declare application+did/jsonld 16:12:45 ...? 16:12:52 q? 16:13:18 s/application+did/application/ 16:13:18 ivan: it's unclear whether did/ld+json is acceptable 16:13:26 s/jsonld/did+jsonld/ 16:13:37 application/did+ld+json 16:13:55 no one does this^ ... but it doesn't seem illegal ... and questionable what tools would do. 16:14:00 ivan: there is no current registered mimetype that uses two + signs 16:14:09 ... so we don't know if this is really possible 16:15:03 dlongley: VC WG did not choose a mimetype 16:15:16 q? 16:15:18 ack azaroth 16:15:18 azaroth, you wanted to discuss application/ld+json (with a profile) 16:15:23 ivan: rthat is a case where this might make sense 16:15:28 https://www.w3.org/TR/annotation-protocol/#annotation-retrieval 16:15:37 VCWG didn't pick a MIME type that i can see 16:15:40 azaroth: for Annotations, we went with a profile 16:16:09 azaroth: you can trigger a file extension from a profile, says IANA 16:16:27 https://github.com/w3c/did-spec/issues/1#issuecomment-545103700 16:16:59 azaroth: but I don't ahve a reference for that 16:17:07 https://www.iana.org/assignments/profile-uris/profile-uris.xhtml 16:17:46 ... we would have to go search the minutes 16:19:55 ivan: we defined no extension for annotation 16:19:58 s/ahve/have/ 16:20:10 ACTION: azaroth to find reference to file extensions for profiles re annotation 16:21:21 azaroth: if we did this, processors would have to know about it, whcih would be a normative change to the algorithym 16:21:34 iban: it would chage the documents to allow this new media type in parallel to the older one 16:21:35 q+ 16:21:55 ... it is simple for the document, but causes a lot of change elsewhere 16:22:17 ack dlongley 16:22:28 q+ re xml schema 16:23:07 azaroth: we aren't going to decide this today 16:23:47 ... if there is no change here, we are on-track for CR 16:23:56 ... a chnage here would push CR back by at elast 2 weeks 16:24:02 we want this group to enable other groups to be able to extend jsonld MIME type w/ file extension support -- just a question of whether we need to register `application/jsonld` or not ... either way should provide some advice to extenders on what to do 16:26:19 dlongley: we did discuss this in the 1.0 days, but it might not recorded in issues 16:27:18 https://github.com/w3c/did-spec/issues/1#issuecomment-545103700 16:27:20 azaroth: if you _can_ register a file extension to a profile, than that is what we could recommend 16:28:59 azaorth: how does application/jsonld solve the problem? 16:29:11 q+ 16:29:12 ack azaroth 16:29:12 azaroth, you wanted to discuss xml schema 16:29:13 ivan: because then you can do applicaiton/did+jsonld 16:29:19 s/azaorth/azaroth/ 16:29:20 ... no multiple plus signs 16:29:45 azaroth: this came up in XML days 16:30:50 application/xhtml+xml 16:31:14 ivan: i couldn't find any example of this (mulitple plus signs) in IANA 16:32:00 q? 16:32:29 ivan: if I have a doc that is did+ld+json, and a JSON-LD proc, then that proc _should_ handle it fine 16:32:46 ... if I do did+json, then a JSON-LD proc may or may not work correctly 16:32:54 ack pchampin 16:32:54 ...(handle it as JSON-LD) 16:33:18 pchampin: at the discussion at theDID WG, there is duscussion of an alias 16:33:30 ... is this an official construct of IANA? 16:33:43 ivaN: I don't know, but i think not 16:34:52 ... I propose that azaroth digs up th remark from IANA about file extensions 16:35:30 q+ 16:35:33 ack dlongley 16:35:56 q+ 16:35:59 ack pchampin 16:36:03 q+ re joint call? 16:36:31 pchampin: this could look pretty complicated to some people 16:36:48 ... it might be a shame, in terms of marketing 16:37:00 +1 16:37:07 ack azaroth 16:37:07 azaroth, you wanted to discuss joint call? 16:39:05 azaroth:dlongley: the two WGs can meet at the next JSON-LD WG meeting 16:39:13 ... to discuss this 16:39:30 ACTION: azaroth to comment in issue inviting DID WG to JSON-LD WG regular call next week to discuss 16:39:41 q? 16:40:08 Subtopic: closing issues 16:40:08 SUBTOPIC: closable issues 16:40:10 https://github.com/w3c/json-ld-syntax/issues/269 16:40:59 https://github.com/w3c/json-ld-framing/issues/69 16:43:18 TOPIC: AOB? 16:43:55 rrsagent, draft minutes 16:43:55 I have made the request to generate https://www.w3.org/2019/10/25-json-ld-minutes.html ivan 16:43:55 zakim, bye 16:43:55 rrsagent, bye 16:43:55 I see 4 open action items saved in https://www.w3.org/2019/10/25-json-ld-actions.rdf : 16:43:55 ACTION: bigbluehat to register profiles with IANA [1] 16:43:55 recorded in https://www.w3.org/2019/10/25-json-ld-irc#T16-07-35 16:43:55 ACTION: ivan to check with plh if he is the right contact person [2] 16:43:55 recorded in https://www.w3.org/2019/10/25-json-ld-irc#T16-08-37 16:43:55 ACTION: azaroth to find reference to file extensions for profiles re annotation [3] 16:43:55 recorded in https://www.w3.org/2019/10/25-json-ld-irc#T16-20-10 16:43:55 ACTION: azaroth to comment in issue inviting DID WG to JSON-LD WG regular call next week to discuss [4] 16:43:55 recorded in https://www.w3.org/2019/10/25-json-ld-irc#T16-39-30 16:43:55 leaving. As of this point the attendees have been azaroth, ajs6f, pchampin, dlehn, dlongley 16:43:55 Zakim has left #json-ld 16:43:57 TOPIC: Adjourn :)