Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • May 10 14:01
    laurensdeb commented #258
  • May 10 13:52
    elf-pavlik edited #258
  • May 10 13:51
    elf-pavlik opened #258
  • Apr 19 16:32
    justinwb commented #253
  • Apr 14 20:43

    github-actions[bot] on gh-pages

    deploy: f6b422e59a082d1b3e3a577… (compare)

  • Apr 14 20:42
    elf-pavlik closed #201
  • Apr 14 20:42
    elf-pavlik commented #201
  • Apr 14 20:42

    elf-pavlik on main

    primer: updated some snippets … primer: updated names of scopes primer: updated some snippets … and 4 more (compare)

  • Apr 14 17:28
    elf-pavlik commented #241
  • Apr 12 12:57
    elf-pavlik edited #257
  • Apr 12 12:43
    elf-pavlik edited #257
  • Apr 12 12:43
    elf-pavlik edited #257
  • Apr 12 12:42
    elf-pavlik review_requested #257
  • Apr 12 12:42
    elf-pavlik opened #257
  • Apr 10 23:29
    elf-pavlik assigned #201
  • Apr 10 23:07
    elf-pavlik closed #108
  • Apr 10 21:48
    elf-pavlik labeled #256
  • Apr 10 21:48
    elf-pavlik opened #256
  • Apr 10 21:37
    elf-pavlik closed #113
  • Apr 10 21:33
    elf-pavlik closed #242
Dmitri Zagidulin
@dmitrizagidulin
(have to drop; thanks all!)
elf Pavlik
@elf-pavlik
@justinwb netlify needs to be updated to match how authentication-panel works - run build.sh
elf Pavlik
@elf-pavlik
I'm merging those old PRs into archive, @justinwb could you please take a look at those two stale branches? https://github.com/solid/data-interoperability-panel/branches/stale
elf Pavlik
@elf-pavlik

I'm merging those old PRs into archive

done https://github.com/solid/data-interoperability-panel/pulls

@justinwb I think we should change default branch to main and prune branches in the repo https://github.com/solid/data-interoperability-panel/branches

this repo seems to be one of the last ones still using master as the base branch

Justin Bingham
@justinwb
oh yeah lets switch it
sorry just seeing these other @ s
@elf-pavlik deleted both stale branches :white_check_mark:
elf Pavlik
@elf-pavlik
elf Pavlik
@elf-pavlik
q+
elf Pavlik
@elf-pavlik
hRicklefs
@hRicklefs
One for next week but I would be curious to understand how the conversation we just had relates to what you talk about in the authorisation panel.
1 reply
@elf-pavlik could you send me and @JulietteCarter an invite for the meeting you mentioned to talk about the interfaces.
elf Pavlik
@elf-pavlik
I'm going to send each one of you a direct message
elf Pavlik
@elf-pavlik
I hope we can merge this primer PR on Tuesday solid/data-interoperability-panel#119 -- rendered preview
elf Pavlik
@elf-pavlik
Proposal of small change to Create Data Instance which will should allow to keep IRIs opaque for the client solid/data-interoperability-panel#120
hRicklefs
@hRicklefs
On leave today so wont join later on
Justin Bingham
@justinwb
enjoy the time off @hRicklefs !
Justin Bingham
@justinwb
@/all HackMD for today - please add as you like - https://hackmd.io/@hAlm_W2-T-q16baquNyRXg/H1oZNqmqu
Justin Bingham
@justinwb
@elf-pavlik have provided some feedback on solid/data-interoperability-panel#119
elf Pavlik
@elf-pavlik
thanks @justinwb! I've just addressed your feedback
elf Pavlik
@elf-pavlik

@/all HackMD for today - please add as you like - https://hackmd.io/@hAlm_W2-T-q16baquNyRXg/H1oZNqmqu

I added couple of things, rather than trying to resolve them during the call we could pick some actions (self-assign on those issues) and resolve them over the next couple of days

Eric Prud'hommeaux
@ericprud
example PR with pr-preview links in first comment: w3c/lds-wg-charter#73
Justin Bingham
@justinwb
@elf-pavlik IIRC we talked about devoting this week’s panel session to client library work
Justin Bingham
@justinwb
Here’s what would likely be the regular HackMD - https://hackmd.io/@hAlm_W2-T-q16baquNyRXg/ByNXp1pcu
But lets decide at start whether we want to dive into tooling this session and use it for the agreed upon monthly tooling session
elf Pavlik
@elf-pavlik

@elf-pavlik IIRC we talked about devoting this week’s panel session to client library work

I think we can prioritize it if @JulietteCarter and @hRicklefs are joining and would like to discuss their ideas related to TS implementation

Justin Bingham
@justinwb
Also if @jaxoncreed makes it this week we can talk a bit about some of the rdf tooling that would be related
(he just confirmed he’s joining so i’ll add that to agenda)
elf Pavlik
@elf-pavlik
I added solid/data-interoperability-panel#122 just hoping to take 2 min to ensure that no one has any objections
Justin Bingham
@justinwb
:white_check_mark:
elf Pavlik
@elf-pavlik
q+
Justin Bingham
@justinwb
q+ re: agent access
elf Pavlik
@elf-pavlik
q+ re: authorization system
elf Pavlik
@elf-pavlik
q+ re: emphasis on data discovery
elf Pavlik
@elf-pavlik
q+ re: creating data instances
elf Pavlik
@elf-pavlik
elf Pavlik
@elf-pavlik
q+ re: who owns the data - collaborative ecosystem
justinwb @justinwb will have to jump in 2m
elf Pavlik
@elf-pavlik
@justinwb can I just go ahead and merge #122 ?
elf Pavlik
@elf-pavlik
actually we can merge #121 as well, after that I will
Justin Bingham
@justinwb
@elf-pavlik #122 merged / #121 approved/merged!
elf Pavlik
@elf-pavlik
thank you @justinwb, i made new PR for running validation on turtle snippets solid/data-interoperability-panel#123
matthieu-fesselier
@matthieu-fesselier
Hello here! Does anyone know if there has been some work already to implement the spec in the community solid server?
elf Pavlik
@elf-pavlik
Hi, current spec shouldn't require additions to the storage servers. Applications and Authorization Agent should be able to handle everything.
Personally I find it a very interesting options to explore for storage servers to directly support Data Grants rather than require Authorization Agent to generate something like ACP or WAC based on them. But as the spec currently stands it assumes that Authorization Agent would set access policies on the storage server based on data grants.
To be clear, I meant Solid Application Interoperability spec. The https://shapetrees.org/TR/specification/ most likely can benefit from support on the solid storage.