09:50:56 <RRSAgent> RRSAgent has joined #wot-td
09:50:56 <RRSAgent> logging to http://www.w3.org/2016/01/27-wot-td-irc
10:09:04 <taki> taki has joined #wot-td
10:10:13 <dsr> dsr has joined #wot-td
10:10:38 <dsr> scribenick: dsr
10:11:14 <dsr> Sebtastian introduces the metamodel and the discussions arising from the plugfests
10:11:55 <dsr> This time, we introduced a shared repository for thing descriptions.
10:12:20 <dsr> The implementations were mainly for HTTP plus a few for CoAP.
10:12:46 <dsr> as well as some WebSockets and MQTT implementations.
10:13:12 <dsr> (Sebastian to link his slides later)
10:13:23 <dsr> rrsagent, set logs public
10:14:28 <dsr> Some technical questions arising, e.g. whether to provide the local or external IP address, how to indicate data types with ranges, access control, decoupling semantics from link relation types
10:15:58 <dsr> This morning we will go through the agenda topics on the wiki. This afternoon a joint session, and tomorrow …
10:16:53 <dsr> Karsten: how do we get IP addresses of components
10:17:05 <dsr> URIs provide IP addresses
10:17:41 <dsr> We need to distinguish local network and public internet addresses
10:18:41 <dsr> In respect to security, not everyone may be allowed to access all resources on a given device
10:19:08 <dsr> For links, what is the mapping from link names to RDF URIs
10:19:56 <dsr> For relative links we need a base URI
10:23:11 <dsr> Carsten: thing descriptions should be able to specify an explicit base URI
10:47:50 <yuki_> yuki_ has joined #wot-td
11:42:57 <dsr> … long discussion on communication metadata …
11:45:50 <dsr> In summary, we need communication metadata for each platform. The vocabulary will depend on the platform. URIs are useful, but may not always be sufficient.  In some cases, it will be necessary to query the platform to get the details, e.g. the URIs for specific thing properties, or a named recipe (set of rules) for constructing these URIs.
11:49:36 <dsr> The communications metadata could also allow a server to map application layer queries for specific sensors, to platform specific handling of multiplexed data comprising data from many sensors.
11:50:51 <dsr> We then switched over to the technology landscape. We agreed to put the table on “ice” for now and to request input on each technology. We assigned owners to each technology - see the updated github page.
11:51:01 <dsr> rrsagent, make minutes
11:51:01 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/27-wot-td-minutes.html dsr
12:30:05 <Yuki_Matsuda> Yuki_Matsuda has joined #wot-td
12:41:57 <Yuki_Matsuda> Yuki_Matsuda has left #wot-td
12:46:46 <katsu> katsu has joined #wot-td
12:46:53 <Jasper> Jasper has joined #wot-td
12:47:04 <andrew-kwisa> andrew-kwisa has joined #wot-td
12:49:56 <taki> taki has joined #wot-td
12:50:30 <vcharpenay> vcharpenay has joined #wot-td
12:50:56 <mdadas> mdadas has joined #wot-td
12:50:56 <RuiFerreiraDaCosta> RuiFerreiraDaCosta has joined #wot-td
12:51:06 <mkovatsc> mkovatsc has joined #wot-td
12:51:06 <mdadas> present+ Mohammed
12:52:09 <romain> romain has joined #wot-td
12:52:47 <dsr> dsr has joined #wot-td
12:52:51 <michael_> michael_ has joined #wot-td
12:53:02 <vcharpenay> Soumya: topic: discovery/filtering-relevant information needed from a Thing Description?
12:53:33 <kaz> kaz has joined #wot-td
12:54:20 <Reynier> Reynier has joined #wot-td
12:55:35 <michael_> michael_ has left #wot-td
12:56:03 <mmrissa> mmrissa has joined #wot-td
12:56:04 <Soumya> Soumya has joined #wot-td
12:56:08 <akeranen> akeranen has joined #wot-td
12:56:16 <cabo> cabo has joined #wot-td
12:56:28 <vcharpenay> open question. First, other topic.
12:56:29 <vcharpenay> topic: Thing vs. Server metadata
12:56:37 <vcharpenay> (suggested by Dave)
12:59:34 <vcharpenay> Dave: WoT -> platform of platforms. Distributed.
13:01:52 <vcharpenay> two kinds of developers: app dev (using scripting on a given platform) vs. platform dev
13:02:25 <vcharpenay> therefore, different levels of metadata. Threefold: things/communications/security
13:04:07 <crispus> crispus has joined #wot-td
13:04:32 <vcharpenay> minimal set of core metadata along those three dimensions?
13:07:00 <Soumya> Dave: Extra info for discovery could be determined by the server
13:07:16 <Soumya> Can included sleep time for example
13:09:38 <Soumya> trade off between laterncy and buffering .... (in relation to the best practices)
13:11:09 <vcharpenay> Matthias: view of TF-DI on discovery? Concrete problems?
13:13:33 <vcharpenay> TD Repository was done in TF-TD and already supports queries. Did TF-DI emerge with other discovery mechanisms?
13:14:15 <vcharpenay> Ex: printer needed in a certain room with certain properties (resolution > x dpi)
13:14:45 <vcharpenay> Darko: requires additional/domain-dependent knowledge (about printers in this case)
13:15:55 <vcharpenay> Extension of the TD model, e.g. with SSN. At the moment {td: {type: Property, name: "BrighnessSensor"}}
13:16:24 <vcharpenay> better to have {td: {type: ssn:Sensor...}}
13:18:13 <vcharpenay> Sebastian: <presentation of the "triple search" feature of the TD Repo>
13:18:32 <vcharpenay> is still limited.
13:19:22 <vcharpenay> Soumya: How/when to get information from the TD if not discovered yet? Different scenarii:
13:20:26 <vcharpenay> https://www.w3.org/WoT/IG/wiki/Discovery_Categories_and_Tech_Landscape
13:22:34 <vcharpenay> finding things in a network (see link above). Concept of Social network of things.
13:22:53 <vcharpenay> Question to Martin.
13:23:02 <dsr> dsr has joined #wot-td
13:23:15 <vcharpenay> Martin: there is little that has been made @ oneM2M for discovery.
13:24:03 <vcharpenay> 1. String match, 2. SPARQL using annotations (see presentation yesterday)
13:25:38 <vcharpenay> Semantic-based discovery (see link). Keyword to formal concepts
13:27:08 <vcharpenay> Dave: Thingsonomy, people tag things
13:29:37 <vcharpenay> Soumya: moving to the next topic: filtering
13:30:07 <vcharpenay> guidelines from TF-TD to that respect?
13:31:55 <vcharpenay> Dave: 1. server-side SPARQL query, 2. Client-side gathering of TDs and SPARQL, 3. higher-level platform
13:32:14 <crispus> Martin: Release 1 of oneM2M has only simple String matching for discovery of oneM2M resources, Release 2 enables semantic discovery based on filter in SPARQL which is applied to semantic description
13:34:28 <vcharpenay> where to filter? RDF: already a lot of solutions
13:35:11 <vcharpenay> Soumya: CoRE Link format should also be supported
13:35:29 <vcharpenay> and possibly others
13:38:05 <vcharpenay> [Maxime spoke between Martin and Soumya]
13:39:30 <vcharpenay> Carsten: point: never standardized Google Search. Need for a unified search mechanism?
13:40:38 <vcharpenay> Anyway, CoRE Link format would benefit from a higher abstraction level for querying.
13:42:37 <Soumya> rrsagent, draft minutes
13:42:37 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/27-wot-td-minutes.html Soumya
13:42:56 <vcharpenay> Maxime: target the Semantic Web, define an ontology, use existing mechanisms and wrap them over other formats like CoRE Link
13:44:12 <Soumya> rrsagent, draft minutes
13:44:12 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/27-wot-td-minutes.html Soumya
13:44:34 <taki> taki has joined #wot-td
13:44:37 <Reynier> Reynier has joined #wot-td
13:44:44 <dsr> dsr has joined #wot-td
13:45:48 <RuiFerreiraDaCosta> RuiFerreiraDaCosta has left #wot-td
13:51:27 <Hitoshi_> Hitoshi_ has joined #wot-TD
13:52:51 <cabo> cabo has joined #wot-td
13:57:44 <akeranen> akeranen has joined #wot-td
14:38:42 <cabo> cabo has joined #wot-td
15:03:59 <cabo> cabo has joined #wot-td
15:09:27 <cabo> cabo has joined #wot-td
15:23:22 <yingying> yingying has joined #wot-td
15:24:09 <taki> taki has joined #wot-td
15:33:46 <dsr> dsr has joined #wot-td
16:22:07 <Hitoshi_> Hitoshi_ has left #wot-td
17:33:02 <cabo> cabo has joined #wot-td