This thread is mostly SHOULDs and pedantically-explicit explanations of how existing FEPs and existing AP/AS behaviors work together. Buried among the self-evident stuff are a few novel behaviors and ideas, but the main purpose was to make existing FEPs easier to test (see the attached specification for a Test Case, with sample implementation forthcoming).
This was informed by conversations with Lisa Dusseault who has been working on this much larger spec. Not sure what Lisa’s handle is on here.
For more context, see also the socialweb thread for FEP-7952 and the Actor-Relative URLs FEP.
NOTE: the title changed when I switched back to more easily/automatically backwards compatible Move activities for updates to movedTo and copiedTo (keeping the Announce for Tombstone retyping, as per ActivityStreams prior art). This also changed the FEP identifier to e965. Not sure how to change a title on here…