Closed thern743 closed 1 year ago
The concept of DTDL "partner extensions" is being deprecated in favor of "feature extensions". Instead of extensions defined for the needs of specific partner services such as IoT Central, DTDL is now employing extensions that each provide a specific language feature intended to have wider applicability than a single service. Examples include Historization, Streaming, and Annotation.
It seems more appropriate that the IoT Central partner extensions have a more generic @context (such as Microsoft/Azure/IoT) instead of IoT Central as a specific solution. For instance, if IoT Central were to change (or become deprecated) it wouldn't make sense to have an orphaned or misaligned @context. Also, if Microsoft offers the same extensions in another service, such as Azure Digital Twins (ADT), IoT Hub, or Azure Device Update (ADU), it would be confusing to have an @context that was duplicated, mixed, or overlapping with an adjacent but irreverent service. Overall, it makes sense to offer these extensions more broadly under a generic context since they aren't intrinsic to IoT Central.