LDP Next CG Meeting 2016-07-21
Agenda
- Review the 8 proposed deliverables and technical issues of charter set forth by LDP Next 2015 Charter.
- Propose and discuss additions to list, if any.
- Discuss relevant independent works (on the above), needed or in progress.
- Vote on a general prioritization.
- Discuss preferred collaboration and communication methods, plus next steps.
Meeting Outcomes
- We decided to create a new for continued collaboration and information recording amongst the group; see LDP_Next_Community_Group
- We decided to create another Doodle vote in order to determine best time-slot for bi-weekly meetings; see http://doodle.com/poll/i9eqbhf37vxceame
- Team was OK with join.me for web and voice conferencing, but did not like the chat; suggested use of IRC instead.
- Team discussed and added new items to the Technical Issues for consideration from the group.
- Community Group members should identify their areas of interest (willingness to work on) in the table under 'Participants and Interests' on the new wiki page.
Meeting Recording
https://recordings.join.me/9vjUU8rKR0SkS-d5693GkQ
(The meeting recording will probably not be kept online indefinitely, so the link above will eventually be broken; sorry.)
Chat Log
- base22cody@All: +1 to brief intros
- base22cody@All: Solid project: http://solid.mit.edu/
- Rob Sanderson@All: name, institution, one sentence about LDP background?
- Rob Sanderson@All: Go down the list after Jim, so Andrew, then Floriano, Jared, Mark, Miguel, Nandana, Nick, Amy, ...
- Mark Matienzo (DPLA)@All: +1
- base22cody@All: Jim - can you drop in some links to the implementations? (especially the Javascript one)
- Tom Johnson@All: Andrew: on community groups, anyone can assign a chair if none are assigned. Someone (me) nominated you. You can resign at any time :)
- Andrew Woods@All: Thanks, Tom. That would explain it.
- Nandana Mihindukulasooriya@All: http://www.ldp4j.org/#/
- Jim Amsden@All: http://oslc.github.io/developing-oslc-applications/oslc-open-source-node-projects.html
- Andrew Woods@All: https://wiki.duraspace.org/display/FF/Fedora+Repository+Home
- Tom Johnson@All: https://github.com/ruby-rdf/rdf-ldp
- Rob Sanderson@All: Thanks Cody! Always good to know who we're talking with :)
- Mark Matienzo (DPLA)@All: @Sarven: We're based in Boston but most of us work remotely.
- Mark Matienzo (DPLA)@All: @Sarven but we're usually in Boston once a quarter or so.
- Nandana Mihindukulasooriya@All: LDP access control - UCR
- Nandana Mihindukulasooriya@All: https://www.w3.org/TR/ldp-acr/
- Jim Amsden@All: Many of these items are addressed by OASIS OSLC Core 3.0 which is built on LDP 1.0
- Mark Matienzo (DPLA)@All: @Sarven I think we'd be happy to anyhow :)
- Dmitri Zagidulin (Solid)@All: what mechanism was that, for change tracking?
- Rob Sanderson@All: +1 -- notification of change
- Rob Sanderson@All: rather than requesting a change
- Miguel@All: +1
- Andrew Woods (Fedora Repo)@All: Background info following a previous LDP WG meeting: https://lists.w3.org/Archives/Public/public-ldp-wg/2015Apr/0013.html
- Jim Amsden@All: How can LDP resources be constrained (i.e., closing the world down a bit) for a particular usage. Possible examples are OSLC ResourceShapes and W3C SHACL.
- Mark Matienzo (DPLA)@All: +1 to the promotion activities
- Andrew Woods (Fedora Repo)@All: https://www.w3.org/community/hydra/
- Tom Johnson (DPLA)@All: +1 to this approach
- Nandana Mihindukulasooriya@All: +1 to sandro
- Andrew Woods (Fedora Repo)@All: https://www.w3.org/2012/ldp/wiki/LDPNext2015_Charter#Deliverables
- Dmitri Zagidulin (Solid)@All: as far as additions, I'd also like to add -- we'd love to hear feedback on our iteration of the Web Access Control spec, https://github.com/solid/web-access-control-spec
- Tom Johnson (DPLA)@All: as an aside: is it within our purview to fix known issues on the test suite? https://github.com/w3c/ldp-testsuite/issues
- Miguel (CarbonLDP)@All: That’s a very good question
- Miguel (CarbonLDP)@All: Tom
- Sarven Capadisli@All: I can mention a few things about the Linked Data Notification initiative
- Andrew Woods (Fedora Repo)@All: Dimitri: what is the most effective way to provide webac feedback?
- Dmitri Zagidulin (Solid)@All: open github issues on that repo, or, if it's an informal sort of feedback, feel free to drop in our Gitter channel, https://gitter.im/solid/chat
- Andrew Woods (Fedora Repo)@All: Dimitri: thanks
- rhiaro (Amy Guy)@You: Cody Burleson can you change the name on the slide from Dominik to Sarven?
- rhiaro (Amy Guy)@You: (For LDN)
- Andrew Woods (Fedora Repo)@All: Dimitri: can you please paste in the webac github project link?
- Rob Sanderson@All: hangouts with automatic mute-on-join? :D
* Dmitri Zagidulin (Solid)@All: Andrew, of course. https://github.com/solid/web-access-control-spec
- Tom Johnson (DPLA)@All: +1
- Tom Johnson (DPLA)@All: (+1 biweekly)
* Mark Matienzo (DPLA)@All: +0 (biweekly might be hard for me to join) * Andrew Woods (Fedora Repo)@All: +1 - biweekly to start * Floriano Scioscia (poliba.it)@All: +1 biweekly
- Rob Sanderson@All: biweekly to start sounds good, especially if people can't attend every call
- Rob Sanderson@All: Then at least they can be on once a month :)
- Nandana Mihindukulasooriya@All: +1 for bi-weeky, may be 1 hour
- Nandana Mihindukulasooriya@All: and ask again for a suitable timeslot that works
- Nandana Mihindukulasooriya@All: for us, europe, and may be asia too
- rhiaro (Amy Guy)@All: IRC!
- sandro2@All: This chat is terrible -- I'ts white on lime green. I can only read it by highlighting the text.
- sandro2@All: I suggest IRC for the chat....
- Andrew Woods (Fedora Repo)@All: sandro2: +1... it will be easier for chat between meetings as well.
- Rob Sanderson@All: +1 to Sandro
- Nandana Mihindukulasooriya@All: Thanks a lot Cody for restarting LDP work
- Tom Johnson (DPLA)@All: Thanks Cody!
- Nandana Mihindukulasooriya@All: Bye!