Skip to content

SHACL template ontologies owl:imports themselves #10

Closed

Description

@opendpp-node

Summary

The bundled SHACL templates declare their ontology as importing itself, which is a no-op
(and can send import-resolving loaders into a redundant self-fetch).

Where

# core/src/test/resources/shacl-templates/battery_pass_shacl.ttl:8-9
<http://example.org/battery-passport> a owl:Ontology ;
    owl:imports <http://example.org/battery-passport> .

Same pattern in:

  • core/src/test/resources/shacl-templates/vehicle_shacl.ttl:9-10
  • core/src/test/resources/shacl-templates/electronics_shacl.ttl:8-9
  • api/rest/src/test/resources/shacl-templates/test-addition.ttl:8-9
  • datastore/pgsql/src/test/resources/shacl-templates/test-addition.ttl:8-9

Suggested fix

Drop the self-referential owl:imports line from each template (or point it at a real
imported vocabulary if an import was intended).

Context

Spotted while building an implementer node against your suite. Happy to send a one-line PR if useful — just wanted to flag it separately from the
shapes contribution in #9.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions