yep fixing the namespaces in the original data files fixes it - but you have to perform quite a few gymnastics before everything is lined up :-)
On Tuesday, June 30, 2020 at 5:52:08 PM UTC+10 Rob Atkinson wrote: > hmm units uses: > a <http://qudt.org/schema/qudt#ElectricCurrentUnit> > > but the qudt schema it imports uses: > a <http://qudt.org/schema/1.0/qudt#ElectricCurrentUnit> > > ouch! > > the other ns was an artefact of a different failed experiment importing > QUDT stuff.. > > On Tuesday, June 30, 2020 at 5:31:23 PM UTC+10 Rob Atkinson wrote: > >> >> not sure what ttl to send - the file is >> TopBraid/LinkedModels/unit-v1.0.ttl and ?I just want to know how to expose >> that via GraphQL - or confirm that it cannot be done for some reasone >> >> If I create an ontology, then execute OWL 2 SHACL then it shows: >> >> <http://qudt.org/schema/1.0/qudt#Unit> >> a owl:Class ; >> a sh:NodeShape ; >> >> >> but when I include this in my data graph... >> >> owl:imports <urn:x-evn-master:qudt_schema> ; >> >> then it doesnt show up: >> >> qudt:Unit >> a owl:Class ; >> qudt:informativeReference >> >> because somehow its picked up a different namespace >> @prefix qudt: <http://qudt.org/schema/qudt/> . >> >> now to find out why... >> On Tuesday, June 30, 2020 at 5:08:10 PM UTC+10 Holger Knublauch wrote: >> >>> Hi Rob, >>> >>> is the Unit class also instance of sh:NodeShape? >>> >>> Feel free to send me what you have as a TTL file and I can take a look. >>> >>> Holger >>> >>> >>> On 30/06/2020 17:03, Rob Atkinson wrote: >>> >>> >>> I have tried to make the QUDT units ontology (pre-loaded) accessible via >>> GraphQL and failed... >>> >>> If I include it into a empty data graph I can traverse and inspect all >>> the contents... >>> >>> I can set the search root to be, for example Unit >>> >>> I then add statements like this to the graph root object.. >>> >>> graphql:publicClass qudt:Unit ; >>> teamwork:mainClass qudt:Unit ; >>> teamwork:rootClass qudt:Unit ; >>> >>> but the Unit class does not show up as an option the the GraphQL schema: >>> >>> { _rootTypeShapes { >>> rootQueryField >>> } } >>> >>> => >>> >>> { >>> "data": { >>> "_rootTypeShapes": [] >>> } >>> } >>> >>> >>> I also tried loading the file into an ontology, running OWL->SHACL then >>> defining the graphqL public classes, and incuding into the data graph. >>> Still navigable and not queryable. >>> >>> even if i wanted to, I cannot import the file - it complains about >>> having classes defined. >>> >>> And in the search panel the search class is listed, but it doesnt offer >>> the class hierarchy and the search box is greyed out. >>> >>> I also tried building the lucene indices. >>> >>> What exactly is the requirement for GraphQL to be enabled? - and can >>> anyone provide an example recipe that works to allow query for any or all >>> of the various models available in EDG by default. >>> >>> >>> >>> -- >>> 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-user...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/topbraid-users/4764465c-5296-4328-b04d-6b1f00ff9e75n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/topbraid-users/4764465c-5296-4328-b04d-6b1f00ff9e75n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- 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/e7c3905c-b1e3-4e62-b234-35bcb0d0e89fn%40googlegroups.com.
