Re: Should the specs be forked and maintained elsewhere?

On Fri, 24 Mar 2023 at 17:23, Benjamin Goering <ben@bengo.co> wrote:

> http content negotiation is normatively required by the activitypub spec
> (3.2).
> I'll also point out that some URIs from the TRs already support it.
>
> ```
>
>> bengo@bengo ~ ⚡  curl -H "Accept: application/json"
>> https://www.w3.org/ns/activitystreams | head -n 10
>>   % Total    % Received % Xferd  Average Speed   Time    Time     Time
>>  Current
>>                                  Dload  Upload   Total   Spent    Left
>>  Speed
>> 100  7985  100  7985    0     0  39142      0 --:--:-- --:--:-- --:--:--
>> 40125
>> {
>>   "@context": {
>>     "@vocab": "_:",
>>     "xsd": "http://www.w3.org/2001/XMLSchema#",
>>     "as": "https://www.w3.org/ns/activitystreams#",
>>     "ldp": "http://www.w3.org/ns/ldp#",
>>     "vcard": "http://www.w3.org/2006/vcard/ns#",
>>     "id": "@id",
>>     "type": "@type",
>>     "Accept": "as:Accept",
>>
>
Nice, did not think to try that :) I had not considerent JSON-LD, and was
expecting ;-

    Accept: text/turtle

Is there a standards clause for this ?

Maybe we can get it implemented across the board ?

Aaron