Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: SemanticHubResolutionStrategy #67

Open
arnoweiss opened this issue Mar 13, 2023 · 3 comments
Open

Idea: SemanticHubResolutionStrategy #67

arnoweiss opened this issue Mar 13, 2023 · 3 comments

Comments

@arnoweiss
Copy link

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.

@LuLeRoemer
Copy link
Contributor

So your proposal would basically be to allow distributed Semantic Hubs that can request each other, did I get that correct?

@arnoweiss
Copy link
Author

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".

@agg3fe
Copy link
Contributor

agg3fe commented Aug 4, 2023

Hi,
We are currently working on handling BAMM and SAMM models in Semantic-Hub. We will update you on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants