These are chat archives for csarven/ldn

25th
Oct 2016
Henry Story
@bblfish
Oct 25 2016 12:45

I don’t find this very clear

make an HTTP GET request on the target URL and, for RDF sources [RDF 1.1], the Inbox is the object of the predicate http://www.w3.org/ns/ldp#inbox.

Ah I see, you mean one is meant to look at the content of the resource to find a link in there.
Sarven Capadisli
@csarven
Oct 25 2016 12:49
Yes
Henry Story
@bblfish
Oct 25 2016 13:44
so this is saying: look at the header or the body for a link to the inbox.
( clearly if only looking for the header then a HEAD is all that is needed )
1) For the header it is quite clear what needs to be looked at.
2) For the body it is not so clear what needs to be looked for, unless the content is an RDF document, or has an interpretation as an RDF graph.
Amy Guy
@rhiaro
Oct 25 2016 13:45
We're assuming the content is RDF, yes
to advertise an inbox for a non-RDF document, the only way is to use the header
Henry Story
@bblfish
Oct 25 2016 13:49
yes, but the second bullet point is missing the word “content” or “representation”
Should I open an issue for that?
Amy Guy
@rhiaro
Oct 25 2016 13:50
I see what you mean. Go ahead, thanks!
Henry Story
@bblfish
Oct 25 2016 13:50
ok
Henry Story
@bblfish
Oct 25 2016 15:25
The link in the Note of 3.3.2 to Activity Streams 2.0 Collection does not work.
Amy Guy
@rhiaro
Oct 25 2016 15:33
Thanks @bblfish, should be fixed in current WD now
Melvin Carvalho
@melvincarvalho
Oct 25 2016 15:41
I was thinking about LDN today
could it be used to ASK for permission to view a resource?
you get back a 4xx which has an inbox ... you then send a message to that inbox asking for permission to view ... the inbox grants you permission and then sends you a notification?
Amy Guy
@rhiaro
Oct 25 2016 15:42
If you wrote a consumer that knew what such notifications meant, and could present a UI to allow the user to act on them, then sure
(or some automation, not UI necessarily)
Melvin Carvalho
@melvincarvalho
Oct 25 2016 15:42
yes exactly
i think this could be a common use case
Amy Guy
@rhiaro
Oct 25 2016 15:43
and an implementation can be all of a receiver, sender, and consumer, in what you describe
It would be good to see more of those I think
Melvin Carvalho
@melvincarvalho
Oct 25 2016 15:43
i think it would help to write out what the messages would look like, perhaps even make a spec for it