(it is coming from Modbus but we should check other bindings as well)
We could also make the ResponseCode class consistent with the other classes that you have defined like Entity, Function where you use a list pointing to named individuals with colon like :Coil. Here a URI pointing to the individual is used, but maybe there was a rational behind it.
:ResponseCode rdf:type owl:Class ;
owl:equivalentClass [ rdf:type owl:Class ;
owl:oneOf ( <https://www.w3.org/2019/wot/modbus/errorCode#01>
<https://www.w3.org/2019/wot/modbus/errorCode#02>
<https://www.w3.org/2019/wot/modbus/errorCode#03>
<https://www.w3.org/2019/wot/modbus/errorCode#04>
<https://www.w3.org/2019/wot/modbus/errorCode#05>
<https://www.w3.org/2019/wot/modbus/errorCode#06>
)
] ;
rdfs:subClassOf :Data_Field ;
rdfs:comment "For an Exception Response, the server returns an exception code as data response field. Exception code defines the server condition that caused the exception as well as the reason of the error."@en ;
rdfs:label "Exception code"@en .
(it is coming from Modbus but we should check other bindings as well)
We could also make the
ResponseCode
class consistent with the other classes that you have defined likeEntity, Function
where you use a list pointing to named individuals with colon like:Coil.
Here a URI pointing to the individual is used, but maybe there was a rational behind it._Originally posted by @mahdanoura in https://github.com/w3c/wot-binding-templates/pull/331#discussion_r1417212347_