Re: Linked Data Notifications: Call for feedback and implementations

Hi,

Some comments about Linked Data Notifications  : 
https://linkedresearch.org/ldn/

Best regards,

Olivier Corby




1.1 Social Web Working Group

complimentary protocols
->
complementary ?



3.1 Discovery


Senders and consumers should omit the Link header discovery when 
specifically targeting URIs with fragment identifiers.
->
The text switch from URL to URI ?


If the target contains a fragment identifier,
->
If the target URL contains



3.2 Sending

There is no mention of ldn in the JSON-LD content in "Example 
notification send request to an Inbox." ?


3.3.2 Making Inbox contents available to consumers

The JSON-LD content type must be available for all resources
->
RDF resources ?


3.4 Consuming

"Fetching the individual notifications" is not defined :
is it done by dereferencing the URI of the notification ?



Consumers may also want to check the notifications against any 
constraints as announced by an Inbox before further processing or use.
->
Not clear, give an example ?


NOTE
Note that the fetched URI may not necessarily be same as the resolved 
value of @id ...
->
Which URI are you talking about here ?


NOTE
Given the nature of the notification payload, consumers may want to take 
precautions when ascertaining the veracity of the contents. The 
"open-world assumption" applies here.
->
Give a reference for "open-world assumption"



4.1 Payload Examples

A single triple statement is the simplest notification in terms of its 
data payload. It contains the most essential data which makes up a 
notification e.g, A note is a reply to an article:
->
e.g., a note



"Larger collections of triples or qualified relations"
->
Give a reference for "qualified relation" or define it



--

General comments:

Notification URI can be seen as the URI of a named graph that is the 
notification payload.

can owl:imports statement be used and interpreted as an import in a 
notification payload ?

can named graphs be used in notification payload ?

how long time  notifications stored on a server remain available ?

there is no filter mechanism to fetch notifications ? filter on 
timestamp, on type of resources, on subscription criteria, etc.