Creating instances in extension ontologies

[Tim Smith]

Hi,

I created a new ontology that is intended to be an extension of Enterprise Assets.  There are some classes that are subclasses of EDG classes and some are not.  For those that are not, I have added them to the "public classes" property of the ontology via the GraphQL view.

When I create a new Enterprise Asset collection, I import the new ontology.  However, I cannot create instances for any custom classes that are not a subclass of an EDG class.  Based on previous responses to my questions, I expected declaring my classes as public classes would have been sufficient to enable instance creation.

Am I missing something?  Do I need to make everything a subclass of an existing Enterprise Asset class?

Thanks in advance for your insight,

Tim

[Irene Polikoff]

Yes, there is a concept of a class which (transitive) instances can be stored in a given type of an asset collection. 

For Enterprise Asset collection these are instances of Enterprise Asset. So, yes, if you want to capture something in an Enterprise Asset collection it should be an enterprise asset. For Technical Asset collection, it is Technical Asset, etc.

Within data graphs and reference datasets you can store instances of any classes as long as they are public.

--
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/CAF0WbnK8RCqa_%3DWNxKVGBVJ4o-GRij7%3Dydt6mzhY0q4GykWV4w%40mail.gmail.com.