Meetings:Telecon2015.10.15

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=20151015T11&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, first available on the scribe list.

Minutes of last meeting

PROPOSED: Approve minutes of the 8 October Telecon: http://www.w3.org/2015/10/08-shapes-minutes.html

Next meeting

• Telecon 2015.10.22

Disposal of Raised Issues

PROPOSED: Open ISSUE-102

• ISSUE-102: Some defaults cannot be explicitly coded

Test Suite update

• Test suite repo

ISSUE-95: Template Simplifications (if Peter present)

PROPOSED: Close ISSUE-95, adopting Holger's proposed simplifications

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

ISSUE-86: ontology association

PROPOSED: Close ISSUE-86, adopting Dimitris's proposal: https://lists.w3.org/Archives/Public/public-data-shapes-wg/2015Oct/0077.html

• ISSUE-86: Associating shapes with ontologies or vocabularies

ISSUE-98: Node constraints

PROPOSED: Close ISSUE-98, adopting Holger's proposed changes

• ISSUE-98: Can property constraints also apply to focus nodes?

ISSUE-61: Direction of sh:nodeShape

PROPOSED: Close ISSUE-61, adopting Dimitris's proposal: https://lists.w3.org/Archives/Public/public-data-shapes-wg/2015Oct/0089.html

• ISSUE-61: Direction of individual scoping: sh:nodeShape vs. sh:individualScope

ISSUE-93: engine / language

Discuss ISSUE-93: SHACL engine vs. SHACL instance requirements

ISSUE-94: separate syntax and semantics

Discuss ISSUE-94: Should RDF syntax requirements be separated from SHACL semantics

ISSUE-96: Violation IDs

Discuss ISSUE-96: Should the validation results contain stable IDs to indicate the type of violation

AOB