Re: FYI - Physical Web

Last year we published an article about Physical Web and the different mechanisms to broadcast URLs on heise.de<http://heise.de> [1]: x The Article is in German if you wish the englisch version please let me know.
Please note that Physical Web can use other mechanisms and technologies than Eddystone/BLE-Beacon in the future to broadcast URLs. mDNS and SSDP are already discussed in the Project [2].

[1]: http://www.heise.de/developer/artikel/Einfuehrung-in-das-Physical-Web-2919078.html

[2]: https://github.com/google/physical-web#contents


thx,
Louay
On 12 Feb 2016, at 18:38, Soumya Kanti Datta <Soumya-Kanti.Datta@eurecom.fr<mailto:Soumya-Kanti.Datta@eurecom.fr>> wrote:

Dear Thomas,
Thanks for sharing the good news. In TF-DI we have studied the UriBeacon. It is a good input for our tech landscape study.

BR,
Soumya

Research Engineer, EURECOM, France | +33658194342 | @skdatta2010
https://sites.google.com/site/skdunfolded | Skype id: soumyakantidatta

On 12-02-2016 20:45, Thomas Amberg wrote:
http://techcrunch.com/2016/02/11/google-chrome-for-android-will-soon-support-interactions-with-bluetooth-beacons/

Kind regards,
Thomas

On 27 Nov 2014, at 18:31, Thomas Amberg <tamberg@yaler.net> wrote:

Hi all,

just to clarify: anybody could build a "browser" for the proposed UriBeacon format.

Relying on URIs makes the approach more generic, distributed and open than iBeacon (where apps "resolve" IDs).

But, as Rob says, when it comes to prioritise the "search" result list of URIs in your proximity, the browser with most context info available probably wins.

Kind regards,
Thomas

On 27 Nov 2014, at 11:56, Rob van Kranenburg <kranenbu@xs4all.nl> wrote:

Hi all,

I had a talk on that with
Charalampos Doukas
Thomas Amberg
https://twitter.com/tamberg

https://twitter.com/BuildingIoT


on this latest Google initiative: trailing on urls for objects

https://github.com/google/physical-web/blob/master/documentation/technical_overview.md


and we realized that as you assign your device through the (bluetooth) beacon you are effectively adding these devices to the Google web. So if you go out to a friend you will see their devices. But in what order? Who prioritizes the devices, according to which criteria? Google ads! :)- the relevant sorting. Maybe you have to pay for being shown all devices on the discovery list?

So dangerous and yet so alluring to developers, just assign urls to objects.

The idea itself is good.

Thomas says: you as a user will help them catalogue the devices — location

But what if the list goes to an open and public initiative? It should not feed into Google of course.

Then you could walk around and feed your local internet of neighborhoods,

Greetings, Rob

Rob van Kranenburg 罗万魁
Founder of Council;  theinternetofthings.eu
Community Manager; sociotal.eu
Chair of Activity Chain 8 Societal of the IERC; www.internet-of-things-research.eu






Op 27-nov.-2014, om 02:15 heeft 전종홍 <hollobit@etri.re.kr> het volgende geschreven:

Hi All,

FYI - Google Reveals ‘The Physical Web,’ A Project To Make Internet Of Things Interaction App-Less.

How about to consider it in the scope of WoT IG.

http://techcrunch.com/2014/10/02/google-the-physical-web/

https://google.github.io/physical-web/


Best Regards,

--- Jonathan Jeon