I'm hoping to get some help in modeling some node shapes and property shapes around a particular set of user needs. (This is in EDG 6.2.4.)
A simplified version of my scenario is this: - ex:SubClassA, ex:SubClassB, and ex:SubClassC are all subclasses of ex:SuperClass. All of these are owl:Classes and also sh:NodeShapes. - ex:property is an owl:ObjectProperty with an rdfs:domain of ex:SuperClass, although in reality it is applicable only to ex:SubClassA and ex:SubClassB, and NOT to ex:SubClassC. - I have defined a property shape for ex:property on ex:SuperClass, in order to establish some display settings and some constraints on permissible values and cardinality. My question is: How would I prohibit ex:property from appearing on Edit or Search forms for instances of ex:SubClassC, while still allowing users to use ex:property in searching for instances of ex:SuperClass? (For what it's worth, ex:SuperClass has no direct instances; only its subclasses do.) It seems to me that the best solution here would be to add a restriction to the property shape for ex:property, specifying that subjects of it must NOT be instances of ex:SubClassC, but I'm not sure how to do that because constraint expressions on property shapes generally constrain the value nodes, rather than the focus nodes. Does my approach even make sense, or is there a better way to do it? Thanks. -- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/b8e034ce-b6c4-4d72-960b-92ef0bad5b11%40googlegroups.com.
