Meeting minutes
No updates for task forces core, node expressions.
No updates for task force profiles.
Updates for task force UI: task force meeting time shifted.
No updates for task force SHACL rules: meeting on Wednesday; meeting with Dörthe from N3 group.
Andy: a few prs in progress.
<ajnelson-nist> I assume this is the "Eye" reasoner noted? https://
Updates for compact syntax: no response from task force members.
<simonstey> two PRs defining the auto-publish workflows for node-expr and rules: w3c/
simonstey: discussing auto-publishing
<TallTed> Please update calendar for UI task force
simonstey: also auto-publish all task force work, e.g. node expressions, rules, ...
… Carine set up the auto publishing.
simonstey: auto-publishing for sparql works
caribou: First Public WD is always published manually, then workflow can be set up
TallTed: time in calendar for UI should be updated
AndyS: discussion for timelines
… chartered until end of this year December
… at least 4 months before end we should have a stable version.
… so implementers can pick it up
elianaP: q1 to see what absolutely should be implemented
… have a plan until next month
elianaP: for core and sparql it should be fine
… for other parts, maybe risky timeline.
AndyS: node expr and rules list/use a lot of functions
… implementation takes a lot of time
AndyS: maybe we don't need proof for every detail of implementation
elianaP: but we need two implementations, right?
simonstey: either implemented or not; how can we leave out parts?
… tests should cover it.
simonstey: don't think we can leave out parts of the implementation
elianaP: group functions and reduce workload
simonstey: can we find a middle ground? are the already such cases?
caribou: if we don't meet two implementations for some parts, we can mark them at risk
… for some features, implementers might not implement it at all -> mark it at risk.
AndyS: sparql picked up already defined functions
… which datatypes are expected to be supported?
… example duration: you need datetime + duration function
elianaP: in the next months task force gorups should make a list of features and then look for parties to implement.
bergos: Holger has the needed functions implemented, so we can reuse.
… core, sparql, node expr should be covered.
simonstey: people in the task forces can implement.
elianaP: please update task force calendars