Re: iBeacon + LDP or ie: SoLiD

i think the answer is somewhat explained here[1] with particular note to
Web Bluetooth [2], but the fundamental question is whether the data -
fundamentally need to be transmitted to google servers?

or can they be private and/or decentralised without necessitating access by
google A.I. networked capabilities...

Tim.H.

[1] https://www.youtube.com/watch?v=vyfy7AdPk2g
[2] https://www.w3.org/community/web-bluetooth/


On Mon, 23 May 2016 at 22:46 Kis, Zoltan <zoltan.kis@intel.com> wrote:

> I think it is obvious that the Physical Web concept, and beacons in
> general, are already in scope of the WoT IG, as Dave described.
>
> The Physical Web concept leaves the data model open, and provides means
> for discovery, retrieve, update, and notify, but not for remote creation
> and deletion of things (or resources in OCF terminology). Attached 2 slides
> I made out of this.
>
> For instance, with the Physical Web one could use BLE services and
> characteristics:
> https://developer.bluetooth.org/gatt/services/Pages/ServicesHome.aspx
>
> https://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicsHome.aspx
> or other, proprietary or standardized data models.
>
> Anyone can well implement their own Physical Web.
>
> I agree with Dave that the most important concept to deal with here (in
> relation to discovery+CRUDN) is that of user agents.
>
> Do I understand right that Timothy you'd like to add support for control
> on what things (services) can be discovered and accessed by a given device
> identity + capabilities + permissions + interests, sort of "service
> agents", for instance things/resource directories?
>
> Best regards,
> Zoltan
>
>
> On Mon, May 23, 2016 at 3:01 PM, Adrian Hope-Bailie <adrian@hopebailie.com
> > wrote:
>
>> Check out the Physical Web project
>> http://google.github.io/physical-web/
>>
>> On 22 May 2016 at 11:11, Timothy Holborn <timothy.holborn@gmail.com>
>> wrote:
>>
>>> Looking into iBeacon technology and found the google offering [1]
>>> alongside the apple version.
>>>
>>> I'd rather have the infrastructure owned by the property owner and use
>>> linked-data more generically (rather than via service provider).  Any
>>> suggested links for existing solutions that are less service-provider /
>>> vendor tied?
>>>
>>> I also found the paypal beacon [2] which also looked interesting,
>>> pondering whether bluetooth ble's might be usable as a 2-part hardware
>>> token that people might carry on their keychains (amongst the many other
>>> uses)...
>>>
>>> Tim.H.
>>>
>>> [1] https://github.com/google/eddystone
>>> [2]
>>> http://blog.verifone.com/apple-ibeacon-paypal-beacon-and-ble-what-does-it-all-mean/
>>>
>>>
>>
>