Hi, I find the semantics of local class restrictions, particularly the use of "some" vs "all", unintuitive for the less knowledgeable and not as friendly for re-use when attempting to automatically discover the ontology within a collection of triples.
Thus, I'm considering creating my own framework for declaring relationships between properties and classes. Before I do, is there any support for this within the current implementation of SPIN? I was looking through all of the available templates and it seems that spl:Attribute may contain most of the semantics I wish to express such as: 1. Associating a property to a class 2. Defining the "type" of said property 3. Min/Max cardinality Assuming I'm interpreting the intended use of spl:Attribute correctly, is there a way to handle cases where the object of the property could be of type Class1 OR Class2 OR Class3... etc? Thanks for your insight, Tim -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en --- 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.
