@reiver ⊼ (Charles) 

Linked Data in HTTP Headers rather than in JSON (i.e., JSON-LD), etc

⁂

Many Fediverse servers will give you different content depending on the "Accept" header in the HTTP request.

If "application/activity+json" you get ActivityPub/ActivityStreams JSON-LD metadata. If something else, you get actual file/payload.

If we encoded Linked Data as HTTP headers (key-value pairs), we could include the Linked Data with the actual file/payload.

#ActivityPub #ActivityStreams #FediDev #LinkedData #JSONLD

4:50pmWeb
Show threadJan Martin Keil6h ago
@reiver
I think this is a bad idea. HTTP headers are for request/response metadata, not for content metadata. Including Linked Data (which fits only in simple cases in key-value pairs) would violate the separation of concerns in the protocol stack. If you want to send both together, use <script type="application/ld+json">...</script> in the HTML header. With content negotiation the server sends exactly the payload wanted by the client. And the client can decide to send two requests.