I see your point. Using sh:class still worked with the superclass
(c223:InletPoint).
Here is my working shape (this time for an InletPoint, which has a
subClassOf AirInletPoint):
b20:InletPressureShape
rdf:type sh:PropertyShape ;
sh:path c223:hasInletPressure ;
sh:name "Inlet Pressure Sh
The type triples do work for me. Try for example the Kennedys example:
Here is the configuration that I used
Are we talking about the same things?
Holger
On 2020-12-11 6:14 pm, 'Bohms, H.M. (Michel)' via TopBraid Suite Users
wrote:
I sent them in my first mail
I have instances of a subcl
On 2020-12-12 3:59 am, Steve Ray wrote:
Holger,
Your example is tremendously helpful! Thanks so much. I can see how
the sh:filterShape and sh:nodes statements always come in pairs, and
that the outermost sh:path (inside the sh:values) needs an sh:nodes to
operate on. These are all things that
Dear Users,
TopQuadrant is pleased to announce the official release of TopBraid
6.4.3! This release includes a few improvements and bug fixes. If your EDG
application uses SAML, please follow the guidelines on the migrations page
of the documentation. For details, please see the Version 6.4.3
I sent them in my first mail
I have instances of a subclass of Anomaly.
After reasoning no instances of Anomaly.
Instances are in anomalies-f—ijsselbridge, rest is just imported
Like
aib:PartialLockingRotation_3
a anomaly:PartialLockingRotation ;
anomaly:forPhysicalObject ib:Pillar_H ;
a
