W3C

- DRAFT -

SV_MEETING_TITLE

30 May 2019

Attendees

Present
Henry_S, Michiel_dJ, Matthias_E, Armando
Regrets
Chair
SV_MEETING_CHAIR
Scribe
MItzi

Contents


<armando> Sorry, problems with connection!

<bblfish> what company does armando work for?

<michielbdejong> https://github.com/solid/solid-spec/issues/174#issuecomment-496829681

(Michiel) https://github.com/solid/solid-spec/issues/174

Lots of items in the spec that have been talked about and not recorded

Would like to map what those items are to be able to update the spec

<bblfish> It's a holiday in Germany

<Matthias_Evering> there are very fine granulated rights in solid

How to go about recording the past conversations?

use the NSS v5 implementation as a guide for updating the spec, although there are many items that are not ideal

<bblfish> I thought that LDP did settle deleting of directories.

(Henry) originally there was only an IRC channel and the master card introduction led to some diffused conversations

(Henry) contradiction between linkage and security

(Henry) could do with bridging to the security community

to appeal to the academics it would be helpful to think about how to create papers

(Michiel) Could ask app developers to submit issues they face

(Mitzi) how can we allow a free write from MIT group and what could be the threshold to active the another more complex decision making process

(Henry) can get a list of questions from the app developers

(Mitzi) could do it by number of people concerned

(Henry) perhaps we need to define the people that can raise concerns

(Michiel) look at the people working on Solid apps and their concerns

(Michiel) if something is changed there needs to be a record of the reasoning

(Michiel) almost any spec change is going to be problematic for app developers

(Michiel) identify reasons why people trigger spec changes. list the motivations

e.g. removing ambiguity

(Mitzi) what is there is free write and if 5 people on the Solid Panel flag that they are concerned then the vote kicks in

(Michiel) e.g. making the solutions more elegant

(Michiel) the Tim blog from 2009 gives a good overview of the Solid spec aim

(Michiel) lots of experts on linked data which is a slightly different from the web of data vision

(Henry) It would be nice to have search but can do it in multiple ways, some which are more generalisable to the whole web

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/05/30 09:00:50 $

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: Henry_S Michiel_dJ Matthias_E Armando
No ScribeNick specified.  Guessing ScribeNick: MItzi
Inferring Scribes: MItzi

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: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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]