Joshua Watt

And also there are plenty of examples of the relationship not necessarily matching the "conceptual" direction of the arrow

There is also: https://www.w3.org/TR/owl-ref/#Deprecation

https://github.com/JPEWdev/shacl2code/pull/46 adds support for `owl:DeprecatedClass` and `owl:DeprecatedProperty` to `shacl2code` and the generated bindings. If someone can explain how the `owl:deprecated` annotation is supposed to work, I can add that also;...

See #16 However, that PR needs to be reworked to support compiling against both the new version and the old version.

Ya, something seems incorrect about that. It's not showing any remote compiles on `icecc-worker-1` or `icecc-worker-2`

This is cause by the prefix in the annotations not matching the actual model prefix: https://github.com/spdx/spdx-spec/blob/260e8d97fbedc573282c9bd095fab2e3d80b4b29/serialization/jsonld/annotations.ttl#L1C1-L1C42 It looks like the annotations have been updated to use "3.0" for the version,...

> @JPEWdev - let me know if I'm on the right track and if this is usable for the HTML generator > > BTW - decided to write the example...

I disagree that `sh:nodeKind` is superfluous in all these cases; specifically for `owl:Class` and `sh:NodeShape`, `sh:nodeKind` can be either: `sh:BlankNodeOrIRI` -> The node can have either a blank node or...

> In spdx, all `Class, NodeShape` happen to be declared BlankNodeOrIri. That is superfluous. > > If spdx had insisted that resources of a certain class must be IRI or...

Ah, OK, so this is more of "don't specify what's already the default". We could possibly do that, but as long as having them in there isn't hurting anything, I...