16:58:13 <RRSAgent> RRSAgent has joined #rdf-star
16:58:17 <RRSAgent> logging to https://www.w3.org/2026/01/15-rdf-star-irc
16:58:22 <ktk> Agenda: https://www.w3.org/events/meetings/e5234c80-4c06-4c6b-af43-c78a1dbd390a/20260115T120000/
16:58:22 <agendabot> clear agenda
16:58:22 <agendabot> agenda+ Approval of last week’s minutes: -> 1 https://www.w3.org/2026/01/08-rdf-star-minutes.html
16:58:22 <agendabot> agenda+ Horizontal Reviews Tracking -> 2 https://github.com/w3c/rdf-concepts/issues/254  -> 3 https://github.com/w3c/rdf-semantics/issues/164  -> 4 https://github.com/w3c/rdf-n-triples/issues/79
16:58:23 <agendabot> agenda+ Review of open actions, available at -> 5 https://github.com/orgs/w3c/projects/20/views/3
16:58:25 <agendabot> agenda+ Identifying issues to solve before CR -> 6 https://github.com/orgs/w3c/projects/20/views/8
16:58:27 <agendabot> agenda+ Any Other Business (AOB), time permitting
16:58:53 <j22> j22 has joined #rdf-star
16:59:27 <olaf> olaf has joined #rdf-star
16:59:56 <pfps> pfps has joined #rdf-star
17:00:01 <niklasl> niklasl has joined #rdf-star
17:00:27 <fsasaki> fsasaki has joined #rdf-star
17:01:13 <ora> ora has joined #rdf-star
17:01:19 <Dominik_T> present+
17:01:30 <ora> present+
17:01:34 <ora> chair+
17:01:36 <pfps> present+
17:01:43 <fsasaki> present+
17:01:44 <AndyS> present+
17:01:47 <fsasaki> scribe: fsasaki
17:01:52 <ktk> present+
17:01:53 <olaf> present+
17:01:53 <j22> present+
17:02:19 <gtw> present+
17:02:38 <pfps> github appears to be having problems.
17:03:16 <ktk> Zakim, open item 1
17:03:16 <Zakim> agendum 1 -- Approval of last week’s minutes: -> 1 https://www.w3.org/2026/01/08-rdf-star-minutes.html -- taken up [from agendabot]
17:03:25 <enrico> Present+
17:03:35 <pfps> minutes look acceptable to me
17:03:35 <pchampin> present+
17:03:40 <TallTed> present+
17:03:41 <niklasl> present+
17:03:56 <ora> PROPOSAL: Approve last week's minutes
17:04:00 <niklasl> +1
17:04:00 <pfps> +1
17:04:00 <Dominik_T> +1
17:04:00 <fsasaki> +1
17:04:02 <enrico> +1
17:04:02 <olaf> +1
17:04:04 <pchampin> +1
17:04:05 <ora> +0 (regrets)
17:04:08 <gtw> +1
17:04:12 <ktk> +1
17:04:30 <ora> RESOLVED: Approve last week's minutes
17:05:27 <ktk> Zakim, next item
17:05:27 <Zakim> agendum 2 -- Horizontal Reviews Tracking -> 2 https://github.com/w3c/rdf-concepts/issues/254  -> 3 https://github.com/w3c/rdf-semantics/issues/164  -> 4
17:05:28 <TallTed> +1
17:05:30 <Zakim> ... https://github.com/w3c/rdf-n-triples/issues/79 -- taken up [from agendabot]
17:05:34 <doerthe> doerthe has joined #rdf-star
17:05:46 <doerthe> present+
17:06:03 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html TallTed
17:06:06 <fsasaki> pa: horizontal review of concepts, semantics, n-triples
17:06:17 <fsasaki> ... on non-closed tracking issues, I reached out to groups
17:06:23 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html AndyS
17:06:32 <fsasaki> ... accessibility said that we do not have issues, I asked them to close them
17:06:52 <fsasaki> ... i18n has raised about rdf concepts to be more explicit to be more explicit about bidi text
17:07:03 <fsasaki> ... the TAG closed the issue on rdf semantics
17:07:07 <TallTed> previous meeting: https://www.w3.org/2026/01/08-rdf-star-minutes.html
17:07:07 <TallTed> next meeting: https://www.w3.org/2026/01/22-rdf-star-minutes.html
17:07:20 <fsasaki> ... no  pending PRs on concepts. and remark on multiple versions (on turtle)
17:07:30 <fsasaki> ... I will go back to Sarven to see if our responses are ok
17:07:35 <fsasaki> ... privacy: no remarks
17:08:05 <fsasaki> ... security: has invited the chairs and me to the next security IG meeting to give a summary, so they can speed up the review
17:08:21 <fsasaki> ... so moving forward, horizontal reviews will be closed in a few weeks
17:08:32 <fsasaki> ora: so after that, what are next steps for us?
17:08:51 <fsasaki> pa: we create a snapshot of CR docs and make a transition request
17:09:06 <fsasaki> ... we go through the team, disable ecidna
17:09:19 <fsasaki> ... once the CRs are published, we announce them, call for implementations
17:09:53 <fsasaki> ... need evidence of 2 implementations
17:10:07 <fsasaki> .. AC vote will take 28 days
17:10:22 <fsasaki> ... may be in parallel or before, tbc
17:10:27 <fsasaki> ora: CRs will have new URLs?
17:10:51 <fsasaki> pa: short URL will not change, version URLs with date etc. will have "-CR" shortname
17:11:03 <fsasaki> ... the short URL will then point to CR, not the latest working draft
17:11:06 <ktk> q?
17:11:07 <pfps> So what needs to be done (for Semantics, in particular)?
17:11:09 <fsasaki> ora: great
17:11:22 <pfps> q+
17:11:32 <fsasaki> ... the chairs and PA proposed a presentation at the KG conference as a status update
17:11:40 <fsasaki> ... conference will be in 1st week of May
17:12:21 <fsasaki> ... had a conference like that last year, was well attended
17:12:27 <ora> ack pfps
17:12:28 <fsasaki> ... people want to see what is happening
17:12:35 <fsasaki> pfps: what are our next steps?
17:13:40 <fsasaki> ... there are some specific feedback items during horiziontal review, TAG and accessibilty
17:14:36 <fsasaki> pfps: I am looking at accessibilty request 139
17:14:58 <fsasaki> ... less operational one is the general comment from W3C "ping" (privacy guys)
17:15:07 <fsasaki> pa: they do not see that as blocking,
17:15:19 <Souri> Souri has joined #rdf-star
17:15:25 <Souri> present+
17:15:29 <fsasaki> ... suggestion was to make the abstract more introductory
17:15:55 <fsasaki> pfps: impossible for semantics
17:16:30 <fsasaki> ora: these concerns are not too strong
17:16:57 <fsasaki> pfps: the privacy one: maybe they want to have more explanatory text
17:17:03 <AndyS> q+
17:17:03 <fsasaki> ... we can have that after CR
17:17:07 <fsasaki> pa: agree
17:17:18 <fsasaki> pfps: fine on ignoring the semantics comment completely
17:17:20 <fsasaki> ora: agree
17:17:36 <pchampin> q+
17:17:39 <ora> ack AndyS
17:17:40 <fsasaki> pfps: need to look into semantics: what is in the tables
17:17:52 <Dominik_T> rrsagent, draft minutes
17:17:53 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html Dominik_T
17:17:59 <fsasaki> andy: on CR and ecidna
17:18:07 <fsasaki> ... can we still do PRs on the docs or do we have to delay that?
17:18:22 <fsasaki> pa: no need to keep the repo in line with CR
17:18:28 <fsasaki> ... so one can continue PRs
17:18:38 <fsasaki> ... editors draft is still linked from GH pages
17:18:52 <fsasaki> ... any class 3-4 changes should not be merged
17:19:15 <fsasaki> ... as long as we do changes that do not cause problems after CR, we can merge them into the main branch
17:19:16 <niklasl> Is there a link to the problem with tables in Semantics? (I think e.g. https://www.w3.org/TR/rdf12-semantics/#simple is a table, those could just be a box-styled ul or ol.)
17:19:35 <fsasaki> pa: no what to do next: ensure that the test suites are complete
17:19:55 <fsasaki> ... will be focus during CR period
17:20:09 <fsasaki> andy: do we have to freeze the test suite?
17:20:23 <fsasaki> ... so if we get an implementation report, we need to know what is being reported on
17:20:41 <ora> ack pchampin
17:20:55 <ora> q+
17:21:27 <fsasaki> pa: if we have radical changes after getting an implementation report, we may have an issue
17:21:31 <ora> ack ora
17:21:38 <fsasaki> ... making such changes would be not nice towards implementers
17:21:51 <fsasaki> ora: how does the spec life cycle work
17:22:01 <fsasaki> ... can we go from one CR to a new version of CR?
17:22:04 <TallTed> "CR Snapshot"
17:22:07 <fsasaki> pa: there are CR snap shot
17:22:18 <fsasaki> ... we do not need to bounce back to WD esp. for editorial changes
17:22:28 <fsasaki> ora: do we then list the changes?
17:22:30 <fsasaki> pa: sure
17:23:02 <ktk> q?
17:23:07 <ktk> Zakim, next item
17:23:07 <Zakim> agendum 3 -- Review of open actions, available at -> 5 https://github.com/orgs/w3c/projects/20/views/3 -- taken up [from agendabot]
17:23:18 <Dominik_T> rrsagent, draft minutes
17:23:19 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html Dominik_T
17:23:56 <fsasaki> pa: item on ecidna, will be closed after check on RDF interop republishing
17:24:08 <fsasaki> adrian: should we pause it?
17:24:13 <fsasaki> pa: yes
17:24:21 <ktk> Zakim, next item
17:24:21 <Zakim> agendum 4 -- Identifying issues to solve before CR -> 6 https://github.com/orgs/w3c/projects/20/views/8 -- taken up [from agendabot]
17:26:05 <fsasaki> adrian: waiting for editors notes issue
17:27:18 <fsasaki> adrian: ora and I will take care of dashboard access issue
17:27:25 <fsasaki> adrian: implementation reports - skipped
17:27:57 <ktk> https://github.com/w3c/rdf-star-wg/issues/187
17:27:57 <gb> https://github.com/w3c/rdf-star-wg/issues/187 -> Issue 187 Confirm organisation of implementation reports (by afs) [ms:CR]
17:28:09 <fsasaki> ... on organization of implementation report, who should respond to this?
17:28:26 <fsasaki> andy: per document or put them into the RDF test repo
17:28:53 <ktk> q?
17:29:43 <fsasaki> andy: I would do "per doc repo"
17:29:55 <fsasaki> ... so it gets frozen once it is available
17:30:07 <fsasaki> ... rdf test repo will not have the same state
17:30:13 <fsasaki> adrian: makes sense
17:30:53 <fsasaki> andy: test suite is currently borken, need to check it can run
17:31:26 <fsasaki> adrian: should the tests be next to the docs?
17:31:36 <fsasaki> andy: json-ld does "per doc", not sure
17:31:43 <ora> s/borken/broken
17:32:28 <fsasaki> adrian: is there a reason against this?
17:32:38 <fsasaki> pa: "per doc" makes sense
17:33:08 <niklasl> Yep, JSON-LD has tests in https://github.com/w3c/json-ld-api/
17:33:20 <fsasaki> pa: json-ld is a bit different
17:33:41 <fsasaki> adrian: it seems there is not a consistent way how they publish tests in json-ld 1.1
17:33:54 <fsasaki> .... we could then consistently put the tests in the git repo
17:34:03 <pchampin> q+
17:34:04 <fsasaki> ora: where would people look for tests?
17:34:13 <fsasaki> ... per doc makes a lot of sense
17:34:27 <ktk> ack pchampin
17:34:27 <fsasaki> pa: header has links to test suite and implementation report
17:34:35 <Dominik_T> s/adrian:/ktk:/
17:34:45 <fsasaki> ... if several specs point to same report, they should find their way
17:35:49 <fsasaki> adrian: should we make a comment in the issue to record the decision
17:36:12 <fsasaki> pa: I will create a topic in the minutes and cite the minutes in the issue
17:36:18 <pchampin> s/adrian: implementation reports - skipped/subtopic: implementation reports
17:36:31 <pchampin> RRSAgent, make minutes
17:36:32 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html pchampin
17:37:26 <pchampin> meeting: RDF & SPARQL Working Group meeting
17:37:30 <ktk> q?
17:38:02 <fsasaki> adrian: line item 9 , on paragraph and n-triples
17:38:10 <fsasaki> ... can be merged as well, 2 approvals
17:38:16 <ktk> https://github.com/w3c/rdf-n-triples/pull/90
17:38:16 <gb> https://github.com/w3c/rdf-n-triples/pull/90 -> Pull Request 90 add paragraph stating that N-Triples 1.2 is not ambiguous for 1.1 implems (by pchampin) [ms:CR]
17:38:46 <fsasaki> pa: andy had comments on this PR
17:39:02 <fsasaki> ... tried to apply them, andy please check
17:39:17 <fsasaki> ... it is dublicating what you did in concepts
17:39:39 <fsasaki> adrian: line item 10 is super new
17:39:50 <fsasaki> ... last one is super new, will talk about that next time
17:39:51 <Souri> s/dublicating/duplicating/
17:40:21 <fsasaki> ... may be the same thing the accessibility people pinged us about
17:40:26 <ktk> q?
17:40:30 <fsasaki> adrian: any other comments?
17:40:39 <ktk> Zakim, next item
17:40:39 <Zakim> agendum 5 -- Any Other Business (AOB), time permitting -- taken up [from agendabot]
17:41:17 <fsasaki> ora: no task force meeting tomorrow
17:41:39 <fsasaki> andy: propsed closing on RDF concepts about a PR
17:41:41 <Dominik_T> Dominik_T has joined #rdf-star
17:42:13 <fsasaki> pa: propose closing a PR by william about adding more examples about triple based reification
17:42:26 <fsasaki> ... I think most of the examples belong to a separate doc
17:42:27 <fsasaki> ... I proposed closing
17:42:42 <fsasaki> ... William said: what to do for having the examples included somewhere else
17:42:56 <fsasaki> ... so he is ok with closing this, we owe him a response
17:43:25 <fsasaki> ... a reiffication best practice doc would be the right place
17:43:29 <pchampin> i/line item 9 , on paragraph/subtopic: other open PRs
17:43:35 <pchampin> meeting: RDF & SPARQL Working Group meeting
17:43:38 <fsasaki> enrico: I can respond.
17:43:47 <fsasaki> ... I created the structure for the doc
17:43:56 <fsasaki> pa: first create it on your web space
17:44:02 <fsasaki> ... if we adopt it we will move the repo
17:44:03 <pchampin> RRSAgent, make minutes
17:44:04 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html pchampin
17:44:10 <fsasaki> enrico: ok
17:44:12 <fsasaki> ora: AOB?
17:44:17 <Dominik_T> rrsagent, create minutes
17:44:18 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html Dominik_T
17:44:57 <fsasaki> ora: next steps - chairs and PA will attend security IG group meeting
17:45:39 <olaf> olaf has left #rdf-star
17:46:36 <RRSAgent> I have made the request to generate https://www.w3.org/2026/01/15-rdf-star-minutes.html TallTed