Hi everybody,
I'm not sure if the baseline interface is really the default interface according to the specification. The core specification seems to say nothing about it except that the default interface should be defined by the specification related to the resource type. Then, I looked into the resource specification. The Default Interface associated with all Resource Types defined in this specification shall be the supported interface listed first within the applicable enumeration in the definition of the Resource Type (see Section 6 Resource Type definitions); [...] In all definitions I looked at, the baseline interface was listed last. Therefore, the baseline interface seems not to be the default interface according to the specification. Personally, I would also prefer to have the baseline interface as the default, but it does not seem to be the case. Have I missed something? Thanks, Johannes Spangenberg ________________________________ From: iotivity-dev-boun...@lists.iotivity.org <iotivity-dev-boun...@lists.iotivity.org> on behalf of Morrow, Joseph L <joseph.l.mor...@intel.com> Sent: Wednesday, September 20, 2017 10:56:01 PM To: Lea, Thomas; iotivity-dev@lists.iotivity.org Subject: Re: [dev] Unable to set custom default interface on a created resource Hi Thomas, The baseline interface is required as per the OCF Core Spec. It is the “Default Interface” for most, if not all, resources. https://openconnectivity.org/specs/OCF_Core_Specification_v1.0.0.pdf OCF Core Specifiation - Open Connectivity Foundation<https://openconnectivity.org/specs/OCF_Core_Specification_v1.0.0.pdf> openconnectivity.org Copyright Open Connectivity Foundation, Inc. © 2016-2017. All rights Reserved 5 107 Resource based discovery: mechanisms ... —> ctrl+f for “default interface” and read all the material around the topic. (There’s only 10-20 locations the term is used in the Core Spec.) For purposes of IoTivity use, it is meant to be used against OCF compliant apps. For your use, possibly non-OCF compliant, you should consider some other steps. * Change value of DMV and ICV in your Device properties, so other implementations of IoTivity know you’re not OCF compliant * Change the default ports and addresses you use for discovery, so you don’t hinder OCF compliant apps. * I hope someone else on this thread can help provide information here. * Create a new API in CSDK and other APIs for something along the lines of UnbindResourceType(), where in your case you would invoke UnbindResourceType(HandleToResource, “oic.if.baseline”); Thanks, Joey Morrow From: <iotivity-dev-boun...@lists.iotivity.org<mailto:iotivity-dev-boun...@lists.iotivity.org>> on behalf of "Lea, Thomas" <thomas_...@comcast.com<mailto:thomas_...@comcast.com>> Date: Wednesday, September 20, 2017 at 12:08 PM To: "iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>" <iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>> Subject: [dev] Unable to set custom default interface on a created resource It looks like iotivity explicitly sets the default/first interface on created resources to be baseline. I have custom resources that I want to use a different default interface. Why does iotivity force baseline to be the default? If this is just oversight, I'll create a patch. Thanks, Thomas Lea Comcast
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
