Content-Type requirement and Content Negotiation #86
Description
Section 6 requires the content type of the callback request to be the same as the topic's content type. For resources that support content negotiation, this is impossible as the same topic URL has multiple, equally valid content types.
If the specification requires a single type, then the content-location URL would be required as the Topic URL, requiring the publisher to provide many notifications for each change.