Meetings:Telecon2017.05.31

Wednesday at 9:00am US Eastern time for 60 minutes

  Please check your timezone:
  -- http://www.timeanddate.com/worldclock/converted.html?iso=2017-05-31T06:00:00&p1=224&p2=43&p3=48&p4=47 
 WebEx (for audio): https://mit.webex.com/mit/j.php?MTID=m2f433ba94951cf59f6da984c15500e5e
  To join by phone: +1-617-324-0000 US Toll Number
  Access code/Meeting number: 646 464 360
IRC channel: #shapes on irc.w3.org on port 6665 (irc link, W3C web irc link)
To start meeting (ignore errors related to Zakim not knowing what teleconf this is): trackbot, start meeting
Zakim instructions:  http://www.w3.org/2001/12/zakim-irc-bot.html
RRSAgent instructions: http://www.w3.org/2002/03/RRSAgent

Admin

• Chair: Ted Thibodeau
• Scribe: First available on the scribe list.

Minutes of last meeting

• PROPOSED: Approve minutes of the 24 May 2017 Telecon: https://www.w3.org/2017/05/24-shapes-minutes.html

Next meeting

• None planned, pending W3C process

PR Status Update

New Issues and Formal Objections

• None so far

WG Notes

• SHACL Advanced Features: http://w3c.github.io/data-shapes/shacl-af/
• SHACL JavaScript Extensions: http://w3c.github.io/data-shapes/shacl-js/
• SHACL Compact Syntax: http://w3c.github.io/data-shapes/shacl-compact-syntax/

SHACL Community Group

Potential announcement text:

The mission of the SHACL Community Group is to continue the development of SHACL-related specifications and to support the further adoption of SHACL after the W3C Data Shapes Working Group has ended. Desirable outcomes include the development of educational material (primers, best practices), the application of SHACL to frequently used RDF vocabularies, libraries of constraint components for common constraint types, improved integration with established technologies such as JavaScript, further work on theory and practice around SHACL rules, a compact SHACL syntax, and a SHACL internet protocol. Additional work may go into delivering "de-facto standard" fixes to some gaps left in the current SHACL specifications (e.g., handling recursion, and addressing more comprehensive syntax checks).

AOB