Re: New project for documenting miscellaneous terms

discoverable and suspended all use the unique joinmastodon namespace as
recommend by the extension document, since they were not approved by the
Social CG via a consensus process the way that the original 4 extensions
were. "indexable" does not appear to be a thing

On Sun, Apr 7, 2024, 7:14 PM Ryan Barrett <public@ryanb.org> wrote:

> Yes! I had the same idea. Mastodon has a long list, many could be good
> candidates, notably indexable, discoverable, suspended, as:sensitive,
> etc.
> https://docs.joinmastodon.org/spec/activitypub/#extensions-not-defined-by-activitystreams
>
> On Sun, Apr 7, 2024 at 5:13 PM Aaron Gray <aaronngray@gmail.com> wrote:
>
>> We have to deal and include mastodon’s extensions because they have now
>> became an unofficial de facto standard. I have seen them being used in
>> other implementations too.
>>
>> I will take some time this over the next two weeks to get up to speed on
>> this so I may be useful.
>>
>> Thanks Evan for all your hard work pulling everything together. I should
>> have thanked you before now.
>>
>> Regards,
>>
>> Aaron
>>
>> Aaron Gray - @AaronNGray@fosstodon.org
>>
>> Independent Open Source Software Engineer, Computer Language Researcher,
>> Information Theorist, and Computer Scientist.
>>
>>
>>
>> On Mon, 8 Apr 2024 at 01:06, Evan Prodromou <evan@prodromou.name> wrote:
>>
>>> The extensions policy currently in draft version explicitly says that
>>> new extensions should define a unique namespace.
>>>
>>> https://swicg.github.io/extensions-policy/
>>>
>>> Evan
>>>
>>> On Apr 7, 2024 19:47, nightpool <eg1290@gmail.com> wrote:
>>>
>>> (That's not the recommended way to do extensions any more,
>>> but it was popular in the early days of AP.)
>>>
>>> Is this true? All of the extensions I've seen that we use for Mastodon
>>> explicitly say {@id: "as:whatever"} in the context document. Which
>>> extensions are you referring to?
>>>
>>> On Sun, Apr 7, 2024, 6:37 PM Evan Prodromou <evan@prodromou.name> wrote:
>>>
>>> Hello! In our meeting on Friday, the CG decided to create a report
>>> documenting widely-used terms added to the Activity Streams 2.0
>>> namespace using the "@vocab" feature so far in the history of the
>>> protocol.
>>>
>>> (If you just drop a property into an AS2 document, because the AS2
>>> context document includes '@vocab: "_:"', those properties are in the
>>> AS2 namespace. That's not the recommended way to do extensions any more,
>>> but it was popular in the early days of AP.)
>>>
>>> The goal of this report is to document popular terms inserted into the
>>> AS2 namespace, and include them in a separate context document. Then, we
>>> can use the Extensions Policy to add the terms into the AS2 context.
>>>
>>> The secondary goal is to test the SocialCG's extension policy, currently
>>> in draft status:
>>>
>>> https://swicg.github.io/extensions-policy/
>>>
>>> This project would push the bounds of that extension policy in at least
>>> one way; it doesn't use a well-defined namespace -- by definition! But
>>> otherwise it should be a good test of the policy.
>>>
>>> If you have ideas for existing undocumented AS2 terms seen in the wild
>>> that should be included, please make a note here:
>>>
>>> https://github.com/swicg/miscellany/issues
>>>
>>> The current context doc is here:
>>>
>>> https://purl.archive.org/socialweb/miscellany
>>>
>>> And the document will be here when it's written (currently boilerplate
>>> ReSpec):
>>>
>>> https://swicg.github.io/miscellany/
>>>
>>> Lastly, I had one person step forward to help out with this; if you
>>> think you'd be a good co-editor on this document, let me know.
>>>
>>> Evan
>>>
>>>
>>>
>>>
>
> --
> https://snarfed.org/
>