...
we've been envisioning in our discussions to date (at last with respect to Registry->consumer integration features):
To hit the high points (hopefully):
...
(c) A messaging mechanism (likely XMPP and/or using JMS and possibly some queuing system queuing system -- ActiveMQ, RabbitMQ, or even Amazon SNS) whereby events whereby events filtered and (possibly) transformed through the business logic layer can be posted to one or more message queues, where where consumers that prefer to retrieve event notifications via this mechanism can receive such notifications. Delivery of a specific a specific queuing mechanism is out of scope for the P&I effort, although providing standard interfaces for connecting to queuing mechanisms queuing mechanisms (JMS, XMPP) is in-scope. In some cases, there may be no intervening queuing system, per se, and messages may messages may be delivered directly to consumer interfaces (where that's supported by the consumer).
(8) Support for bulk provisioning (both for the inception of new consumers and for resolving state inconsistencies introduced by failed operations failed operations during incremental import processes and mishandled events) can be provided via simple flat-file extracts using the file the file extractor mechanism in orange, or via SCIM bulk provisioning (a full data extract can be processed through the routing and transformation and transformation business logic layer and delivered to a consumer as a SCIM bulk provisioning "bundle").