Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 27 15:38

    csarven on main

    Add recommendation for Conforma… (compare)

  • Sep 27 15:21

    csarven on main

    Add recommendation for Consider… (compare)

  • Sep 26 12:49
    csarven edited #456
  • Sep 26 12:46
    csarven locked #456
  • Sep 26 12:45
    csarven opened #456
  • Sep 23 13:41
    elf-pavlik commented #455
  • Sep 23 13:41
    csarven commented #455
  • Sep 23 13:28
    elf-pavlik commented #455
  • Sep 23 13:18
    elf-pavlik commented #454
  • Sep 23 13:16
    elf-pavlik commented #454
  • Sep 23 11:13
    RubenVerborgh commented #454
  • Sep 23 10:51
    rubensworks commented #455
  • Sep 23 10:19
    csarven commented #455
  • Sep 23 10:13
    csarven commented #455
  • Sep 23 10:13
    matthieubosquet commented #455
  • Sep 23 07:00
    rubensworks commented #455
  • Sep 23 06:50
    csarven commented #455
  • Sep 23 06:50
    csarven commented #455
  • Sep 23 06:33
    rubensworks commented #455
  • Sep 23 06:33
    rubensworks commented #455
Dmitri Zagidulin
@dmitrizagidulin
(given that we don't have need for this yet, don't have vocab to define how to constrain or what to constrain, etc)
Sarven Capadisli
@csarven
@dmitrizagidulin For the constraints defined in the Solid spec, that's not much of an issue because whatever is defined in the spec will be common to all servers and clients in the ecosystem.
In the case of a response body describing the problem details, yes, it;d be necessary provide the vocab. That's covered in solid/specification#28
Sarven Capadisli
@csarven
Even just making it possible to describe the problem details can help clients without necessarily having prior knowledge of the vocab.
Dmitri Zagidulin
@dmitrizagidulin
I think what might help me is an example
because as an implementer, I'm looking at that spec text, and it says a server MUST advertise constraints, and I'm thinking.. what constraints? In what cases? and how do I express them?
Sarven Capadisli
@csarven
Say server denies an update. It can return 409 and link to the spec constraint saying that server doesn't allow client to update containment triples.
Dmitri Zagidulin
@dmitrizagidulin
so what's an example of that?
(so that I know what to return on a 409)
Sarven Capadisli
@csarven
With this specific example, it'd be https://www.w3.org/TR/ldp/#ldpc-put-mbrprops
(or whatever the URI is in the Solid spec)
Dmitri Zagidulin
@dmitrizagidulin
I see, thanks
Justin Bingham
@justinwb
@csarven i had commented on the ticket but do you assume shape validation falls into this bucket
Sarven Capadisli
@csarven
Not sure about exact categorisation. There are similar concepts in play but I'd say that SV is possibly a specific kind of a constraint (ie. linked via constrainedBy). Besides that, constrainedBy can handle HTTP, authn/z based constraints, in addition to data.
Comes back around to what I've asked several times about the relationship/diff with solid:shape...
Justin Bingham
@justinwb
@csarven are you good for session today?
Sarven Capadisli
@csarven
Yea.
Justin Bingham
@justinwb
:+1:
Sarven Capadisli
@csarven
solid/specification#187 is an important one. Reviews would be great and super helpful.
Justin Bingham
@justinwb
will do!
Sarven Capadisli
@csarven
@acoburn Noted your preference. Just want to be clear that the PR captures the rough consensus - and there was quite a bit of gaps/unknowns all around DELETE (as you know from the issues).
Sarven Capadisli
@csarven
@namedgraph_twitter Do you use acl:accessTo with 1 or n?
Sarven Capadisli
@csarven
Do you use acl:default ? Can a resource inherit an ACL instead of having its own?
Martynas Jusevicius
@namedgraph_twitter
you mean acl:accessTo with one or multiple values?
as a general case multiple
we don't use acl:default
Sarven Capadisli
@csarven
How about own ACL or inheritance?
Martynas Jusevicius
@namedgraph_twitter
what do you mean with "own ACL"?
Sarven Capadisli
@csarven
When a resource is deleted, do you clean-up eg. remove an associated ACL?
Link rel=acl foo.acl
or however you associate - data level.
Martynas Jusevicius
@namedgraph_twitter
we mostly use acl:accessToClass
acl:accessTo only with "singleton" system resources
with acl:accessToClass there's no cleanup that needs to be done when an instance goes away
Sarven Capadisli
@csarven
I presume somewhere you have foo rel=acl foo.acl . What happens to foo.acl (and say it uses acl:accessTo foo) if foo is deleted?
Martynas Jusevicius
@namedgraph_twitter
we don't :)
why should we?
Sarven Capadisli
@csarven
Can a client discover a resource's ACL so that it can update?
Martynas Jusevicius
@namedgraph_twitter
no. but it can request access if it doesn't have it
that part is an extension of W3C ACL
Sarven Capadisli
@csarven
I don't know why you should or not. I'm merely trying to understand how your systems are making use of WAC/ACL... and comparing with how Solid is going at it. Trying to find where things can be reconciled or really FUBAR'd.
Martynas Jusevicius
@namedgraph_twitter
but what use case are we talking about here?
Sarven Capadisli
@csarven
Extension of W3C ACL?
I just said.. client. If I have an article and I only want you to read it, how would I achieve that?
Martynas Jusevicius
@namedgraph_twitter
if you want to read it but currently do not have access?
request read access
the app admin will see a request and grant it - or deny it
Sarven Capadisli
@csarven
Is app admin like the owner or controller of the resource?
Does that mean that acl:agent doesn't actually control ( in the general sense) the resource referred from accessTo?