FEP-7628: Move actor - how to reference from LOLA (W3C WG doc) #846

lisad commented 2026年05月22日 01:29:58 +02:00

Currently the LOLA spec references FEP-7628 for a description of how Move Actor is used and the MovedTo property. Since the LOLA spec (https://swicg.github.io/activitypub-data-portability/lola.html) is adopted by the the SocialWeb WG, normative references to FEPs need to be resolved somehow. @silverpill do you have opinions on how this should be done? happy to collaborate

Currently the LOLA spec references FEP-7628 for a description of how Move Actor is used and the MovedTo property. Since the LOLA spec (https://swicg.github.io/activitypub-data-portability/lola.html) is adopted by the the SocialWeb WG, normative references to FEPs need to be resolved somehow. @silverpill do you have opinions on how this should be done? happy to collaborate

silverpill commented 2026年05月22日 23:31:23 +02:00

Hello @lisad
I am not familiar with W3C processes. How a normative reference could be resolved?

Hello @lisad I am not familiar with W3C processes. How a normative reference could be resolved?

lisad commented 2026年05月23日 00:05:02 +02:00

First approach, and what I'm doing with the other references to FEPs, would be to make the reference informational. That's one way to resolve the reference stability, but I don't want to do that in case of the reference to FEP-7628 because LOLA relies on MovedTo so it can't be an informational reference unless it removes MovedTo and finds another solution. MovedTo is much better used consistently than defining a new thing to avoid the reference.

Another way is to promote the reference - to submit the FEP, basically, as short document that can become a W3C Technical Report at the same status as the LOLA doc. This is best done through the new SocialWeb WG, a short document that is a needed reference ought to be doable.

The last way is to move the needed parts right into LOLA. This is my recommendation and preference, and I'd be happy to discuss details of credit/authorship and clarify anything this might change about change control itself. (It doesn't stop any number of further FEPs, for example.). But before doing this, I wanted to check about any concerns. happy to have a real-time conversation about this (my contact information is in the spec)

First approach, and what I'm doing with the other references to FEPs, would be to make the reference informational. That's one way to resolve the reference stability, but I don't want to do that in case of the reference to FEP-7628 because LOLA relies on MovedTo so it can't be an informational reference unless it removes MovedTo and finds another solution. MovedTo is much better used consistently than defining a new thing to avoid the reference. Another way is to promote the reference - to submit the FEP, basically, as short document that can become a W3C [Technical Report](https://www.w3.org/TR/) at the same status as the LOLA doc. This is best done through the new SocialWeb WG, a short document that is a needed reference ought to be doable. The last way is to move the needed parts right into LOLA. This is my recommendation and preference, and I'd be happy to discuss details of credit/authorship and clarify anything this might change about change control itself. (It doesn't stop any number of further FEPs, for example.). But before doing this, I wanted to check about any concerns. happy to have a real-time conversation about this (my contact information is in the spec)

silverpill commented 2026年05月24日 13:37:49 +02:00

I am fine with any approach that doesn't require my active involvement. The document is in public domain, so you can use it freely.

It is not finalized, though. I opened an issue with a todo list for myself - silverpill/feps#22. If you have any suggestions regarding FEP-7628 content, let's continue discussion there. The issue tracker here at fediverse/fep is for administrative tasks related to FEP repository maintenance.

I am fine with any approach that doesn't require my active involvement. The document is in public domain, so you can use it freely. It is not finalized, though. I opened an issue with a todo list for myself - https://codeberg.org/silverpill/feps/issues/22. If you have any suggestions regarding FEP-7628 content, let's continue discussion there. The issue tracker here at `fediverse/fep` is for administrative tasks related to FEP repository maintenance.