While you are looking at overriding here - I have collections of terms that that don't logically have broader concepts - lets say I have 500 such "code lists" I want to manage as a single reference collection, then create property value selectors as needed.
If i model them as skos:Collections I see no way to navigate in the Taxonomy or Ontology editors. So Creating an override of the class selector for a specific collection would be cool - I'd be happy to create a graph with the relevant selectors - if I could see a way to bind it to the given collection. On Saturday, February 16, 2019 at 5:04:47 AM UTC+11, Adam Kimball wrote: > > Hi, > > I have two taxonomy projects: > > Taxonomy_1 = http://my.example/tax/people# > Taxonomy_2 = http://my.example/tax/locations# > > Note: Taxonomy_1 contains links to Taxonomy_2 with predicates like > ex:lives_in > > When a user in EDG goes to Taxonomy_2, they see their curated location > terms underneath the one scheme. > > When a user in EDG goes to Taxonomy_2, they see the locations scheme > (imported) and the people scheme (primary). > > What I'd like is to somehow keep Taxonomy_1 from showing up at all, > though any IRIs should still be available to navigate. I just want the > scheme to be hidden. > > One way is to factor out the schemes and import them separately but that > strikes me as a lot of maintenance. > > Suggestions for me? > > Thanks, > Adam > -- 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.
