Previous minutes

<inserted> July-13

<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> PR 35

<kaz> Statically rendered version HTML by Toumura-san

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> section 5.2

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> 7.1 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> WoT WG Chair's Dashboard tool

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

OGC's 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]