User story : share & reuse
An organization can have the "same" things (up to deployed endpoints) in different soas (collaborating with different people), or have its own SOA with only parts of it exposed (for other people to use it) without wanting to share the rest (in read or at least write).
Problem: how to share documents / propagate validation rules / notifications to all children documents? (e.g. a document attached to a Service must be made available to all Endpoints of the service)
Some services of an "internal" / organization soa are exposed in a multi-organization collaborative SOA. Example : at AXXX, DPS SI exposes DpsAccountService and Core SI exposes CoreContactService and consume each other's in the same collaboration SOA, but DPS SI has additional "internal-only" services such as DpsWorkflowService and DpsProjectService. DPS doesn't want to make those available (at least writable) to Core SI, but still see as much as possible of it together (at least impls, if possible services). DPS SI works with exposed services (mainly) in the collaboration SOA.
Same thing, but the organization exposing services doesn't want to have anything to do in collaborative SOA "importing" them. Example : a service "pure player" exposes only the "API" part of its services along with dedicated tests, so everybody can test it by "importing" exposed services & tests in their own SOA. The organization works with "API" services only within its own SOA.