David - > equivalentClass and exactMatch do not have the same semantics.
Yes, this is my point. equivalentClass is for relating classes to other classes, while exactMatch relates concepts to other concepts. And according to the SKOS model, concepts are individuals. They do not have the same semantics, primarily following from the fact that the subject and object are T-box in the one case, and A-box in the other. QUDT 1.1 is primarily a T-box model. All the principal resources are rdf:type owl:Class. In this context use properties that relate to classes. The target of the relationships (dbpedia resources) does not have a declared type anyway, so punning is not necessary. Simon Cox On Sun, Jul 14, 2013 at 8:13 PM, <[email protected]> wrote: > Today's Topic Summary > > Group: http://groups.google.com/group/topbraid-users/topics > > - QUDT - issues and prospects? <#13fdcaba7a08ca17_group_thread_0> [2 > Updates] > > QUDT - issues and > prospects?<http://groups.google.com/group/topbraid-users/t/4bb10ef52716a7f2> > > Simon Cox <[email protected]> Jul 13 04:16AM -0700 > > Is OWL2 punning in the DL profile? I thought it was only OWL Full. > > All the exactMatch and closeMatch assertions in QUDT relate to > resources of > rdf:type owl:Class. > Surely owl:equivalentClass would be more appropriate? > There is really no need to even call on punning. > > Simon > > On Friday, July 12, 2013 6:46:32 PM UTC+10, David Price wrote: > > > > > David Price <[email protected]> Jul 13 07:22PM +0100 > > In OWL Full there is no need for punning as a concept at all. Punning > exists in OWL 2 exactly to support meta-modeling in the OWL 2 Direct > Semantics spec. > > equivalentClass and exactMatch do not have the same semantics. > However, I'm not familiar with the details of the design rationale for QUDT > so can't really comment more on decisions made there. > > Cheers, > David > > On 13 Jul 2013, at 12:16, Simon Cox wrote: > > > > > -- > -- 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 Ensemble, 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/groups/opt_out. > > > -- -- 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 Ensemble, 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/groups/opt_out.
