i did a quick ctrl+f search and found 0 results for ld+json; so it looks like the "ld+json with the activitystreams profile" option is not given any consideration. this is to some extent understandable since content negotiation often works on the base media type without any parameters, and "profile negotiation" is something that still isn't ready yet. but it probably deserves a mention at least in some places throughout the document. whether this is inadvisable, or whether usage of an HTTP Link header with rel=profile ought to be mentioned as well, or whether some other outcome, it should probably be acknowledged as a potential issue.
i did a quick ctrl+f search and found 0 results for
ld+json;so it looks like the "ld+json with the activitystreams profile" option is not given any consideration. this is to some extent understandable since content negotiation often works on the base media type without any parameters, and "profile negotiation" is something that still isn't ready yet. but it probably deserves a mention at least in some places throughout the document. whether this is inadvisable, or whether usage of an HTTP Link header with rel=profile ought to be mentioned as well, or whether some other outcome, it should probably be acknowledged as a potential issue.