Meeting minutes
<ktk> Zakim: help
<ktk> it was my bad, should work now
<ktk> I added the agenda to the wrong part of the event
<ktk> huh
<ktk> ok no idea what I do wrong
<ora> You are getting some attitude from Zakim.
<ktk> yeah :)
<ktk> won't read it from the event page today for some reason
<ktk> scribe AndyS
<ktk> chair ora
Visitor: Jerven Bolleman
Scribe: Seaborne, Andy (alternate: Patel-Schneider, Peter)
Approval of last week's minutes:
<pfps> Last meeting's minutes look fine to me.
ora: Last meeting minutes https://
<ora> proposal: approve previous minutes
<ktk> +1
<ora> +1
<rubensworks> +1
<pchampin> +0 (was not present)
<doerthe> +1
<olaf> +1
<gtw> +1
+1
<enrico> +1
<AZ> +1
RESOLUTION: approve previous minutes
Issues with "First Public Working Draft" (FPWD)
ora: FPWD - issues with redirects
pfps: I use /rdf11-schema
AndyS: The schema doc uses the short name to deduce the last REC
… it is the only doc that does that.
… can put in the URl of the doc should be.
<AndyS> s/URi/URL/
pchampin: should separate two issues
… old docs using short name as if "rdf11-*"
… second - our docs to have no cycles.
… find a common recipe.
pfps: need the right changes for semantics and entailment
<ora> proposal: publish semantics and entailment docs asap
<ora> +1
<rubensworks> +1
<ktk> +1
<ora> proposal: publish semantics and entailment FPWD docs 2023-06-06
<ora> +1
<rubensworks> +1
<Tpt> +1
<pchampin> +1
+1
<doerthe> +1
<olaf> +1
<AZ> +1
<enrico> +1
<pfps> +1
<ktk> +1
RESOLUTION: publish semantics and entailment FPWD docs 2023-06-06
<pfps> hopefully someone will tell me what changes, if any, need to be made
pchampin: /TR not being the REC -- The docs were stable long term so the change has surprised some people.
ktk: Living standards came up.
… any statement we should be making?
ACTION: pchampin, fix broken links (to "latest rec") in old and new RDF/SPARQL TR docs
ora: should probably make statement
… send an email to the WG email list
pchampin: it is a choice to make in this WG. We're are not there yet. Needs to happen before REC.
ktk: agrees to send an email to the list
SPARQL 1.2 Community Group Renaming
ora: more confusion re "SPARQL 1.2"
jerven: here to help with any renaming
ktk: sparql 1.2 came out of the Berlin workshop.
… now a confusion with this WG - but it is not the same.
… CG has w3c/
<pchampin> and a good place for incubating "new features" if we opt for the living standard mode
pchampin: andys: short name in the URL is hard to change. Can rename github repo easily.
… the mailing list and signup is tied to the "1.2" name.
… mailinglist can be rename/or with an extra one so SPARQL 1.2 is only in the URL of the CG.
ora: can we have a link on the homepage?
<ktk> so the only remaining URL with 12 in it would be this one? https://
<Zakim> AndyS, you wanted to ask if we can have a redirect?
pchampin: need to check about redirect - may be possible.
ACTION: pchampin to check with sys team to have a redirect from community/sparql-next to community/sparql-12
<ghurlbot> Created action #62
ora: Ok for "sparql-next"?
<ora> proposal: rename to sparql-next, if feasible
<ktk> +1
+1
<ora> +1
<rubensworks> +1
<pfps> +1
<AZ> +1
<enrico> +1
<olaf> +1
<pchampin> +1
<doerthe> +1
<gtw> +1
RESOLUTION: rename to sparql-next, if feasible
<Tpt> +1
Review of open actions, available at
ora: Open actions https://
<ghurlbot> Action 57 respond to W3C about TPAC meeting (on rdfguy) due 11 May 2023
<ktk> Close #57
ktk: TPAC - close action
<ghurlbot> Closed action #57
pchampin: echidna in progress
zkim, open item 6
Review of pull requests, available at
pfps: CSS changes
… thought was we'd wait for consensus was we were
… but seems to have been rolled out.
… maybe different versions in different repos.
… problems: harder to read on narrow tabs/screens
… font size change in tables
ora: tables + mobile => tricky
pfps: we seem to have tradedoff mobile devices against small screen appearance
… opinion - if a table is too wide, person viewing can reduce the font. Roughly same effect.
… rendering info on small screens is difficult : but we seem to have not arrived the right place.
… one problem is broken ids across lines.
… fixed resize rule for table font change.
ora: can we get advice from W3C?
pfps: also choice of colors.
pchampin: we can contact accessibility team
ora: who is the team contact for current CSS work?
ktk: can ping pchampin on the thread
ktk: will add UC TF to agenda next week
pfps: we have a real use case.
… going to send an email to the list
pchampin: to editors of semantics and entailment.
… OK to update the docs for FPWD?
pfps: need advice on the correct content for header.
<pchampin> s/Topic: RDF-star WG weekly meeting//
<pchampin> s/agendum 1 -- 1. Scribe: Seaborne, Andy (alternate: Patel-Schneider, Peter) -- taken up [from ktk]//
<pchampin> s|s/Topic: RDF-star WG weekly meeting//||