Thiago Macieira writes:
> > Suppose I have an engine that supports OCF messaging and data model, 
> > but only over TCP/IP.  I do not see why that should not be considered 
> > conformant.
>
> Certification is a choice. Specifically, we need to choose a combination to 
> require all 
> devices to speak, so that they can talk to each other. If we allow a range of 
> choices
> so that two devices can be compliant, receive the logo, be on the same 
> network, and
> not talk to each other, we lose the value of the brand.

Thiago is exactly right.  This is very intentional in OCF.  Two devices that 
have the OCF
logo must be able to talk to each other or the logo loses its value.

Devices can support other combinations in addition to what's mandatory, but the
mandatory one is mandatory for the reason Thiago explained.

Dave
_______________________________________________
iotivity-dev mailing list
iotivity-dev@lists.iotivity.org
https://lists.iotivity.org/mailman/listinfo/iotivity-dev

Reply via email to