Document Repository: Difference between revisions
No edit summary |
|||
| Line 29: | Line 29: | ||
==See Also== | ==See Also== | ||
This actor is often grouped with: [[Document Source]], [[Document Registry]], [[Information Source]], [[Secure Node]] and [[Time Client]] | |||
This actor is often grouped with: [[Secure Node]] | |||
This page is based on the [[Actor Template]] | This page is based on the [[Actor Template]] | ||
Revision as of 15:48, 28 November 2006
This is a template page. Click edit, Do Not Save This Page, Copy the current text then go edit your page and paste it in.
<Your page name should simply be Actor-Name Actor with spaces, with capitals, without the acronym. e.g. Order Placer Actor>
The Document Repository is responsible for both the persistent storage of these documents as well as for their registration with the appropriate Document Registry. It assigns a URI to documents for subsequent retrieval by a Document Consumer.
<Explain the flavor of the tasks and information the actor is responsible for. This section is profile neutral.>
Responsibilities in Profiles
The responsibilities placed on this actor in the context of each Profile is summarized here. For the actual specifications, refer to the Technical Framework.
A system that supports an Actor does not have to meet the requirements in any given Profile unless the system claims support of that Profile in the product Integration Statement.
<Profile 1>
This Profile depends on the actor to <explain in broad terms>.
<Profile 2>
This Profile depends on the actor to <explain in broad terms>.
See Also
This actor is often grouped with: Document Source, Document Registry, Information Source, Secure Node and Time Client
This page is based on the Actor Template