Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

solid/solid-spec

https://github.com/solid/specification

People

Repo info

Activity

Jan 14 13:58

RubenVerborgh on websockets-version-format

(compare)
Jan 14 13:58

RubenVerborgh on master

Remove slash from version numbe… Drop alpha from version number.… Replace warning by explanation.… and 1 more (compare)
Jan 14 13:58

RubenVerborgh closed #230
Jan 14 13:58

RubenVerborgh closed #221
Jan 13 20:37

WhyINeedToFillUsername commented #230
Jan 04 02:47

ewingson commented #221
Jan 01 22:15

scenaristeur commented #221
Jan 01 22:15

scenaristeur commented #221
Jan 01 22:10

scenaristeur commented #221
Jan 01 20:05

bourgeoa commented #221
Jan 01 16:48

scenaristeur commented #221
Dec 09 2020 16:16

TallTed commented #209
Dec 09 2020 15:54

michielbdejong closed #193
Dec 09 2020 15:53

michielbdejong closed #209
Dec 09 2020 15:53

michielbdejong closed #192
Dec 09 2020 15:51

michielbdejong closed #191
Dec 09 2020 15:51

michielbdejong closed #179
Oct 02 2020 12:28

Potherca opened #231
Sep 11 2020 06:27

csarven transferred #195
Sep 10 2020 17:07

csarven commented #195

Sarven Capadisli

@csarven

Aside: I don't think "trustedApp" is so far out that it doesn't belong in the ACL vocab either. I've seen worse.

Martynas Jusevicius

@namedgraph_twitter

so what do you propose i change?

i can do a PR for the web-access-control-spec re. trustedApp namespace

but i'm not gonna look for and replace all its usages

Sarven Capadisli

@csarven

I'd suggest to first make an issue and outline the case. Give others a chance to respond and move the discussion forward. If need be, PR can follow that.

Arne Hassel

@megoth_twitter

I think it's important to note that acl:trustedApp was merely intended as an interim solution for Solid - uncertain that we need to spec it in the long term...

Michiel de Jong

@michielbdejong

See also https://gitter.im/solid/specification

Jordan Shurmer

@JordanShurmer

it's still true that every Solid server is an LDP server right? I.e. part of implementing solid is implementing LDP?

hmm, I'll move this to the new chat room :D

Michiel de Jong

@michielbdejong

@JordanShurmer only the BasicContainer part of LDP, not the other two container types

Jordan Shurmer

@JordanShurmer

:thumbsup: thanks

Mike Adams

@mikeadams1

@JordanShurmer our brains may be soft wired because I have been working on warp for the past three hours

Mike Adams

@mikeadams1

Warp is a great app

Jordan Shurmer

@JordanShurmer

warp?

Mike Adams

@mikeadams1

https://mikeadams1.github.io/warp/index.html#/list/

It came from here; https://github.com/linkeddata/warp

I am going to pimp it out a little, if thats even possible but, I think I can.

Mike Adams

@mikeadams1

@timbl suggested that maybe we should be looking at combining apps to make things. That is what I am trying to do.

take a piece from here and a piece from there, that sort of thing so, it requires me to become familiar with almost everything working with solid currently.

Mike Adams

@mikeadams1

I am thinking that there are several apps I would like to use from one location, so Iframe's really make great use of combining applications in one place. Something like https://index.inrupt.net/

Sarven Capadisli

@csarven

@JordanShurmer re https://gitter.im/solid/solid-spec?at=5daf9ff914d55a37855abf5d , LDP describes behaviour for the most part optional. Solid will set specific constraints and clarify or strengthen the requirements from LDP. For example, LDP doesn't require any specific type of container to be implemented however it prescribes how they should behave if adopted. See also solid/specification#47 for containers for the upcoming Solid spec.

Jordan Shurmer

@JordanShurmer

thanks, makes sense

DJ Tinkers

@TinkersDj_twitter

SOLID as in that no dependency thingy?

Anyone interested in an opensource project?

Spec oriented development speeds up programming by generating code based on tests/specs. Tests required will be the same or less specs as a normal developer writes.

https://github.com/Neur0plasticity/spec-dev

MSG me if interested

Eureka Chen

@EurekaChen

What is the relationship between webid and did（https://www.w3.org/TR/did-core/）？

What is the relationship between webid and did（https://www.w3.org/TR/did-core/ ）？

Sarven Capadisli

@csarven

@EurekaChen This channel is no longer in use. We are over at https://gitter.im/solid/specification . See also solid/identity-panel#1

Eureka Chen

@EurekaChen

ok，thank you！

Noel De Martin

@NoelDeMartin

I've been looking at the spec repos and I found this comment https://github.com/solid/solid-spec/issues/159#issuecomment-488292554

Node-Solid-Server also implements n3-patch which seems to be different from RDF patch, and relies on http://www.w3.org/ns/solid/terms#inserts, http://www.w3.org/ns/solid/terms#deletes, and http://www.w3.org/ns/solid/terms#where which seems pretty custom and undocumented?

Is it safe for a client to rely on that? Or is that just a node-solid-server thing?

Tim Berners-Lee

@timbl

It’s a NSS thing at the moment. The plan is to a) implement N3 patch, b) send patches up the web socket instead of pub pings with no data; c) open up the client to peer to peer configurations like mesh configurations and CRDT and stuff. N3 patches anyone can parse and add more data to.

Would love it if someone did it but it is research level or someday pile at this stage on the roadmap.