Sending notifications

[Dexagod]

Sending notifications

Validation

Validation is required for sending notifications. If this were not the case, the receiver would possibly be unable to read / process the received notification, without the sender knowing about this problem.
Validation is currently handled by the parsing libraries in the rdf-parse library.

Format conversion

Format conversions are required to be able to convert the data from any input format to any outpu format.
This may be useful for cases where one receiver prefers a certain format, while another prefers an other format.
This way, the same notification can be converted to both output formats before being posted.

Format conversions are done using rdf-parse to parse the notifications, and serialized using rdf-serialize.

Inbox discovery

Inbox discovery is handled accoring to the spec.

Notification Posting

The notification is posted to all receivers (target, cc and bcc).

Concrete questions

• Should shape validation be a thing for sending notifications? (Client is only able to send notifications that match a given shape?)
• How to do error handling in case one of many inboxes cannot be found?
• Inbox discovery in the case of multiple inboxes
  • This is a more general question as to how multiple inboxes for multiple applications / use cases / ... can be handled in LDP.