Possible Errata
Version 1 (Shiraz Memon, 11/06/2012 01:18 PM)
| 1 | 1 | Shiraz Memon | h1. Possible Errata |
|---|---|---|---|
| 2 | 1 | Shiraz Memon | |
| 3 | 1 | Shiraz Memon | This page intends to hold all possible errata to discuss of the GLUE 2.0 Specification v. 2.0, March 3, 2009. |
| 4 | 1 | Shiraz Memon | * Page 53: In ToComputingService, there is a relation StorageService, but in Storage service (page 44) there is not. Probably you want one with multiplicity 0..*. |
| 5 | 1 | Shiraz Memon | ** SOLUTION: No, it is not a mistake because StorageAccessProtocol already has a relation with ToComputingService. |
| 6 | 1 | Shiraz Memon | * Page 19: In Policy, there is a relation to UserDomain, but there may be no UserDomain to point to. |
| 7 | 1 | Shiraz Memon | ** Example: The bdii has no access control. By Stephen Burke: "also e.g. you could have authz by explicit DNs or by some other mechanism that doesn't relate directly to VOs. Even where there is a VO there is no guarantee that the ForeignKey will actually have anything to point to, and in EGEE it probably won't because we aren't likely to publish UserDomain objects, at least I don't think we plan it at the moment." |
| 8 | 1 | Shiraz Memon | ** In case this changes, we should also change Page 20 AccessPolicy and Page 21 MappingPolicy. |