A corollary of this issue is the GraphQL public schema We need to make a statement about the ontology in order to enable things in a data graph based on that ontology. We are interested in this for the data graph. Is it logical to push graphql:publicShape my:lovelyClass statements into the proxy/facade shapes and make them available for all data graphs that use it, or replicate it in each data graph - in which case how best to automate this important step?
should it be possible to override an imported statement with a local preference? In general, is this the same problem - we have autogenerated shapes for all ontologies available, but we can import one or more profiles based on these to control display options? If so, automation of population of graphql:publicShape should be considered since things dont work well without them On Wednesday, 29 April 2020 11:36:29 UTC+10, Ralph Hodgson wrote: > > Facade is maybe a good name > > Sent from my iPhone > > > On Apr 28, 2020, at 8:03 PM, Holger Knublauch <[email protected] > <javascript:>> wrote: > > > > On 28/04/2020 20:27, dprice wrote: > > > >> 1) Looks really good. Note that TQ has used the term “proxy ontology” > to mean an OWL/RDFS representation of an XSD in many presentations and > customers. > >> > >> What about “profile ontology”? That’s what OMG calls UML > subsets/extensions of the language basics and is what OWL 2 uses to mean > specific subsets of the language. I think DCAT standard also has the same > “profile” idea. > > > > I picked "proxy" because these ontologies are really just empty shells > around existing Turtle graphs. They merely add triples but the definitions > of classes and their labels etc remain in the original imported graphs. > > > > I didn't know Proxy ontology was already used. Profile ontology doesn't > work much better for me though unless we prefix it with something like > "Shape Profile ontology". Maybe I just call this feature "Create EDG > Ontologies for existing files"? > > > > Where is 2) ? :) > > > >> > >> 3) Can I also use this if starting from a SHACL shapes graph and subset > it for specific scenarios? If not, can that be added? I’ve had two customer > situations where there was a mix of OWL and SHACL that needed to be > subsetted. > > > > This wizard does not have the ability to batch-deactivate certain > shapes. That could be a separate dialog from the Ontology editor. Feel free > to create a Jira ticket if you have input. > > > > Holger > > > > > > -- > > 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] <javascript:>. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/46c98ea4-4ac9-f718-4280-2883534998cf%40topquadrant.com. > > > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/7c703c20-e63f-46ea-bef6-db84a9d815c0%40googlegroups.com.
