Skip to content

[Feat. Req.] Server-Side filtering on Submodel-Descriptors #158

@arnoweiss

Description

@arnoweiss

What is missing?

AssetAdministrationShellRegistries and SubmodelRegistries can get big. Clients may already know what they are looking for and benefit from server-side filtering. This would reduce processing effort and network load.

How should it be fixed?

Allow parameters on the /submodel-descriptors API in the AASRSS and SRSS such as
/submodel-descriptors?semanticId=someSemanticId

It may make sense to allow the same mechanism for attributes other than semanticId. To what degree this collides with the /submodel-descriptors/{{submodelId}} endpoint - I don't know.

  • I have signed the required Developer Certificate of Origin (DCO) already.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions