> On 8 Jul 2019, at 20:53, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > <topbraid-users@googlegroups.com> wrote: > > 3. I found it strange that you are embedding a unit of measure into a string > e.g., “2.40m”. > > > well when the datatype is taken by the quantitykind...this is the only > > place left when using simple datatype properties........ > > its not that strange, often used for GIS like coordinates etc. (general: > > WKT-WellKnownText strings). > > https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry > > <https://en.wikipedia.org/wiki/Well-known_text_representation_of_geometry> > > (ex) >
The WKT is not really very similar to doing a special encoding of UoM inside a datatype. One is encoding lists of lists, arrays, etc. (which RDF cannot handle or cannot handle very nicely) of numerical values as strings, and the other is simply taking shortcuts with the modelling. As QUDT and other similar UoM ontologies show, it is not difficult to model and encode values with a UoM in normal RDF that require no specialised tools. Using an odd datatype encoding extension means that only specialised tools that understand that encoding can do any calculations, comparisons, etc. over those values. If the UoM is modelled in a normal way, then all RDF tools (e.g. vanilla SPARQL endpoints) can be used out-of-the-box to do calculations, comparisons, etc. Cheers, David UK +44 (0) 7788 561308 US +1 (336) 283-0808 -- 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 topbraid-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CA00F884-FF8F-4075-AD2D-945030D7BA6E%40topquadrant.com. For more options, visit https://groups.google.com/d/optout.
