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
I think it'd be great to have an extension of io.openmanufacturing.sds.ascpectmodel.resolver.AbstractResolutionStrategy that gets a specified model from a specified Semantic Hub instance via the API. This would be an elegant way to load aspect models without having to store them locally. Since the API of sldt-semantic-hub is not part of the SAMM-spec, I suspect it would be inappropriate to include it in the eclipse-esmf-sdk directly.
The text was updated successfully, but these errors were encountered:
Whether a network works with distributed semantic hubs or a central semantic hub is irrelevant for this issue. Either way, a user looking to load an aspect model into esmf-sdk will have to specify where the semantic hub is running that it wants to GET the aspect model from.
Again: this would mainly benefit users of esmf-sdk but transcends the SAMM-spec and therefore might be better placed here - almost as a kind of "client library".
I think it'd be great to have an extension of
io.openmanufacturing.sds.ascpectmodel.resolver.AbstractResolutionStrategy
that gets a specified model from a specified Semantic Hub instance via the API. This would be an elegant way to load aspect models without having to store them locally. Since the API of sldt-semantic-hub is not part of the SAMM-spec, I suspect it would be inappropriate to include it in the eclipse-esmf-sdk directly.The text was updated successfully, but these errors were encountered: