Tomasz Pluskiewicz

Collection property not exposed with other properties

2

Hydra vocabulary clearly states that `hydra:collection` is a `hydra:Link`. Whatever tool performs the assertion regarding hydra vocabulary must understand it's semantics. _Originally posted by @alien-mcl in https://github.com/HydraCG/api-examples/pull/8_

Enabling typings generation (#32) forced me to make some members public on exported classes. I will change them back once Microsoft/TypeScript#17293 is fixed. * https://github.com/wikibus/Alcaeus/pull/32/files#diff-3ad85688dcca0ae5d4e6a61774dbbc32L9 * https://github.com/wikibus/Alcaeus/pull/32/files#diff-6c1185e51c6365a1c8252e6b2a50e2e5L39

Adding the well-known symbol will give nicer debugging output instead of whatever the result of applying mixins

While not exactly Hydra-specific, it would be good to add a convenient way to access `Link` headers attached to loaded resource

Provide a CLI

4

Would it be nice to have a simple CLI provided by this package. I would propose a simple interface which would load data+shapes to memory and offer at least two...

I suppose it would be as simple as a top-level result similar to ```turtle [] a sh:ValidationReport ; sh:result [ sh:resultSeverity sh:Warning ; sh:resultMessage "The maximum number of error (100)...

From what we have in Cube Creator ```turtle a sh:NodeShape; sh:property [ sh:message "needs a schema:name" ; sh:or ( [ sh:path schema:name ; sh:minCount 1 ; sh:datatype xsd:string ; ]...

Improve validation message of `sh:xone`

1

I would propose tweaking the detail validation result message when an XONE constraint is violated Currently it produces no message at all. Without even knowing which sub shapes are conflicted,...

Shape inheritance only works when single dataset is used

5

The validator supports shape hierarchies using `rdfs:subClassOf` but they are not applied correctly if the data graph and shapes graph are separate instances of `Dataset` Consider this [example](https://runkit.com/embed/8tb3fbh5v4k2). The result...

Weird RDF list returned as validation result focusNode

2

I don't understand but there seems to be a bug in the validation results. Here's an example shapes graph: ```turtle @prefix sh: . @prefix schema: . @prefix rdfs: . @prefix...