Meeting minutes
FPWD
elianaP: SHACL Core and SHACL SPARQL are now live as of last week
… should now be on auto update
TF Updates
elianaP: no updates on core/sparql?
elianaP: profiling?
nicholascar: nothing to report since last week, have a meeting later this week
edmond: finished widget scoring; also started initial implementation
… will be sharing this with the group tmrw
… hopefully get something into a PR later this week/next week
… learned more about node expressions and how to utilize it for SHACL UI
<AndyS> w3c/
edmond: we will skip then the next couple of meetings (over xmas/ny)
AndyS: <asking about status of publishing node expression document>
nicholascar: I thought it was already set to autopublishing
caribou: rules were published to TR last week, but not node expr
… will update the scripts to include node-expr all
AndyS: so are we publishing node-expr to TR as well?
elianaP: yes
<caribou> I will add the GH workflow to autopublish Rules
AndyS: this week's TF meeting will be on Wed the 17th 11:30 CET
… the topic for wed. is stuff about stratification
elianaP: no one from CS group right now
simonstey: I've also a web tool
nicholascar: we've a couple of implementations for SHACL rules
DavidHabgood: I've a javascript implementation, but I need to tidy it up
… will be open source
caribou: we need to record the resolution that we publish the node expr wd
… we need to record ns locations
<AndyS> Not clear that rules will need to refer to node-expr namespace, maybe only use the NS.
<AndyS> +1 to publish node-expr
elianaP: show of hands, who agrees on publishing node-expr wd
<simonstey> +1
elianaP: no objection recorded
RESOLUTION: publish shacl12 Node Expressions as FPWD
AndyS: I can start a rules namespace document
caribou: they will be directly created in the ns repo
<caribou> w3c/
caribou: ns documents don't get automatically published when (FP)WD are published
… if we define some new ns in there, and we get the approval for FPWD, then the namespace is approved. ns names aren't expected to change until rec
… we need to get an approval the first time we "reserve" our ns URI
… and afterwards, whatever we maintain there is up to the wg
bergos: branches in our github repo..
… a lot of them are stale
… can we do some housekeeping and delete them?
… merged branches vs closed ones
caribou: once they are merged, they can def. be deleted
bergos: I'll go ahead and close the merged ones and make a list of all branches with closed PRs
next meetings this year
elianaP: who will be around next week?
<simonstey> +1
nicholascar: I guess we can skip the next one
elianaP: the next 2 meetings will be skipped then unless something comes up
RESOLUTION: the next 2 meetings 22.12/29.12 will be skipped