W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > April 2016

shapes-ISSUE-150 (nested severities): Treatment of nested severities [SHACL Spec]

From: RDF Data Shapes Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 18 Apr 2016 10:50:17 +0000
To: public-data-shapes-wg@w3.org
Message-Id: <E1as6kz-0009PL-6v@maia.w3.org>
shapes-ISSUE-150 (nested severities): Treatment of nested severities [SHACL Spec]

http://www.w3.org/2014/data-shapes/track/issues/150

Raised by: Dimitris Kontokostas
On product: SHACL Spec

It is currently not defined (nor there is a WG decision) how nested severities work in SHACL

for example which severity will be returned if ex:p1 fails due to ex:p2 or due to ex:p3 

ex:TopShape a sh:Shape
sh:property [
  sh:predicate ex:p1
  sh:severity sh:Warning ;
  sh:valueShape [
    a sh:Shape
    sh:property [
      sh:predicate ex:p2
      sh:severity sh:Info ;
      #.. constraints
    ]
    sh:property [
      sh:predicate ex:p3
      sh:severity sh:Violation ;
      #.. constraints
    ]
  ]
]

Options:
proposal 1: take into account only the top severity and ignore all nested severities even if top severity is not defined (default to sh:Violation)

proposal 2:take into account only the child severities and ignore the top one

proposal 3: take into account only the top severity only if the child severity is lower, otherwise use the child severity.
Received on Monday, 18 April 2016 10:50:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:31 UTC