16:52:06 <RRSAgent> RRSAgent has joined #rdf-star
16:52:11 <RRSAgent> logging to https://www.w3.org/2023/01/19-rdf-star-irc
16:52:11 <Zakim> RRSAgent, make logs Public
16:52:12 <Zakim> please title this meeting ("meeting: ..."), pchampin
16:52:30 <pchampin> meeting: RDF-star WG
16:53:35 <AndyS> present+
16:53:48 <pchampin> pchampin has changed the topic to: RDF-star WG 2023-01-19 — https://www.w3.org/events/meetings/8a431cda-d732-4c77-a896-be3a6e4a0028
16:54:37 <pchampin> pchampin has changed the topic to: RDF-star WG 2023-01-19 — https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Jan/0024.html
16:54:43 <pchampin> agenda: https://lists.w3.org/Archives/Public/public-rdf-star-wg/2023Jan/0024.html
16:54:43 <agendabot> clear agenda
16:54:43 <agendabot> agenda+ Agenda
16:54:43 <agendabot> agenda+ Status of GH repositories
16:54:43 <agendabot> agenda+ GH Project for collecting issues [1]
16:54:43 <agendabot> agenda+ Continuation of last weeks discussion in the call
16:54:55 <pchampin> present+
16:57:37 <AndyS> TIL -- There's a list of all previous meetings : https://www.w3.org/services/meeting-minutes?channel=rdf-star&num=200
16:58:26 <pchampin> previous meeting: https://www.w3.org/2023/01/12-rdf-star-minutes.html
16:58:47 <pchampin> next meeting: https://www.w3.org/2023/01/26-rdf-star-minutes.html
16:59:07 <AndyS> someone ought invent a standard for for news feed on the web.
17:00:16 <enrico> enrico has joined #rdf-star
17:00:17 <gkellogg_> gkellogg_ has joined #rdf-star
17:00:21 <enrico> present+
17:01:04 <AZ> AZ has joined #rdf-star
17:01:14 <gtw> present+
17:01:22 <AZ> present+
17:01:53 <gkellogg> gkellogg has joined #rdf-star
17:02:16 <olaf> olaf has joined #rdf-star
17:02:16 <pchampin> agenda?
17:02:32 <TallTed> TallTed has joined #rdf-star
17:02:35 <olaf> present+
17:02:54 <ktk> present+
17:03:23 <Dominik_T> Dominik_T has joined #rdf-star
17:03:58 <pfps> pfps has joined #rdf-star
17:04:12 <gkellogg> gkellogg has joined #rdf-star
17:04:52 <pfps> present+
17:05:02 <Dominik_T> present+
17:05:05 <ktk> additional items proposed for agenda:
17:05:05 <ktk> * GH Project for collecting issues [1]
17:05:05 <ktk> * Suri: Slide on storage, performance, and future-proofing aspects related to multi-edge handling (5m)
17:05:08 <ktk> * Gregg: Editor assignments
17:05:11 <TallTed> present+
17:05:39 <gkellogg> gkellogg has joined #rdf-star
17:05:57 <AndyS> zakim, who is present?
17:05:57 <Zakim> I don't understand your question, AndyS.
17:06:24 <Doerthe> Doerthe has joined #rdf-star
17:06:24 <AndyS> scribe: AndyS
17:06:30 <Doerthe> present+
17:06:39 <Dominik_T> Dominik_T has joined #rdf-star
17:06:41 <ktk>  https://www.w3.org/2023/01/12-rdf-star-minutes.html
17:06:42 <Dominik_T> present+
17:07:24 <AndyS> ktk: accept the minutes
17:07:35 <AndyS> ... feedback on agenda
17:07:38 <gkellogg> gkellogg has joined #rdf-star
17:07:39 <Souri> Souri has joined #rdf-star
17:07:53 <AndyS> ... GH repos
17:07:57 <Souri> present+
17:08:13 <AndyS> ... a GH repo for issues of all docs
17:08:31 <AndyS> ... Souri would like a 5 min slot
17:08:53 <AndyS> ... gkellogg asked about editors
17:08:54 <gkellogg> gkellogg has joined #rdf-star
17:09:55 <AndyS> pchampin: created a GH repo per specification
17:10:16 <AndyS> ... github pages active
17:10:25 <AndyS> ... 'main' protected
17:10:26 <AndyS> q+
17:11:03 <pfps> q+
17:11:30 <ktk> AndyS: What is published to GH pages, is it the whole repo or a particular subdirectory?
17:11:35 <ktk> pchampin: it's the whole repo
17:12:01 <AndyS> ack me
17:12:29 <pfps> q-
17:12:49 <AndyS> pfps: Q about how GH page work
17:12:51 <pchampin> q+
17:12:58 <AndyS> ... respec can run locally?
17:13:18 <pchampin> q-
17:13:20 <ktk> AndyS: yes it can be run locally, it's some javascript in the spec itself
17:13:54 <pchampin> q+
17:13:57 <ktk> pfps: can we have pre-commits for checking things on commits?
17:14:37 <ktk> AndyS: there are some pre-commit hooks but they only check basic things, not respec related
17:14:41 <pchampin> q-
17:14:51 <AndyS> pfps: will dig into checking possibilites for reSpec.
17:15:09 <ktk> AndyS: I haven't pushed any content on SPARQL stuff yet, I was working separately.
17:15:29 <ktk> ... I got some respec errors and will push after that.
17:16:40 <pfps> q+
17:16:40 <AndyS> topic: Issues project
17:17:49 <AndyS> ktk: Idea is a GH project for organising work.
17:18:14 <AndyS> ... also issues across repos
17:18:17 <TallTed> q+ to ask how GitHub projects handle GitHub notifications
17:18:33 <pchampin> w3c already uses GH rojects, so it should be possible
17:18:37 <AndyS> ... one central place to see all work
17:18:53 <TallTed> q?
17:18:55 <pchampin> s/GH rojects/GH projects/
17:19:03 <AndyS> ack pfps
17:19:31 <AndyS> pfps: New feature of sub-projects may be useful
17:19:38 <AndyS> ... "task lists"
17:19:51 <AndyS> ... in an issue link to sub issues
17:20:49 <pfps> q-
17:22:29 <AndyS> ack TallTed
17:22:29 <Zakim> TallTed, you wanted to ask how GitHub projects handle GitHub notifications
17:22:53 <AndyS> TallTed: GH creates features that are not fully thought out.
17:23:10 <AndyS> ... how does GH handle notifications?
17:23:42 <AndyS> ktk: subscribe is per project
17:24:25 <AndyS> ... should be cautions in using the features
17:24:44 <AndyS> s/cautions/cautious/
17:25:19 <AndyS> ktk: PA and chairs will come back with a proposal.
17:25:41 <gkellogg> gkellogg has joined #rdf-star
17:27:29 <AndyS> topic: Editor assignments
17:27:57 <AndyS> ktk: gregg gave a list of docs he's interested in.
17:28:04 <olaf> q+
17:28:12 <pfps> q-
17:28:31 <AndyS> q+
17:28:37 <ktk> ack olaf
17:29:00 <TallTed> +1 handle in an issue. Possibly with checklist of docs at top, to be supplemented with Editors as volunteered/assigned.
17:29:26 <gkellogg> gkellogg has joined #rdf-star
17:29:26 <TallTed> q+
17:29:34 <ktk> AndyS: I assume we do not do a complete review-cycle since the 1.1 specs
17:29:40 <TallTed> ack AndyS
17:29:54 <ktk> ack TallTed
17:30:19 <ktk> TallTed: I think most changes would be between 1.1 and today. but it would be good if reviewers still have a look at the whole document.
17:31:05 <ktk> TallTed: Errata in a previous edition should be corrected in a new addition
17:31:36 <ktk> ... if we find an error in a previous edition it should be corrected in any way.
17:32:02 <ktk> AndyS: it depends on how much work this creates. we have only 18 months of time
17:32:16 <ktk> TallTed: if errors create work, we should be able to extend the timeframe
17:32:46 <pfps> q+
17:33:12 <ktk> pfps: if we get a comment that creates massive changes for everything, we can say it is out of scope.
17:33:28 <AndyS> pfps: we have the option of declining comments
17:33:33 <AndyS> ack pfps
17:33:36 <ktk> TallTed: if the need for change is valid, like they discover a broken thing in the current spec, it should be treated with respect.
17:35:50 <TallTed> s/handle in an issue. Possibly/handle Editor assignments in an issue. Possibly/
17:35:57 <AndyS> ktk: Will create issue to record editor offers
17:36:40 <AndyS> ACTION ktk, to create an issue for editors offers
17:37:46 <TallTed> Zakim, help
17:37:46 <Zakim> Please refer to http://www.w3.org/2001/12/zakim-irc-bot for more detailed help.
17:37:48 <Zakim> Some of the commands I know are:
17:37:48 <Zakim>  xxx is yyy       - establish yyy as the name of unknown party xxx
17:37:48 <Zakim>                     if yyy is 'me' or 'I', your nick is substituted
17:37:49 <Zakim>  xxx may be yyy   - establish yyy as possibly the name of unknown party xxx
17:37:49 <Zakim>  I am xxx         - establish your nick as the name of unknown party xxx
17:37:49 <Zakim>  xxx holds yyy [, zzz ...] - establish xxx as a group name and yyy, etc. as participants within that group
17:37:49 <Zakim>  xxx also holds yyy - add yyy to the list of participants in group xxx
17:37:49 <Zakim>  who's here?      - lists the participants on the phone
17:37:49 <Zakim>  who's muted?     - lists the participants who are muted
17:37:50 <Zakim>  mute xxx         - mutes party xxx (like pressing 61#)
17:37:50 <Zakim>  unmute xxx       - reverses the effect of "mute" and of 61#
17:37:50 <Zakim>  is xxx here?     - reports whether a party named like xxx is present
17:37:51 <Zakim>  list conferences - reports the active conferences
17:37:51 <Zakim>  this is xxx      - associates this channel with conference xxx
17:37:51 <Zakim>  excuse us        - disconnects from the irc channel
17:37:51 <Zakim> I last learned something new on $Date: 2020/12/31 21:20:53 $
17:38:02 <AndyS> rrsagent, help
17:39:00 <AndyS> ACTION: ktk to create an issue for editors offers
17:39:07 <ghurlbot> Created -> action 11 https://github.com/w3c/rdf-star-wg/issues/11
17:39:20 <AndyS> souri: present slide
17:41:11 <AndyS> The scribe asks that the slide be sent to the WG email list.
17:43:57 <pfps> I'm confused.  What is supposed to be happening here?  An example that is part of a worked-out use case seems indicated.
17:45:12 <gkellogg> gkellogg has joined #rdf-star
17:45:25 <AndyS> timestamp
17:46:10 <pfps> timestamp is the use case?  How is this being represented?
17:47:35 <AndyS> I'm confused.
17:49:12 <AndyS> pfps: This depends on what is presented and how. What's the UC?
17:49:31 <AndyS> ... the WG should pay attention to use cases
17:50:04 <AndyS> ... provenance, modal logic. Can't future proof everything.
17:51:19 <gkellogg_> gkellogg_ has joined #rdf-star
17:51:37 <TallTed> q+
17:54:51 <AndyS> ack TallTed
17:55:22 <pfps> This looks like an attempt to change the RDF semantics from set-based to bag-based.  This is a fundamental change.
17:55:34 <AndyS> TallTed: slide implies an automatic id - which is not always the case.
17:55:53 <AZ> There's existing work (quite a lot actually) about mapping relational data to RDF (and back). It works. Do we need a new RDF that mimmics relational data so much that it's essentially doing the same thing?
17:55:59 <AndyS> ... I think you are asking for implicit and explicit naming
17:56:11 <AndyS> ... need to explain the slides
17:56:50 <TallTed> +1 to explicit use case (which I don't have ... yet)
17:57:04 <AZ> +1 for concrete use cases
17:57:43 <pfps> I agree that introducing things via email is better.
17:57:56 <olaf> olaf has left #rdf-star
17:58:32 <AndyS> zakim, end meeting
17:58:32 <Zakim> As of this point the attendees have been AndyS, pchampin, enrico, gtw, AZ, olaf, ktk, pfps, Dominik_T, TallTed, Doerthe, Souri
17:58:34 <Zakim> RRSAgent, please draft minutes
17:58:36 <RRSAgent> I have made the request to generate https://www.w3.org/2023/01/19-rdf-star-minutes.html Zakim
17:58:43 <Zakim> I am happy to have been of service, AndyS; please remember to excuse RRSAgent.  Goodbye
17:58:43 <Zakim> Zakim has left #rdf-star
17:58:52 <AndyS> rrsagent, please excuse us
17:58:52 <RRSAgent> I see 1 open action item saved in https://www.w3.org/2023/01/19-rdf-star-actions.rdf :
17:58:52 <RRSAgent> ACTION: ktk to create an issue for editors offers [1]
17:58:52 <RRSAgent>   recorded in https://www.w3.org/2023/01/19-rdf-star-irc#T17-39-00