According to 8.4 General Execution Instructions for SHACL Rules implementations modify the data graph if triples get inferred, and/or may "construct a logical data graph that has the original data as one subgraph and a dedicated inferences graph as another subgraph, and where the inferred triples get added to the inferences graph only."

I've been following the Classification With SHACL Rules article and I would like to extract the graph of inferred triples which would include <http://bakery.com/ns#AppleTartC> a <http://bakery.com/ns#NonGlutenFreeBakedGood>, <http://bakery.com/ns#VeganBakedGood> . merged into the data graph or as a inference graph.

Is this feature available?

If a PropertyShape is declared with sh:datetype xsd:string, instance data with a string with a language tag will trigger a validation error, declaring the string to not be of type xsd:string. This appears to be isolated to sh:datatype constraints; sh:nodeKind does not appear to influence this behavior.

I will be filing a PR in a moment to add a demonstration test, after getting an Issue number.

Hi there,

Validating an xsd:float gives me an unexpected validation report. I am using "PySHACL Version: 0.19.0".

Example:

shapes graph "shapes.json":

{
  "@context": {
    "owl": "http://www.w3.org/2002/07/owl#",
    "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
    "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
    "xsd": "http://www.w3.org/2001/XMLSchema#",
    "skos": "http://www.w3.org/2004/02/skos/core#",
    "prov": "http://www.w3.org/ns/prov#",
    "dcat": "http://www.w3.org/ns/dcat#",
    "sh": "http://www.w3.org/ns/shacl#",
    "shsh": "http://www.w3.org/ns/shacl-shacl#",
    "dcterms": "http://purl.org/dc/terms/",
    "schema": "http://schema.org/",
    "rescs": "http://rescs.org/"
  },
  "@graph": [
    {
      "@id": "rescs:dash/monetaryamount/MonetaryAmountShape",
      "@type": "sh:NodeShape",
      "rdfs:comment": {
        "@type": "xsd:string",
        "@value": "A monetary value or range. This type can be used to describe an amount of money such as $50 USD, or a range as in describing a bank account being suitable for a balance between £1,000 and £1,000,000 GBP, or the value of a salary, etc. It is recommended to use [[PriceSpecification]] Types to describe the price of an Offer, Invoice, etc."
      },
      "rdfs:label": {
        "@type": "xsd:string",
        "@value": "Monetary amount"
      },
      "sh:property": {
        "sh:datatype": {
          "@id": "xsd:float"
        },
        "sh:description": "The value of the quantitative value or property value node.\\\\n\\\\n* For [[QuantitativeValue]] and [[MonetaryAmount]], the recommended type for values is 'Number'.\\\\n* For [[PropertyValue]], it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'.\\\\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similiar Unicode symbols.\\\\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.",
        "sh:maxCount": {
          "@type": "xsd:integer",
          "@value": 1
        },
        "sh:minCount": {
          "@type": "xsd:integer",
          "@value": 1
        },
        "sh:minExclusive": 0,
        "sh:name": "value",
        "sh:path": {
          "@id": "schema:value"
        }
      },
      "sh:targetClass": {
        "@id": "schema:MonetaryAmount"
      }
    }
  ]
}

data sample "monetaryamount.json":

{
  "@context": {
    "@vocab": "http://schema.org/",
    "xsd": "http://www.w3.org/2001/XMLSchema#"
  },
  "@type": "MonetaryAmount",
  "value": {
    "@type": "xsd:float",
    "@value": 100000
  }
}

pyshacl -sf json-ld -s shapes.json -df json-ld monetaryamount.json gives me:

Validation Report Conforms: False Results (1): Constraint Violation in DatatypeConstraintComponent (http://www.w3.org/ns/shacl#DatatypeConstraintComponent): Severity: sh:Violation Source Shape: [ sh:datatype xsd:float ; sh:description Literal("The value of the quantitative value or property value node.\n\n* For [[QuantitativeValue]] and [[MonetaryAmount]], the recommended type for values is 'Number'.\n* For [[PropertyValue]], it can be 'Text;', 'Number', 'Boolean', or 'StructuredValue'.\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similiar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.") ; sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:minExclusive Literal("0", datatype=xsd:integer) ; sh:name Literal("value") ; sh:path schema1:value ] Focus Node: [ :value Literal("100000", datatype=xsd:float) ; rdf:type :MonetaryAmount ] Value Node: Literal("100000", datatype=xsd:float) Result Path: schema1:value Message: Value is not Literal with datatype xsd:float

Changing the @value to 100000.0 or "100000" makes it pass. However, I think all three variants should be valid, no?

I tried the example above on https://shacl.org/playground/ which worked fine.

Could you tell me whether I am doing something wrong or this is a bug?

Thanks a lot!

Is there an official pySHACL image and if not, could you release one and upload it for example at DockerHub? I could release one myself if you prefer but I think there are some advantages if the image is created and released by the developers of the project.

Hi there

I've been using pyshacl since a few days and I like it!

I noticed the --imports flag and wanted to try it right away after having read about it in #18.

So I tried the following:

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix schema: <http://schema.org/> .
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .

<http://datashapes.org/sh/tests/core/complex/personexample.test>
  rdf:type owl:Ontology ;
  rdfs:label "Test of personexample" ;
  owl:imports <http://datashapes.org/schema> ;
.

schema:PersonShape
    a sh:NodeShape ;
    sh:targetClass schema:Person ;
    sh:property [
        sh:path schema:gender ;
        sh:in ( "female" "male" ) ;
    ] .

Which gives me the error:

Bad syntax (expected '.' or '}' or ']' at end of statement) at ^ in: "b'\n\n \n '^b'<META http-equiv="Content-Type" content="text/html; charset='..." File "/usr/local/lib/python3.9/site-packages/rdflib/graph.py", line 1256, in parse raise ParserError( rdflib.exceptions.ParserError: Could not guess RDF format for <rdflib.parser.InputSource object at 0x10f9f1730> from file extension so tried Turtle but failed.You can explicitly specify format using the format argument.

I figured that the source of the problem is that it got HTML instead of Turtle.

So I tried:

...
owl:imports <http://datashapes.org/schema.ttl> ; --> note the ttl extension
...

And got:

rdflib.plugins.parsers.notation3.BadSyntax: at line 4 of <>: Bad syntax (expected '.' or '}' or ']' at end of statement) at ^ in: "...b'ttp://topbraid.org/tosh">\n <owl:Ontology rdf:about="">\n '^b'sh:declare\n sh:PrefixDeclaration\n <sh:prefix'..." raise ParserError( rdflib.exceptions.ParserError: Could not guess RDF format for <rdflib.parser.InputSource object at 0x110035cd0> from file extension so tried Turtle but failed.You can explicitly specify format using the format argument.

This time it was XML instead of Turtle (https://www.topbraid.org/tosh). http://datashapes.org/schema.ttl imports http://datashapes.org/dash which imports https://www.topbraid.org/tosh. Manually, I can easily figure out that it should be https://www.topbraid.org/tosh.ttl but I have no control over this using pyshacl.

So my question is: Is there some mechanism for content negotiation (HTTP accept header) or some convention regarding the file extension pyshacl could use when processing owl:imports to avoid the problem described above?

https://github.com/RDFLib/pySHACL/issues/92 fixed RDFLib 6.0, but a big change in RDFlib 6.0 was integrating rdflib_jsonld into RDFlib itself: https://github.com/RDFLib/rdflib/pull/1354

Due to this, the rdflib_jsonld project has been archived and is not maintained anymore: https://github.com/RDFLib/rdflib-jsonld#archived

Since rdflib_jsonld cannot be installed anymore with the newest version of setuptools, since it has use_2to3 set to true, see https://github.com/pypa/setuptools/issues/2769, this makes pySHACL unusable with JSON-LD with the newest version of setuptools.

Graph().serialize(format='json-ld') should just work out of the box now with RDFLib 6.0.

One slightly related issue (but irrelevant if the move away from rdflib_jsonld is done) is that the code in https://github.com/RDFLib/pySHACL/blob/master/pyshacl/rdfutil/load.py#L21-L26 doesn't work:

File "/home/zenon/DEV/ETH/renku-python/renku/core/utils/shacl.py", line 21, in <module>
    from pyshacl import validate
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/__init__.py", line 4, in <module>
    from .shapes_graph import ShapesGraph
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/shapes_graph.py", line 7, in <module>
    from .constraints.constraint_component import CustomConstraintComponentFactory
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/constraints/__init__.py", line 4, in <module>
    from pyshacl.constraints.constraint_component import ConstraintComponent
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/constraints/constraint_component.py", line 36, in <module>
    from pyshacl.rdfutil import stringify_node
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/rdfutil/__init__.py", line 7, in <module>
    from .load import get_rdf_from_web, load_from_source  # noqa: F401
  File "/home/zenon/.pyenv/versions/renku-python/lib/python3.7/site-packages/pyshacl/rdfutil/load.py", line 22, in <module>
    import rdflib_jsonld  # noqa: F401
ModuleNotFoundError: No module named 'rdflib_jsonld'

It raises a ModuleNotFoundError for me, not an IndexError on Python 3.7.4

Unless I have overlooked something, the SHACL spec does not state that the severity of a sh:not (a property shape) is by default sh:violation. Therefore, I would think that a sh:not with sh:severity sh:Warning should return warnings. That is not the case when testing with this minimal example below:

@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix ex: <http://example.org/ex#> .

ex:Foo ex:prop1 "a" .

ex:FooShape
    sh:targetNode ex:Foo ;
    sh:not [
        a sh:PropertyShape ;
        sh:path ex:prop1 ;
        sh:hasValue "a" ;
        sh:severity sh:Warning ;
    ] ;
.

The output is:

$ pyshacl -s foo.ttl foo.ttl
Validation Report
Conforms: False
Results (1):
Constraint Violation in NotConstraintComponent (http://www.w3.org/ns/shacl#NotConstraintComponent):
        Severity: sh:Violation
        Source Shape: ex:FooShape
        Focus Node: ex:Foo
        Value Node: ex:Foo
        Message: Node ex:Foo conforms to shape [ rdf:type sh:PropertyShape ; sh:hasValue Literal("a") ; sh:path ex:prop1 ; sh:severity sh:Warning ]

In the report the resource found in a http://www.w3.org/ns/shacl#value is empty, see the json below.

[
  {
    ...
    "@type": [
      "http://www.w3.org/ns/shacl#ValidationResult"
    ],
    "http://www.w3.org/ns/shacl#focusNode": [
      {
        "@id": "http://vangoghmuseum.nl/data/artwork/d0005V1962"
      }
    ],
    ...
    "http://www.w3.org/ns/shacl#value": [
      {
        "@id": "_:N6087b61f1f1d44e08519420c185ba3f2"
      }
    ]
  },
  {
    "@id": "_:N6087b61f1f1d44e08519420c185ba3f2"
  },

This report is the result of a propertyShape with a sh:node constraint. The first validation result in the example contains the information of the shape containing the sh:node. This fine. The value (N6087b61f1f1d44e08519420c185ba3f2) should contain the information of the result for the sh:node. I confirmed this in TopBraid.

The path is not getting interpreted correctly: file://c:\my\full\path\test.ttl/ does not look like a valid URI, trying to serialize this will break.

I've tried with forward slashes, backslashes, no slashes (all files in current directory), full filespec (with and without c:), etc. Couldn't get any of them to work.

Windows 10.

Hi @ashleysommer ,

I am trying to write a small "Gluing" SHACL shapes graph that combines two ontologies that have their own SHACL shapes. One of the gluing points is I want to make a ClassAB that is a subclass of classA and classB. classA has a certain property, propertyA, with a minimum-cardinality constraint, sh:min 1, and classB has an analagous property, propertyB, without that cardinality constraint. My use case happens to call for, whenever propertyA is assigned, propertyB should also be assigned with the same target. (The benefits to doing this lie in the class hierarchy above and below this "Gluing point.")

This feels to me like a good opportunity to try some multiple-inheritance with classes and with properties. However, when I tried defining a subproperty propertyAB, this was not being recognized by pyshacl as a usage of propertyA or propertyB.

I think I know the answer is basically "Yes, that's right," due to this quote from @HolgerKnublauch:

... sh:paths do not look at rdfs:subPropertyOf ...

and also from not seeing the word "subProperty" appear anywhere in the SHACL specification.

I can resort to a some scripting to save a little bit of typing, and/or sh:sparql to still make the data guarantees I want to make. But, is it true that rdfs:subPropertyOf will just be ignored by SHACL?

This issue can be reproduced with the following shapes graph and instance data. The expected sh:focusNodes are the ones with the comment of XFAIL. The ones actually returned are:

• kb:classApropertyAB
• kb:classApropertyB
• kb:classBpropertyAB
• kb:classBpropertyA

shapes.ttl:

@prefix ex: <http://example.org/ontology/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix sh: <http://www.w3.org/ns/shacl#> .

ex:ClassA
	a
		owl:Class ,
		sh:NodeShape 
		;
	sh:property [
		a sh:PropertyShape ;
		sh:minCount 1 ;
		sh:nodeKind sh:BlankNodeOrIRI ;
		sh:path ex:propertyA
	] ;
	sh:targetClass ex:ClassA ;
	.

ex:ClassB
	a
		owl:Class ,
		sh:NodeShape 
		;
	sh:property [
		a sh:PropertyShape ;
		sh:minCount 1 ;
		sh:nodeKind sh:BlankNodeOrIRI ;
		sh:path ex:propertyB
	] ;
	sh:targetClass ex:ClassB ;
	.

ex:propertyA
	a owl:ObjectProperty ;
	.

ex:propertyB
	a owl:ObjectProperty ;
	.

ex:propertyAB
	a owl:ObjectProperty ;
	rdfs:subPropertyOf
		ex:propertyA ,
		ex:propertyB
		;
	.

data.ttl:

@prefix ex: <http://example.org/ontology/> .
@prefix kb: <http://example.org/kb/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

kb:classApropertyA
	a ex:ClassA ;
	rdfs:comment "PASS" ;
	ex:propertyA [] ;
	.

kb:classApropertyAB
	a ex:ClassA ;
	rdfs:comment "PASS" ;
	ex:propertyAB [] ;
	.

kb:classApropertyB
	a ex:ClassA ;
	rdfs:comment "XFAIL" ;
	ex:propertyB [] ;
	.

kb:classBpropertyA
	a ex:ClassB ;
	rdfs:comment "XFAIL" ;
	ex:propertyA [] ;
	.

kb:classBpropertyAB
	a ex:ClassB ;
	rdfs:comment "PASS" ;
	ex:propertyAB [] ;
	.

kb:classBpropertyB
	a ex:ClassB ;
	rdfs:comment "PASS" ;
	ex:propertyB [] ;
	.

The command I used to see the failure was:

pyshacl -s shapes.ttl data.ttl

This patch series will add tests to confirm behaviors of XSD integer types aside from xsd:integer. It stems from trying to test a sample with a literal "0"^^xsd:positiveInteger and not receiving an error.

It is not entirely clear to me if corrections from this patch series should be in pySHACL or upstream in RDFLib.

This is a port of a comment I'd made on Sep. 16 on Issue 89. I've migrated the comment here to avoid expanding the scope of that ticket.

I've come across undesired behavior related to pySHACL's ontology graph and shapes graph mix-in strategy. The short of it is, my community adopted a SHACL-based mechanism to review some OWL requirements and cross-check SHACL and OWL definitions with general patterns. (The shapes graph for this is here. We'd also appreciate hearing if you've seen something like this elsewhere; we couldn't find something like it.) My community's ontology is managed as Turtle files, one per namespace, and each Turtle file includes all OWL and SHACL statements for concepts in that namespace.

What we didn't appreciate is that this incurs a significant cost on reviewing all data graphs, due to the mix-in strategy, so our "TBox"-targeting tests also run on "ABox" data review because pyshacl mixes the "ontology" TBox and ABox stuff together. With our ontology (a few hundred classes and properties, each with associated SHACL shapes), this is a 20--30 second cost per pyshacl run, guaranteed to be redundantly re-reviewing the ontology.

So, I'd like to discuss whether the whole ontology mix-in is still the right approach in all cases.

The case my community is facing at the moment is our ontology is written including SHACL shapes and OWL definitions in the same graph file, so we feed SHACL statements into .validate()'s ont_graph keyword argument. Question: Would the ontology graph pySHACL uses (ont_graph) ever be expected to include SHACL statements? My guess is no.

I was considering whether there could be a further reasonable trim based on the user's inferencing capabilities request, but I think the answer there may be no. I suspect SHACL-SPARQL makes the whole ontology graph always potentially necessary, though I can't think of a good example at the moment - maybe linking via some annotation property only available in the ontology, or searching for deprecated classes?

For now, my one question is just the SHACL-in-ontology-graph question: Can SHACL be safely trimmed from the ontology graph?

Dear RDFlib people!

I have a combination of SHACL shapes. With "meta_shacl= True" they are processed but leaving a trace in the wake.

With "meta_shacl= False" I get only a stack trace.

Evidence below.

I do not understand this behavior. Can anyone please shed light. I would have expect the behavior reversed.

Cheers, Volker

Setting meta_shacl= True :

/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/bin/python /home/volker/workspace/PYTHON5/SHACL_validation/shacl/validate.py 
Shacl File does not validate against the Shacl Shapes Shacl file.
Validation Report
Conforms: False
Results (21):
Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent):
	Severity: sh:Violation
	Source Shape: [ sh:maxCount Literal("0", datatype=xsd:integer) ; sh:path sh:path ]
	Focus Node: [ sh:hasValue <http://publications.europa.eu/resource/dataset/planned-availability> ; sh:path skos:inScheme ]
	Result Path: sh:path
	Message: More than 0 values on [ sh:hasValue <http://publications.europa.eu/resource/dataset/planned-availability> ; sh:path skos:inScheme ]->sh:path
Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent):
	Severity: sh:Violation
	Source Shape: [ sh:maxCount Literal("0", datatype=xsd:integer) ; sh:path sh:path ]
	Focus Node: [ sh:hasValue <http://dcat-ap.de/def/licenses> ; sh:path skos:inScheme ]
	Result Path: sh:path
	Message: More than 0 values on [ sh:hasValue <http://dcat-ap.de/def/licenses> ; sh:path skos:inScheme ]->sh:path
Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent):
	Severity: sh:Violation
	Source Shape: [ sh:maxCount Literal("0", datatype=xsd:integer) ; sh:path sh:path ]
	Focus Node: [ sh:hasValue <http://publications.europa.eu/resource/dataset/planned-availability> ; sh:path skos:inScheme ]
	Result Path: sh:path
	Message: More than 0 values on [ sh:hasValue <http://publications.europa.eu/resource/dataset/planned-availability> ; sh:path skos:inScheme ]->sh:path

then a trace.

Setting meta_shacl= False :

/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/bin/python /home/volker/workspace/PYTHON5/SHACL_validation/shacl/validate.py 
Traceback (most recent call last):
  File "/home/volker/workspace/PYTHON5/SHACL_validation/shacl/validate.py", line 31, in <module>
    conforms, report_graph, report_text = pyshacl.validate(
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/validate.py", line 435, in validate
    conforms, report_graph, report_text = validator.run()
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/validate.py", line 265, in run
    _is_conform, _reports = s.validate(
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/shape.py", line 511, in validate
    _is_conform, _reports = c.evaluate(target_graph, focus_value_nodes, _e_p)
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/constraints/core/shape_based_constraints.py", line 108, in evaluate
    _nc, _r = _evaluate_property_shape(p_shape)
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/constraints/core/shape_based_constraints.py", line 102, in _evaluate_property_shape
    _is_conform, _r = prop_shape.validate(target_graph, focus=v, _evaluation_path=_evaluation_path[:])
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/shape.py", line 511, in validate
    _is_conform, _reports = c.evaluate(target_graph, focus_value_nodes, _e_p)
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/constraints/core/shape_based_constraints.py", line 196, in evaluate
    _nc, _r = _evaluate_node_shape(n_shape)
  File "/home/volker/workspace/venvs/shacl-v-H5Zt4z-py3.9/lib/python3.9/site-packages/pyshacl/constraints/core/shape_based_constraints.py", line 182, in _evaluate_node_shape
    raise ReportableRuntimeError(
pyshacl.errors.ReportableRuntimeError: Shape pointed to by sh:node does not exist or is not a well-formed SHACL NodeShape.

Process finished with exit code 1

Dear RDFlib developers!

At first thank you so much! Without your code our Open-Data Portal https://datenadler.de would never have taken flight. We do not use CKAN, we programmed from scratch. Currently we are the second most populated Open-Data portal in Germany.

But now we need SHACL. pySHACL generally runs fine but I seems that we are running into some detail problems.

This may be an exotic case. It does not work on other SHACL processors, too. So it may be a limitation of SHACL itself.

So this is not a bug report but more stating of a SHACL fact.

Given the following data

xsd:dateTimeStamp rdfs:subClassOf xsd:dateTime .

<https://geobasis-bb.de#dcat_Dataset_568978c5-fa73-48d1-a6f9-487aabdc1aef> a dcat:Dataset;
  dct:description "Für die Digitalen Topographischen Karten werden Vektordaten.."@de;
  dct:identifier "568978c5-fa73-48d1-a6f9-487aabdc1aef";
  dct:modified "2022-11-17T09:37:25.626789"^^xsd:dateTimeStamp;

and the following shape

:DateOrDateTimeDataType_Shape
    a sh:NodeShape ;
    rdfs:comment "Date time date disjunction shape checks that a datatype property receives a temporal value: date, dateTime, gYear or gYearMonth literal" ;
    rdfs:label "Date time date disjunction" ;
    sh:message "The values must be data typed as either xsd:date, xsd:dateTime, xsd:gYear or xsd:gYearMonth" ;
    sh:or ([
            sh:datatype xsd:date
        ]
        [
            sh:datatype xsd:dateTime
        ]
		[
            sh:datatype xsd:gYear
        ]
		[
            sh:datatype xsd:gYearMonth
        ]
    ) .

OK, the files are a bit more complex but it boils down to that.

We get an 

Validation Report
Conforms: False
Results (20):
Constraint Violation in NodeConstraintComponent (http://www.w3.org/ns/shacl#NodeConstraintComponent):
	Severity: sh:Violation
	Source Shape: :Dataset_Property_dct_issued
	Focus Node: <https://geobasis-bb.de#dcat_Dataset_568978c5-fa73-48d1-a6f9-487aabdc1aef>
	Value Node: Literal("2022-11-17T09:37:25.626872" = None, datatype=xsd:dateTimeStamp)
	Result Path: dct:issued
	Message: Value does not conform to Shape :DateOrDateTimeDataType_Shape

Is it possible with pySHACL to inject the inheritance information:

xsd:dateTimeStamp rdfs:subClassOf xsd:dateTime .

If so, how? Any help appreciated.

Cheers, Volker

Dear PySHACL Developers!

PySHACL fails to open a http resource if it is chunked. I propose a quickfix and additional info below the stacktrace.

Code to reproduce:

from pyshacl.rdfutil import load_from_source

load_from_source('http://publications.europa.eu/resource/dataset/planned-availability')

Stacktrace:

Traceback (most recent call last):
  File "/usr/lib/python3.9/xml/sax/expatreader.py", line 217, in feed
    self._parser.Parse(data, isFinal)
xml.parsers.expat.ExpatError: syntax error: line 1, column 0

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/volker/workspace/PYTHON2/shacl/sandbox/error2.py", line 3, in <module>
    load_from_source('http://publications.europa.eu/resource/dataset/planned-availability')
  File "/home/volker/workspace/venvs/shacl-WIAd6my0-py3.9/lib/python3.9/site-packages/pyshacl/rdfutil/load.py", line 352, in load_from_source
    target_g.parse(source=cast(IO[bytes], _source), format=rdf_format, publicID=public_id)
  File "/home/volker/workspace/venvs/shacl-WIAd6my0-py3.9/lib/python3.9/site-packages/rdflib/graph.py", line 1330, in parse
    parser.parse(source, self, **args)
  File "/home/volker/workspace/venvs/shacl-WIAd6my0-py3.9/lib/python3.9/site-packages/rdflib/plugins/parsers/rdfxml.py", line 604, in parse
    self._parser.parse(source)
  File "/usr/lib/python3.9/xml/sax/expatreader.py", line 111, in parse
    xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib/python3.9/xml/sax/xmlreader.py", line 125, in parse
    self.feed(buffer)
  File "/usr/lib/python3.9/xml/sax/expatreader.py", line 221, in feed
    self._err_handler.fatalError(exc)
  File "/usr/lib/python3.9/xml/sax/handler.py", line 38, in fatalError
    raise exception
xml.sax._exceptions.SAXParseException: <unknown>:1:0: syntax error

Process finished with exit code 1

The case of the problem is in load.py : 161

                filename = resp.geturl()
                fp = resp.fp  # type: BufferedIOBase
                source_was_open = False
                source = open_source = fp

Here the filepointer resp.fp of the response is used as source for the parser. This goes well as long as the response is not chunked.

If the response is chunked there is a difference between

resp.read(20) b'<rdf:RDF\n xmlns:r'

and

resp.fp.read(20) b'3ae7\r\n<rdf:RDF\n x'

This is due to the fact that fp is the low level filepointer, which has to be used differently with chunking. b'3ae7\r \n' is position of the next chunk.

Patching load.py : 161 to

fp = resp solves the problem for this case.

But this code is complex and maybe some other use cases do need the use of the filepointer.

Cheers,

Volker

I would like to share a reusable GitHub Actions workflow to use pySHACL in a CI pipeline. The repository is https://github.com/KonradHoeffner/shacl and it is on the market place as konradhoeffner/[email protected]. I found it really useful for our projects and would like to know if this is useful for the pySHACL developers / userbase. If yes, are you interested in integrating it into pySHACL and/or the RDFLib organization? If you are interested and it makes sense to integrate it directly into this repository, then I could create a pull request. However I'm not sure how that would be managed in the best way, because right now it installs the newest version <2 from pip, and maybe the action number should be synchronized with the pySHACL version.

Example

On https://github.com/hitontology/ontology you can see an example of how it works.

Workflow

The workflow .github/workflows/shacl.yaml calls the reusable workflow konradhoeffner/[email protected] (could be @v1 as well).

name: SHACL

on:
  workflow_dispatch:
  push:
    branches:
      - dist

jobs:
  shacl:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/[email protected]
        with:
          ref: 'dist'

      - name: Build and Validate
        uses: konradhoeffner/[email protected]
        with:
          data: all.ttl
          shacl: shacl.ttl

Status report on success

Status report on failure from another repository

Badge

Technical details and history

At first there was a separate workflow that built a Dockerfile that just installed pySHACL on top of a Python image and included a custom entry point script that calls pySHACL in a loop over the potentially multiple data files and that creates the right output strings to interface with GitHub to get nice output like errors, warnings and info notifications and groups. The reason to use a Dockerfile was that GitHub actions use a lot of time and clutter the log with messages to install dependencies and I wanted a quick build time and a clean log with only the statements that are interesting for the user who is validating SHACL data and is not interested in logging about installing things. However I learned that while Docker is amazing for many things, it is not the preferred GitHub-way of doing things, because an action already has a "runner" which is kind of like a virtual machine / container, and using Docker on top of that does seem to integrate that well. For example, the idea was to build the Docker image only once and save all the time for setup, but now GitHub actions would create the Docker image at every run, ruining all the potential benefits. So I had to create another workflow inside the repository that built the Dockerfile and deployed it to the GitHub container registry. While this was a few seconds quicker and the output more clean, this approach was much too convoluted and could get out of sync between the Docker image and the action itself, for example when running an older version of the workflow. So the current version v1 replaces the Dockerfile with a composite action that installs Python and then runs the entrypoint script directly. While that created a few problems, for example that a workflow referencing the shared workflow from another repository couldn't access the entrypoint script or that there was no file at the target repository to create a hash for the setup-python cache for, this was solvable by disabling the setup-python cache and using actions/cache instead and by using the ${{github.action_path}}.