Meeting minutes
<nicholascar> Thanks TallTed!
phase 1 deliverables
nicholascar: any infos?
AndyS: were there any comments wrt. the wide review?
nicholascar: yeah I have to review the reviews.
AndyS: I can have a look if you link me the issue with the links to the requests
<nicholascar> Issues #634& #635
nicholascar: we've got a few, issues 634 and 635
<AndyS> w3c/
<AndyS> w3c/
AndyS: on the rdf documents there has been quite a lot of silence, other than some internationalization
nicholascar: I contacted the compact syntax guys; we need to see a scope within the next 2 weeks
… and a complete outline within a month
… and a completed first draft by June
… if they want to continue on the REC track
simonstey: may have to delete the compact syntax tab from the examples
review old PRs
nicholascar: can someone comment on the closing of old issues/PRs activity?
HolgerK: a lot of old issues that were closed were either already addressed or have been stale for >6 months
… but I always encouraged the authors to reopen the issues if they feel they are still relevant
nicholascar: anything regarding old PRs?
… currently at ~ 17?
ajnelson-nist: I started tackling them, not forgotten, but didn't get to it
TF reports
nicholascar: core, sparql?
HolgerK: in core we merged rootclass and subclassof
… nothing else to report (also not nodeexpr)
nicholascar: regarding profiles, couple of PRs out there with couple of comments against them
… substantive comments from ajnelson-nist
… hope to have a lot addressed by Thursday
… the next two things are profiling of standards and data (nothing too much to say about profiling data yet)
edmond: regarding UI -> still reviewing PRs
… want to create a matrix table of all core constraints
… covers so far most of the constraints but some thing like the minmax and logical constraints are not covered yet
… finalizing also the widget scoring
nicholascar: so what's the next thing after you're done with the scoring?
edmond: we'll be covering the constraints that aren't covered by widgets directly
… logical constraints e.g.
AndyS: rules -> merged a couple of PRs; and to redo the introduction and added the stratification algo
… btw., you (currently) can't publish a document >= 2 on the same day (caching issue)
rdf/xml -1
AndyS: what's the WGs feeling wrt. rdf/xml?
ajnelson-nist: my understanding of the finance sector is that they had a lot of regulations were they had to encode data transits in XML
ajnelson-nist: I recall it was required for some RDF spec?
AndyS: yeah RDF 1.0
dataset exchange wg
nicholascar: the WG is reforming, and I think they are a user of SHACL
<AndyS> https://
nicholascar: in my AC review of their charter, that they have all these concerns about profiling
<AndyS> (old charter)
nicholascar: I remember them being predicated on RDF, all their outcomes are RDF things.
… so how do they propose to write constraints?
… are they prepared to recommend SHACL?
… previously and/or the current DCAT spec often drifts off into a bit of a handwavy territory