Re: Bootstrapping the Web of Things Community Group

Hi all,
I'd like to share with you some lessons learned.
I'm working on the "Semantic Web of Things", you can find more 
information on this web page: http://sensormeasurement.appspot.com/.

For the semantic web part, there is really a need to share semantic web 
best practices to domain experts to easily reuse their domain 
ontologies, datasets and rules.

As you can see on this web page 
(http://sensormeasurement.appspot.com/index.html?p=ontologies), there 
are a great deal of interesting domain ontologies which cannot be reused 
since they not follow semantic web guidelines and are not referenced by 
semantic web tools or search engines.

We are also concerned by security issues:
http://sensormeasurement.appspot.com/?p=stac
We propose an ontology-based security knowledge to help to secure the 
Internet of Things.

Finally, we are working on the "Linked Open Rules" to easily share and 
reuse semantic domain rules.

Regards,
Amelie Gyrard

  On 22/01/2014 13:07, Xiang Su wrote:
> Another thing is semantics, how to enable sensors/actuators as data
> sources of linked data is a challenge. Can ready W3C languages,
> including OWL ontologies, SPARQL, RIF or SWRL reasoning languages be
> used in WoT straightforwardly? We need to think how to take benefits
> from these.
>
> Moreover, it important to enjoy the benefit of Web technologies and
> semantics, without breaking the constraints on resource usage. In our
> group, we also study resource consumptions, e.g. usage of processor,
> memory, bandwidth, and energy in WoT applications.
>
> br,
> -Xiang
>
> On 20.1.2014 15:39, Markus.Isomaki@nokia.com wrote:
>>
>> Hi Dave,
>>
>> One very “Web of Things” oriented effort, that I have not seen
>> mentioned on this list before, is the standardization of the
>> Constrained Application Protocol (CoAP) in the IETF, see
>> http://datatracker.ietf.org/wg/core/charter/ and
>> http://datatracker.ietf.org/doc/draft-ietf-core-coap/.
>>
>> CoAP is an application protocol that supports the RESTful CRUD methods
>> similar to HTTP (in practice GET, PUT, DELETE and POST), but in a more
>> lightweight manner. For instance, it runs over UDP (and DTLS for
>> security), and is binary encoded. In addition to the baseline
>> protocol, some of the related infrastructure, such as resource
>> directories, mirror proxies etc. are being standardized. The idea is
>> that CoAP is so compact, that it fits nicely on top of IP even on the
>> most constrained radio links, such as Zigbee or Bluetooth Low Energy.
>> Otherwise all the normal Web design principles apply.
>>
>> I don’t know how far the Community Group effort will go, but it would
>> be certainly interesting to get CoAP JS API standardized, so that it
>> could be supported in browsers or web apps, for instance.
>>
>> You can find the contact details of the active CoAP people from the
>> CoRE WG pages, including chairs and draft authors. Carsten Bormann,
>> Cullen Jennings (WG chairs) and Zach Shelby (base protocol main
>> author) good candidates, for instance.
>>
>> There is also IP for Smart Objects (IPSO) Alliance,
>> http://www.ipso-alliance.org/, an industry group dedicated to the
>> promotion of IP/Internet and Web technologies for “smart objects”.
>> Geoff Mulligan is the chair.
>>
>> Regards,
>>
>> Markus
>>
>> *From:*ext Dave Raggett [mailto:dsr@w3.org]
>> *Sent:* 17 January, 2014 18:54
>> *To:* public-web-of-things@w3.org
>> *Subject:* Bootstrapping the Web of Things Community Group
>>
>> The group has been very quiet until now, and I would like to get
>> things moving, especially, as we want your help with the planning the
>> W3C Web of Things Workshop to be held this June somewhere in Europe.
>> The dates and location are still to be decided. Please let us have
>> your ideas!
>>
>>
>> The aim of the workshop will be to discuss opportunities for
>> standardization as a basis for interoperability and a thriving
>> ecosystem. To support that we will be looking for examples of use
>> cases, and analyses of requirements and architectures, as well as
>> implementation experiences. Please help us to frame the scope of the
>> workshop in more detail.
>>
>> Which people/organizations should we invite to become part of the
>> workshop's program committee?
>>
>> Send your comments to the Web of Things Community Group mailing list
>>
>>  * public-web-of-things@w3.org <mailto:public-web-of-things@w3.org>
>>
>> Please note that note that everyone on the older list (public-wot)
>> have been moved over to the above list. Newcomers to the Web of Things
>> Community Group will be automatically subscribed to the above mailing
>> list.
>>
>> Looking forward to working with you all.
>>
>> -- Dave Raggett <dsr@w3.org> <mailto:dsr@w3.org>
>> http://www.w3.org/People/Raggett
>>
>

Received on Thursday, 23 January 2014 10:45:23 UTC