ISSUE-211: Eliminate property constraints
property constraints
Eliminate property constraints
- State:
- CLOSED
- Product:
- SHACL Spec
- Raised by:
- Karen Coyle
- Opened on:
- 2016-11-20
- Description:
- Peter's email: https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0018.html
Begins: "SHACL currently has shapes, constraints, constraint components, parameters,
and the special property sh:property. This leads to a complex formalism
that the SHACL document continues to struggle to adequately describe.
This complexity is not necessary. Both shapes and constraints can be merged
into a single notion of shapes. The special property sh:property can be
turned into the single parameter of a new constraint component."
Follow-up email with two proposals
https://lists.w3.org/Archives/Public/public-rdf-shapes/2016Nov/0053.html - Related Actions Items:
- No related actions
- Related emails:
- Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-02-01)
- Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-01-26)
- Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from holger@topquadrant.com on 2017-01-26)
- Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from kontokostas@informatik.uni-leipzig.de on 2017-01-26)
- Re: shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from holger@topquadrant.com on 2017-01-26)
- shapes-ISSUE-221 (sh:Shape hierarchy): Simplify the class hierarchy of shapes [SHACL - Core] (from sysbot+tracker@w3.org on 2017-01-25)
- ISSUE-170: EXISTS removed (from holger@topquadrant.com on 2017-01-12)
- Proposed next steps (was: Re: core remaining issues) (from kontokostas@informatik.uni-leipzig.de on 2017-01-09)
- Re: core remaining issues (from holger@topquadrant.com on 2017-01-08)
- Re: core remaining issues (from kontokostas@informatik.uni-leipzig.de on 2017-01-06)
- Re: Process Question: How to clean up meeting minutes (from eric@w3.org on 2017-01-06)
- Re: core remaining issues (from irene@topquadrant.com on 2017-01-06)
- core remaining issues (from kontokostas@informatik.uni-leipzig.de on 2017-01-06)
- Re: Process Question: How to clean up meeting minutes (from holger@topquadrant.com on 2017-01-06)
- Re: WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-04)
- Re: WG Meeting 2017-01-04 (from bart_van_leeuwen@netage.nl on 2017-01-03)
- Re: WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-03)
- Re: WG Meeting 2017-01-04 (from pano.maria@gmail.com on 2017-01-02)
- WG Meeting 2017-01-04 (from holger@topquadrant.com on 2017-01-02)
- Re: ISSUE-211: Should we turn sh:property and sh:sparql into constraint components? (from holger@topquadrant.com on 2016-12-17)
- ISSUE-211: Should we turn sh:property and sh:sparql into constraint components? (from holger@topquadrant.com on 2016-12-16)
- Re: Please vote on ISSUE-211 (from holger@topquadrant.com on 2016-12-13)
- Re: Please vote on ISSUE-211 (from irene@topquadrant.com on 2016-12-12)
- Re: Please vote on ISSUE-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-12)
- Re: Please vote on ISSUE-211 (from irene@topquadrant.com on 2016-12-12)
- Re: Please vote on ISSUE-211 (from kcoyle@kcoyle.net on 2016-12-12)
- Re: Please vote on ISSUE-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-12)
- Re: Please vote on ISSUE-211 (from kcoyle@kcoyle.net on 2016-12-12)
- Please vote on ISSUE-211 (from lehors@us.ibm.com on 2016-12-12)
- Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-09)
- Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-09)
- Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-09)
- Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-08)
- Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-08)
- Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-08)
- Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-08)
- Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
- Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
- Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
- Re: proposal for issue-211 (from irene@topquadrant.com on 2016-12-07)
- Re: proposal for issue-211 (from kcoyle@kcoyle.net on 2016-12-07)
- Re: proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
- Re: proposal for issue-211 (from holger@topquadrant.com on 2016-12-07)
- proposal for issue-211 (from kontokostas@informatik.uni-leipzig.de on 2016-12-07)
- Re: shapes-ISSUE-211 (property constraints): Eliminate property constraints [SHACL Spec] (from holger@topquadrant.com on 2016-11-22)
- shapes-ISSUE-211 (property constraints): Eliminate property constraints [SHACL Spec] (from sysbot+tracker@w3.org on 2016-11-20)
Related notes:
RESOLUTION: Close ISSUE-211 as already discussed (extensively) and too late for such a fundamental change, see https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Nov/0117.html
See https://www.w3.org/2016/12/14-shapes-minutes.html#resolution03
RESOLUTION: close issue-211 as essentially solved, with Dimitris putting remaining fragmentary concern in a fresh issue (220)
https://www.w3.org/2017/01/25-shapes-minutes.html
Display change log