FWIW, I can't say I agree
If you have a function which only works with a Property Path, you still
conditional code to check whether a Property Shape has a Property or
Sequence Path. It's just shifting that same complexity from one place to
another. At the same time sacrificing simple of use
FWIW on my machine this took 96 seconds to infer 272152 triples. Then
another minute or two to remove redundant inferences.
Our OWL-RL implementation is what it is. The design it a pretty
simplistic implementation of the spec. To take more control of
performance, use SPARQL CONSTRUCT queries?
This constraint is specified at
https://www.w3.org/TR/shacl/#property-path-sequence and was
intentionally designed like that. As you say it could theoretically have
the same effect as IRI properties, yet then the algorithms would need to
make an additional IF for the special case, and I assume
Hi
I was surprised to find out today that a Property Path declared as an RDF
List with only a single element is not a valid construct and fails
validation with SHACL.js
I would expect [ sh:path ( ex:property ) ] be treated equally to [ sh:path
ex:property ]
Why is sequence path defined to
> On 19 Feb 2021, at 13:24, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
> wrote:
>
> It seems it just took a long time….
> Result is there when patient enough
>
> Can this be speeded up ?
>
> It’s removing redundant stuff for a long time I see now…
All I can suggest wrt speed, is more
It seems it just took a long time….
Result is there when patient enough
Can this be speeded up ?
It’s removing redundant stuff for a long time I see now…
Thx michel
Dr. ir. H.M. (Michel) Bohms
Scientist Specialist
Structural Reliability
T +31 (0)88 866 31 07
M +31 (0)63 038 12 20
E
Wondering why my property chain is not inferred?
(I ticked the owl-rl profile)
I try to bring the valued properties from type-level to instance level.
Thx for any tip, Michel
Dr. ir. H.M. (Michel) Bohms
Scientist Specialist
Structural Reliability
T +31 (0)88 866 31 07
M +31 (0)63 038 12 20
E
