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

[Task] CLI - relax fixed models directory structure #512

Open
BirgitBoss opened this issue Jan 23, 2024 · 1 comment
Open

[Task] CLI - relax fixed models directory structure #512

BirgitBoss opened this issue Jan 23, 2024 · 1 comment
Labels
acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps. task

Comments

@BirgitBoss
Copy link
Contributor

Is your task related to a problem? Please describe.
In
https://eclipse-esmf.github.io/esmf-developer-guide/tooling-guide/samm-cli.html#models-directory-structure a strict folder structure is required to be able to resolve shared namespaces or splitted namespaces

In the future I would like to add SAMM models as part of a Submodel Template, e.g. here
https://github.com/admin-shell-io/submodel-templates/tree/main/published/Control%20Component%20Instance/1/0 in a subfolder "semantics" or similar

The thinking is similar to https://github.com/eclipse-tractusx/sldt-semantic-models/tree/main/io.catenax.battery.battery_pass/3.0.1/gen, (in gen .aasx files are generated) only the other way around

Describe the solution you'd like
Similar to the system variable "PATH" it should be possible to define where to look for (shared) aspect models.

Or you may add a configuration file (similar to a registry with logical IDs and mapping to endpoints)

<namespace> <path>, <namespace#aspect> <path>

where to look for and this configuration file could be an additional parameter is the CLI call

@chris-volk
Copy link
Contributor

(See also somewhat related issue #474 )

@chris-volk chris-volk added the acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps. label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
acknowledged Has been viewed by one of the maintainers and is ready for further work, discussion or other steps. task
Projects
None yet
Development

No branches or pull requests

2 participants