14:38:07 RRSAgent has joined #rdf-star 14:38:07 logging to https://www.w3.org/2021/04/30-rdf-star-irc 14:38:09 RRSAgent, make logs Public 14:38:10 please title this meeting ("meeting: ..."), pchampin 14:38:16 meeting: RDF-star 14:38:19 chair: pchampin 14:38:32 agenda: https://lists.w3.org/Archives/Public/public-rdf-star/2021Apr/0008.html 14:38:32 clear agenda 14:38:32 agenda+ Announcements and newcomers 14:38:32 agenda+ Open actions 14:38:32 agenda+ PR 161: Media-types 14:38:32 agenda+ PR 162: Semantics 14:38:34 agenda+ Open-ended discussions 14:38:46 Previous meeting: https://w3c.github.io/rdf-star/Minutes/2021-04-23.html 14:38:53 Next meeting: https://w3c.github.io/rdf-star/Minutes/2021-05-07.html 14:47:27 AndyS has joined #rdf-star 14:47:34 Hi 14:48:01 hi 14:48:34 AndyS has joined #rdf-star 14:57:09 TallTed has joined #rdf-star 14:57:47 Julian has joined #rdf-star 14:59:36 james_ has joined #rdf-star 14:59:59 gatemezing has joined #rdf-star 15:00:12 gkellogg has joined #rdf-star 15:00:51 olaf has joined #rdf-star 15:01:52 present+ 15:02:16 present+ 15:02:45 present+ 15:02:53 present+ 15:03:06 thomas has joined #rdf-star 15:03:31 present+ 15:04:12 present+ 15:04:19 present+ 15:05:01 scribe: olaf 15:05:03 "not knowing who has scribed, I nominate Ora" 15:05:11 zakim, next agendum 15:05:11 agendum 1 -- Announcements and newcomers -- taken up [from agendabot] 15:05:48 pchampin: RDF-star will be presented at the KGC 15:05:52 present+ 15:06:05 q? 15:06:10 zakim, next agendum 15:06:10 agendum 1 was just opened, pchampin 15:06:35 zakim, agendum 2 15:06:35 I don't understand 'agendum 2', pchampin 15:06:38 zakim, next agendum 15:06:38 agendum 2 -- Open actions -- taken up [from agendabot] 15:07:02 https://github.com/w3c/rdf-star/issues?q=is%3Aopen+is%3Aissue+label%3Aaction 15:07:09 pchampin: no pending actions on github 15:07:31 andys: checkup on the issue about the SPARQL-star grammar 15:07:52 https://github.com/w3c/rdf-star/issues/163 15:08:02 pchampin: the grammar is not complete 15:08:21 ... double-pointy brackets for expressions are missing 15:08:29 I've made it an "action" and assigned it to myself. 15:08:51 q? 15:09:08 AndyS: wrapped up about organizing the manifests 15:09:13 ... has been merged 15:09:18 q? 15:09:29 zakim, next agendum 15:09:29 agendum 3 -- PR 161: Media-types -- taken up [from agendabot] 15:09:58 pchampin: wrote a section based on discussion from last week 15:10:22 ... including a listing of pros and cons of the different approaches 15:10:37 ... and clarification that the group didn't reach consensus 15:10:52 ... Hope that all arguments are captured 15:11:10 q? 15:11:18 q+ 15:11:26 ack thomas 15:11:46 thomas: question: what ways are there to make explicit that an endpoint supports SPARQL-star? 15:12:14 q+ 15:12:29 ack gkellogg 15:12:34 pchampin: no answer 15:12:49 https://example.org/sparql -> https://example.org/sparql-star :-) 15:12:55 gkellogg: it would be reasonable to add something for a SPARQL-star service description 15:13:09 +1 to add a SPARQL service description 15:13:09 https://www.w3.org/TR/sparql11-service-description 15:13:45 https://www.w3.org/TR/sparql11-service-description/#sd-feature 15:13:52 ... retrieving the service descr. is not part of the protocol 15:14:18 https://www.w3.org/TR/sparql11-service-description/#sd-resultFormat 15:14:37 ... it's a machine-readable approach 15:14:38 It's not currently part of "every client's" activity; more part of advanced client's activity, when they're looking for a specific (typically more advanced) feature 15:15:31 pchampin: we may define an IRI for a SPARQL-star feature 15:15:42 ... to be used in such service description 15:15:59 ... and then encourage providers to include it in their service descr. 15:16:15 the "standard" features are described in the service description recommendation 15:16:28 AndyS: another use of the service descr. ... 15:16:34 ... used by aggregators 15:16:38 more details, including example features -- https://www.w3.org/TR/sparql11-service-description/#sd-Feature 15:17:14 ora has joined #rdf-star 15:17:16 Action: pchampin to add a paragraph on SPARQL service description and sd:feature 15:17:43 https://www.w3.org/TR/sparql11-service-description/#sd-Language might be more appropriate, i.e., SPARQL-star is a different language than SPARQL 1.0 or SPARQL 1.1 15:18:05 pchampin: good approach for the optimistic perspective regarding the mimetypes 15:18:32 present+ 15:18:39 Sorry I was late. 15:18:40 see also https://www.w3.org/TR/sparql11-service-description/#lang-sparql10query and following 15:18:59 ... my fear is that having an x-... mimetype may make people use it 15:19:21 Zakim, who is here? 15:19:21 Present: gkellogg, gatemezing, pchampin, james_, olaf, thomas, AndyS, TallTed, ora 15:19:24 On IRC I see ora, thomas, olaf, gkellogg, gatemezing, james_, TallTed, AndyS, RRSAgent, Zakim, pchampin, agendabot, rhiaro 15:19:29 gkellogg: that's orthogonal to the service descr. issue 15:19:50 ... it's reasonable to have an RDF-star namespace 15:20:07 q? 15:20:39 pchampin: will keep the PR on media types open for a few days 15:20:55 ... so that everyone can take a look and react 15:21:04 q? 15:21:16 ... and if no complaints in a few days, then the PR will be merged 15:21:19 zakim, next agendum 15:21:20 agendum 4 -- PR 162: Semantics -- taken up [from agendabot] 15:21:43 pchampin: made another PR about the semantics of RDF-star 15:21:55 ... it's less disruptive than the previous one 15:22:09 ... Two advantages: 15:22:17 first, get rid of hidden IRIs 15:22:47 q+ about simple literals 15:23:00 q+ to ask about simple literals 15:23:29 second, it's consistent with SPARQL-star eval.semantics (at least, PA things so) 15:23:48 s/things/thinks 15:24:18 pchampin: doesn't change anything in the semantics-related test suites 15:24:39 q? 15:24:41 ... any opinions about it? 15:24:44 ack AndyS 15:24:44 AndyS, you wanted to ask about simple literals 15:25:02 AndyS: talking about simple literals causes trouble 15:25:15 ... they don't exist in RDF but only in the syntax 15:25:24 pchampin: that's right 15:25:42 ... it was already in the previous version 15:25:48 https://w3c.github.io/rdf-star/cg-spec/editors_draft.html#mapping 15:26:40 ... agree that they way it's phrased is ambiguous 15:26:52 ... Peter suggested something else 15:27:03 ... which is probably a better idea 15:27:29 ... PR will be adapted accordingly 15:28:09 q? 15:28:55 ... Waiting for Dörthe and others to take a look 15:29:11 ... if no complaints in a couple of days, then it will be merged 15:29:30 ... only things it changes are things that none liked before 15:29:42 q? 15:29:49 zakim, next agendum 15:29:49 agendum 5 -- Open-ended discussions -- taken up [from agendabot] 15:30:23 AndyS: "How do we get out of this" question 15:30:55 ... how do we get to a finished version? 15:31:25 ... what time frame? 15:31:36 ... shall we call the next draft the "last call"? 15:31:53 "time" isn't the best measurement. "the point where none of us see major issues" would be good. 15:32:13 q+ 15:32:14 ... agrees to TallTed 15:32:25 ... but there are no more major issues 15:32:56 TallTed: the point of this task force is to focus on a particular thing 15:33:11 ... if we don't see no major issues with that thing, then 15:33:24 ... the report should go to RDF-DEV CG 15:33:55 AndyS: The last call may go to RDF-DEV CG 15:34:04 q+ 15:34:07 william has joined #rdf-star 15:34:07 ... Is there a list of remaining major issues? 15:34:08 We can tag here https://github.com/w3c/rdf-star/issues "mejor issues" ? 15:34:35 pchampin: tag issue in github 15:34:55 s/issue/issues 15:35:06 AndyS: tie that to the document 15:35:08 q- 15:35:47 action: create "outsanding issues" in the CG-report as being the things to complete before we're done 15:36:00 ack thomas 15:36:26 thomas: want to confirm that he is working on a longish email about the semantics 15:36:51 q+ 15:36:59 ... wants to convince the group of moving to transparency semantics 15:37:21 ack gkellogg 15:37:41 gkellogg: in addition to an email, a PR would be great 15:38:05 ... that PR should capture the alternative proposal 15:38:28 AndyS: instead of a PR (which freezes it), put it into a separate document 15:38:52 gkellogg: or on a wiki page 15:39:12 thomas: my aim is still to change it 15:39:21 q+ 15:39:25 ... I would like to have a discussion first 15:39:37 ... but, of course, prefer a note 15:40:03 pchampin: agrees that, at least, the rationale for the decision should be in the report 15:40:19 ... regarding freezing: we can have both 15:40:41 ... it's similar to the discussion of the seminal example 15:41:02 ... it's good to have the report as the single-point of reference 15:41:18 TallTed: what#s nice here is that we are not an immutable academic paper 15:41:34 ... we can make it a "snapshot draft" 15:42:09 ... which may include pointers to the discussions in the github issues, the mailing list, etc 15:42:37 pchampin: agrees 15:42:57 ... yet, it would be nicer for the reader of the report to have a summary in the report 15:43:06 ... rather than just a link to somewhere else 15:43:10 thomas: yes 15:43:30 action: add a section about the rationale for semantic opacity / transparency 15:43:53 TallTed: may even be marked as a "feature with risk" 15:44:03 AndyS: this can get out of control 15:44:24 ... wouldn't have a report with a long discussion of the alternatives 15:44:47 ... counterproductive opposite the Property Graphs community 15:45:53 ... may seem as if nothing was agreed 15:46:34 pchampin: no, instead, intention is to give a rationale for the solution (semantics) that we keep in the end 15:46:57 ... really only explain the consequences of the semantics 15:47:45 TallTed: didn't think the focus of this work was to convert PG people to the RDF world 15:48:00 q? 15:48:04 ... but instead to avoid people turning from RDF to PGs 15:48:24 gkellogg: it provides a formal underpinning 15:48:29 q- 15:48:39 ... marketing 15:49:04 pchampin: to Ted: I think it works both ways 15:49:25 q? 15:49:26 q+ 15:49:35 s/instead to avoid people turning from RDF to PGs/instead to fill a perceived gap in RDF that might send people from RDF to PGs.../ 15:49:43 kgellogg: another thing that came up... 15:50:07 s/kgellogg/gkellogg/ 15:50:25 ... difference between relationship and attributes in PGs 15:51:26 ... there is a distinction that some people see when comparing commerical PGs and RDF triple stores 15:51:47 s/commerical/commercial 15:52:05 pchampin: see how it is related to the PG versus RDF discussion 15:52:20 ... but not specific to RDF-star 15:53:46 ... usually, we consider this a representation issue 15:54:08 ... however, it may also be deeper 15:54:12 Discussion is in EasierRDF https://github.com/w3c/EasierRDF/issues/45 15:54:33 ... for instance, in Cypher the distinction is also in the query expressions 15:54:53 ... perhaps out of scope 15:55:24 gkellogg: suggest to take a look at the issue in EasierRDF github 15:55:30 ... and to chime in 15:55:46 AndyS: Actually, it is in OWL 15:55:56 ... datatype properties versus object properties 15:56:16 pchampin: okay, OWL has this distinction 15:56:39 ... but rarely any visual representations of RDF graphs 15:56:50 ... that make this distinction 15:57:11 ... e.g., by visualizing an RDF graph more in a PG-like manner 15:57:12 q? 15:57:21 ack ora 15:57:40 ora: comment on what Ted said earlier about the perceived gap between 15:57:43 ... PG and RDF 15:57:58 ... when talking to customers who are just starting 15:58:14 ... they almost always ask whether they should go for RDF or PG 15:58:31 ... and it seems to them that there is no going back 15:58:45 ... RDF-star may help to narrow the gap 15:58:51 Ora, that perception is not because you provide both PG and RDF in your tools? 15:59:11 AndyS: primarily about provenance of (RDF) data 15:59:26 ... and being able to handle it in a convenient way 15:59:45 ora: to the question from the chat: it is not only about that 15:59:52 ... not always the case 16:00:03 ... instead, more general discussions about graphs 16:00:04 q? 16:00:09 Thanks ora! Makes sense 16:00:13 ... even before a decision which type of DB to pick 16:01:01 pchampin: KGC next week, but no overlap with the call 16:01:02 Bye! 16:01:05 bye! 16:01:05 Bye 16:10:34 olaf has left #rdf-star 17:46:49 gkellogg has joined #rdf-star