Right, so can you confirm this is at the moment an issue for qudt2 files? Say 2 files both having ‘unit’ prefix but related to a different uri (although hsaring large part of that uri)
Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E [email protected]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707> [cid:[email protected]]<http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. From: [email protected] [mailto:[email protected]] On Behalf Of Irene Polikoff Sent: Wednesday, November 22, 2017 4:27 PM To: [email protected] Subject: Re: [topbraid-users] puzzled (unit:YR as datatype revisited) The best practice is to have each prefix declaration in one place only. Otherwise, you may end up with a situation where the same prefix is associated with two different namespaces and then the tool may sometimes resolve the name to one namespace and other times to another namespace. If, for some reason, you can’t have each prefix declaration be in only one place, you need to be very careful in checking them and making sure that there is one to one correspondence between a prefix and a namespace across all your graphs. On Nov 22, 2017, at 10:06 AM, Bohms, H.M. (Michel) <[email protected]<mailto:[email protected]>> wrote: Ok, so it works again with “add existing…” (by doing all the changes to the qudt2 files as attached). But still, not using “Add existing” but empty line, and then filling in manually “unit:YR” gives a red text that cannot be chosen….. <image001.png> (hint: if you “select existing..” first and then manually backspace to nothing and type unit:YR it staus black….) Leaves further: I have now two (or more) files with units, both having their own/different unit prefix. How can I reuse both in another ontology: do I need to make two diff. prefixes like unit-st and unit-m for resp. reuse of space-time and mechanical units? Guess you have some solution for this in mind for qudt2 architecture…. Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E [email protected]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707> <image002.gif><http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Irene Polikoff Sent: Wednesday, November 22, 2017 3:22 PM To: [email protected]<mailto:[email protected]> Subject: Re: [topbraid-users] puzzled (unit:YR as datatype revisited) Your last screenshot shows quit:Unit with a globe icon. Typically, when this happens it means that the type of the resource is unknown. Are you sure that QUDT is included? On Nov 22, 2017, at 7:19 AM, Bohms, H.M. (Michel) <[email protected]<mailto:[email protected]>> wrote: I imported qudt:Unit and all its instances: <image001.png> They are all there including YR: <image002.png> I also import an ontology stating: qudt:Unit rdfs:subClassOf rdfs:Datatype ; . I now have a property called residualLife which I want to constrain in a shape. When I want to select my unit:YR at sh:datatype I get: <image005.jpg> So qudt:Unit is there but without all the instances! Must be something very simple but what? Thx again! Michel Ps My guess that it is related to the prefixes in the files containing the actual units. Eg in the file VOCAB_QUDT-UNITS-SPACE-AND-TIME-v2.0.ttl (the latest from github) we have: # baseURI: http://qudt.org/2.0/vocab/unit/space-and-time # imports: http://qudt.org/2.0/schema/qudt # imports: http://qudt.org/2.0/schema/qudt/science # imports: http://qudt.org/2.0/vocab/quantitykind/base # imports: http://qudt.org/2.0/vocab/unit/base # imports: http://www.linkedmodel.org/schema/vaem @prefix dc: <http://purl.org/dc/elements/1.1/> . @prefix dcterms: <http://purl.org/dc/terms/> . @prefix dimension: <http://qudt.org/vocab/dimension/> . @prefix owl: <http://www.w3.org/2002/07/owl#<http://www.w3.org/2002/07/owl>> . @prefix prov: <http://www.w3.org/ns/prov#<http://www.w3.org/ns/prov>> . @prefix quantitykind: <http://qudt.org/vocab/quantitykind/> . @prefix qudt: <http://qudt.org/schema/qudt/> . @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#<http://www.w3.org/1999/02/22-rdf-syntax-ns>> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#<http://www.w3.org/2000/01/rdf-schema>> . @prefix skos: <http://www.w3.org/2004/02/skos/core#<http://www.w3.org/2004/02/skos/core>> . @prefix unit: <http://qudt.org/vocab/unit/> . @prefix vaem: <http://www.linkedmodel.org/schema/vaem#<http://www.linkedmodel.org/schema/vaem>> . @prefix voag: <http://voag.linkedmodel.org/schema/voag#<http://voag.linkedmodel.org/schema/voag>> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#<http://www.w3.org/2001/XMLSchema>> . Where maybe the second red should be the same as the first red? But then…if I have multiple such files (ie also VOCAB_QUDT-UNITS-MECHANICS-v2.0.ttl) can I in the end use units from these different files? Dr. ir. H.M. (Michel) Böhms Senior Data Scientist T +31888663107 M +31630381220 E [email protected]<mailto:[email protected]> Location<https://www.google.com/maps/place/TNO+-+Locatie+Delft+-+Stieltjesweg/@52.000788,4.3745183,17z/data=!3m1!4b1!4m5!3m4!1s0x47c5b58c52869997:0x56681566be3b8c88!8m2!3d52.000788!4d4.376707> <image006.gif><http://www.tno.nl/> This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. TNO accepts no liability for the content of this e-mail, for the manner in which you use it and for damage of any kind resulting from the risks inherent to the electronic transmission of messages. -- 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/d/optout. <VOCAB_QUDT-UNITS-SPACE-AND-TIME-v2.0.ttl> -- 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/d/optout. -- 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/d/optout. <README.TXT> -- 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/d/optout. -- 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/d/optout.
