Arno Weiß

You should be able to connect to a UA-Server using Siemens Siome, load the address space and export it as ua-nodeset. It's a manual process but works well.

@mhrimaz - there's a bigger issue here: The [constraints](https://aas-core-works.github.io/aas-core-meta/v3/index.html) the spec makes are largely unenforceable at development-time. Another example for the same phenomenon is [AASd-120](https://aas-core-works.github.io/aas-core-meta/v3/SubmodelElementList.html) which specifies that members of...

This is still open and will lead to the RDF-serialization to cause data loss when parsing & serializing

Yes, that would be required, however the generator would have to make sure that the `aas:index` property does not get serialized to json & xml as it's not part of...

Spoke to some colleagues and they used **32** in similar specifications. After all, it's up to the workstream AAS if this should be specified at all (I think it's relevant...

The DSP specification project will soon commence under EDWG governance and will move in the process. This PR has already been open for a while so please get it in...

1. The spec has moved to https://github.com/eclipse-dataspace-protocol-base/DataspaceProtocol. 2. This PR introduces breaking changes and should thus have been sounded with the community.

I think this issue can be closed as the profile appears to be managed here [1] and there's no reference in the spec to it. [1] https://github.com/International-Data-Spaces-Association/ODRL-profile-for-IDS

This is likely just an issue of publication layout and should disappear when IDSA and EDWG documents are more separated. I think it's implausible that could be interpreted as a...

This appears to remain relevant as neither "access control" nor "discoverability" have been added to the terms [1]. [1] https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/terminology