Download
1 / 8
80 likes | 197 Vues
System Directory for Document Sharing (SDDS). Vassil Peytchev, Epic February 1, 2010. Scope. Scope is around Document Sharing Cross-Community document sharing Cross-Enterprise document sharing Initial use cases provided the general Actor-Transaction Diagram. Updater. Service Directory.
E N D
System Directory for Document Sharing(SDDS) Vassil Peytchev, Epic February 1, 2010
Scope • Scope is around Document Sharing • Cross-Community document sharing • Cross-Enterprise document sharing • Initial use cases provided the general Actor-Transaction Diagram Updater Service Directory Requestor
Scope • Expand use cases to show how the different Document Sharing actors can be grouped with the Updater and Requester actors
Use Cases • XDS • Document Consumer – a new consumer joins an affinity domain. • As an updater, the consumer provides information about the entity it represents (ID, certificate, link to provider registry entry/entries) • As a requestor, needs to know the registry entity and the RSQ service information; list of repositories and their RDS service information; or, alternatively, the initiating gateway entity and its RSQ and RDS service information • Document Source – a new document source joins an affinity domain; a document source switches repositories • As an updater, the source provides information about the entity it represents (ID, certificate, link to provider registry entry/entries) • As a requestor, the source needs to know the repository entity/entities and their PnR service information
Use Cases XDS (continued) Document Registry – A new participant joins the affinity domain As an updater, the registry provides information about the entity it represents (ID (no ID), certificate); the services it supports (R, RSQ); the affinity domain configuration As a requestor, needs to know the repository and consumer entities; the responding gateway entity Document Repository – a new document repository joins an affinity domain; a new document source is added to the repository. As an updater, the repository provides information about the entity it represents (ID, certificate, (link to provider registry entry/entries) list of sources); the services it supports (PNR, RDS). As a requestor, the repository needs to know the registry entity/entities and their R service information.
Use Cases XDS with XCA Initiating gateway – A new participant (source, consumer, repository) joins the affinity domain As an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate) and the services it supports As a requestor, may need to know the document consumers, and the entities they represent Responding gateway – A new participant (source, consumer, repository) joins the affinity domain As an updater, the responding gateway provides information about the entity it represents (ID, certificate) As a requestor, the repository needs to know the registry entity, the repository and their services information.
Use Cases XCA (and XCPD) Initiating gateway – A new participant joins a group of networked communities As an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate, location) As a requestor, needs to know the responding gateways, the entities they represent, and the services they support Responding gateway – A new participant joins a group of networked communities As an updater, the responding gateway provides information about the entity it represents (ID, certificate); the services it supports. As a requestor, the repository needs to know the initiating gateway entities that may use its services.
Transactions ITI-Y1 Request ITI-Y2 Update ITI-Y3 Notifications (cost of notification)
