Hi Jens,
Sorry, this time I didn’t manage to respond any earlier…
Her suggestion (B) to simply remove the url from the code and not to mention it in any documentation does not make much sense to me. After all, the code only makes any sense with this single url as there is no other service that implements exactly the same API as Yahoo does, so the url itself is not replacable by another without breaking the system. Nonetheless, I consider Eclipse SmartHome „Add-ons“ like this binding an optional part, that is not required to run and use Eclipse SmartHome. The users have the possibility to use other extensions and e.g. get weather data through other channels (e.g. MQTT).
Best regards, Kai
True, Sorry! I started thinking about
that topic but it seems these thoughts never reached the mailing
list ;-)
My first idea was, why not use something which can be used out of
the box?
The second thing would be to provide some sort of user interaction
for this: like requesting to put in a URL, and provide a default
value (which has still to be entered) with a note that references
the terms and conditions. In this case one would be able to enter
a different URL and the whole thing would clearly be a works-withs
dependency, since it is up to you what you place in there.
I am not so sure, if this is the case when the only possible URL
is yahoo, and it is nailed down in the source code. Which might be
a wrong assumption.
As a reference, we did have a similar discussion about an Eclipse
SCADA sample with Arduino. Since we don't distribute the sample
with our release, and it was only a tutorial, not part of the
Eclipse SCADA "product", it was ok to use works withs, as far as I
remember. So if this HTTP call is only in a sample file, on the
wiki, this would seem similar to me.
Again, this is only what came across my mind, and I would like to
understand it better!
And sorry for the delay!
Jens
On 04/15/2015 07:03 PM, Kai Kreuzer wrote:
As I did not get any reply or comments yet, I would
like to bring this question back to your attention :-)
Thanks,
Kai
Dear PMC
colleagues,
In Eclipse SmartHome, we have implemented a
„Yahoo Weather Binding“ as a reference for developers to
see how bindings should be developed. It is not really
meant to be used by anybody productively, but rather
only for testing and demos. The IP team now pointed out
correctly, that the Yahoo weather API itself comes with
its own terms & conditions (see https://developer.yahoo.com/weather/).
It was suggested to treat the HTTP calls to
this API as a dependency like a code dependency. I
therefore wonder if you would agree that it could be
classified as a works-with dependency? The binding is
not required for using Eclipse SmartHome as it is
optional and as mentioned above, rather for reference.
Let me know what you think!
Thanks,
Kai
_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc
_______________________________________________ iot-pmc mailing list iot-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/iot-pmc
|