-
Notifications
You must be signed in to change notification settings - Fork 6
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
What are the various types of JSON representations for a submodel? #115
Comments
Hi Jon, not really sure if i understood correctly, but from what we see, the serialization endpoint returns an AAS-environment which consists, among others, of an array of submodels and also concept descriptoins. The one submodel GET response returns only one submodel, whicle you can define the answer based on parameters, e.g., deep or shallow representation of nested contents. |
Hi Sten, Thank you for the reply. Use case where the difference in response has an impact. Questions
|
Hi, sorry i so dumb to understand what are "object in the object store", are those aasx files? |
ObjectStore Use case Question
Note: The answer to issue eclipse-aaspe/package-explorer#254 could provide an explanation for the JSON from Package Explorer. |
Examples of the differences could be helpful :) Did you check the REST API (https://app.swaggerhub.com/apis/Plattform_i40/SubmodelRepositoryServiceSpecification/V3.0.2_SSP-001#/Submodel%20Repository%20API/GetSubmodelById)? Is this the "extent" thingy? But i guess i misundestand. |
Your first answer was the solution to the problem with the SDK methods. Thank you for the help! |
What are the various types of JSON representations for a submodel, and what are their use cases?
API
Why are the https://admin-shell.io/api/v3.0 JSON response for the endpoints
GET/serialization?submodelIds={submodelIdentifier}
andGET/submodels/{submodelIdentifier}
different?Package Explorer
Are any of the API endpoints related to the
Import/Export submodel from JSON
in the Package Explorer?The text was updated successfully, but these errors were encountered: