Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 06 00:07
    csarven synchronize #346
  • Dec 06 00:07

    csarven on n3-patch

    Stabilise n3-patch spec:require… (compare)

  • Dec 05 23:02
    csarven synchronize #346
  • Dec 05 23:02

    csarven on n3-patch

    Minor (compare)

  • Dec 05 22:47
    csarven synchronize #346
  • Dec 05 22:47

    csarven on n3-patch

    Minor (compare)

  • Dec 05 20:52
    csarven synchronize #352
  • Dec 05 20:52

    csarven on authoritative-contained-resource-data

    Update protocol.html Co-author… (compare)

  • Dec 05 20:48
    csarven synchronize #352
  • Dec 05 20:48

    csarven on authoritative-contained-resource-data

    Update protocol.html Co-author… (compare)

  • Dec 05 20:01
    RubenVerborgh commented #352
  • Dec 05 16:50
    csarven commented #352
  • Dec 05 16:48
    csarven review_requested #352
  • Dec 05 16:48
    csarven review_requested #352
  • Dec 05 16:48
    csarven review_requested #352
  • Dec 05 16:48
    csarven review_requested #352
  • Dec 05 16:48
    csarven review_requested #352
  • Dec 05 16:48
    csarven commented #352
  • Dec 05 16:39
    csarven synchronize #352
  • Dec 05 16:39

    csarven on authoritative-contained-resource-data

    Minor Add contained-resource-metadata… (compare)

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'
Sarven Capadisli
@csarven
It just means that there is an identity associated to a policy that's controlling the target resource (root container).
Sarven Capadisli
@csarven

@/all Meeting with the CredentialsCG is fixed to March 10 at 15:00 UTC and 18:00 UTC (two ~1h sessions) - seems to work for most. CCG presents to SocialCG in the first session, and the other way around in the second session.

They've suggested that an intro to their following work items would be of interest to us: Universal Wallet, DID-Core, Secure Data Storage + others. Also asking any specific work items or areas they should cover.

Please share (here) what you'd like to learn more about.. I'll collect the responses here and send. In https://gitter.im/solid/specification?at=6001ada781c55b09c70d2da8 I suggested some areas:

Identity/Identifiers: WebID, DID
Access control / Capability-based security models: ACL, OCAP
VC data model
Signatures/Encryption
All sorts of Security and Privacy Considerations

I think we should definitely hear more about the security models they're working on. I'm not sure about "Universal Wallet" (as per their suggestion) at this time - not sure if that's high priority.. but I have no strong opinion otherwise.

Henry Story
@bblfish
I am fine with that date. I am just reading up on that and will post questions I have in the Solid Authentication channel. (could do here to).
Sarven Capadisli
@csarven
Re specific questions, let's track them and bring that up in the meeting. For now, let's just agree on a few specs/topics of interest that we'd like from them.
CCG didn't indicate any specific topic from us, so I'll just say we'll do an overview of our key work items (as mentioned awhile back).
Henry Story
@bblfish
I put some initial questions I have over here: solid/authentication-panel#126
Sarven Capadisli
@csarven
Great, thanks!
Fred Gibson
@gibsonf1
A quick question on the persistence of reference URIs in the specs. For example: https://solidproject.org/TR/protocol#resource-type-heuristics With TrinPod we support a full causal systems digital twin, including requirements against systems. We would like to link to the requirements in all the different specs and associate them with our systems so we can automate compliance control. Are the bookmarks etc in the Specs going to persist - or are they not reliable as URI references to mission critical system specs?
My thought is that we duplicate the spec text in the twin such that when it's revisited, we can compare what we have with current published spec and flag if any changes have happened
Also great would be a way to retrieve the master index of spec sections to confirm we have them all or if something has been deleted etc
Martynas Jusevicius
@namedgraph_twitter
the heuristics looks like it's going against URI opaqueness...
Fred Gibson
@gibsonf1
We would also be happy to host a pod that presents a systems model linked to Solid specs for the protocol
Martynas Jusevicius
@namedgraph_twitter
Fred Gibson
@gibsonf1
Maybe I'm asking for something different - a reliable master index of URI's for all the solid specs and their sections