Thanks Holger.
If I undestand you correctly, the bottom line is that it doesn't make sense 
to develop/model, as a standard, any behavior that cannot stand alongside 
basic inferencing.
I think I agree with that.

I will have to read up on the Shapes WG and SHACL and possibly ask further 
questions there, but if you can
what are the similiarities and or differencies between the Shapes WG and 
the discussions at  https://lists.w3.org/Archives/Public/public-rdf-shapes/

Τη Σάββατο, 4 Απριλίου 2015 - 6:42:45 π.μ. UTC+3, ο χρήστης Holger 
Knublauch έγραψε:
>
>  Hi Nikolaos,
>
> this is certainly an interesting question, yet I don't see how to solve 
> this. As soon as inferencing is activated, and you have a class hierarchy 
> such as
>
> rdfs:Resource
>     ex:RootClass   rule1
>         ex:ChildClass   rule2 overrides rule1
>
> and ex:Instance a ex:ChildClass, then an inference engine would add 
> ex:Instance a ex:RootClass, and things become really messy to check. I 
> believe rules and constraints should only ever narrow down the semantics.
>
> It would help me to see a real-world example of such scenarios. Maybe 
> there are work-arounds using multiple inheritance/multiple rdf:types.
>
> BTW this is an interesting discussion in regards to the ongoing W3C Shapes 
> Working Group, that quite possibly creates something close to a "SPIN 2.0", 
> called SHACL [1]. In that spec, take a look at the proposed sh:scope 
> attribute that would allow you to place pre-conditions in front of 
> constraints.
>
> Thanks
> Holger
>
> [1] https://w3c.github.io/data-shapes/shacl/
>
>
>
> 

-- 
You received this message because you are subscribed to the Google Group 
"TopBraid Suite Users", the topics of which include Enterprise Vocabulary 
Network (EVN), Reference Data Manager (RDM), TopBraid Composer, TopBraid Live, 
TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to [email protected]
--- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to