On Mar 2, 2017 4:23 PM, "Thiago Macieira" <thiago.macieira at intel.com> wrote:
On quinta-feira, 2 de mar?o de 2017 13:18:05 PST Gregg Reynolds wrote:
> On Mar 2, 2017 2:56 PM, "Thiago Macieira" <thiago.macieira at intel.com>
wrote:
>
> IoTivity-constrained can. The whole point of this discussion is whether we
> should even try to get the full one to fit.
>
>
> or rather, the underlying question is "what does 'Iotivity' mean?"
> regrettably, the name of the protocol is the same as the name of the
> organization. If "Iotivity" were the name of the protocol, we would be
> talking about variant implementations of the protocol. as it stands,
> "implementation of iotivity" is meaningless, since iotivity _is_ an
> implementation. iotivity-constrained is an ocf implementation that
happens
> to have 'iotivity' in its name. in fact it has little to do with
> "iotivity", as far as i can see.
IoTivity is not the name of the protocol, OCF is.
IoTivity is the name of the organisation and the name of the main
application.
This is just like Apache:
Protocol Project Application name
HTTP Apache httpd
OCF IoTivity iotivity (full?)
not really. there is no "main application" for apache. in fact the apache
http server project is a project, not an app. apache is the organization,
which has many projects, none of which are "apache" afaik.
Where does that leave iotivity-constrained? or other ocf implementations? i
think a better analogy is ietf or w3c:
protocol: http
project: many (e.g. apache httpd)
implementation: many (at least 2, independent)
if iotivity is the organization, then it should do like apache and keep the
org separate from the projects. in particular it should not have just one
project called"iotivity", with a million different branches and repos for
different implementations.
what happens when companies start certifying stuff. "ocf certified" or
"iotivity certified"?
sincerly, gregg
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170302/53a4c879/attachment.html>
