14:45:21 RRSAgent has joined #rdf-star 14:45:21 logging to https://www.w3.org/2021/05/28-rdf-star-irc 14:45:23 RRSAgent, make logs Public 14:45:24 please title this meeting ("meeting: ..."), pchampin 14:45:29 meeting: RDF-star 14:45:33 chair: pchampin 14:45:45 agenda: https://www.w3.org/mid/438dcce8-738c-a690-3327-260ab9277bb9@ercim.eu 14:45:46 clear agenda 14:45:46 agenda+ Announcements and newcomers 14:45:46 agenda+ Admin 14:45:46 agenda+ Open actions 14:45:46 agenda+ Open-ended discussions 14:47:10 Previous meeting: https://w3c.github.io/rdf-star/Minutes/2021-05-21.html 15:00:12 gkellogg has joined #rdf-star 15:00:14 ora has joined #rdf-star 15:00:24 present+ 15:02:04 present+ 15:02:10 present+ 15:02:41 james has joined #rdf-star 15:02:48 present+ 15:02:56 Don't forget - zoom call today. 15:03:04 present+ 15:03:13 thomas has joined #rdf-star 15:04:00 present+ 15:04:01 Reminder that we’re on Zoom this week. 15:05:03 TallTed has joined #rdf-star 15:05:24 regrets: olaf 15:06:04 scribe: gkellogg 15:06:14 zakim, next agendum 15:06:14 agendum 1 -- Announcements and newcomers -- taken up [from agendabot] 15:06:26 q? 15:07:18 pchampin: Olaf had tweeted about an interview on using RDF-star, but haven’t seen a reference. 15:07:25 q? 15:07:29 … Using Ontotext GraphDB? 15:07:34 zakim, next agendum 15:07:34 agendum 2 -- Admin -- taken up [from agendabot] 15:07:36 https://www.synaptica.com/rdf-star-graphdb-graphite/ 15:07:42 present+ 15:08:05 Also - there was a blog from TopQuadrant. 15:08:21 pchampin: I think we’re narrowing the things we have to discuss, and it’s been more convenient to have calls less frequently. I think we can go to one call every two weeks. 15:08:59 +0 15:09:01 q+ 15:09:06 ack AndyS 15:09:24 AndyS: The next objective is to get a community report done. 15:09:42 … I’d think the intro and the SPARQL bits are what remains, both nearlly done. 15:09:45 q+ 15:09:53 … When do we plan that for? 15:10:16 pchampin: Maybe we can defer the change of schedule until after the report is published. 15:10:21 ack thomas 15:10:56 thomas: GitHub has been active lately on semantics and vocabulary. Is there interest in becoming more concrete on semantic extensions? 15:11:29 pchampin: My understanding was that the vocabulary was not blocking for the publishing of the final report (first). 15:11:43 … THe idea is to make it a bit more milestone-ish. 15:12:22 q+ 15:12:22 thomas: I feer it then becomes an afterthought and is left to the WG. I think the extension part should be as concrete as possible. 15:13:02 pchampin: I made a proposal following my action about what issues are considered to be blocking before “Final Report” milestone. 15:13:18 thomas: I’m fine with “milestone”. 15:13:32 pchampin: This was a list of blocking issues, and the vocabulary was not part of it. 15:13:54 … My understanding is that we can discuss the vocabulary afterwards and have other milestones before a final final report. 15:14:13 … It’s good to show progress before an upcoming charter draft. 15:14:40 … I’m not proposing to stop our work after the FR is out. We have some open issues, and my goal is to address them. 15:15:02 q? 15:15:14 thomas: It’s the fring bits of RDF-star that are left, and intrest will deminish. 15:15:25 ack ora 15:16:05 ora: I think the questions of semantics are very important. ONe of the big mistakes with the original RDF spec is that we weren’t very formal, which was rectified later. 15:16:29 … I’m in favor of working on semantic questions, but my feer is that we might want to address issues of schema. 15:16:44 … At this point, it’s not clear how to write a schema that makes use of RDF-star. 15:16:47 q? 15:17:37 pchampin: Regarding the vocabulary, it started with an idea to have a term for the “class” of embedded triples, so that we could describe a property to expect and embedded triple. 15:18:02 … We also had the idea of having a standard way of expressing that something is an instance of a triple in a graph. 15:18:40 … There was a question of what voculary to use, but the key was an IRI expressing the type of an embedded triple. 15:19:33 q+ 15:19:33 … This opens a can of worms; we agreed not to decide where to put the vocabulary, so this is not low-hanging fruit, which is why I preferred to defer until after the next milestone. 15:19:35 q? 15:19:39 q+ 15:19:46 ack thomas 15:20:20 thomas: THe two properties “occurance of” and “in graph” could be defined informally. THat would show how it can/should be done. 15:20:39 q+ 15:20:47 https://w3c.github.io/rdf-star/cg-spec/editors_draft.html#occurrences-example 15:21:20 pchampin: The “in” hides it’s own issues. Is the object a graph, or a graph document, … 15:21:32 thomas: I think it can be solved pragmatically. 15:21:40 q? 15:21:47 pchampin: I’m not sure something ambiguous is better than nothing. 15:21:55 ack ora 15:22:31 ora: I wanted to say I agree with PA, but we have to go there soon. If not now, at least we should have some words to say that something like this is needed. 15:22:47 … I don’t want to end up like the PG community, where there is no schema language. 15:22:54 ack gkellogg 15:22:58 scribe+ 15:23:14 gkellogg: we have to be careful about talking about graphs. 15:23:30 ... RDF does not really provides way to talk about graphs, 15:23:42 ... because the semantics of named graphs is not defined. 15:24:02 ... Talking about the default graph is sometimes done with <>. 15:24:17 q+ 15:24:31 ack thomas 15:24:56 thomas: If it can be done in SPARQL, that’s good enough for me. 15:25:10 pchampin: Can we make such a comitment for RDF? 15:25:31 thomas: We could use mild terms to suggest that it could/should be done. 15:26:34 gkellogg: some groups (VC) depend on the ability to use the graph name to identify it 15:26:48 ... If we need to define that, then it needs to be in the charter. 15:26:56 ... Certainly will attract people. 15:27:40 q+ 15:27:42 pchampin: Back to the final report, I propose to add a chapter on the RDF-star vocabulary, but only reference the open issues plus some non-normative notes about being addressed in the future. 15:28:15 STRAWPOLL: have a "placeholder" section about the RDF-star vocabulary, containing links to the issues 15:28:21 +1 15:28:23 +1 15:28:32 +1 15:29:21 +1: Many issues raised are wider than RDF-star. A placeholder seems the way to go. (Separate RDF-DEV group?) 15:29:26 james: I’m perplexed as to the reluctance for using SPARQL expressions when so much work has been done. Even if you don’t know the consequences, it would help the discourse. 15:29:44 … It would be worth to have this discussion in the chapter. 15:30:12 pchampin: I’m reluctant to make it a blocking condition on the milestone final report. After it’s published, I think we should address it. 15:30:34 james: Then why not put it in now? I’d like to make it as concrete as possible ASAP. 15:30:55 pchampin: My feeling is that it may draw us into discussions that will further delay the milestone. 15:30:58 +1 15:31:08 +1 15:31:53 +0 15:31:57 how many "final reports" are there? what differentiates a first "final report" from others? will they be marked as molestones? 15:32:20 q+ 15:32:26 ack james 15:32:29 pchampin: I don’t know how many, just that we don’t exclude the possibility of having another one in the future. 15:32:33 q? 15:32:55 ack thomas 15:33:20 thomas: I see the time pressure, but if it’s named “Final Report”, I don’t see how we have several of them. 15:34:33 gkellogg: We’re bound by the set of possible W3C document types, “draft” and “final”. 15:35:18 thomas: We could try to get the vocabulary right as James or I have proposed for the next 2-3 weeks. If we don’t get agreement, then we can defer, otherwise try to include. 15:35:36 q? 15:36:59 nb. i am not even proposing that we get it "right", just the the document indicates some application of the terms 15:37:35 thomas: Can we agree to work on it over the next three weeks? 15:37:55 pchampin: This work is a side-project for all of us, so we don’t have strict deadlines anyway. 15:38:03 q+ 15:38:11 ack AndyS 15:39:12 AndyS: We can have multiple final reports, or split it into parts. Delaying on this point ... 15:39:45 … I think it will interest other people, and we had an agreement on the process, but if we keep changing it, I lose confidence. 15:40:15 q+ 15:40:16 pchampin: Our first priority is to get a report out, and wanted to mention the section even if it’s not complete. 15:40:42 … It’s a question of what the editor’s prorities are in the coming weeks. Merging the current PRs or working on a new PR. 15:41:01 q? 15:41:13 ack thomas 15:41:41 thomas: I feel that more people want to postpone it, but I feer that it will be postponed for a long time. 15:42:02 pchampin: That’s reallly not the goal, there is a section that will need to be filled. 15:42:38 STRAWPOLL: change to a call every 2 weeks start now 15:42:51 +1 15:42:59 +0 15:43:04 +0 15:43:12 0 15:43:14 +0 15:43:20 -1 for a few more weeks 15:43:28 +0.8 15:44:11 i could change my vote to -0.5 15:44:15 let's postpone that decsion 15:44:48 zakim, next agendum 15:44:48 agendum 3 -- Open actions -- taken up [from agendabot] 15:44:58 https://github.com/w3c/rdf-star/issues?q=is%3Aopen+is%3Aissue+label%3Aaction 15:45:28 https://github.com/w3c/rdf-star/issues/121 15:45:29 pchampin: PR #121 has a lot of work done. 15:46:03 gkellogg: some wordsmithing issues left, but I'm astisfied with the substance 15:46:15 ... I have always found SPARQL equality challenging 15:46:37 AndyS: There are some more minor changes needed. 15:46:37 ... I'm passing all the tests. 15:47:08 … It’s important to have a stable ordering. 15:47:12 q? 15:47:18 https://github.com/w3c/rdf-star/issues/164 15:47:48 pchampin: Next was #1164 on Sparql Service Description. I’ll reference that in the TBD section. 15:47:55 https://github.com/w3c/rdf-star/issues/166 15:48:36 … The section on the rationale for transparence/opacity. I noticed that PRs fail on CI, while AndyS’s succeeds. 15:49:13 AndyS: I avoided a lot of ReSpec features and just wrote raw HTML. I didn’t have the energy on how to drop in. 15:50:40 .. In addition to ARIA, there’s an empty-ID warning. 15:52:02 pchampin: To be clear, the idea is that the different semantics proposed in the document could be seen as layers of semantic extensions on top of the first one. 15:52:10 q+ 15:52:17 ack thomas 15:52:19 … I didn’t think that would cause too much discussion, 15:52:57 thomas: I saw this as marketing. I made a mistake in an answer. I had some things mixed up. I still don’t like what we’re doing. 15:53:09 … You’re leaving out common-sense entailments. 15:53:49 … I’m not as concerned about it now, but I’d be much happier if we could point to something about semantic extensions, but we don’t have that now. 15:54:33 pchampin: I don’t want to have the debate about which is best, because we agreed to say that there was no concensus in the group. You might use this as a semantic extension, or as a replacement, but we couldn’t agree. 15:55:18 … The term has a precise definition in the RDF spec. The alternative sematncis work on top of the opaque semantics. 15:55:32 thomas: I’m refering to my discussions with olaf. 15:55:50 pchampin: I’m just try to get to the point where we can merge the PR. 15:56:17 … We’ll need to continue on GitHub. The goal was to see if we can make progress. 15:56:21 https://github.com/w3c/rdf-star/issues/168 15:56:30 https://github.com/w3c/rdf-star/issues/175 15:56:31 pchampin: The charter hasn’t progressed. 15:57:01 … We haven’t done anything on the media-type or conneg discussions yet. 15:57:47 … AndyS mentioned that it could break some things. 15:57:56 q+ 15:58:23 ack james 15:58:55 james: WRT #175, AndyS requested that it introduce an issue in the sparql-12 group, which I have. 15:59:20 james - thx 15:59:41 thomas: Any feedback on my proposal? 16:00:24 pchampin: I see where you’re going. Having an alternative syntax for transparency is interesting, but until we’ve agreed on the vocabulary, I think it’s too early. 16:01:13 … I think the issue raised by pfps on non-obvious ramifications is a bit embarassing, 16:01:48 … It is dependent on our agreeing on transparency. 16:01:50 q? 16:07:46 zakim, end meeting 16:07:46 As of this point the attendees have been james, jbollema, ora, gkellogg, thomas, AndyS, olaf, pchampin, TallTed, rivettp 16:07:49 RRSAgent, please draft minutes 16:07:49 I have made the request to generate https://www.w3.org/2021/05/28-rdf-star-minutes.html Zakim 16:07:52 I am happy to have been of service, gkellogg; please remember to excuse RRSAgent. Goodbye 16:07:56 Zakim has left #rdf-star 16:08:26 rrsagent, bye 16:08:26 I see no action items