16:04:04 RRSAgent has joined #rdf-star 16:04:08 logging to https://www.w3.org/2023/08/31-rdf-star-irc 16:04:08 RRSAgent, make logs Public 16:04:09 present+ 16:04:09 please title this meeting ("meeting: ..."), gkellogg 16:04:09 present+ 16:04:09 present+ 16:04:09 present+ 16:04:10 present+ 16:04:18 present+ 16:04:19 present+ 16:04:25 present+ 16:04:51 chair: ora 16:06:08 present+ 16:06:30 Ora: let us put a link to the scribe list in the agenda 16:06:34 previous meeting: https://www.w3.org/2023/08/24-rdf-star-minutes.html 16:06:44 next meeting: https://www.w3.org/2023/09/07-rdf-star-minutes.html 16:07:26 we did not declare the scribe 16:07:34 sctibe: olaf 16:07:39 scribe: olaf 16:08:09 agenda: https://www.w3.org/events/meetings/931e4e54-81ad-4aa3-a39f-84efe4b788c7/20230831T120000/#agenda 16:08:09 clear agenda 16:08:09 agenda+ Scribe: Haudebourg, Timothée (alternate: Patel-Schneider, Peter) 16:08:09 agenda+ Approval of last week's minutes: -> 1 https://www.w3.org/2023/08/24-rdf-star-minutes.html 16:08:09 agenda+ Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 16:08:10 agenda+ Review of pull requests, available at -> 3 https://github.com/orgs/w3c/projects/20/views/4 16:08:13 agenda+ Issue Triage, available at -> 4 https://github.com/orgs/w3c/projects/20/views/5 16:08:16 agenda+ Any Other Business (AOB), time permitting 16:08:28 zakim, open item 2 16:08:28 agendum 2 -- Approval of last week's minutes: -> 1 https://www.w3.org/2023/08/24-rdf-star-minutes.html -- taken up [from agendabot] 16:08:41 minutes look ok 16:08:58 proposal: approve last week's minutes 16:09:01 0 16:09:01 ora: anyone any worries about last week's minutes? 16:09:04 +1 16:09:05 +1 16:09:06 Souri has joined #rdf-star 16:09:09 +1 16:09:10 +1 16:09:12 +1 16:09:13 +1 16:09:16 present+ 16:09:19 +1 16:09:28 +1 16:09:29 +1 16:09:45 resolved: approve last week's minutes 16:10:13 zakim, open item 3 16:10:13 agendum 3 -- Review of open actions, available at -> 2 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot] 16:10:53 AZ: I added a new message with a proposal for the 'compliance' question 16:11:25 ... the proposal contains a "RDF 1.2 Basic" profile 16:11:34 ... and "RDF 1.2 Full" 16:11:47 ... where the former excludes quoted triples 16:12:08 q+ 16:12:25 ... Then, for the various specs, there need to be statements saying that "this piece is not needed for Basic" 16:12:33 q+ 16:12:42 q+ 16:12:46 ... Question was how this would affect SPARQL. 16:12:48 ack pchampin 16:13:11 pchampin: Regarding concrete syntaxes 16:13:44 ... why do we need to say something there, rather than just saying which profile one is in. 16:14:05 AZ: not strictly needed but good for clarity 16:14:18 pchampin: Okay, it would helpful 16:14:47 ora: Are we going to have all possible combinations when SPARQL comes in the picture? 16:14:50 ack AndyS 16:15:11 ack gkellogg 16:15:18 AndyS: I thought we are talking only about RDF Basic and the corresponding effect on the abstract syntax 16:15:19 q+ 16:15:39 richard-lea has joined #rdf-star 16:15:47 present+ 16:15:53 gkellogg: If I have a Turtle parser, do I have to parameterize it to only emit RDF 1.2 Basic? 16:16:18 ... How to communicate that a parser can have two modes? 16:16:27 q+ 16:16:46 ... What happens if one merges a "Basic" graph and a "Full" one? 16:17:13 ... Can SPARQL "Basic" be used to query a "Full" graph? 16:17:24 ora: So, it is indeed more components. 16:17:26 q+ 16:17:46 gkellogg: Reasoners are another issue. 16:17:59 ... It becomes a combinatorial issue. 16:18:18 ack AndyS 16:18:24 ... We need to treat lightly. 16:19:02 AndyS: For RDF, we could put a note in all the grammars. That should be practically possible. 16:19:36 TallTed has joined #rdf-star 16:19:55 ... For SPARQL, the challenge is whether we actually need it. 16:20:22 ... It gives all different combinations, and it affects the result formats as well. 16:20:27 ack AZ 16:21:00 AZ: For the serialization formats, it may not be necessary. Just for clarification. 16:21:24 ... I imagine these two profiles to be similar to the OWL profiles. 16:21:35 ... For OWL, there are more profiles. 16:21:51 ... and it doesn't make things more complicated. 16:22:08 TallTed has changed the topic to: RDF-star 2023-08-31 Agenda: https://www.w3.org/events/meetings/931e4e54-81ad-4aa3-a39f-84efe4b788c7/20230831T120000/ 16:22:20 ... Regarding SPARQL, I agree we should keep it simple. Not a "SPARQL Basic" 16:22:27 ack niklasl 16:22:32 ... but we need some text in the SPARQL spec. 16:22:42 RRSAgent, draft minutes 16:22:43 I have made the request to generate https://www.w3.org/2023/08/31-rdf-star-minutes.html TallTed 16:22:50 present+ 16:22:54 niklasl: I agree with gkellogg that there are a bunch of problems in this. 16:23:06 RRSAgent, make logs public 16:23:15 ... A question is, how does "RDF 1.2 Basic" related to RDF 1.1? 16:23:34 gkellogg: text direction may be a difference from RDF 1.1 16:23:37 q+ 16:23:48 present+ AZ 16:23:49 q+ 16:23:57 ack ora 16:24:24 s/sctibe: olaf// 16:24:32 ora: We don't have any profiles right now. So, we need some baseline. It makes sense to include in such a baseline all those little fixes we are doing. 16:24:57 Current RDF 1.1/1.2 changes: https://www.w3.org/TR/rdf12-concepts/#changes-12 16:26:08 niklasl: Another thing would be that a parser could parse TriG-star into RDF 1.1 16:26:56 ... It is necessary to track how "RDF 1.2 Full" is used in the wild. 16:27:45 ... You might have a parser that converts TriG-star into reification statements. 16:27:54 even in the CG report, unstar(G) does not have the same meaning as G 16:27:59 AndyS: Shouldn't that better be seen as a transformation. 16:27:59 ack gkellogg 16:28:00 w3c/rdf-concepts#34 16:28:01 https://github.com/w3c/rdf-concepts/issues/34 -> Issue 34 Terminology for graph/dataset without quoted triples. (by gkellogg) 16:28:12 gkellogg: We have an issue on terminology here. 16:28:43 q+ 16:28:50 ... We need terminology to be able to talk about triples that do not contain quoted triples, etc. 16:29:36 q+ 16:29:38 ... Regarding transformations, there may be no practical way to "round trip" 16:29:50 ack AndyS 16:29:52 AndyS: You can do the reverse process. 16:30:10 ... How is Issue 34 different? 16:31:05 gkellogg: Such terminology can be useful; in particular, for talking about profiles. 16:31:05 ack niklasl 16:31:16 niklasl: Yes that's important. 16:31:29 ... I am concerned with backwards compatibility. 16:31:48 ... Is the notion of profiles useful for us to distinguish? 16:32:07 q+ 16:32:12 ... I have talked to people who are worried when I tell them that there will be profiles in RDF. 16:32:32 ... I compare the unstar process to how RDF Lists have been handled. 16:32:49 ... as syntactic sugar 16:33:35 ack ora 16:33:37 "lean" also exists, but it is something different 16:33:38 AndyS: There is a notion of well-formed for RDF lists, but I don't think it is officially defined. 16:33:53 niklasl: Yes, so it might be useful to have well-formed reification. 16:33:59 https://www.w3.org/TR/rdf11-mt/#dfn-lean 16:34:26 ora: How do the 1.2 profiles relate to 1.1? 16:34:30 q? 16:34:50 ... e.g., does supporting 1.2 Basic require supporting 1.1? 16:34:54 gb, status 16:34:54 pchampin, the delay is 15, issues are on, names are on; and the repositories are https://github.com/w3c/rdf-common https://github.com/w3c/rdf-concepts https://github.com/w3c/rdf-n-quads https://github.com/w3c/rdf-n-triples https://github.com/w3c/rdf-new https://github.com/w3c/rdf-primer 16:34:54 … https://github.com/w3c/rdf-schema https://github.com/w3c/rdf-semantics https://github.com/w3c/rdf-star-wg https://github.com/w3c/rdf-trig https://github.com/w3c/rdf-turtle https://github.com/w3c/rdf-ucr https://github.com/w3c/rdf-xml https://github.com/w3c/sparql-concepts 16:34:55 … https://github.com/w3c/sparql-entailment https://github.com/w3c/sparql-federated-query https://github.com/w3c/sparql-graph-store-protocol https://github.com/w3c/sparql-new https://github.com/w3c/sparql-protocol https://github.com/w3c/sparql-query https://github.com/w3c/sparql-results-csv-tsv 16:34:58 … https://github.com/w3c/sparql-results-json 16:35:16 ... I realize that this issue is more complication than I initially thought. 16:35:41 gb, use w3c/rdf-star-wg 16:35:42 pchampin, OK. 16:36:23 q+ 16:36:28 ... Should we define the compliance in terms of these difference "components" (parts of the overall set of specs) when they define different profiles? 16:36:33 ack pchampin 16:36:45 ... I start to think the answer to this question is yes. 16:36:49 pchampin: yes 16:38:05 ... Regarding niklasl concerns, the boundary between the profiles should be such that the transition from 1.1 to 1.2 is as smooth as possible (for system that have not (yet) implemented support for quoted triples). 16:38:06 q+ 16:38:14 ack niklasl 16:38:32 ... To give some ground to what kind of compliance can be expected. 16:39:18 niklasl: It is also not fully determined what the RDF-star part exactly is (semantics!) 16:39:32 ... generally, it should be made as less complex as possible 16:39:41 ora: other actions? 16:39:54 pchampin: The ones marked as complete can be closed. 16:40:14 ... The PRs of rdf-tests appear on the dashboard now. 16:40:24 ... No progress on Action 77 16:40:42 ... Configutration of Github is still a mystery to me. 16:41:13 s/Github/Github bot 16:41:13 gb, status 16:41:13 pchampin, the delay is 15, issues are on, names are on; and the repositories are https://github.com/w3c/rdf-star-wg https://github.com/w3c/rdf-common https://github.com/w3c/rdf-concepts https://github.com/w3c/rdf-n-quads https://github.com/w3c/rdf-n-triples https://github.com/w3c/rdf-new 16:41:13 … https://github.com/w3c/rdf-primer https://github.com/w3c/rdf-schema https://github.com/w3c/rdf-semantics https://github.com/w3c/rdf-trig https://github.com/w3c/rdf-turtle https://github.com/w3c/rdf-ucr https://github.com/w3c/rdf-xml https://github.com/w3c/sparql-concepts 16:41:14 … https://github.com/w3c/sparql-entailment https://github.com/w3c/sparql-federated-query https://github.com/w3c/sparql-graph-store-protocol https://github.com/w3c/sparql-new https://github.com/w3c/sparql-protocol https://github.com/w3c/sparql-query https://github.com/w3c/sparql-results-csv-tsv 16:41:17 … https://github.com/w3c/sparql-results-json 16:41:21 q? 16:41:59 pchampin: I don't know what changes the order of the repos in github bot 16:42:17 ... The last action then is about the "last version" of each spec. 16:42:34 ... What "last version" means is not fully clear. 16:42:51 ... It may refer to the last published version. 16:43:03 q+ 16:43:10 q+ 16:43:38 ... There may be some "accidents" in some of the 1.0 docs. 16:43:48 ack ora 16:43:49 ... I have asked the W3C Web masters 16:44:05 ... When they come back, we can decide to fix the ones that are broken. 16:44:27 q+ 16:44:40 ack gkellogg 16:45:15 gkellogg: W3C is inconsistent with the numbering and the popups that point to newer versions. 16:45:43 ... we should do both 16:45:57 ack AndyS 16:46:07 ... it is a question for the documents team, but we should try to be consistent 16:46:56 AndyS: A comment from the community was that the 'latest' link should go to the latest published version, not to the latest working draft. 16:47:00 "Latest version" is ambiguous. "Latest published version" and "Latest editor's draft" would be clearer. 16:47:18 ora: It seems there are two equally natural notions of what "latest" means. 16:47:39 q? 16:47:46 gkellogg: What JSON-LD there is a latest published version, and latest recommendation 16:48:08 +1 for latest published Rec. (highest number with Rec status) 16:48:13 ... I don't think here is the place to discuss/decide how these things are supposed to work. 16:48:20 ... We should call for clarification. 16:49:02 pchampin: Okay, I keep Action 84 open and will get back to the group once the Web masters have replied. 16:49:37 Topic: what to discuss atTPAC 16:49:53 ora: AndyS wanted to discuss what to do at TPAC. 16:50:11 q+ 16:50:14 AndyS: We have limited amount of time at TPAC and we should use that time well. 16:50:27 ack gkellogg 16:50:29 ora: We still have two weeks to decide. 16:50:52 gkellogg: There are three major topics that overlap with I18N 16:51:04 ... we should have a joint meeting with them 16:51:31 ... Having an agenda beforehand would be helpful 16:51:43 ... in particular for people who plan to join remotely. 16:52:21 AndyS: In terms of items, the semantics needs to advance. I am hoping that the semantics task force comes out with a proposal. 16:52:53 ... Additionally, I would like to schedule some time for the most controversial outstanding issues for SPARQL. 16:53:35 ora: If you have opinions of what should be put on the agenda, mention it on the mailing list. 16:53:50 ... We will then put together a tentative agenda. 16:54:22 the label "discuss-f2f" is already available on all our repos 16:54:33 gkellogg: What has been useful in the past is to have topics for which specific people can present. 16:54:51 AndyS: Do we have a time booked with the I18N folks? 16:55:05 ora: I will ping him (?) again. 16:55:25 ... Is https://github.com/w3c/rdf-star/issues/275 the one about sparql `exists`? 16:55:26 AndyS: What part of the day would work best for you? 16:55:38 s/him/Addison (I18N) 16:55:39 q+ 16:55:41 gkellogg: 12pm until ... 16:55:45 ack pchampin 16:57:00 pchampin: Regarding gkellogg's suggestion, should we add a new type of "f2f" tag/label that people can use to tag issues in the repos that they want to discuss during the F2F at TPAC? 16:57:18 https://github.com/w3c/sparql-query/issues/72 ? 16:57:53 RRSAgent, make minutes 16:57:54 I have made the request to generate https://www.w3.org/2023/08/31-rdf-star-minutes.html pchampin 16:58:10 https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Aug/0024.html 16:58:28 olaf has left #rdf-star 16:58:52 https://github.com/w3c/sparql-query/issues/ 17:09:21 gkellogg has joined #rdf-star 17:09:51 Zakim, end meeting 17:09:51 As of this point the attendees have been AZ, gtw, niklasl, draggett, gkellogg, AndyS, ora, pchampin, Amin_Anjomshoaa, olaf, Souri, richard-lea, TallTed 17:09:54 RRSAgent, please draft minutes 17:09:56 I have made the request to generate https://www.w3.org/2023/08/31-rdf-star-minutes.html Zakim 17:10:02 I am happy to have been of service, TallTed; please remember to excuse RRSAgent. Goodbye 17:10:02 Zakim has left #rdf-star 17:10:06 RRSAgent, bye 17:10:06 I see no action items meeting: RDF-star WG weekly meeting next meeting: https://www.w3.org/2023/09/12-rdf-star-minutes.html