Meetings:Telecon2015.11.12

Thursday at 2pm US Eastern time for 90 minutes
  The US and Europe should be back on the usual time offset, but please effect check your timezone: -- http://www.timeanddate.com/worldclock/converted.html?msg=RDF+Data+Shapes+meeting&iso=20151112T11&p1=224&p2=43&p3=195&p4=26&p5=240 
 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: Arnaud
• Scribe: Eric Prud'hommeaux, first available on the scribe list.

Minutes of last meeting

PROPOSED: Approve minutes of the 5 November Telecon: http://www.w3.org/2015/11/05-shapes-minutes.html

Next meeting

• Telecon 2015.11.19

Disposal of Raised Issues

PROPOSED: Open ISSUE-111, ISSUE-112

• ISSUE-111: How should the working group address the issues called out in the WG charter?
• ISSUE-112: SHACL uses RDFS properties in ways that violate their intended RDFS meaning

Requirements

Update on SHACL Requirements coverage table

• ACTION-30: Karen Coyle to Send email to group with unclear "satisfied by's"

ISSUE-65: nomenclature consistency

PROPOSED: Close ISSUE-65, while not perfect, the recent editorial fixes and rewrites have sufficiently addressed this. Further inconsistencies to be treated incrementally.

• ISSUE-65: Consistency and cohesiveness of nomenclature (e.g., shapes, scopes, and constraints)
• ISSUE-65 Proposal
• Glossary

ISSUE-96: Violation IDs

PROPOSED: Close ISSUE-96, adding an ID to validation results for each constraint type. These should align with the URIs of the templates and node validation functions in the SHACL system vocabulary.

• ISSUE-96: Should the validation results contain stable IDs to indicate the type of violation
• ISSUE-96 Proposals & Votes

ISSUE-78: sh:abstract

PROPOSED: Close ISSUE-78, adding to sh:ShapeClass an optional boolean property sh:abstract.

• ISSUE-78: Should SHACL support marking classes as abstract
• ISSUE-78 Proposals & Votes

ISSUE-92: additive repeated properties

PROPOSED: Close ISSUE-92, with no changes at all. The basic combinations in SHACL are non-additive.

• ISSUE-92: Should repeated properties be interpreted as additive or conjunctive?
• ISSUE-92 Proposals & Votes

ISSUE-95: Template Simplifications

PROPOSED: There are two kinds of constraints: built-in and extensions. Extensions are either native or templates.

• ISSUE-95: Proposed simplification and clean up of template mechanism
• ISSUE-95 Proposals & Votes

ISSUE-63: sh:hasShape

PROPOSED: Close ISSUE-63, requiring that engines with full SHACL support must implement a sh:hasShape function (the current specification may have issues with recursion, but these are mentioned in other tickets). Some implementations may use recursive code generation as an optimization.

• ISSUE-63: Nested shapes: sh:hasShape function versus recursive SPARQL code generation
• ISSUE-63 Proposals & Votes

AOB