RDF-star

<fabio> hello everybody

Announcements and newcomers

pchampin: TPAC : September - Vancouver.

<gkellogg> https://www.w3.org/wiki/TPAC/2022

pchampin: WG F2F meeting
… TPAC will be hybrid

<pchampin> https://github.com/w3c/strategy/issues/304

advanced notice to the advisory committee will be sent soonish

pchampin: after that I will send it to the SemWeb mailing list
… expect a lot of feedback / opinions
… after some weeks, take the feedback into account and submit the charter to ??
… at this point we need the chairs
… to know who the chairs will be

Open actions

<pchampin> https://github.com/w3c/rdf-star/issues?q=is%3Aopen+is%3Aissue+label%3Aaction

<pchampin> https://github.com/w3c/rdf-star/issues/247 Ping Danbri about final report

pchampin: anything to report on the open action items?
… had email conversation with danbri
… he responded on a side topic (chartering)
… but has still not published our final report on the CG Web page
… now sent another email to him this morning, asking him again to click the "publish" button

ora: no progress on the AWS blog post

WG chartering

<pchampin> https://github.com/w3c/rdf-star-wg-charter/issues

pchampin: 2 issues: one minor (typo)
… and one about RDFa
… csarven asked to either add RDFa or remove RDF/XML
… https://github.com/w3c/rdf-star-wg-charter/issues/19

gkellogg: do we explain the choice process was for docs mentioned?

pchampin: some explanation - could say directly that it is RDF WG and SPARQL WG docs.

Action: pchampin to add an explicit rationale about the choice of documents to include (those coming from the RDF and SPARQL WG)

AndyS: concern about extra features getting added

gkellogg: Also text direction. We do have the rechartering point.

pchampin: i18n commented in the strategy review on text direction.
… possible future "living spec". Need to start WG to show it will work.

Chairs

pchampin: danbri has concerns re: multiple edges.

<fabio> I need to go. See you next time!

<TallTed> It's possible to reply to a tweet, even years later, to ask for things like starting a GitHub issue, statement of the use cases he mentioned, etc.

https://twitter.com/danbri/status/1505608948191268870

Schedule next call

Action: pchampin to add the data and time of next call on the web page

Action: pchampin see with Danbri to publish our calls on the RDF-dev calendar

<pchampin> PROPOSAL: next call in 2 weeks, 8th of April

<olaf_> +1

<pchampin> +1

<AndyS> +1

<gkellogg> +0

<TallTed> 8th, 15th, 22nd are all fine by me

<ora> +1

<Dominik_T> +1

<TallTed> +0

Resolution: next call in 2 weeks, 8th of April

Open-ended discussions