Dear Ralph Any more info on qudt2? (when published)
Thx Michel Dr. ir. H.M. (Michel) Böhms Sr. Research Scientist Technical Sciences T +31 (0)88 866 31 07 M +31 (0)63 038 12 20 E [email protected]<mailto:[email protected]> Location<http://www.tno.nl/locaties/dtm> Disclaimer<http://www.tno.nl/emaildisclaimer> [cid:[email protected]]<http://www.tno.nl/> From: [email protected] [mailto:[email protected]] On Behalf Of Ralph TQ [Gmail] Sent: donderdag 29 augustus 2013 4:38 To: [email protected] Cc: [email protected] Subject: Re: [topbraid-users] QUDT and VAEM ontologies issues. Hi Artem, Thanks for pointing this out. We have placed a new version of VAEM 1.2 at qudt.org<http://qudt.org>'s catalog site - http://linkedmodel.org/doc/vaem/1.2/ . QUDT 1024 strings are fixed in version 2. Ralph Hodgson, @ralphtq<http://twitter.com/ralphtq> On Aug 26, 2013, at 3:47 AM, Artem Kozlov <[email protected]<mailto:[email protected]>> wrote: Hi Everyone, I've been trying to use qudt and vaem ontologies and have lots of troubles with them. I know that qudt version 2 will be released soon, so I wonder if all these issues are going to be fixed: Wrong definitions for custom datatypes. For example in vaem ontology there is custom datatype vaem:numericUnion: vaem:numericUnion rdf:type rdfs:Datatype ; rdfs:label "numeric union"^^xsd:string ; rdfs:subClassOf rdfs:Resource ; vaem:description "A datatype that is the union of numeric xsd data types. LMC's 'numericUnion' is equivalent to the xsd specification that uses an xsd:union of memberTypes='xsd:decimal xsd:double xsd:float xsd:integer'."^^xsd:string ; owl:unionOf (xsd:float xsd:decimal xsd:integer xsd:double) . It is wrong custom datatype definition, instead it should be: vaem:numericUnion rdfs:label "numeric union"^^xsd:string ; vaem:description "A datatype that is the union of numeric xsd data types. LMC's 'numericUnion' is equivalent to the xsd specification that uses an xsd:union of memberTypes='xsd:decimal xsd:double xsd:float xsd:integer'."^^xsd:string ; owl:equivalentClass [ rdf:type rdfs:Datatype; owl:unionOf (xsd:float xsd:decimal xsd:integer xsd:double) . ] . Or lets look into qudt: qudt:string1024 rdf:type rdfs:Datatype ; rdfs:label "string1024"^^xsd:string ; rdfs:subClassOf xsd:string ; owl:equivalentClass [ rdf:type rdfs:Datatype ; owl:onDatatype xsd:string ; owl:withRestrictions ([ xsd:maxLength "1024"^^xsd:nonNegativeInteger ]) ] . >From protege mailing list >(http://protege-ontology-editor-knowledge-acquisition-system.136.n4.nabble.com/Property-classified-as-DatatypeProperty-and-ObjectProperty-at-the-same-time-Bug-td4658771.html): " If you have X rdfs:subClassOf Y then X and Y must be class expressions (i.e. not data ranges - so the statement isn't valid OWL). " One more things that I've noticed is violation of your own constraints. For example there is property: qudt:description rdf:type owl:DatatypeProperty ; rdfs:label "description"^^xsd:string ; rdfs:range qudt:string1024 ; rdfs:subPropertyOf vaem:description . But almost everywhere you violate your own constraint, and use literal which is much bigger than 1024 characters. I hope you will take all of the above into consideration for version 2. And to be honest, I was very surprised that these bugs haven't been fixed (or even noticed) in version 1.1. Thanks, Artem. -- -- 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]<mailto:[email protected]> To unsubscribe from this group, send email to [email protected]<mailto:[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]<mailto:[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 Insight, SPARQLMotion, SPARQL Web Pages and SPIN. To post to this group, send email to [email protected]<mailto:[email protected]> To unsubscribe from this group, send email to [email protected]<mailto:[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]<mailto:[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 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/groups/opt_out.
<<inline: image001.gif>>
