In a discussion @cabo and I had recently, it came up that it might be useful to allow for definitions of SDF protocol mappings that can be reused at the affordance level (using sdfRef). These protocol mappings could either be global/located at the top-level of a model, or associated with an sdfThing or sdfObject to allow for sharing common definitions (such as IP addresses).
At the top-level or grouping level, the format of the sdfProtocolMapping might need to allow for defining multiple mappings for the same operation that can then be referenced from different affordances (e.g., two read operations that referenced from two sdfProperty definitions). But the details of that could potentially be left to the specifications that define mappings for specific protocols.
In a discussion @cabo and I had recently, it came up that it might be useful to allow for definitions of SDF protocol mappings that can be reused at the affordance level (using
sdfRef). These protocol mappings could either be global/located at the top-level of a model, or associated with ansdfThingorsdfObjectto allow for sharing common definitions (such as IP addresses).At the top-level or grouping level, the format of the
sdfProtocolMappingmight need to allow for defining multiple mappings for the same operation that can then be referenced from different affordances (e.g., two read operations that referenced from twosdfPropertydefinitions). But the details of that could potentially be left to the specifications that define mappings for specific protocols.