W3C

- DRAFT -

WoT Discovery

25 May 2020

Agenda

Attendees

Present
Kaz_Ashimura, Andrea_Cimmino, Christian_Glomb, Cristiano_Aguzzi, Farshid_Tavakolizadeh, Kevin_Olotu, Kunihiko_Toumura, Michael_McCool, Takahisa_Suzuki, Tomoaki_Mizushima, Zoltan_Kis
Regrets
Chair
McCool
Scribe
kevin

Contents


<kaz> scribenick: kevin

Invited guests

no invited guests today, though IE procedure for Cristiano is still ongoing

Previous minutes

need to revisit pagination

<kaz> May-11 minutes

Minutes published with addition

<kaz> (Christian Glomb has been added to the regrets list)

PR 20

<kaz> PR 20

no objections to merging PR 20

PR 20 merged

<kaz> (Andrea will submit a use case based on the UC template, and we'll continue discussion during the Architecture/UC call)

PR 23

PR still work in progress

PR 23 merged with no objections

Requirements

<kaz> preliminary requirements document

<scribe> new requirements can be added through PR and can be discussed in the meetings

start to think about use cases for each of the requirements

Design Decisions

need to find resolutions for open topics

<kaz> FT wonders about the second point, "Use of JSON to encode results from directory services"

McCool suggests using at least JSON as encoding

<kaz> Cristiano has a question about authentication

Cristiano asks why to use OAuth vs free service

McCool: OAuth spec is free

<kaz> (also mentions WebID: https://en.wikipedia.org/wiki/WebID)

allow use of OAuth2 and allow use of WebID added as points for discussion

<kaz> JSON Web Token - Verifiable Credentials Data Model

<kaz> kaz suggests we do some more survey about the existing standards for those points like the Verifiable Credentials Data Model which has a section for JWT-based authentication

McCool asks whether JSON-LD should be used as encoding to use SQARQL on it

Andrea asks how to store TDs

could be plain JSON in the directory

<kaz> McCool explains his proposed 3 options: fixed (.well-known), basic (keyword query, eg JSONPath/XPath), advanced (SPARQL)

use of JSON-LD 1.1 to encode results from directory service to enable SPARQL searchability

<McCool> proposal: Use of HTTP for directory services

Cristiano suggests JSON-LD 1.1 would be overkill for simple services

McCool explains JSON-LD 1.1 is more flexible than 1.0

it can be treated as plain JSON

<kaz> Christian wonders which these points belong to, phase 1 or phase 2

McCool asks for objections to proposed resolutions

Cristiano suggests not to put it into fixed decisions yet

kaz suggests we rather make a resolution to simply work on those topics for today, and then adding concrete descriptions to the design.md

mccool will create a PR

PR will contain a draft for the index.html

<kaz> [adjourned]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/06/01 14:10:28 $