ISSUE-1  Inferencing | 
CLOSED | 
What inferencing can or must be used? | 
2014-11-18 | 
SHACL Spec | 
0 | 
ISSUE-2  Audience skills | 
CLOSED | 
What skills are expected/required from our audience? | 
2014-11-18 | 
SHACL Spec | 
0 | 
ISSUE-3  Shape association | 
CLOSED | 
How is a shape associated with a graph? | 
2014-11-18 | 
SHACL Spec | 
0 | 
ISSUE-4  Test | 
CLOSED | 
Test - please ignore | 
2014-11-26 | 
 | 
0 | 
ISSUE-5  Resource Shape Association | 
CLOSED | 
How is a resource associated with shapes? | 
2014-12-04 | 
SHACL Spec | 
0 | 
ISSUE-6  ShExC example | 
CLOSED | 
Story S2 - upgrade ShExC part | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-7  S4 no story | 
CLOSED | 
Story S4 is missing a story | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-8  S6 Clarification  | 
CLOSED | 
S6 doesn't clearly state what feature is required | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-9  S7 no story | 
CLOSED | 
S7 does not appear to have a story | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-10  S8 no story | 
CLOSED | 
S8 does not have a story | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-11  S9 impossible | 
CLOSED | 
S9 is about existing but unspecified values | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-12  S10 story upgrade | 
CLOSED | 
S10 needs a better story | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-13  S12 no constraints | 
CLOSED | 
it is not apparent where S12 involves constraints | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-14  S14 constraints? | 
CLOSED | 
S14 might be about change not constraints | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-15  S17 constraint? | 
CLOSED | 
S17 is about access not constraints | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-16  S18 constraints? | 
CLOSED | 
S18 does not appear to be about constraints | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-17  S19 and S20 ontologies | 
CLOSED | 
S19 and S20 need information to distinguish from ontology recognition | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-18  S35 examples | 
CLOSED | 
S35 needs to state what constraints are required | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-19  S35 not RDF | 
CLOSED | 
S35 appeals to something that is not RDF | 
2014-12-19 | 
User Stories | 
0 | 
ISSUE-20  S2 ShExC calling | 
CLOSED | 
ShExC example in S2 doesn't indicate how to set it up | 
2014-12-29 | 
User Stories | 
0 | 
ISSUE-21  Shape Expressions? | 
CLOSED | 
What is shape expressions? | 
2015-02-24 | 
 | 
0 | 
ISSUE-22  recursion | 
CLOSED | 
Treatment of recursive shape definitions | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-23  ShapeClass | 
CLOSED | 
Shapes as classes | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-24  specialisation | 
CLOSED | 
Can shapes specialise other shapes? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-25  core/lite | 
CLOSED | 
What's in Core/Lite? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-26  invoke-highlevel | 
CLOSED | 
Can extensions invoke the high-level language? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-27  extensions-in-highlevel | 
CLOSED | 
Can extension constraints be used in the high-level language? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-28  macros | 
CLOSED | 
Is the macro facility part of the high-level language or of the extension mechanism? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-29  formalism | 
CLOSED | 
Formalism for definition of high-level language | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-30  shape-and-data-graphs | 
CLOSED | 
Are shapes and data in the same graph? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-31  unitary semantics | 
CLOSED | 
Is there going to be a single unitary semantics for all of SHACL | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-32  SHACL+- | 
CLOSED | 
SHACL = high-level + extensions ? | 
2015-03-28 | 
SHACL Spec | 
0 | 
ISSUE-33  shape selection | 
CLOSED | 
Shifting section "Shape Selection" to introduction? | 
2015-04-01 | 
SHACL Spec | 
0 | 
ISSUE-34  OrConstraint | 
CLOSED | 
2 disjuncts at a time in sh:OrConstraint | 
2015-04-02 | 
SHACL Spec | 
0 | 
ISSUE-35  Language-tags Req | 
CLOSED | 
Language-tags Requirement | 
2015-04-02 | 
Requirements | 
0 | 
ISSUE-36  Value type facet | 
CLOSED | 
Naming of value type facet | 
2015-04-02 | 
SHACL Spec | 
0 | 
ISSUE-37  Node kind facet | 
CLOSED | 
Naming of node kind facet | 
2015-04-02 | 
SHACL Spec | 
0 | 
ISSUE-38  Cardinality facet | 
CLOSED | 
Naming of cardinality facets | 
2015-04-02 | 
SHACL Spec | 
0 | 
ISSUE-39  Value shape facet | 
CLOSED | 
Naming of value shape facet | 
2015-04-02 | 
SHACL Spec | 
0 | 
ISSUE-40  Property Cardinality | 
CLOSED | 
sh:min/max constrains properties, not values | 
2015-04-05 | 
 | 
0 | 
ISSUE-41  property paths (sh:path?) | 
CLOSED | 
Using property paths to refer to values/types? | 
2015-04-07 | 
SHACL Spec | 
0 | 
ISSUE-42  sh:notEqual | 
CLOSED | 
Adding sh:notEqual to potential datatype properties? | 
2015-04-07 | 
SHACL Spec | 
0 | 
ISSUE-43  SHACL-Part-1-FPWD | 
CLOSED | 
Proposal for creating the FPWD of SHACL Part 1 | 
2015-04-09 | 
SHACL Spec | 
0 | 
ISSUE-44  Graph dependencies | 
CLOSED | 
How to express dependencies between graphs | 
2015-04-15 | 
SHACL Spec | 
0 | 
ISSUE-45  SPARQL-extension | 
CLOSED | 
Should SPARQL be a built-in extension language | 
2015-04-17 | 
SHACL Spec | 
0 | 
ISSUE-46  RDF lists | 
CLOSED | 
Support for RDF Collections? | 
2015-04-22 | 
Requirements | 
0 | 
ISSUE-47  sparqling-shape-graph | 
CLOSED | 
Can SPARQL-based constraints access the shape graph, and how? | 
2015-04-23 | 
SHACL - SPARQL | 
0 | 
ISSUE-48  scope-of-shape | 
CLOSED | 
How do we limit the scope for a shape? | 
2015-04-28 | 
SHACL Spec | 
0 | 
ISSUE-49  scoped/unscoped shapes | 
CLOSED | 
Distinction between scoped and unscoped shapes | 
2015-05-13 | 
SHACL Spec | 
0 | 
ISSUE-50  presentation requirements | 
CLOSED | 
Presentations to the working group | 
2015-05-21 | 
 | 
0 | 
ISSUE-51  Results Vocabulary | 
CLOSED | 
What types of validation results should be returned | 
2015-05-22 | 
SHACL Spec | 
0 | 
ISSUE-52  abstract syntax | 
CLOSED | 
Define an Abstract Syntax for SHACL | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-53  multi-occurence | 
CLOSED | 
 Multi-occurrence of the same predicate | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-54  labra | 
CLOSED | 
OneOf vs. SomeOf | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-55  labra | 
CLOSED | 
Triple constraints (drop me) | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-56  labra | 
CLOSED | 
Inverse triple constraints (drop me) | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-57  group cardinality | 
CLOSED | 
Cardinalities on expressions or groups of triple constraints | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-58  Closed shapes | 
CLOSED | 
Signalling closed shapes/Defining closed shapes | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-59  default cardinalities | 
CLOSED | 
What are the default values for cardinalities? | 
2015-05-23 | 
SHACL Spec | 
0 | 
ISSUE-60  Other Extension Languages | 
CLOSED | 
Shall SHACL support other extension languages beside SPARQL (like JavaScript)? | 
2015-05-30 | 
SHACL Spec | 
0 | 
ISSUE-61  Direction of sh:nodeShape | 
CLOSED | 
Direction of individual scoping: sh:nodeShape vs. sh:individualScope | 
2015-05-30 | 
SHACL Spec | 
0 | 
ISSUE-62  General selection or filtering | 
CLOSED | 
Selection or filtering by arbitrary expressions and shapes | 
2015-05-30 | 
SHACL Spec | 
0 | 
ISSUE-63  sh:hasShape | 
CLOSED | 
Nested shapes: sh:hasShape function versus recursive SPARQL code generation | 
2015-06-01 | 
SHACL - SPARQL | 
0 | 
ISSUE-64  XSD Datatype facets | 
CLOSED | 
Should the Core vocabulary support datatype facets such as sh:minInclusive and sh:maxLength? | 
2015-06-01 | 
SHACL Spec | 
0 | 
ISSUE-65  nomenclature consistency | 
CLOSED | 
Consistency and cohesiveness of nomenclature (e.g., shapes, scopes, and constraints) | 
2015-06-01 | 
SHACL Spec | 
0 | 
ISSUE-66  non-convergence | 
CLOSED | 
SHACL spec ill-founded due to non-convergence on data loops | 
2015-06-10 | 
SHACL Spec | 
0 | 
ISSUE-67  | 
CLOSED | 
Http://www.w3.org/2014/data-shapes/track/issues/66 | 
2015-06-11 | 
 | 
0 | 
ISSUE-68  pre-binding | 
CLOSED | 
pre-binding not defined in SHACL spec | 
2015-06-12 | 
SHACL - SPARQL | 
0 | 
ISSUE-69  rdf:langString | 
CLOSED | 
status of rdf:langString values with xsd:string datatype | 
2015-06-19 | 
SHACL Spec | 
0 | 
ISSUE-70  blank node default type | 
CLOSED | 
special treatment of blank node types | 
2015-06-19 | 
SHACL Spec | 
0 | 
ISSUE-71  Protocol | 
CLOSED | 
SHACL Endpoint Protocol | 
2015-06-19 | 
SHACL Spec | 
0 | 
ISSUE-72  QCRs | 
CLOSED | 
Qualified Cardinality Restrictions | 
2015-06-25 | 
SHACL Spec | 
0 | 
ISSUE-73  sh:hasShape error handling | 
CLOSED | 
how do recursion errors from sh:hasShape interact with SPARQL | 
2015-07-10 | 
SHACL - SPARQL | 
0 | 
ISSUE-74  SPARQL endpoint support | 
CLOSED | 
Should SHACL support validating RDF graphs accessible via unmodified SPARQL endpoints | 
2015-07-12 | 
SHACL Spec | 
0 | 
ISSUE-75  error vs violation | 
CLOSED | 
How to distinguish constraint violations from errors | 
2015-07-13 | 
SHACL Spec | 
0 | 
ISSUE-76  commutability | 
CLOSED | 
Specifying execution order and commutativity of AND and OR | 
2015-07-13 | 
SHACL Spec | 
0 | 
ISSUE-77  sh:pattern flags | 
CLOSED | 
Shall sh:pattern also support sh:flags? | 
2015-07-24 | 
SHACL Spec | 
0 | 
ISSUE-78  sh:abstract | 
CLOSED | 
Should SHACL support marking classes as abstract | 
2015-08-04 | 
SHACL Spec | 
0 | 
ISSUE-79  Validation functions | 
CLOSED | 
Cleaner separation between value checking and property iteration | 
2015-08-13 | 
SHACL Spec | 
0 | 
ISSUE-80  Scheme URIs | 
CLOSED | 
Constraint to limit IRIs against scheme/namespace, possibly with dereferencing | 
2015-08-13 | 
SHACL Spec | 
0 | 
ISSUE-81  Property pair constraints | 
CLOSED | 
Shall SHACL Core include support for disjoint properties and other property pair constraints? | 
2015-08-19 | 
SHACL Spec | 
0 | 
ISSUE-82  Unique language | 
CLOSED | 
Shall SHACL Core include support for unique language constraints? | 
2015-08-19 | 
SHACL Spec | 
0 | 
ISSUE-83  multiple sh:qualifiedValueShapes | 
CLOSED | 
How should multiple definitions of sh:qualifiedValueShape of a property constraint be treated? | 
2015-08-21 | 
SHACL Spec | 
0 | 
ISSUE-84  Allowed IRIs | 
CLOSED | 
Constraint to limit IRIs of focus nodes to a given enumeration (similar to owl:oneOf) | 
2015-09-02 | 
SHACL Spec | 
0 | 
ISSUE-85  only one xor | 
CLOSED | 
what is the definition of XOR? | 
2015-09-09 | 
SHACL Spec | 
0 | 
ISSUE-86  ontology association | 
CLOSED | 
Associating shapes with ontologies or vocabularies | 
2015-09-10 | 
SHACL Spec | 
0 | 
ISSUE-87  Turtle file | 
CLOSED | 
Shall we publish RDF files for the SHACL namespace? | 
2015-09-11 | 
SHACL Spec | 
0 | 
ISSUE-88  qualifiedValue | 
CLOSED | 
Should we add sh:qualifiedValue ? | 
2015-09-11 | 
SHACL Spec | 
0 | 
ISSUE-89  recursion without properties | 
CLOSED | 
How should recursion that does not involve a property be handled? | 
2015-09-15 | 
SHACL Spec | 
0 | 
ISSUE-90  Literal focus nodes | 
CLOSED | 
Can the focus node be a literal? | 
2015-09-21 | 
SHACL Spec | 
0 | 
ISSUE-91  default cardinality | 
CLOSED | 
Default Cardinality in property constraints | 
2015-09-24 | 
SHACL Spec | 
0 | 
ISSUE-92  additive repeated properties | 
CLOSED | 
Should repeated properties be interpreted as additive or conjunctive? | 
2015-09-24 | 
SHACL Spec | 
0 | 
ISSUE-93  engine / language | 
CLOSED | 
SHACL engine vs. SHACL instance requirements | 
2015-09-24 | 
SHACL Spec | 
0 | 
ISSUE-94  separate syntax and semantics | 
CLOSED | 
Should RDF syntax requirements be separated from SHACL semantics | 
2015-09-24 | 
SHACL Spec | 
0 | 
ISSUE-95  Template Simplifications | 
CLOSED | 
Proposed simplification and clean up of template mechanism | 
2015-09-29 | 
SHACL Spec | 
0 | 
ISSUE-96  Violation IDs | 
CLOSED | 
Should the validation results contain stable IDs to indicate the type of violation | 
2015-09-29 | 
SHACL Spec | 
0 | 
ISSUE-97  sh:derivedValues | 
CLOSED | 
Shall SHACL include a mechanism to define constraints using derived values | 
2015-09-29 | 
SHACL Spec | 
0 | 
ISSUE-98  Node constraints | 
CLOSED | 
Can property constraints also apply to focus nodes? | 
2015-10-02 | 
SHACL Spec | 
0 | 
ISSUE-99  special cases | 
CLOSED | 
special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) | 
2015-10-02 | 
SHACL Spec | 
0 | 
ISSUE-100  sh:index | 
CLOSED | 
Specifying the order of property constraints (e.g. with sh:index) | 
2015-10-07 | 
SHACL - UI | 
0 | 
ISSUE-101  templates as classes | 
CLOSED | 
use of rdfs:subClassOf for template inheritance | 
2015-10-08 | 
SHACL Spec | 
0 | 
ISSUE-102  Specifying defaults | 
CLOSED | 
Missing a way to explicitly code unbound cardinality and open shapes | 
2015-10-14 | 
SHACL Spec | 
0 | 
ISSUE-103  Syntax simplifications | 
CLOSED | 
Can we further simplify the syntax of some constraint types? | 
2015-10-19 | 
SHACL Spec | 
0 | 
ISSUE-104  Union ranges | 
CLOSED | 
Should sh:datatype and sh:class have better support for OR? | 
2015-10-23 | 
SHACL Spec | 
0 | 
ISSUE-105  defined prefixes | 
CLOSED | 
SHACL SPARQL constraints depend on namespaces in a graph, which is not defined | 
2015-10-29 | 
SHACL Spec | 
0 | 
ISSUE-106  annotation properties | 
CLOSED | 
Annotation properties are not defined well | 
2015-10-29 | 
SHACL Spec | 
0 | 
ISSUE-107  annotations v. arguments | 
CLOSED | 
annotations and arguments use different mechanisms for specifying the SPARQL variable name | 
2015-10-29 | 
SHACL Spec | 
0 | 
ISSUE-108  operations | 
CLOSED | 
Should operations be specified? | 
2015-10-29 | 
SHACL Spec | 
0 | 
ISSUE-109  function calling | 
CLOSED | 
SHACL requires that SPARQL implementations be able to call functions defined on the fly | 
2015-11-04 | 
SHACL - SPARQL | 
0 | 
ISSUE-110  single-property constraints | 
CLOSED | 
relationship between sh:constraint and sh:property and sh:inverseProperty | 
2015-11-04 | 
SHACL Spec | 
0 | 
ISSUE-111  charter issues | 
CLOSED | 
How should the working group address the issues called out in the WG charter? | 
2015-11-05 | 
 | 
0 | 
ISSUE-112  misuse of some RDFS properties | 
CLOSED | 
SHACL uses rdfs:label and rdfs:comment in ways that violate their intended RDFS meaning | 
2015-11-05 | 
SHACL Spec | 
0 | 
ISSUE-113  SHACL and user interfaces | 
CLOSED | 
Let a user interface group design the connection between SHACL and UI tools | 
2015-11-12 | 
SHACL - UI | 
0 | 
ISSUE-114  Property Groups | 
CLOSED | 
Should SHACL include a grouping mechanism of properties (for UI purposes) | 
2015-11-12 | 
SHACL - UI | 
0 | 
ISSUE-115  ClosedShape | 
CLOSED | 
Closeness is an aspect of a Shape, but the current syntax treats it like all other constraints. | 
2015-12-16 | 
SHACL Spec | 
0 | 
ISSUE-116  | 
CLOSED | 
108 | 
2015-12-17 | 
 | 
0 | 
ISSUE-117  non-classes as classes | 
CLOSED | 
sh:class should not require that its objects be known to be instances of rdfs:Class | 
2016-01-11 | 
SHACL - Core | 
0 | 
ISSUE-118  syntax errors | 
CLOSED | 
syntax errors should not be confusable with validation results | 
2016-01-11 | 
SHACL Spec | 
0 | 
ISSUE-119  rdf:Lists | 
CLOSED | 
Defining constraints on (values of) rdf:Lists | 
2016-01-27 | 
SHACL - Core | 
0 | 
ISSUE-120  shape-class-instance-defs | 
CLOSED | 
The spec must be more precise and consistent about when a resource is a shape, a class, and an instance of a class | 
2016-01-28 | 
SHACL - Core | 
0 | 
ISSUE-121  # in graph name | 
CLOSED | 
Should the SHACL owl:Ontology include the # character | 
2016-02-04 | 
SHACL Spec | 
0 | 
ISSUE-122  no-shapes-file | 
CLOSED | 
Should we postpone publishing a SHACL shapes file (indefinitely)? | 
2016-02-10 | 
SHACL Spec | 
0 | 
ISSUE-123  DirectType syntax | 
CLOSED | 
Shall we unify the syntax of sh:directType and sh:class? | 
2016-02-28 | 
SHACL - Core | 
0 | 
ISSUE-124  sh:group | 
CLOSED | 
sh:group is only mentioned in examples | 
2016-03-06 | 
SHACL Spec | 
0 | 
ISSUE-125  sh:NodeConstraint missing | 
CLOSED | 
sh:NodeConstraint is mentioned but never defined | 
2016-03-06 | 
SHACL Spec | 
0 | 
ISSUE-126  sh:TemplateConstraint undefined | 
CLOSED | 
sh:TemplateConstraint is used in examples but not defined | 
2016-03-06 | 
SHACL Spec | 
0 | 
ISSUE-127  sh:TemplateScope undefined | 
CLOSED | 
sh:TemplateScope is mentioned but not defined | 
2016-03-06 | 
SHACL Spec | 
0 | 
ISSUE-128  rdfs:range | 
CLOSED | 
sh:defaultValueType is rdfs:range | 
2016-03-06 | 
SHACL Spec | 
0 | 
ISSUE-129  existential constraints | 
CLOSED | 
Existential constraints should be consistent | 
2016-03-07 | 
SHACL - Core | 
0 | 
ISSUE-130  rdf dataset assumption | 
CLOSED | 
SHACL should not assume that the data graph is in an RDF dataset | 
2016-03-07 | 
SHACL Spec | 
0 | 
ISSUE-131  sh:hasShape ill defined | 
CLOSED | 
The definition of sh:hasShape has errors and holes | 
2016-03-07 | 
SHACL Spec | 
0 | 
ISSUE-132  sh:predicate in constraints | 
CLOSED | 
sh:predicate is used in many constraints but not always available | 
2016-03-07 | 
SHACL - Core | 
0 | 
ISSUE-133  syntax | 
CLOSED | 
syntax simplification and regularization | 
2016-03-08 | 
SHACL - Core | 
0 | 
ISSUE-134  knowing inverse | 
CLOSED | 
does SHACL syntax distinguish inverse property constraints | 
2016-03-10 | 
SHACL Spec | 
0 | 
ISSUE-135  and/or syntactic sugar | 
CLOSED | 
Should sh:and/sh:or/sh:not/sh:valueShape support constraints too? | 
2016-03-10 | 
SHACL - Core | 
0 | 
ISSUE-136  Property pair names | 
CLOSED | 
Can we clarify the names of property pair constraint types? | 
2016-03-13 | 
SHACL - Core | 
0 | 
ISSUE-137  language tag | 
CLOSED | 
Missing constraint for language tag | 
2016-03-14 | 
SHACL - Core | 
0 | 
ISSUE-138  Property constraints as lists | 
CLOSED | 
Should property constraints use rdf:Lists? | 
2016-03-18 | 
SHACL - Core | 
0 | 
ISSUE-139  Universal applicability | 
CLOSED | 
Can all constraint properties be applied in all scenarios? | 
2016-03-18 | 
SHACL - Core | 
0 | 
ISSUE-140  Individual validation | 
CLOSED | 
SHACL needs to support validation of individual nodes | 
2016-03-21 | 
SHACL - Core | 
0 | 
ISSUE-141  Mixed ranges | 
CLOSED | 
How to represent mixed datatype-or-class ranges | 
2016-03-22 | 
SHACL - Core | 
0 | 
ISSUE-142  loose terminology | 
CLOSED | 
SHACL spec is too loose with its uses of terminology | 
2016-03-30 | 
SHACL Spec | 
0 | 
ISSUE-143  pre-binding in core | 
CLOSED | 
more pre-binding is needed in Section 3 | 
2016-04-08 | 
SHACL - Core | 
0 | 
ISSUE-144  substitution | 
CLOSED | 
substitution is sometimes used instead of pre-binding | 
2016-04-08 | 
SHACL Spec | 
0 | 
ISSUE-145  minExclusive code incorrect | 
CLOSED | 
the SPARQL code for sh:minExclusive is incorrect | 
2016-04-08 | 
SHACL - Core | 
0 | 
ISSUE-146  sh:qualifiedMinCount  | 
CLOSED | 
treatment of unbound results from sh:hasShape in sh:qualifiedMinCount (and elsewhere) | 
2016-04-08 | 
SHACL - Core | 
0 | 
ISSUE-147  vocabulary typos | 
CLOSED | 
[EDITORIAL] misspelled vocabulary in specification document | 
2016-04-10 | 
SHACL Spec | 
0 | 
ISSUE-148  scope syntax | 
CLOSED | 
non-uniform syntax in scopes | 
2016-04-15 | 
SHACL - Core | 
0 | 
ISSUE-149  ? vs $ in nodeKind | 
CLOSED | 
the SPARQL codefor nodeKind uses both ?value and $value | 
2016-04-18 | 
SHACL - Core | 
0 | 
ISSUE-150  nested severities | 
CLOSED | 
Treatment of nested severities | 
2016-04-18 | 
SHACL Spec | 
0 | 
ISSUE-151  illegal shapes | 
CLOSED | 
[EDITORIAL] shape for sh:and is illegal | 
2016-04-18 | 
SHACL Spec | 
0 | 
ISSUE-152  sh:labelTemplate not defined | 
CLOSED | 
sh:labelTemplate should be defined for all its uses | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-153  sh:sourceConstraintComponent modality | 
CLOSED | 
[EDITORIAL] sh:sourceConstraintComponent is not required but some wording indicates that it is | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-154  value set not defined | 
CLOSED | 
the description of sh:equals and sh:disjoint use the term "value set", which is not defined | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-155  property pair constraints | 
CLOSED | 
problems in the description of property pair constraints | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-156  property pair constraints | 
CLOSED | 
problems in the description of property pair constraints | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-157  constraint component support | 
CLOSED | 
the support for constraint components is incorrectly stated | 
2016-04-28 | 
SHACL Spec | 
0 | 
ISSUE-158  ill-typed literals and sh:datatype | 
CLOSED | 
ill-typed literals do not always trigger a validation result | 
2016-04-29 | 
SHACL - Core | 
0 | 
ISSUE-159  | 
CLOSED | 
[Editorial] Eliminate "scope class" from 2.1.3.n | 
2016-05-01 | 
SHACL Spec | 
0 | 
ISSUE-160  Generalize sh:valueShape | 
CLOSED | 
Shall we generalize sh:valueShape to sh:shape | 
2016-05-11 | 
SHACL - Core | 
0 | 
ISSUE-161  terminology | 
CLOSED | 
[EDITORIAL] terminology fixups | 
2016-05-14 | 
SHACL Spec | 
0 | 
ISSUE-162  section 1.2 editorial | 
CLOSED | 
[EDITORIAL] Section 1.2 | 
2016-05-14 | 
SHACL Spec | 
0 | 
ISSUE-163  "constraining" | 
CLOSED | 
should "constraining" and other forms of "constraint" be used less in the specification | 
2016-05-19 | 
SHACL Spec | 
0 | 
ISSUE-164  mutable graphs | 
CLOSED | 
[EDITORIAL] Section 1.4 (and maybe other places) looks as if graphs are mutable | 
2016-05-19 | 
SHACL Spec | 
0 | 
ISSUE-165  shapes and scopes introduction | 
CLOSED | 
[EDITORIAL] The introduction of shapes and scopes has confused a reader | 
2016-05-19 | 
SHACL Spec | 
0 | 
ISSUE-166  two documents | 
CLOSED | 
separate out advanced part of specification | 
2016-05-19 | 
SHACL Spec | 
0 | 
ISSUE-167  implicit class scope | 
CLOSED | 
[EDITORIAL] implicit class scope gives impression of inferencing | 
2016-05-19 | 
SHACL Spec | 
0 | 
ISSUE-168  instance count | 
CLOSED | 
How to constrain number of instances of a class in a graph | 
2016-06-13 | 
SHACL - Core | 
0 | 
ISSUE-169  sh:scopeProperty naming | 
CLOSED | 
Should we rename sh:scopeProperty/InverseProperty | 
2016-06-18 | 
SHACL - Core | 
0 | 
ISSUE-170  exists blank nodes | 
CLOSED | 
SPARQL specifies a different reading for exists and blank nodes than needed for SHACL | 
2016-06-29 | 
SHACL Spec | 
0 | 
ISSUE-171  negated sh:classIn | 
CLOSED | 
sh:classIn SPARQL definition incorrect | 
2016-06-29 | 
SHACL Spec | 
0 | 
ISSUE-172  sh:nodeKind SPARQL definition | 
CLOSED | 
the sh:nodeKind SPARQL definition is unnecessarily complex | 
2016-06-29 | 
SHACL Spec | 
0 | 
ISSUE-173  Hiding SPARQL | 
CLOSED | 
[Editorial] Text related to SPARQL definitions needs to be hidden together with query | 
2016-07-08 | 
SHACL Spec | 
0 | 
ISSUE-174  Scopenode | 
CLOSED | 
Scopenode does not use RDF node definition | 
2016-07-11 | 
SHACL - Core | 
0 | 
ISSUE-175  scope naming | 
CLOSED | 
Alternate naming for term for scope / in-scope | 
2016-07-22 | 
SHACL - Core | 
0 | 
ISSUE-176  Rules | 
CLOSED | 
Should SHACL include a (simple) rules feature | 
2016-08-20 | 
SHACL - SPARQL | 
0 | 
ISSUE-177  abstract-syntax-disconnected | 
CLOSED | 
Abstract Syntax is disconnected from concrete syntax | 
2016-09-07 | 
 | 
0 | 
ISSUE-178  sh:message constraints | 
CLOSED | 
Should sh:message be permitted at constraints, too? | 
2016-09-21 | 
SHACL - Core | 
0 | 
ISSUE-179  label annotations | 
CLOSED | 
Should SHACL include a mechanism to specify display labels? | 
2016-09-22 | 
SHACL Spec | 
0 | 
ISSUE-180  Path bnodes | 
CLOSED | 
Should IRI paths always be interpreted as predicates? | 
2016-09-29 | 
SHACL Spec | 
0 | 
ISSUE-181  | 
CLOSED | 
SHACL conformance for partial validation reports | 
2016-09-29 | 
SHACL Spec | 
0 | 
ISSUE-182  Validation report | 
CLOSED | 
Clarifications needed to section 3.0 | 
2016-09-29 | 
SHACL Spec | 
0 | 
ISSUE-183  undefined term | 
CLOSED | 
Eliminating the term "Undefined" | 
2016-10-02 | 
SHACL Spec | 
0 | 
ISSUE-184  paths & value nodes | 
CLOSED | 
Property paths and value nodes | 
2016-10-02 | 
SHACL Spec | 
0 | 
ISSUE-185  processing order | 
CLOSED | 
Processing order for filters and constraints | 
2016-10-02 | 
SHACL Spec | 
0 | 
ISSUE-186  validation report properties | 
CLOSED | 
Properties in validation report mis-use shapes graph properties | 
2016-10-09 | 
 | 
0 | 
ISSUE-187  severity and message | 
CLOSED | 
sh:severity and sh:message are not defined as shapes graph properties | 
2016-10-09 | 
 | 
0 | 
ISSUE-188  define validation | 
CLOSED | 
"Validation" needs to be defined | 
2016-10-09 | 
 | 
0 | 
ISSUE-189  validation trigger | 
CLOSED | 
Clarify validation report trigger in section 3 | 
2016-10-09 | 
 | 
0 | 
ISSUE-190  Shape identification | 
CLOSED | 
Identifying the shapes in a SHACL Full shapes graph  | 
2016-10-13 | 
SHACL - SPARQL | 
0 | 
ISSUE-191  Parameter value types | 
CLOSED | 
Should the value types of parameters be constraints | 
2016-10-18 | 
SHACL Spec | 
0 | 
ISSUE-192  Are filter shapes shapes? | 
CLOSED | 
Should filter shapes be of type sh:Shape? if not, then what? | 
2016-10-19 | 
 | 
0 | 
ISSUE-193  Focus nodes | 
CLOSED | 
[Editorial] Targets can be refined; focus nodes do not change | 
2016-10-27 | 
 | 
0 | 
ISSUE-194  valueStem | 
CLOSED | 
stems in value sets | 
2016-11-08 | 
 | 
0 | 
ISSUE-195  TTL File | 
CLOSED | 
[Editorial] Prepare TTL file for publication | 
2016-11-15 | 
SHACL Spec | 
0 | 
ISSUE-196  Delete filters | 
CLOSED | 
Should we delete filter shapes? | 
2016-11-16 | 
SHACL Spec | 
0 | 
ISSUE-197  Defined  | 
CLOSED | 
"Defined" and "declared" used in multiple ways, and not defined | 
2016-11-17 | 
SHACL Spec | 
0 | 
ISSUE-198  rdf:langString | 
CLOSED | 
rdf:langString not included in datatypes | 
2016-11-17 | 
SHACL Spec | 
0 | 
ISSUE-199  Constraint component IRIs | 
CLOSED | 
[Editorial] Constraint Component IRIs need to be defined before use | 
2016-11-17 | 
SHACL Spec | 
0 | 
ISSUE-200  Processors/ing | 
CLOSED | 
[Editorial] Processors, processing not defined | 
2016-11-17 | 
SHACL Spec | 
0 | 
ISSUE-201  node target | 
CLOSED | 
how does node target specify targets for a shape? | 
2016-11-17 | 
SHACL Spec | 
0 | 
ISSUE-202  Remove pre-binding from core | 
CLOSED | 
Suggestion to remove pre-binding from core | 
2016-11-17 | 
SHACL - Core | 
0 | 
ISSUE-203  Constraint components | 
CLOSED | 
Constraint component is an IRI | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-204  Constraint node | 
CLOSED | 
Fourth node is unclear | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-205  Validation report | 
CLOSED | 
Section 1.4 - graph is the result of validation | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-206  Target node | 
CLOSED | 
Not clear how a node target specifies targets for a shape | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-207  Parameters | 
CLOSED | 
Parameter descriptions for constraint components | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-208  $THIS | 
CLOSED | 
$this in aggregations | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-209  What is a shape? | 
CLOSED | 
What is a shape | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-210  Expected type | 
CLOSED | 
value types and expected types | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-211  property constraints | 
CLOSED | 
Eliminate property constraints | 
2016-11-20 | 
SHACL Spec | 
0 | 
ISSUE-212  Property constraints | 
CLOSED | 
Property constraints and focus node constraints | 
2016-11-22 | 
SHACL Spec | 
0 | 
ISSUE-213  Finding shapes | 
CLOSED | 
Finding shapes | 
2016-11-22 | 
SHACL Spec | 
0 | 
ISSUE-214  must & may | 
CLOSED | 
[Editorial] Read through for "must" and "may" | 
2016-11-30 | 
SHACL Spec | 
0 | 
ISSUE-215  literal parameters | 
CLOSED | 
parameters with a value type that is a datatype | 
2016-12-01 | 
SHACL Spec | 
0 | 
ISSUE-216  Style | 
CLOSED | 
[Editorial] Shall we switch to the (mathematical) style of definitions suggested by Peter? | 
2016-12-06 | 
SHACL - Core | 
0 | 
ISSUE-217  Path vs predicate clean up | 
CLOSED | 
Further clean up of paths versus predicate | 
2016-12-09 | 
SHACL - Core | 
0 | 
ISSUE-218  Move annotations | 
CLOSED | 
Should we move SPARQL Annotations mechanism into the WG Note? | 
2017-01-17 | 
SHACL - SPARQL | 
0 | 
ISSUE-219  One-of shapes | 
CLOSED | 
Should we add a one-of-a-list-of-shapes operator | 
2017-01-24 | 
SHACL - Core | 
0 | 
ISSUE-220  what is a shape | 
CLOSED | 
defining shapes in a shapes graph | 
2017-01-25 | 
SHACL - Core | 
0 | 
ISSUE-221  sh:Shape hierarchy | 
CLOSED | 
Simplify the class hierarchy of shapes | 
2017-01-25 | 
SHACL - Core | 
0 | 
ISSUE-222  Pre-binding 2 | 
CLOSED | 
Response to "On pre-binding" | 
2017-01-31 | 
SHACL - SPARQL | 
0 | 
ISSUE-223  Shapes mismatching type | 
CLOSED | 
Should we disallow shapes with mismatching type | 
2017-02-05 | 
SHACL - Core | 
0 | 
ISSUE-224  Improved shape type definitions | 
CLOSED | 
Can we improve the language around the use of rdf:types for shapes | 
2017-02-05 | 
SHACL - Core | 
0 | 
ISSUE-225  Validation Report details | 
CLOSED | 
Respond to "Validation results and reports" - part 1 | 
2017-02-08 | 
SHACL - Core | 
0 | 
ISSUE-226  JSON-LD @context | 
CLOSED | 
Should the WG produce a JSON-LD @context | 
2017-02-09 | 
 | 
0 | 
ISSUE-227  SPARQL-based constraint components using EXISTS | 
CLOSED | 
Behavior of SPARQL-based constraint components that use EXISTS | 
2017-02-09 | 
SHACL - SPARQL | 
0 | 
ISSUE-228  Form of the validation report | 
CLOSED | 
Respond to the comment about the form of the validation report | 
2017-02-10 | 
SHACL - Core | 
0 | 
ISSUE-229  results included in a validation report | 
CLOSED | 
Respond to the comment about what results to be included in a validation report | 
2017-02-10 | 
SHACL - Core | 
0 | 
ISSUE-230  $this and $PATH in sh:sparql | 
CLOSED | 
Inconsistency in the use of $this and $PATH in sh:sparql vs constraint components | 
2017-02-10 | 
SHACL - SPARQL | 
0 | 
ISSUE-231  sh:message in components | 
CLOSED | 
Could we allow sh:message for constraint components, not just validators? | 
2017-02-15 | 
SHACL - SPARQL | 
0 | 
ISSUE-232  Privacy and Security | 
CLOSED | 
Respec suggests a section on privacy and security | 
2017-02-15 | 
SHACL Spec | 
0 | 
ISSUE-233  Shapes syntax checking | 
CLOSED | 
Should we require support for checking of well-formed shapes graphs? | 
2017-02-21 | 
SHACL Spec | 
0 | 
ISSUE-234  Peter 2017-02-22 | 
CLOSED | 
Public comment https://lists.w3.org/Archives/Public/public-rdf-shapes/2017Feb/0165.html | 
2017-02-27 | 
SHACL Spec | 
0 |