Meetings:Telecon2015.06.25

Thursday at 2pm US Eastern time for 90 minutes
  Beware US and Europe Daylight Saving Time in effect check your timezone: -- http://www.timeanddate.com/worldclock/converted.html?msg=RDF+Data+Shapes+meeting&iso=20150625T11&p1=224&p2=43&p3=195&p4=26&p5=240 
** WebEx ** (for audio): https://mit.webex.com/mit/j.php?MTID=m3f7be74bc0d7a0abf0405fe5661ee163
  To join by phone: +1-617-324-0000 US Toll Number
  Access code/Meeting number: 640 811 616
IRC channel: #shapes on irc.w3.org on port 6665 (irc link, W3C web irc link)
To start meeting: 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: Bart van Leeuwen, or Michel Dumontier, or first available on the scribe list.

Minutes of last meeting

PROPOSED: Approve minutes of the 18 June Telecon: http://www.w3.org/2015/06/18-shapes-minutes.html

Next meeting

• Teleconf 2015.07.02

Disposal of SHACL Raised Issues

• PROPOSED: Open raised issues: ISSUE-69, ISSUE-70, and ISSUE-71
  • ISSUE-69: status of rdf:langString values with xsd:string datatype
  • ISSUE-70: special treatment of blank node types
  • ISSUE-71: SHACL Endpoint Protocol

ISSUE-1: What inferencing can or must be used?

• ISSUE-1: What inferencing can or must be used?
  • ACTION-26
• PROPOSED: SHACL should include a property sh:sparqlEntailment that can be used to specify a required inferencing level for each SPARQL query, as described in http://w3c.github.io/data-shapes/shacl/#sparql-entailment, per Holger's email
• PROPOSED: sh:valueType must also match subclasses, with its SPARQL implementation using rdfs:subClassOf* as described in http://w3c.github.io/data-shapes/shacl/#sparql-AbstractValueTypePropertyConstraint, per Holger's email
• PROPOSED: SHACL shall include another property sh:directValueType that only matches the directly asserted types (for OSLC use case), per Holger's email
• PROPOSED: sh:scopeClass must also include instances of subclasses, with its SPARQL implementation using rdfs:subClassOf*, per Holger's email
• PROPOSED: SHACL shall include a high-level mechanism to express the scope of direct instances, per Holger's email
• Close ISSUE-1?

ISSUE-47: Can SPARQL-based constraints access the shape graph, and how?

• Three different proposals:

1. PROPOSED: Close ISSUE-47: Can SPARQL-based constraints access the shape graph, and how? by allowing access to the shape graph, per Holger's current draft.
2. PROPOSED: Close ISSUE-47: Can SPARQL-based constraints access the shape graph, and how? by allowing the core to be be defined in the current way if people see this more convenient but not allowing access to the shapes graph outside of core per Dimitris's email
3. PROPOSED: Close ISSUE-47: Can SPARQL-based constraints access the shape graph, and how? not requiring that the shape graph be accessible when evaluating constraints on the data graph, per Peter's email

ISSUE-22: Treatment of recursive shape definitions]

• Discuss ISSUE-22: Treatment of recursive shape definitions

More issues

• Discuss ISSUE-61: Direction of individual scoping: sh:nodeShape vs. sh:individualScope
• Discuss ISSUE-65: A consistent and cohesive definition of shapes, scopes, and constraints
  • Peter and Holger's proposals
• SHACL Editor's draft