17:00:04 RRSAgent has joined #rdf-star 17:00:08 logging to https://www.w3.org/2022/12/22-rdf-star-irc 17:00:26 present+ ora 17:00:31 present+ 17:00:36 present+ 17:00:36 zakim, this will be rdf-star 17:00:36 ok, ora 17:00:45 Enrico has joined #rdf-star 17:00:53 p+ 17:01:09 Meeting: RDF-star WG teleconference 17:01:14 RRSAgent, draft minutes 17:01:16 I have made the request to generate https://www.w3.org/2022/12/22-rdf-star-minutes.html TallTed 17:01:22 zakim, who is present? 17:01:22 I don't understand your question, AndyS. 17:01:23 RRSAgent, make logs public 17:01:36 Zakim, who's here? 17:01:36 Present: ora, TallTed, AndyS 17:01:38 On IRC I see Enrico, RRSAgent, Zakim, ora, TallTed, AndyS, ghurlbot, driib, agendabot, pchampin, Tpt, Timothe, gtw, ktk, rhiaro, csarven 17:01:49 Chair: ora 17:01:51 present+ Enrico 17:02:03 present+ Enrico 17:02:31 gkellogg has joined #rdf-star 17:02:50 present+ 17:03:19 Zakim, who's here? 17:03:19 Present: ora, TallTed, AndyS, Enrico, gkellogg 17:03:23 On IRC I see gkellogg, Enrico, RRSAgent, Zakim, ora, TallTed, AndyS, ghurlbot, driib, agendabot, pchampin, Tpt, Timothe, gtw, ktk, rhiaro, csarven 17:03:45 Folks, please do "present+" if you are present 17:04:13 Souri has joined #rdf-star 17:04:18 present+ 17:06:20 Scribe: AndyS 17:06:28 Dominik_T has joined #rdf-star 17:06:59 present+ 17:07:01 ora: Naming proposal 17:07:11 Topic: Naming Proposal 17:07:12 chair: ora 17:07:58 halfway there -- https://lists.w3.org/Archives/Public/public-rdf-star-wg/2022Dec/ 17:08:33 https://lists.w3.org/Archives/Public/public-rdf-star-wg/2022Dec/0017.html 17:08:33 ... Pierre-Antoine proposal (action item) 17:09:25 https://lists.w3.org/Archives/Public/public-rdf-star/2022Dec/0000.html 17:10:03 gkellogg: Should we be called "RDF WG" given the wider scope of work? 17:10:39 ... consolidate rdf-star, rdf-star-wg mailing lists 17:10:59 tallted: rename rdf-star as rdf-star-cg 17:11:31 ... merging does not make sense as different communities 17:12:06 q+ 17:12:07 gkellogg: Can we have W3C systeam fwd emails automatically? 17:12:31 ack ora 17:13:02 ora: distinction escape most people. 17:13:14 s/escape/escapes/ 17:13:39 tallted: task force of RDF-star still exists. 17:14:47 ora: Mailing list discussions should go to the public-rdf-star-wg 17:14:58 ora: spec names ... 17:15:17 q+ 17:15:28 ack gkellogg 17:15:54 gkellogg: Precedence is "rdf12-*" 17:16:20 ... with "sparql12-*" as "rdf-sparql-*" isn't so short. 17:16:48 ... version 12 issues are a long way out. 17:17:32 ... previous names - current specs reference previous versions. 17:17:40 q+ 17:17:47 ack AndyS 17:17:54 scribe+ gkellogg 17:18:19 andys: what didn't fix was the original 1.0 specs; I suggest we make those consistent. 17:18:43 ... That was for the old sparql 1.0 spec. 17:18:50 SPARQL 1.0 - rdf-sparql-query 17:18:57 ... All older specs should forward to the proper location. 17:18:58 q+ 17:19:05 +1 make all the versionless names redirect to the latest versioned doc 17:19:26 (instead of making the user manually click through) 17:19:39 ack gkellogg 17:20:16 gkellogg: json-ld experience - systeam ensured jsonld* goes to json-ld 1.,1 specs. 17:20:37 ... normal W3C systeam work process 17:20:38 s/1.,1/1.1/ 17:21:06 q+ 17:21:49 https://www.w3.org/TR/rdf-sparql-query/ 17:21:49 sparql-query should eventually be the same as sparql12-query. sparql10-query should be the same as the former rdf-sparql-query. 17:22:49 ora: clarification of all detail needed. 17:23:22 gkellogg: ask team contact to check with the W3C system team. 17:23:39 action: staff contact to refine the naming proposal per WG's discussion 17:23:49 I think https://www.w3.org/TR/rdf12-sparql12-query/ will be the appropriate new target, which becomes the redirect from https://www.w3.org/TR/rdf-sparql-query/ (which should be formally moved to https://www.w3.org/TR/rdf10-sparql10-query/) 17:25:16 Topic: Enrico's thoughts on modal logic 17:25:32 I agree with Ted. 17:25:48 https://lists.w3.org/Archives/Public/public-rdf-star-wg/2022Dec/0055.html 17:27:57 Enrico: (from email) the fact < :messi :scores :last-WC22-goal > is (1) true in the current world/graph, and (2) it corresponds to the existence of a resource over which we can predicate additional facts 17:28:55 q+ 17:29:02 q- 17:30:15 q+ 17:33:33 q+ 17:33:58 q+ 17:34:47 ack ora 17:35:03 ora: need to discuss this work 17:35:30 ... are you suggesting current RDF reification should be revisited? 17:35:48 Enrico: current reification is not defined. 17:36:24 ora: modal logic mentioned in RDF originally but little interest at the time. 17:37:24 ack ora 17:38:43 q+ 17:39:08 need to move on the queue 17:40:20 ack gkellogg 17:41:12 gkellogg: transparent/opacity In RDF-* not RDF-star, triple is asserted. 17:42:15 ... this is something the TF considered. The <<>> is a syntax the triple without asserting it implicitly. 17:43:14 ... <<>> is not a context - that is layered via modeling or via named graphs to keep apart 17:43:41 ack TallTed 17:43:49 q+ 17:44:11 ... with our input <<...>> would be need to be asserted as well if intended. 17:44:41 tallted: RDF-* only considered one case - less used by people in the world. 17:45:17 ... the <<>> are like "words" 17:45:36 ... we need to work with data that exists today 17:46:04 ... not require everyone to redo their RDF. 17:47:15 q+ 17:47:16 ack Souri 17:47:25 ... can say "the sun is black" in a separate named graph to keep things apart 17:47:45 souri: agree with TallTed 17:47:53 ... quoted triple useful 17:48:24 ... need to capture multiple occurences 17:48:31 q- 17:49:46 ... foreign key needs a "name for the triple" 17:52:02 ack AndyS 17:52:03 A graph label is a name. 17:52:19 ... multiple instances of the same triple 17:54:55 ack enrico 17:57:01 Burton+Taylor marriages are a useful foil for the modeling discussion. You *don't know* that your model is broken until their second marriage -- and if you "properly model" for the second (and future), you must also *remodel* all your existing marriage data, for all previous marriages of all previous spouses 17:57:16 q+ 17:57:33 No-one will do this. They will find that RDF is indeed too complicated for their use, and they will move on. That would be bad for everyone. 17:58:01 ora: Happy Holidays 17:59:08 I agree with Ted. 17:59:17 ora: Please continue on the mailing list 17:59:32 zakim, bye 17:59:32 leaving. As of this point the attendees have been ora, TallTed, AndyS, Enrico, gkellogg, Souri, Dominik_T 17:59:32 Zakim has left #rdf-star 17:59:53 Zakim has joined #rdf-star 17:59:53 rrsagent, make logs public 18:00:02 RRSAgent, draft minutes 18:00:03 I have made the request to generate https://www.w3.org/2022/12/22-rdf-star-minutes.html TallTed 18:00:09 rrsagent, draft minutes 18:00:10 I have made the request to generate https://www.w3.org/2022/12/22-rdf-star-minutes.html ora 18:00:46 Zakim, end meeting 18:00:46 As of this point the attendees have been (no one) 18:00:46 RRSAgent, please draft minutes 18:00:47 I have made the request to generate https://www.w3.org/2022/12/22-rdf-star-minutes.html Zakim 18:01:22 I am happy to have been of service, TallTed; please remember to excuse RRSAgent. Goodbye 18:01:22 Zakim has left #rdf-star 18:01:22 rrsagent, bye 18:01:22 I see 1 open action item saved in https://www.w3.org/2022/12/22-rdf-star-actions.rdf : 18:01:22 ACTION: staff contact to refine the naming proposal per WG's discussion [1] 18:01:22 recorded in https://www.w3.org/2022/12/22-rdf-star-irc#T17-23-39 18:01:23 rrsagent, pelase excuse us 18:01:23 I'm logging. I don't understand 'pelase excuse us', AndyS. Try /msg RRSAgent help 18:01:23 rrsagent, please excuse us 18:01:23 I see 1 open action item saved in https://www.w3.org/2022/12/22-rdf-star-actions.rdf : 18:01:23 ACTION: staff contact to refine the naming proposal per WG's discussion [1] 18:01:23 recorded in https://www.w3.org/2022/12/22-rdf-star-irc#T17-23-39