Meetings:Telecon2016.04.07

Thursday at 2pm US Eastern time for 90 minutes
  Please check your timezone:
  -- http://www.timeanddate.com/worldclock/converted.html?msg=RDF+Data+Shapes+meeting&iso=20160407T11&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: Jose Labra, or first available on the scribe list.

Minutes of last meeting

PROPOSED: Approve minutes of the 31 March 2016 Telecon: http://www.w3.org/2016/03/31-shapes-minutes.html

Next meeting

• 2016.04.14

ISSUE-80: Scheme URIs

PROPOSED: Close ISSUE-80, adding sh:stem to the spec outlined in Eric's email https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Mar/0311.html

• ISSUE-80: Constraint to limit IRIs against scheme/namespace, possibly with dereferencing)
• Last discussed on 31 March 2016

ISSUE-78: sh:abstract

PROPOSED: Close ISSUE-78, without adding sh:abstract, given that sh:ShapeClass was dropped

• ISSUE-78: Should SHACL support marking classes as abstract
• ISSUE-78 Proposals & Votes
• Last discussed on 11 Feb 2016

ISSUE-134: knowing inverse

PROPOSED: Close ISSUE-134, making sh:NodeConstraint, sh:PropertyConstraint and sh:InversePropertyConstraint pairwise disjoint per Holger's email https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Apr/0004.html

• ISSUE-134: does SHACL syntax distinguish inverse property constraints

ISSUE-136: property pair names

PROPOSED: Close ISSUE-136, renaming sh:equals, sh:notEquals, sh:lessThan, sh:lessThanOrEquals to sh:equalProperty, sh:notEqualProperty, sh:lessThanProperty, sh:lessThanOrEqualProperty respectively

• ISSUE-136: Can we clarify the names of property pair constraint types?
• ISSUE-136 Proposals

ISSUE-96: Violation IDs

PROPOSED: Close ISSUE-96, adding an ID to validation results for each constraint type. All open proposals include URIs for each constraint component, and these align with the mechanism used by the extension mechanism.

• ISSUE-96: Should the validation results contain stable IDs to indicate the type of violation
• ISSUE-96 Proposals & Votes
• Last discussed on 12 Nov 2015

ISSUE-105: defined prefixes

Discuss ISSUE-105: SHACL SPARQL constraints depend on namespaces in a graph, which is not defined

• Last discussed on 31 March 2016

ISSUE-123: DirectType syntax

Discuss ISSUE-123: Shall we unify the syntax of sh:directType and sh:class?

• Last discussed on 3 March 2016

ISSUE-124: sh:group

Discuss ISSUE-124: sh:group is only mentioned in examples

Other open issues, time permitting

• Open Issues

AOB