-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add minutes and recording of the 2017-06-26 telecon
- Loading branch information
Showing
3 changed files
with
282 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,172 @@ | ||
| <!doctype html> | ||
| <html lang="en"> | ||
| <head> | ||
| <meta charset="utf-8"> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | ||
| <title>Telecon Minutes for 2017-06-26 | Hydra W3C Community Group</title> | ||
| <meta name="twitter:card" content="summary"> | ||
| <meta name="twitter:site:id" content="1524709850"> | ||
| <meta name="twitter:creator:id" content="64360611"> | ||
| <meta name="twitter:description" content="Hydra simplifies the development of interoperable, hypermedia-driven Web APIs"> | ||
| <link rel="stylesheet" href="http://fonts.googleapis.com/css?family=Exo:400,700"> | ||
| <link rel="stylesheet" href="http://yui.yahooapis.com/pure/0.5.0/pure-min.css"> | ||
| <!--[if lte IE 8]> | ||
| <link rel="stylesheet" href="http://yui.yahooapis.com/pure/0.5.0/grids-responsive-old-ie-min.css"> | ||
| <![endif]--> | ||
| <!--[if gt IE 8]><!--> | ||
| <link rel="stylesheet" href="http://yui.yahooapis.com/pure/0.5.0/grids-responsive-min.css"> | ||
| <!--<![endif]--> | ||
| <link rel="stylesheet" href="/css/styles.css"> | ||
| <link rel="stylesheet" href="/css/minute-styles.css"> | ||
| <!--<![endif]--> | ||
| </head> | ||
| <body> | ||
| <div class="header"> | ||
| <div class="home-menu pure-menu pure-menu-open pure-menu-horizontal pure-menu-fixed"> | ||
| <span class="pure-menu-heading"><a href="/"><img src="/img/logo.svg" alt="Hydra"></a></span> | ||
| <ul> | ||
| <li><a href="/#specifications">Specifications</a></li> | ||
| <li><a href="/#community">Community</a></li> | ||
| <li><a href="/#tooling">Tooling</a></li> | ||
| <li><a href="/minutes/">Minutes</a></li> | ||
| </ul> | ||
| </div> | ||
| </div> | ||
|
|
||
| <div class="content"> | ||
| <div class="pure-g"> | ||
| <div class="l-box pure-u-1"> | ||
| <h1>Hydra W3C Community Group Telecon</h1> | ||
| <h2>Minutes for 2017-06-26</h2> | ||
| <div class="summary"> | ||
| <dl> | ||
| <dt>Agenda</dt> | ||
| <dd><a href="https://www.w3.org/community/hydra/wiki/Conference_Calls">https://www.w3.org/community/hydra/wiki/Conference_Calls</a></dd> | ||
| <dt>Topics</dt> | ||
| <dd><ol> | ||
| <li><a href="#topic-1">Status update on architectural diagram</a> | ||
| <li><a href="#topic-2">schema.org actions PR #125</a> | ||
| <li><a href="#topic-3">Reference client PR #1</a> | ||
| <li><a href="#topic-4">void:classPartition Issue #126</a> | ||
| </ol></dd> | ||
| <dt>Resolutions</dt> | ||
| <dd><ol> | ||
| <li><a href="#resolution-1">Merge schema.org actions PR #125</a> | ||
| </ol></dd> | ||
| <dt>Action Items</dt> | ||
| <dd><ol> | ||
| <li><a href="#action-1">Markus will try to find a tool which will help us with PR reviews; it's currently difficult to keep track what has been addressed and what hasn't</a> | ||
| <li><a href="#action-2">Markus to rename issue #126 to not suggest a solution</a> | ||
| <li><a href="#action-3">Pavlik to drive discussion regarding #126 after the issue has been renamed</a> | ||
| </ol></dd> | ||
| <dt>Chair</dt> | ||
| <dd>Markus Lanthaler</dd> | ||
| <dt>Scribe</dt> | ||
| <dd>elf Pavlik</dd> | ||
| <dt>Present</dt> | ||
| <dd>elf Pavlik, Karol Szczepański, Markus Lanthaler</dd> | ||
| <dt>Audio Log</dt> | ||
| <dd> | ||
| <audio controls="controls" preload="none"> | ||
| <source src="audio.mp3" type="audio/mpeg" /> | ||
| Warning: Your browser does not support the HTML5 audio element, | ||
| please upgrade.<br> | ||
| <a href="audio.mp3">audio.mp3</a> | ||
| </audio> | ||
| </dd> | ||
| </dl> | ||
| </div> | ||
| <div class="information">elf Pavlik is scribing.</div> | ||
|
|
||
| <h1 id="topic-1" class="topic">Topic: Status update on architectural diagram</h1> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: <a href="https://github.com/HydraCG/Specifications/pull/128">https://github.com/HydraCG/Specifications/pull/128</a></div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: ruben made PR and send an email that he can not join the call today</div> | ||
| <div class="comment-continuation">... PR includes script that generates SVG from LaTeX on travis and adds it to gh-pages branch</div> | ||
| <div class="comment-continuation">... we should just probably move this discussion to PR or mailing list</div> | ||
|
|
||
| <h1 id="topic-2" class="topic">Topic: schema.org actions PR #125</h1> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: <a href="https://github.com/HydraCG/Specifications/pull/125">https://github.com/HydraCG/Specifications/pull/125</a></div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: I think I addressed all feedback [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... I touched a few more things than just schema.org actions</div> | ||
| <div class="comment-continuation">... one thing is, e.g. the #events link</div> | ||
| <div class="proposal"><strong>PROPOSAL:</strong> Merge schema.org actions PR #125</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: +1</div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: +1</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: +1</div> | ||
| <div id="resolution-1" class="resolution"><strong>RESOLUTION:</strong> Merge schema.org actions PR #125</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: I will merge it after the meeting</div> | ||
|
|
||
| <h1 id="topic-3" class="topic">Topic: Reference client PR #1</h1> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: <a href="https://github.com/HydraCG/Heracles.ts/pull/1">https://github.com/HydraCG/Heracles.ts/pull/1</a></div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: karol would you like to give us quick update ?</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: I made new commit yesterday which addressed most of the feedback</div> | ||
| <div class="comment-continuation">... I still don't have this 'lazy parsing', possibly I would leave it for the future</div> | ||
| <div class="comment-continuation">... up to you (Markus) if you need it now or we can wait</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: I don't see it as blocking issue</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: everything now stays behind interfaces facade so we can replace everything behind it later</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: did you already add a TODO ?</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: in general i try to stick to the Use Cases</div> | ||
| <div class="comment-continuation">... currently we have a little bit of implementation</div> | ||
| <div class="comment-continuation">... ApiDocumentation fetching and EntryPoint fetching</div> | ||
| <div class="comment-continuation">... we should have some integration tests based on Ucs</div> | ||
| <div class="comment-continuation">... i would like to root it in the use cases</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: I meant just a comment with TODO just as a reminder for what we discussed and decided to address in the future</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: we can also create issues in the gh repo</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: creating an issue sounds like a good way to go</div> | ||
| <div class="comment-continuation">... in general if someone creates PR and we want to defer addressing some of the issues, creating gh issues makes sense</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: I'll create issues for what we want to deffer from this PR</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: I find it difficult to track of all those comments we make in PR reviews</div> | ||
| <div class="comment-continuation">... do you know any other tool that might handle it better</div> | ||
| <div class="comment-continuation">... if author of the PR could mark a thread as addressed or not</div> | ||
| <div class="comment-continuation">... i could suggest something after small research</div> | ||
| <div id="action-1" class="action"><strong>ACTION</strong>: Markus will try to find a tool which will help us with PR reviews; it's currently difficult to keep track what has been addressed and what hasn't</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: one question regarding my PR</div> | ||
| <div class="comment-continuation">... this 10 days long discussion stops me from further development</div> | ||
| <div class="comment-continuation">... how we can speed up our PR process so it doesn't block my development</div> | ||
| <div class="comment-continuation">... from my perspective current pace feels slow</div> | ||
| <div class="comment-continuation">... waiting 10 days seems to long</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: maybe making smaller PRs will make things faster</div> | ||
| <div class="comment-continuation">... this one as initial one included a lot of things</div> | ||
| <div class="comment-continuation">... if you nail down interfaces first, which requires most discussion</div> | ||
| <div class="information">and focus on implementation later this would speed things up</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: IMO our needs have to be a driver, it may benefit a final outcome if requirements drive it</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: interfaces could be driven by use cases, what user of this library would need to work with given use case</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: i'll try to think it over and will propose something to the community</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: what next things you would like to work on?</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: i would like to start with integration tests, and add datasets based on our use cases</div> | ||
| <div class="comment-continuation">... so that we can start extracting some data that other implementations could eventually also use</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: given we didn't come up with a specific solution on how to speed it up, maybe also you could ask on mailing list for reviews</div> | ||
| <div class="information">and when you see it ready to merge we can make a 'last call' on mailing list to ask if anyone objects</div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: I think if we get disciplined and keep focused in PRs we could get much faster [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... we shouldn't get sidetracked by unrelated stuff but move that aggresively to separate issues</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: we should try everything what could speed up the process</div> | ||
|
|
||
| <h1 id="topic-4" class="topic">Topic: void:classPartition Issue #126</h1> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: <a href="https://github.com/HydraCG/Specifications/pull/126">https://github.com/HydraCG/Specifications/pull/126</a></div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: I'm not sure this is worth discussing yet but given we have time... [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... I think we should find a better pattern for links in the EntryPoint that point to collections of resources of a specific type</div> | ||
| <div class="comment-continuation">... the example was the "events" link in the EntryPoint that points to a collection containing all Events</div> | ||
| <div class="comment-continuation">... we need to be able to describe that to a client in a better way</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: We discussed this before in the context of Data Shapes [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... OWL would be another solution</div> | ||
| <div class="comment-continuation">... but it opens a can of worms and may be difficult for the client to use</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: SHACL was the name</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: OWL works and has capacity to express it, but it opens a can of worms that it has a lot of power and clients should have to fully implement it</div> | ||
| <div class="comment-continuation">... class partition seems nice, but hydra should handle it natively give as common use case in APIs</div> | ||
| <div class="comment-continuation">... we should investigate options of nice short pattern</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: we could use issue #126 to discuss it in more detail</div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: I'll post a link how SOLID solves this [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... OWL has something but it doesn't seem practical in real world scenarios</div> | ||
| <div class="comment-continuation">... we should come up with a better solution</div> | ||
| <div id="action-2" class="action"><strong>ACTION</strong>: Markus to rename issue #126 to not suggest a solution</div> | ||
| <div id="action-3" class="action"><strong>ACTION</strong>: Pavlik to drive discussion regarding #126 after the issue has been renamed</div> | ||
| <div class="comment"><span class="name">elf Pavlik</span>: Currently the use case is only events [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment-continuation">... if there would be two or more types the problem would become more apparent</div> | ||
| <div class="comment-continuation">... Karol, what do you think about extending the use cases to show this?</div> | ||
| <div class="comment"><span class="name">Karol Szczepański</span>: Sure, I'm open to extending the use cases [scribe assist by Markus Lanthaler]</div> | ||
| <div class="comment"><span class="name">Markus Lanthaler</span>: anything else you would like to discuss today? we still have 30min</div> | ||
| </div> | ||
| </div> | ||
| </div> | ||
| </body> | ||
| </html> |
Oops, something went wrong.