To publish an asset means making it visible to the target audience in a target repository. This requires coordination
of asset content and metadata.
Publishing an asset to another repository provides a cross community view of the asset. To do this requires federating
metadata and content across the repositories. In some cases this is achieved by physically replicating information
while in other cases links are used that users can navigate from one repository to the other. For any artifact that is
replicated between the repositories, it is important to establish which repository owns the "master copy" and which
holds a "cached copy" of the original for the purpose of providing a context-specific view on it.
Each repository serves a community. Different communities require different governance and authorization models. Often
in development context a rather coarse grained "workgroup" model is used to facilitate collaboration where any member
of a workgroup can pretty much perform any operation on an artifact once in the scope of the workgroup; on the other
hand, governance requirements for deployed services often imply a much more fine grained and restrictive model for who
can perform which tasks on specific artifacts. Rather than trying to unify these authorization models, you
can introduce "bridging" roles in each community that are authorized to make content from one environment
available in another environment.
As part of determining ownership and mastership of the asset and metadata, some key metadata must be addressed,
specifically regarding classification and access control. The classification schemas and access control must be
coordinated between repositories. The enterprise should be careful to not betray the access control rights of an asset
in another repository and thereby open up the asset to access it was intended to protect.
|