RE: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
All clear, hopefully quick feedback and resolution! Thx for the good work! Let me know if you want me to test changes, Michel Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E michel.bo...@tno.nl

RE: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Great, thanks! Ps In the meantime I see that the qudt scheme (http://www.qudt.org/schema/qudt) now resolves to an RDF file (not a Turtle file) Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E michel.bo...@tno.nl

Re: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread Steve Ray
Michel, in browser: http://qudt.org/vocab/unit/M works fine http://qudt.org/vocab/quantitykind/Length works fine too http://qudt.org/schema/Unit does however not resolve I haven't yet tackled updating the schema files, so this will go on my list. > in unit.ttl it says: > # imports:

RE: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Hi Steve, see after > > My goals is to get qudt2.1 working without importing files (knowing that I > will have untypes stuff in tbc). So be able to use units, quantitykind by reference. To be able to make its possible to use both of them(also) as datatypes I added 2 triples in my own file to

Re: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread Steve Ray
As David mentioned, our class URIs do not have versions. So, http://qudt.org/vocab/unit/M resolves to either the ttl definition or an html file, depending on the header (turtle or html) (e.g. curl -i -H 'Accept: text/turtle' http://qudt.org/vocab/unit/M or curl -i -H 'Accept: text/html'

RE: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
- stability - security -performance Indeed all good reasons to do things locally. True. Still we see (even I engineering context) a trend towards distribution ie using the web it was meant to be. Clearly one needs more (pre)harmonization of modelling and linking approaches and agree on “who

Re: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread dprice
> On 17 Sep 2019, at 09:53, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > > Thx David for your extensive feedback. I see all your points (esp. from an > IDE viewpoint). At the same time we see a trend away from data > copy/import/exchange to sharing via publication ie more

Re: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread dprice
> On 17 Sep 2019, at 07:53, 'Bohms, H.M. (Michel)' via TopBraid Suite Users > wrote: > > > Mornin David, see after > > > Van: topbraid-users@googlegroups.com > mailto:topbraid-users@googlegroups.com>> > Namens dprice > Verzonden: Monday,

RE: [topbraid-users] qudt2.1 use issue

2019-09-17 Thread 'Bohms, H.M. (Michel)' via TopBraid Suite Users
Mornin David, see after > Van: topbraid-users@googlegroups.com Namens dprice Verzonden: Monday, September 16, 2019 4:50 PM Aan: topbraid-users@googlegroups.com Onderwerp: Re: [topbraid-users] qudt2.1 use issue On 16 Sep 2019, at 15:36, 'Bohms, H.M. (Michel)' via TopBraid Suite Users