16:52:27 RRSAgent has joined #rdf-star 16:52:31 logging to https://www.w3.org/2023/02/02-rdf-star-irc 16:52:31 RRSAgent, make logs Public 16:52:32 please title this meeting ("meeting: ..."), pchampin 16:52:39 meeting: RDF-star WG 16:52:40 gkellogg has joined #rdf-star 16:53:00 regrets+ Gregory_Williams 16:54:49 AndyS has joined #rdf-star 16:55:25 ora has joined #rdf-star 16:55:41 previous meeting: https://www.w3.org/2023/01/26-rdf-star-minutes.html 16:56:08 next meeting: https://www.w3.org/2023/02/09-rdf-star-minutes.html 16:56:12 gkellogg has joined #rdf-star 16:59:47 enrico has joined #rdf-star 16:59:52 prestent+ 16:59:56 present+ 16:59:57 present+ 17:00:07 present+ 17:00:22 present+ 17:00:28 present+ 17:01:00 AZ has joined #rdf-star 17:01:01 present+ 17:01:12 present+ 17:02:18 present+ 17:03:48 pfps has joined #rdf-star 17:03:55 present+ 17:04:01 zakim, who is here? 17:04:01 Present: gkellogg, enrico, ora, pchampin, Timothe, AndyS, AZ, TallTed, pfps 17:04:03 On IRC I see pfps, AZ, enrico, gkellogg, ora, AndyS, RRSAgent, Zakim, TallTed, ghurlbot, Tpt, agendabot, driib, Timothe, gtw, ktk, rhiaro, csarven, pchampin 17:05:40 scribe+ 17:06:23 exit 17:06:25 scribe- pfps 17:06:28 pfps has left #rdf-star 17:06:52 pfps has joined #rdf-star 17:07:02 present+ 17:07:19 exit 17:08:28 exit 17:08:30 exit 17:08:32 ls 17:08:42 zakim, who is here? 17:08:42 Present: gkellogg, enrico, ora, pchampin, Timothe, AndyS, AZ, TallTed, pfps 17:08:45 On IRC I see pfps, AZ, enrico, gkellogg, ora, AndyS, RRSAgent, Zakim, TallTed, ghurlbot, Tpt, agendabot, driib, Timothe, gtw, ktk, rhiaro, csarven, pchampin 17:09:03 Souri has joined #rdf-star 17:10:14 zakim, pick a scribe 17:10:14 Not knowing who is chairing or who scribed recently, I propose TallTed 17:10:43 scribe+ 17:11:10 doerthe has joined #rdf-star 17:11:19 present+ 17:11:21 topic: Last call's minutes 17:11:24 https://www.w3.org/2023/01/05-rdf-star-minutes.html 17:11:36 wrong link 17:11:45 https://www.w3.org/2023/01/26-rdf-star-minutes.html 17:12:08 s|https://www.w3.org/2023/01/26-rdf-star-minutes.html|| 17:12:17 s/wrong link// 17:12:22 Dominik_T has joined #rdf-star 17:12:35 present+ 17:12:50 +1 17:12:55 +1 17:12:56 present+ 17:12:58 +1 17:12:59 +1 17:13:01 +1 17:13:03 +1 17:13:05 +1 17:13:19 RESOLVED: minutes approved 17:13:36 q+ 17:13:51 q- 17:14:00 q+ 17:14:31 Topic: "RDF 1.2 vs. RDF-star" 17:14:31 AZ: I will not repeat everything I wrote in my email 17:14:31 q+ 17:14:33 ... but the gist of it was that I was suprised when the charter was proposed 17:14:53 ... I think there could be an option to standardize RDF-star and SPARQL-star as a separate standard, 17:15:16 ... leave some time for implementations evolve 17:15:33 ... then standardize RDF 1.2 and SPARQL 1.2 17:15:48 ... this would avoid detrimental impact on other standards built on top of RDF. 17:16:14 ... Then Ora propose that RDF/SPARQL 1.2 would have two kinds of comformance : 17:16:18 q? 17:16:21 ack AZ 17:16:31 ... full (with quoted triples) and weak (no quoted triples). 17:16:47 ack ora 17:16:47 ... I would still prefer the 1st option, but could live with the 2nd option. 17:17:12 q+ 17:17:32 q+ to suggest that this leads to fragmentation in the marketplace. 17:17:46 Ora: I think that this option to have 2 levels of comformance is within what the charter allows us to do. 17:18:04 ... But we should then quickly define what the RDF-star features will be. 17:18:36 ... Given the landscape of graph databases and labeld property graphs, 17:18:42 ... we need RDF-star as a standard. 17:19:06 q? 17:19:08 ... Backward compatibility is really important -- unless we find a very good reason to break it. 17:19:12 ack pchampin 17:20:37 q+ 17:20:40 scribe+ 17:20:48 pchampin: Content Negotiation by Profile https://www.w3.org/TR/dx-prof-conneg/ 17:20:55 ack gkellogg 17:20:55 gkellogg, you wanted to suggest that this leads to fragmentation in the marketplace. 17:21:18 gkellogg: there is a slippery slope here; risk of fragmentation of the marketplace. 17:21:50 ... Also, some implementations would more easily support RDF-star if all quoted triples were asserted. 17:22:04 ... That's another thing to consider. 17:22:11 scribe- 17:22:25 ack ora 17:22:36 ... Technically, this is possible, but let's gather some feedback before we decide to go there. 17:22:52 ora: I appreciate the risk of fragmentation, 17:22:58 ... but the fragmentation may happen anyway. 17:23:04 ... A standard is better than no standard. 17:23:16 q? 17:23:20 ... Profiles seem indeed a right way to go. 17:23:23 q+ 17:23:26 q+ 17:23:35 ack AndyS 17:24:11 AndyS: it would work if we defined RDF 1.2 with a set of profiles for restricting it. 17:24:31 ... It would not work if we had [RDF 1.2 + RDF-star on top of it]. 17:24:47 ack Souri 17:24:50 q+ 17:25:14 Souri: by profile, do you mean the same kind of thing as OWL profiles ? 17:25:18 ack ora 17:25:40 pchampin: yes, that's a good analogy IMO. 17:26:09 ora: but the DX work item is also considering content-negociation, which OWL profiles do not cover. 17:26:47 ... Question to AndyS: can you exmplain what you said earlier about referencing features? 17:26:59 q? 17:27:07 AndyS: when SPARQL 1.1 was standardise, some features were conditional to the (future) publication of RDF 1.1. 17:27:35 ora: we don't need to decide this now. 17:27:47 ... Let's continue the discussion on the mailing list. 17:28:31 Topic: editors assignment 17:28:35 https://github.com/w3c/rdf-star-wg/issues/11 17:29:59 q+ 17:30:36 gkellogg: glad to see so much interest in the existing specs 17:30:57 ... the new ones (rdf-new, sparql-new ...) are typically handled at the end, usually lead by the chairs 17:31:08 ... the sparql-concepts can start from the current sparql11-overview document 17:31:22 q+ 17:31:27 q- 17:31:28 ack gkellogg 17:31:30 ack ora 17:31:42 ... it is generally expected to have more than 1 editor per spec, which we have on most of them 17:31:57 q+ to discuss practical matters 17:32:04 ora: happy to have my name on the *-new documents 17:32:04 ack gkellogg 17:32:04 gkellogg, you wanted to discuss practical matters 17:32:32 q+ 17:32:39 gkellogg: we are in the middle of an experiment of using submodules, which I am currently reverting 17:32:48 https://github.com/w3c/rdf-star-wg/wiki/Editor's-guide 17:32:54 q+ 17:33:00 ... so wait until tomorrow until you start working on the repos. 17:33:12 ... There is also an Editor's guide (link above). 17:33:20 ack ora 17:33:29 ... We had an impromptu call with AndyS and Greg Williams. 17:33:46 ack AndyS 17:33:50 ora: can you send a mail on the mailing list when it is ok to clone? 17:34:10 gkellogg: will do. 17:34:33 q+ to ask about the editors call 17:34:48 q? 17:34:55 ack pchampin 17:34:55 pchampin, you wanted to ask about the editors call 17:35:07 gkellogg: when putting yourself as editor in the Respec document, 17:35:20 ... you need to put your W3C ID in the JSON. 17:35:31 ... This number happens in the URL of your W3C account page. 17:35:50 https://www.w3.org/users/myprofile 17:36:10 All editors MUST have a w3cid field, other uses may include it as well. 17:36:23 q+ 17:36:39 ack ora 17:36:49 ora: this is necessary if you are an editor; not to do pull requests 17:36:53 q+ to ask about non-WG PRs 17:37:00 ack AndyS 17:37:00 AndyS, you wanted to ask about non-WG PRs 17:37:09 gkellogg: the W3C id for editors is required by the W3C validation process. 17:37:33 AndyS: are we accepting PRs from outside the WG participants? If so, how does that work? 17:37:55 gkellogg: if a PR is made by someone external, an intervention is needed 17:38:38 ... to ensire that the contributors comply with the parent policy. 17:38:43 s/ensire/ensure/ 17:39:16 AndyS: if an individual makes a PR, who is an employee of a member organization, 17:39:32 ... how does it work? Has the ACrep of the organization to get involved? 17:39:49 ora: I guess it has to go through the ACrep. 17:40:18 q? 17:40:35 s/parent policy/patent policy/ 17:41:16 action: pchampin to check what happens with contribution from member's employees 17:41:24 Created -> action 13 https://github.com/w3c/rdf-star-wg/issues/13 17:41:38 gkellogg: accept external contributions on a per-case basis 17:41:42 q+ 17:41:57 ack pchampin 17:42:15 ... another class of contributions is the ones by the bots 17:44:11 pchampin: would it make sense to add the editor's ad-hoc calls in the WG calendar? 17:44:33 ... pros: creates awareness; cons: clutters everyone's calendar 17:45:05 gkellogg: different expertise in Respec; we can schedule a call for some kind of "tutorial" 17:45:11 q+ 17:45:18 ack ora 17:45:19 ... but I think that most people who have signed up have some experience in Respec. 17:45:30 ... Don't want to be the "respec dictator". 17:46:45 action: pchampin to propose a doodle for an editors call next week 17:46:46 Created -> action 14 https://github.com/w3c/rdf-star-wg/issues/14 17:47:39 gkellogg: a number of changes will need the group's approval 17:48:00 ... but to move forward, we should not require *every* PR to get the group's approval 17:48:28 ... It is always possible to open an issue if the editor's didn't reflect the group's consensus. 17:48:39 q+ to discuss next week's agenda 17:48:45 ... We might want to be more structured once a FPWD is published. 17:48:55 ack ora 17:48:55 ora, you wanted to discuss next week's agenda 17:49:20 Q+ 17:49:33 ora: almost out of time; anybody wants to talk about use-cases? 17:49:35 ack enrico 17:49:51 topic: Use cases 17:50:04 q+ 17:50:10 enrico: I believe there is a class of use-cases, IMO the typical ones for reification, 17:50:24 ... for which the current formalization does not work. 17:50:59 ... Not saying that what has been proposed is wrong, 17:51:09 ... but that we need something in addition. 17:51:20 ghurlbot has joined #rdf-star 17:51:22 q+ to suggest we have a UCR editor (whether it is formally-W3C-published or not) 17:51:52 ack pfps 17:51:55 q+ 17:52:14 ... Something where reified triples are fully transparents. 17:52:32 ack AndyS 17:52:32 AndyS, you wanted to suggest we have a UCR editor (whether it is formally-W3C-published or not) 17:52:33 pfps: I'm uncomfortable discussing technical details without concrete use-cases. 17:52:34 q- 17:52:45 ... So let's create the use-cases documents quickly. 17:53:14 ack ora 17:53:17 AndyS: suggest to find editors for a UCR document, and create the document. 17:53:49 enrico: I appreciate your contrution to this group, it is needed. 17:53:57 ... Also agree with pfps about use-cases. 17:54:23 ... In favour of AndyS' suggestion. 17:54:23 q? 17:55:12 pchampin: should I add the ucr document in https://github.com/w3c/rdf-star-wg/issues/11 ? 17:55:25 ora: maybe mentioning that it might not get published in the end 17:55:31 ... but still a useful document to have. 17:55:53 ... Thanks everyone, adjourned. 17:56:01 I suggest a doc within the rdf-star-wg repo for the UCR, intended to be delivered as a WG NOTE 17:56:22 RRSAgent, make minutes 17:56:23 I have made the request to generate https://www.w3.org/2023/02/02-rdf-star-minutes.html pchampin 17:57:19 s/prestent+// 17:57:22 s/exit// 17:57:28 s/^ls$// 17:57:30 RRSAgent, make minutes 17:57:32 I have made the request to generate https://www.w3.org/2023/02/02-rdf-star-minutes.html pchampin 17:58:03 s/exit//g 17:59:04 s|https://www.w3.org/2023/01/05-rdf-star-minutes.html|https://www.w3.org/2023/01/26-rdf-star-minutes.html| 18:00:33 s|s/^ls$//|| 18:00:36 RRSAgent, make minutes 18:00:37 I have made the request to generate https://www.w3.org/2023/02/02-rdf-star-minutes.html pchampin 18:01:16 agenda: https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Feb/0021.html 18:01:16 clear agenda 18:01:16 agenda+ Scribe 18:01:16 agenda+ Last call's minutes 18:01:16 agenda+ "RDF 1.2 vs. RDF-star" -question 18:01:16 agenda+ Use cases 18:01:18 agenda+ AOB 18:01:18 RRSAgent, make minutes 18:01:19 I have made the request to generate https://www.w3.org/2023/02/02-rdf-star-minutes.html pchampin 18:08:11 gkellogg has joined #rdf-star 18:24:55 gkellogg has joined #rdf-star 18:35:35 gkellogg has joined #rdf-star 18:37:21 gkellogg_ has joined #rdf-star 18:39:28 gkellogg has joined #rdf-star 18:56:13 gkellogg has joined #rdf-star 19:12:26 gkellogg has joined #rdf-star 19:20:29 gkellogg has joined #rdf-star 19:25:19 gkellogg has joined #rdf-star 19:26:57 gkellogg_ has joined #rdf-star 19:43:40 gkellogg has joined #rdf-star 20:03:23 gkellogg has joined #rdf-star 20:25:47 gkellogg has joined #rdf-star 20:42:43 gkellogg has joined #rdf-star 20:49:20 gkellogg_ has joined #rdf-star