You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to automatically create a graph based on the user's incoming CAD file, but in order to do that, we may need to ship DeepLynx with a couple "baked-in" ontology classes. This may not be a feature we want, but I think it should be discussed and considered at least.
Design
If the user wants to use the Model Viewer, these two classes get automatically added to their container's ontology.
Impact
It would add something new. It could potentially conflict with existing ontology classes. There may be other unintended consequences that I'm missing.
The text was updated successfully, but these errors were encountered:
Reason
It would be nice to automatically create a graph based on the user's incoming CAD file, but in order to do that, we may need to ship DeepLynx with a couple "baked-in" ontology classes. This may not be a feature we want, but I think it should be discussed and considered at least.
Design
If the user wants to use the Model Viewer, these two classes get automatically added to their container's ontology.
Impact
It would add something new. It could potentially conflict with existing ontology classes. There may be other unintended consequences that I'm missing.
The text was updated successfully, but these errors were encountered: