Fixed errors in example aas. (#971)

* Added example AAS and included it in the documentation with brief disclaimers. Tested with validation tool: 4 errors remaining that cannot be resolved without breaking smt specification. Tested with FA³ST Service: no errors * Updated model files to include supplementary files. Moved to misc folder and updated usage documentation page
FraunhoferIOSB · Dec 10, 2024 · 59e7c0a · 59e7c0a
1 parent bd1e9f6
commit 59e7c0a
Show file tree

Hide file tree

Showing 4 changed files with 16,501 additions and 147 deletions.
diff --git a/docs/source/aas-examples/Example_AAS.aasx b/docs/source/aas-examples/Example_AAS.aasx
diff --git a/docs/source/basics/usage.md b/docs/source/basics/usage.md
@@ -16,7 +16,7 @@ To manually pass a model file `my-model.aasx` and a configuration file `my-confi
 > java -jar starter-{version}.jar --model my-model.aasx --config my-config.json
 ```
 
-An example model file can be found in the [FA³ST Github-Repository](https://github.com/FraunhoferIOSB/FAAAST-Service/blob/main/docs/source/aas-examples/example-aas.aasx).
+An example model file can be found in the [FA³ST Github-Repository](https://github.com/FraunhoferIOSB/FAAAST-Service/blob/main/misc/examples/model.aasx).
 Regarding AAS examples from other sources it is important to note that the AAS specification is not backwards compatible. Therefore, it is necessary to make sure that the model file conforms to the latest AAS specification (V3).
 Passing an outdated model file will lead to an error. If a model file conforms to V3 of the Asset Administration Shell specification but has duplicate identifiers, FA³ST will not load the file.
 Starting FA³ST with the `--no-validation` flag loads the file in any case but will lead to problems during runtime if there are duplicate identifiers present.

diff --git a/misc/examples/model.aasx b/misc/examples/model.aasx