<Jack_> +present

<TallTed> -present

<scribe> scribenick: hknublau

<ipolikof> PROPOSED: Approve minutes of the 26 April 2017 Telecon: https://www.w3.org/2017/04/26-shapes-minutes.html

+1

<simonstey> +1

<ipolikof> +1

<TallTed> +1

<Jack_> +1

RESOLUTION: Approve minutes of the 26 April 2017 Telecon: https://www.w3.org/2017/04/26-shapes-minutes.html

Formal Objections

ipolikoff: Procedural objection on cut off of tests may need Sandro's input

<ipolikof> https://lists.w3.org/Archives/Public/public-rdf-shapes/2017May/0001.html

ipolikof: Summary of objection
... sequence path does allow other triples than rdf:first and rdf:rest
... Peter then created scenarios where this may confuse users or tools
... Peter suggested alternative definition
... Would require republishing another CR

<simonstey> +q

simonstey: Proposed solution would be OK in principle as long as it doesn't break other parts of SHACL

ipolikof: No strong reason to put comments on the path itself

hknublau: Process is there for a reason. Late changes should only be made for very strong reasons.

<simonstey> +q

simonstey: I am fine with that too, but we need a rational explanation beside process

TallTed: We need a good explanation.

<simonstey> +q

hknublau: We have test cases that exclude the cases that Peter created.

simonstey: If this small change would not change implementations I hope this doesn't require a new CR
... we need to confirm this from Sandro.

<ipolikof> PROPOSAL: Make an editorial clarification that sequence paths are subjects of only 2 triples - as long as sandro confirms it can go in as editorial only

TallTed: We have tests to double-check and confirm the spec, I think this is viable.

<ipolikof> PROPOSAL: Make an editorial clarification that sequence paths should be subjects of only 2 triples, any other triples are ignored by implementations

<TallTed> PROPOSAL: Make an editorial clarification that sequence paths should be subjects of only 2 triples, any other triples shall be ignored by implementations, bringing the prose of the spec in line with the tests which have always carried the intent.

<ipolikof> +1

<TallTed> +1

<simonstey> +1

<Jack_> +1

<pano> +1

0

RESOLUTION: Make an editorial clarification that sequence paths should be subjects of only 2 triples, any other triples shall be ignored by implementations, bringing the prose of the spec in line with the tests which have always carried the intent.

https://lists.w3.org/Archives/Public/public-rdf-shapes/2017May/0004.html

ipolikof: I wrote an email, just summarizing it.
... 1) "Large" number of queries now disallowed
... As soon as you disallow a single keyword, you disallow a large number of queries (of course)
... But we just disallowed SERVICE (which has security and technical issues), MINUS and VALUES, which are syntactic sugar.
... 2) Interoperability: what if some implementations allow them, others don't - ill-formed is rather soft
... we could make this stricter, saying IF a query violates those rules, an impl MUST throw a failure.
... Would require changes to implementations and tests

<simonstey> +q

simonstey: Peter also mentioned equals

<ipolikof> PROPOSAL: Require SHACL_SPARQL processors to throw an error if queries contain MINUS, VALUES or SERVICE keywords

hknublau: This (and other parts of the objection) are outdated and should be resubmitted

<simonstey> http://w3c.github.io/data-shapes/shacl/#EqualsConstraintComponent

<simonstey> https://www.w3.org/TR/shacl/#EqualsConstraintComponent

+1

<simonstey> +1

<ipolikof> PROPOSAL: Require SHACL_SPARQL processors to throw an error if queries contain MINUS, VALUES or SERVICE keywords or violate any restrictions in the pre-binding appendix

+1

<Jack_> +1

<pano> +1

<TallTed> +1

<simonstey> +1

<ipolikof> +1

RESOLUTION: Require SHACL-SPARQL processors to throw an error if queries contain MINUS, VALUES or SERVICE keywords or violate any restrictions in the pre-binding appendix

Open Issues

hknublau: We could add label to indicate they are covered by Formal Objections

TallTed: We could post comment that we will consider they are satisfied in a few days

hknublau: New tests were added, so not everything is green right now.

ipolikof: We should not allow further tests since we are a week over the deadline.

<ipolikof> PROPOSAL: No additional tests from the community will be used in the recommendation process, unless the WG votes to allow them

+1

<TallTed> +1

<pano> +1

<Jack_> +1

<ipolikof> +1

<simonstey> +1

RESOLUTION: No additional tests from the community will be used in the recommendation process, unless the WG votes to allow them

<TallTed> trackbot, end meeting

This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: TallTed, hknublau, simonstey, ipolikof, present, Jack_, pano

WARNING: Replacing previous Present list. (Old list: TallTed, hknublau, simonstey, ipolikof, present, Jack_)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ TallTed, hknublau, simonstey, ipolikof, Jack_

Present: TallTed hknublau simonstey ipolikof Jack_ pano
Found ScribeNick: hknublau
Inferring Scribes: hknublau
Found Date: 03 May 2017
Guessing minutes URL: http://www.w3.org/2017/05/03-shapes-minutes.html
People with action items: