RE: [topbraid-users] from property to constraint

2019-07-09 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Wrt “strings to things” > fully agree, so the “quantityKind as datatype” is only relevant in the case > that the quantity is modelled the simplest wat (OPM L1) that is “as > owl:DatatypeProperty”. (other then going beyond DL putting the quantityKind > at the property declaration. Ps Over Su

RE: [topbraid-users] from property to constraint

2019-07-09 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Agreed. WKT strings in general need extra agreements on the string structure ie how to parse. Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E michel.bo...@tno.nl Location

RE: [topbraid-users] from property to constraint

2019-07-09 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Thx for the update Ralph, see after > “Dereferencing at the graph level is underway.” > That is exactly the feedback for years now. Do you have some point in time? QUDT is now very active again - take a look at the latest catalog which can be reached at www.qudt.org > Th

Re: [topbraid-users] from property to constraint

2019-07-09 Thread Irene Polikoff
I don’t believe that storing quantity kind with the measurements is required in any of the 3 options. With every option, including option 1, you are defining a resource :Height that is used when capturing measurements. And with every option, quantity kind is already associated with the :Height.