-
#### Issue type:
- :bug: Bug
____
#### Description:
It looks like there is a regression issue. BIND-related tests in shacl-engine that passed on August 5th are now failing without any code c…
-
The current description somehow makes sense for JSON-LD, but it isn't very clear as content type independent definition.
Providing a shape in ShEx and SHACL should provide an unambiguous and validata…
-
**Describe the bug**
Validating BioLink RDF with SHACL generated by LinkML (for the biolink-model) fails due to the shapes being `sh:closed`.
Because the SHACL specs specify that an entity shoul…
-
Hello,
Would it be one day possible to build ldo from SHACL shapes ?
My main motivation it to be able to use this tool: https://github.com/ULB-Darmstadt/shacl-form allongside LDO .
thhck updated
7 months ago
-
In [VexNotAffectedVulnAssessmentRelationship](https://spdx.github.io/spdx-spec/v3.0.1/model/Security/Classes/VexNotAffectedVulnAssessmentRelationship/):
> Both impactStatement and justificationType…
-
We need to collect all metadata fields from our JSON-LD columns that should be translated (metadata_graph.metadata and project.metadata).
We can look those up from our legacy repo [GitHub - regen-n…
-
As suggested in the issue https://github.com/SEMICeu/DCAT-AP/issues/355 the contribution of a use case.
SHACL specifies that shacl:message overwrites the message generated by the engine.
Thus …
-
Shape languages already support this themself, such as `sh:not` in SHACL.
I think it’s redundant and confusing to have `si:excludes` as a concept here
-
If we don't always provide a SPARQL endpoint to SemApps instances, it would be important to at least be able to filter LDP containers (and AS collections !), which is where SPARQL is the most relevant…
-
Followup to #52:
- @afs : Have you decided on what complexity the grammar should be?
SPARQL is LL(1), which is simple in tech terms. It is compatible with LALR(1) there are parser generators for e…