- From: a <a@trwnh.com>
- Date: Thu, 23 Mar 2023 10:53:53 -0500
- To: Melvin Carvalho <melvincarvalho@gmail.com>
- Cc: Evan Prodromou <evan@prodromou.name>, Bob Wyman <bob@wyman.us>, public-swicg@w3.org
Received on Thursday, 23 March 2023 15:54:18 UTC
AS3 and AP2 seem wholly unnecessary without concrete proposals on what such specs would include that isn't already covered by existing specs. However, I do agree that vocabulary acceptance is something that has been a historical challenge. Within the FEP process, we've had a proposal to use w3id.org/fep as a namespace for extension terms, and some years before that we had terms unofficially grafted onto the as: namespace -- Hashtag, manuallyApprovesFollowers, movedTo, sensitive. Therefore it would be helpful if: 1) there was a move to adopt some or all of these unofficial terms as officially part of the namespace 2) additional guidance or mechanisms were given to the community to extend AS2 via JSON-LD without having their own "vendor", or doing so in a "vendor-independent" way 2.5) such extensions were formally managed by an "activitystreams standards foundation" similar to the XSF. if this is not done, i suspect the FEP process will continue as-is regardless and effectively fill this role ad-hoc, but some formal recognition and participation might be nice assuming we avoid corporate capture of the process.
Received on Thursday, 23 March 2023 15:54:18 UTC