- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Tue, 28 Jul 2020 16:28:01 +0900
- To: public-wot-wg@w3.org
available at:
https://www.w3.org/2020/07/20-wot-discovery-minutes.html
also as text below.
Thanks a lot for taking the minutes, Cristiano!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
- DRAFT -
WoT Discovery
20 Jul 2020
Attendees
Present
Andrea_Cimmino, Cristiano_Aguzzi, Farshid_Tavakolizadeh,
Kaz_Ashimura, Kunihiko_Toumura, Michael_McCool,
Tomoaki_Mizushima
Regrets
Christian Glomb
Chair
McCool
Scribe
Cristiano
Contents
* [2]Topics
1. [3]Previous minutes
2. [4]First index.html draft
* [5]Summary of Action Items
* [6]Summary of Resolutions
__________________________________________________________
Previous minutes
<inserted> [7]July-13
[7] https://www.w3.org/2020/07/13-wot-discovery-minutes.html
<kaz> (kaz still need to create an issue on RFC)
McCool: Please in the notes try to use TDD for Thing Directory
and TD for Thing Description
... Toumura-san, please create an issue about auto creation of
UML diagrams
Farshid: the sequence diagram should capture the whole
introduction flow.
McCool: any other comments?
... any objection publishing this?
... ok published
First index.html draft
<kaz> [8]PR 35
[8] https://github.com/w3c/wot-discovery/pull/35
<kaz> [9]Statically rendered version HTML by Toumura-san
[9] https://cdn.statically.io/gh/w3c/wot-discovery/3f13162d382d5ba9257a438dc69abecec4e96808/index.html?env=dev
McCool: farshid made some comments on the PR
... there is a problem with the agent that renders the PR
diffs. it might be a bug, it is cause by the fact that the
previous version of the index file does not exist
... however we have a rendered version
... reviewing the index document
... I added the new editors, please double check your
affiliation
... the abstract need to be fixed
... added TDD acronym. We need to be consistent
Farshid: should we add this information also to the TD
document?
McCool: yes
... not sure if we have to use the prefix WoT for each term
defined in the document (i.e. WoT discovery or just discovery)
... forgot to add spatial queries capabilities in the paragraph
5.2
<kaz> [10]section 5.2
[10] https://cdn.statically.io/gh/w3c/wot-discovery/3f13162d382d5ba9257a438dc69abecec4e96808/index.html?env=dev#requirements-search
McCool: the search must be scalable
... for privacy reasons we have a clear action to delete items
inside a TDD
... I defined different introduction mechanisms
... About direct method URLs used there must return TDs
<kaz> [11]7.1 Direct
[11] https://cdn.statically.io/gh/w3c/wot-discovery/3f13162d382d5ba9257a438dc69abecec4e96808/index.html?env=dev#introduction-direct
McCool: in the document we have also different exploration
mechanisms
... in this context we have to define the minimum requirements
for security and privacy
... I think we should merge this so that we could work on this
version
Farshid: Using the direct method it is difficult to know before
hand if the returned TD is a TDD or not
... do we want to distinguish?
McCool: in general we cannot do it. We may define a convention
Farshid: ok, but we need to be consistent. for example also in
DNS method we should not distinguish
McCool: well, it depends. it might be more appropriate to
leverage on the features of the underline mechanisms (i.e. use
types in DNS-Multicast)
... so it might be good types when they are available
... my feeling is that if we have types we'd better use them
Farshid: should we move the content of direct paragraph?
McCool: yes let me do it right now
... adding also special thanks to people who are not editors
... conflicts resolved
... kaz, do you have the w3c number of the new editors?
Kaz: yes, please see the WoT WG Chair's Dashboard below
<kaz> [12]WoT WG Chair's Dashboard tool
[12] https://www.w3.org/PM/Groups/chairboard.html?gid=95969
Farshid: CRUD operation might have their section (i.e.
management)
McCool: we need two different set of api: one for "account"
management and other for searching
Andrea: what about dividing search section in twos ? (i.e.
semantic and not semantic )
... Why XPath? it is all XML
McCool: XPath is a standard and they have next version which
handles JSON
Farshid: what about an API for listing? it is related to search
McCool: yes let me add that
Andrea: if the search result contains another TDD, should the
main TDD do a federated query and automatically retrieve TDs
from it ?
McCool: it is an open question. It is related to links (i.e.
choose to follow a link or not)
Andrea: SPARQL supports federated queries
... We can express even spatial queries with SPARQLs
McCool: there is also other mechanisms to do spatial queries
... may be more efficient and we need to capture them
Cristiano: sparql has an extension called GeoSPARQL designed to
handle spatial queries
[13]OGC's GeoSPARQL
[13] https://www.ogc.org/standards/geosparql
McCool: interesting
... so is it ok to merge the #35?
... ok, we have a baseline. We have still a lot to do. PRs are
welcomed.
... merged.
... we have to define a discovery.md file in the use-cases repo
Farshid: we are working on use cases. We may contribute also to
discovery.md file
McCool: I'll add a horizontal use case document then
Kaz: btw, we should talk about the updated published version
McCool: ok let's close the meeting and I'll add that to next
call agenda
<kaz> [adjourned]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes manually created (not a transcript), formatted by
David Booth's [14]scribe.perl version ([15]CVS log)
$Date: 2020/07/27 14:10:20 $
[14] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[15] http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 28 July 2020 07:28:06 UTC