Context Navigation

ThreatAnalysis

-              v28
+              v29
 Are there any requirements related to version control?  Is it safe to assume that each project will keep track of it?
 Although it does not seem likely with the current ORBIT resources, it is possible that access to some resources, e.g., special instruments, might be limited to protect them from overuse or damage or just to keep the in calibration.http://lists.oasis-open.org/archives/xacml/200404/msg00036.html
+Although it does not seem likely with the current ORBIT resources, it is possible that access to some resources, e.g., special instruments, might be limited to protect them from overuse or damage or just to keep the in calibration.
 Are there any other threats that might require the use of RBAC with ORBIT?
 …
 It is assumed that access control will not need to interface with cost accounting.  It is assumed that any denial of access to overdrawn users will be enforced by user authentication.  If it is required to enforce project-level denial of access due to cost considerations it might be possible to enforce it when an already authorized user attempts to select that project or when he or she accesses an object with a cost associated with it.
-http://lists.oasis-open.org/archives/xacml/200404/msg00036.html
 It is probably a good idea to maintain Unicode compatibility (UTF-8 encoding) with user and project names for international use.