Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 23 20:50
    bblfish commented #325
  • Oct 23 20:49
    bblfish commented #325
  • Oct 23 20:47
    bblfish commented #325
  • Oct 23 20:46
    bblfish commented #325
  • Oct 23 20:45
    bblfish commented #325
  • Oct 23 09:30
    bblfish commented #325
  • Oct 23 09:29
    bblfish commented #325
  • Oct 23 09:29
    bblfish commented #325
  • Oct 23 09:27
    bblfish commented #325
  • Oct 23 09:05
    bblfish commented #325
  • Oct 23 09:03
    bblfish commented #325
  • Oct 23 09:03
    bblfish commented #325
  • Oct 23 08:40
    bourgeoa commented #329
  • Oct 23 07:36

    csarven on main

    Some links to issues (compare)

  • Oct 23 07:36
    csarven closed #331
  • Oct 23 05:58
    damooo commented #329
  • Oct 23 01:21
    crspybits opened #331
  • Oct 22 20:20
    kjetilk commented #330
  • Oct 22 18:57
    jeff-zucker commented #227
  • Oct 22 17:36
    RubenVerborgh commented #330
Sarven Capadisli
@csarven
@namedgraph_twitter @gibsonf1 may I ask you to respond in solid/specification#227 about your implementations. See the use cases and perhaps chime in on the concerns raised there/here..
Fred Gibson
@gibsonf1
We will do the same for documents such that there is a parent node for the overall document, then a hierarchy of m_contains nodes below that
Will do @csarven
Sarven Capadisli
@csarven
@namedgraph_twitter I want to understand better.. could you simplify with an example along the lines of GET /photos/ or maybe pick one or two of the use cases mentioned in that issue?
@justinwb true that.
Martynas Jusevicius
@namedgraph_twitter
1 reply
Aaron Coburn
@acoburn
@csarven if a query endpoint is a not possible, then I would strongly advocate for a consistent paging mechanism across servers
Once you have paging, you can support sorting as well, which is something I consistently hear as a feature request
Sarven Capadisli
@csarven
Both are attractive. Pagination is also attractive for servers not having to cater to clients that can't (or don't want to) rate their requests.. so if they get a container with zillion contains, they loop through and issue a GET. Brings down the browser in the meantime..
@acoburn To be clear, I think we agree that with paged resources, the expectation is that they'd include the additional information about the contained resources?
(for resources that can be read)
Sarven Capadisli
@csarven
I've implemented ActivityStreams' paging in mayktso and dokieli. Can't remember now why I decided not implement LDP's paging :S
Aaron Coburn
@acoburn
For paged RDF, I would be fine with including information about contained resources.
Fred Gibson
@gibsonf1
strange, I'm having a hard time finding any ontology around ldp:inbox - does anyone have a link?
Sarven Capadisli
@csarven
Ontology?
Fred Gibson
@gibsonf1
Yes, triples from the ldp ontology defining the term inbox
Sarven Capadisli
@csarven

curl -H'Accept: text/turtle' http://www.w3.org/ns/ldp

:inbox
    a rdf:Property;
    rdfs:comment "Links a resource to a container where notifications for the resource can be created and discovered.";
    vs:term_status "stable";
    rdfs:isDefinedBy <https://www.w3.org/TR/ldn/>;
    rdfs:label "inbox";
    dcterms:issued "2016-09-29"^^xsd:date;
    dcterms:creator <http://csarven.ca/#i>, <https://rhiaro.co.uk/#me>.

?

Fred Gibson
@gibsonf1
Ahh thanks!
so its ldn:inbox ?
Impressive that you are the author of course
Sarven Capadisli
@csarven
No:
@prefix : <http://www.w3.org/ns/ldp#>.
Fred Gibson
@gibsonf1
is there a link to turtle for the full ldp namespace? I've been using the ldp turtle from lov, and that is missing much
3 replies
Sarven Capadisli
@csarven

Note:
curl -iH'Accept: text/turtle' http://www.w3.org/ns/ldp

HTTP/1.1 200 OK
content-location: ldp.ttl

curl http://www.w3.org/ns/ldp.ttl

Rai
@agentydragon_gitlab
hi, Solid folks :)
I'm Rai, I spent yesterday looking a bit into Solid, and so far the more I learn about it, the more I'm excited.
Sarven Capadisli
@csarven
@agentydragon_gitlab Same here, welcome!
Sarven Capadisli
@csarven
All, we may end up going with March 10 for the meetings with the Credentials CG. I hope that works for everyone? Will keep everyone posted once I know more.
Sarven Capadisli
@csarven
Can we get some eyes on solid/specification#228 ?
Rai
@agentydragon_gitlab
what would be a good place to report bugs that I see as someone starting out with Solid?
for example, I just saw this:
  • create new account on solidcommunity.net
  • see the "Your stuff" screen with a green "plus" button
  • I wanna create a thing, so I click the plus button, then, say, the "tracker" button
  • I get this:
image.png
and that leaves me wondering "ok, how do I create a workspace then?", but I couldn't find that anywhere in the UI.
Rai
@agentydragon_gitlab
never mind, looks like https://github.com/solid/solid/issues is where people are putting those.
Vincent
@Vinnl_gitlab

@agentydragon_gitlab Generally questions like these (that do not pertain to defining the Solid Specification) are best placed in https://gitter.im/solid/chat. In any case, the interface you're looking at at solidcommunity.net is called mashlib (sometimes called "The Data Browser" or "SolidOS"), and bug reports for it go here: https://github.com/solid/mashlib/issues/

(Yes, it's all a bit confusing that there are so many different projects, but that's what you get if you have an open standard that everyone can implement :) )

Sarven Capadisli
@csarven
Sarven Capadisli
@csarven
Jordan Shurmer
@jshurmer_gitlab
Hello all.
I stopped following Solid a while back just due to time constraints. Catching back up with things now - the Spec reads really great now, a lot of improvements from 1yr ago or so- well done
Sarven Capadisli
@csarven
@jshurmer_gitlab welcome back. ask questions. answer questions.
Jordan Shurmer
@jshurmer_gitlab
:)
Jordan Shurmer
@JordanShurmer
I plan on getting back to my slow-going implementation of Solid Server in Rust.
It's a side project for me (if only it was otherwise) and I have 3 kids now :) so I will not have much time for it, but expect my voice in here more often again
Sarven Capadisli
@csarven
++
Jordan Shurmer
@JordanShurmer
It seems the spec doc is missing some meta for the HTTP section. the subsections don't have entries in the TOC and they don't have id attributes
Sarven Capadisli
@csarven
"meta"? I meant to reconsider renaming the subsection names.. that's why I didn't bother because didn't commit to it yet. There is another subsection eg "Required Server-Side Implementation" --- and prefer to have all headings unique. Will revisit.
and trying to keep the headings and their ids close as possible.
Jordan Shurmer
@JordanShurmer
ok. makes sense. thanks for the context
I used "meta" informally :) as in "info describing the thing, not the thing per se"
Jordan Shurmer
@JordanShurmer

what exactly does this mean?

The root container (pim:Storage) MUST have an ACL auxiliary resource directly associated to it. The associated ACL document MUST include an authorization policy with acl:Control access privilege.

the storage root's ACL has to have at least one person with acl:Control privelege?
("person" being used loosely there)
Jordan Shurmer
@JordanShurmer
I guess 'agent' would have been the right term to use rather than 'person'