-
Key: RMS-48
-
Legacy Issue Number: 14971
-
Status: closed
-
Source: Hewlett-Packard ( Bill Manago)
-
Summary:
Are we missing a Repository Service? How do we handle the path were the record will be managed? (Bill Manago, 20091112)
-
Reported: RMS 1.0b1 — Thu, 14 Jan 2010 05:00 GMT
-
Disposition: Resolved — RMS 1.0b2
-
Disposition Summary:
We don't want to build in the idea of location and repository structure any more than is necessary. Specifying locations would defeat many of the goals of Cloud Computing, or even basic distributed data principles.
An implementation may gather information on a desired location (whether we recommend doing so or not) by passing it along as a value of an attribute defined in a AttributeProfile
Revised Text: None -
Updated: Fri, 6 Mar 2015 20:58 GMT
RMS — Are we missing a Repository Service?
- Key: RMS-48
- OMG Task Force: Records Management Services (RMS) FTF