W3C

- DRAFT -

SV_MEETING_TITLE

15 Aug 2019

Attendees

Present
Jim_S, Elf_P, Rob_M, Jason, Dmitri_Z, Max_D, Jackson_M, Mitzi_L
Regrets
Chair
SV_MEETING_CHAIR
Scribe
elf-pavlik

Contents


<Mitzi> Follow up on last week to ask if all questions were resolved

<Mitzi> (Jim S) background information about US Department of Defense including AI assistant

elf-pavlik: purpose of this weekly call given panels have their weekly calls on specific topics

Mitzi: we can use it to have track on the big picture, and to keep in sync with each other
... also easy starting point for people who don't feel familiar with specific areas

Dmitri: I agree with what Mitzi said, especially about those who just join in and don't know about all the specific panels
... also to introduce yourself, tell about projects you work on
... many w3c groups during calls ask about new members and if any introductions and what they work

<Mitzi> (Jackson) kicked off the authentication panel on Monday at 10am ET

Jackson: we kicked off Authentication call - they will happen Monday 10AM EDT
... we also had second App Authorization call - they will happen Wednesday 10AM EDT
... in that call we discussed creating discovery proposal for Data Interoperability Panel

<Mitzi> (thank you Elf-Pavlik)

Max: I work on the privacy
... seeing how it fits GDPR

<Mitzi> https://github.com/solid/process/blob/master/panels.md#app-authorization

Max: we need to look at choices made in other panels and their impact on privacy

<Mitzi> https://github.com/solid/process/blob/master/panels.md#privacy-and-individuals-rights-protection-panel

Max: I've started reviewing the websites, documentation and how someone could try to abuse things
... I will mostly stay silent but from time to time I will share document with what we can improve

Jim: In the Data Interoperability panel we went over 5 existing issues

<Mitzi> https://github.com/solid/process/blob/master/panels.md#data-interoperability

Jim: we discussed models and mechanisms
... different changes and standardizations

<Mitzi> gather use cases covered by the panels

<Mitzi> prioritise things which are needed for implementation

Jackson: So far we discussed Authentication, App Authorization and Data Interop panels

Dmitri: Identity panel haven't met yet, we work around what happens in other panels

elf-pavlik: github repo + gitter channel + hackmd.io for scribing seems to work pretty well together

RRSAgent: please draft minutes

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.154 (CVS log)
$Date: 2019/08/15 14:28:00 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Jim_S Elf_P Rob_M Jason Dmitri_Z Max_D Jackson_M Mitzi_L
No ScribeNick specified.  Guessing ScribeNick: elf-pavlik
Inferring Scribes: elf-pavlik

WARNING: No "Topic:" lines found.


WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]