Closed smichea closed 1 year ago
Not a typo, just a possibly unexpected constraint. Per the DTDL metamodel, zero is both the minimum and maximum value allowed for minMultiplicity.
If DTDL permitted a minMultiplicity greater than zero, this would require any service that supports Relationships to provide a mechanism to simultaneously instantiate an Interface and at least one Relationship sourced from the Interface; otherwise, the Interface would fail to be valid at the moment it is instantiated.
make sense. thank you
It is written here https://github.com/Azure/opendigitaltwins-dtdl/blob/c3d5f1e7759d23cfe22b34521d9b17c261d76187/DTDL/v3/DTDL.v3.md?plain=1#L358 that the property
minMultiplicity
must be equal to 0, instead of >= 0