Sarven Capadisli

Also something fun/ironic about Darmok being a reference to a story about coming to shared understanding from vastly different perspectives.

Kjetil, I believe the suggestion to omit data pod was originally made in https://github.com/solid/specification/issues/15#issuecomment-513466866 (if not earlier, links welcome). I believe this issue is resolved by a number PRs, e.g.,...

>I'm not sure what sending a notification to an inbox is intended to achieve The notification is intended for the attention of the receiver, e.g., 403 -> request access. The...

>the way this is worded makes it sound like an application developer can / should send all 4xx errors to the linked Inbox That's not the case. In the same...

>A more abstract proposal would use Structured Errors / Problem Details to convey any semantically described endpoint that could be usefull for the agent. That's fine too. As I've stated...

>We do have a predicate for inbox already, can't we just use that as a beginning of an approach to do this for #28? We sure can. If we want...

Thanks all. Withdrawing this proposal because apparently demonstrating a solution to meet some use cases (existing issues spanning several years and circumstances) in addition to sharing some implementation experience (with...

I've re-re-reviewed this PR and related considerations, and then rewrote it. All things considered, it is appropriate to include this as non-normative content. We can revisit the requirement levels for...

Noted re surfacing. To help with the spec progress, as always, commitment to implement or adequate implementation experience works. I gather that's been the case here and elsewhere for some...

Ack. I think the main thing would be to use open media formats/codecs that are also accessible/useful with supporting media, e.g., WebVTT ( https://www.w3.org/TR/webvtt1/ ) used in https://dokie.li/media/track/dokieli.vtt alongside the...