[topbraid-users] overspecified?

Would the 3 lines at the end be overdone/double? Or no harm? ex1:LoadLevel rdf:type owl:Class ; rdfs:SubClassOf owl:Thing ; owl:oneOf (ex1:Light ex1:Normal ex1:Heavy) . ex1:Light rdf:type ex1:LoadLevel . ex1:Normal rdf:type ex1:LoadLevel . ex1:Heavy rdf:type ex1:LoadLevel . thx for advice

Re: [topbraid-users] overspecified?

I always add the rdf:type statement for all individuals everywhere. Useful in SPARQL queries and in checking that an item has at least one value from a specific enumerated class. Example: X ex1:hasLoadLevel ex1:Light . Is easily checked by ASK {?x a . ?x ex1:hasLoadLevel ?value . ?value a e

RE: [topbraid-users] overspecified?

Hi David Thx. So if one would not have the instances one would have to rely/depend on reasoning first..? Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E michel.bo...@tno.nl Location

Re: [topbraid-users] overspecified?

> On 18 Dec 2018, at 12:35, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > > > Hi David > > Thx. > > So if one would not have the instances one would have to rely/depend on > reasoning first..? The ASK example I gave would indeed not work pre-reasoner. This is a completene

[topbraid-users] Did exports change with 6.1?

Hi, I'm running TBC ME 6.1, and just exported one of my projects to a zip archive, ready to deploy to TBL on the cloud. However, this time, I noticed that the zip file doesn't start at the project folder level, but rather two levels higher, at the root of our git repository. TBL was not happy with