Microsofthi Alex,
I was the editor for SCIM RFC7643/7644.
SCIM 2 is fully extensible and can support new schema. The only obligation is that it be discoverable through the schema and resourcetypes endpoints. If you want to standardize schema, you could do that. It isn't clear to me if there is an interoperable need.
A lot of the life-cycle requirements you lay out are important for product implementations to consider, but they don't really affect the standard. For example a server is free to suspend or delete DCR registrations that are deemed temporary. It doesn't change how SCIM protocol works.
Regarding event notifications, there is a new SCIM Events spec going through final publication process now. See: https://datatracker.ietf.org/doc/draft-ietf-scim-events/
This proposed RFC defines event notifications that parallel the SCIM's CRUD operations, support HTTP asynchronous completion requests, and feed management events (add and remove subjects). This is complementary to the OIDF Shared Signals specs.
Cheers!
Phil Hunt
ps. I just saw Mark Wahl's agentic schema draft and will take a look!
